Privacy Policy

Information we collect

• Account information: your name, email address, password hash, email-verification state, and subscription status.
• Project information: business or project names, website URLs, logos, colours, and widget settings supplied by account holders.
• Testimonial information: a submitter’s name, testimonial, rating, consent choice, and—when provided—company, job title, email address, and photo. Photo submission is available only where the requesting account’s plan permits it.
• Service and security information: IP address, request metadata, error and security logs, and session data needed to operate, protect, and diagnose the service.
• Acquisition information: when an account is registered, we may retain the first landing path, referring website hostname, and bounded campaign labels supplied in UTM parameters. We do not retain the full referring URL or its query string for this purpose.
• Promotional attribution information: when GetTraffic365 attribution is enabled, a promotional link may supply a random, opaque visit identifier. If you register, we may associate that identifier and its capture time with your account for a limited period.
• Support information: information included when you contact us.

We ask only for information needed to provide and protect the current service. Testimonial email addresses are available to the requesting business for review but are not displayed on public Walls of Love or widgets.

GetTraffic365 promotional attribution

When a promotional link brings a gt365_visit identifier in the page URL, TestiFollow asks whether you allow measurement before using it. A valid identifier is held for up to 15 minutes in the encrypted server-side session while you choose and is removed from the visible URL. If you accept, TestiFollow retains the first valid identifier in that session; if you decline, it discards it. The ordinary TestiFollow session cookie identifies the session, but no separate GetTraffic365 tracking cookie is set. If you register after accepting, the identifier and capture time may move to your account record. Although the identifier is random and opaque, it can then be associated with your account.

Only after you accept and the integration is enabled may TestiFollow send limited, signed server-to-server events to GetTraffic365 to measure registration, project creation, a Pro subscription start, or a Pro subscription renewal. Registration and Pro billing events can also be sent without a matching visit identifier and are then unattributed; a project-created event requires a valid identifier. A rejection prevents these events for your account. Each event contains a random event ID, event type and time, and an identifier if it is still eligible. Pro billing events also contain the amount actually paid in minor currency units, the currency, and a controlled non-sensitive plan code. Renewals after the attribution window may be sent without the earlier identifier.

This integration does not send your name, email address, password, testimonial or customer content, payment-card details, billing address, full Stripe payload, unnecessary Stripe or customer identifiers, or your full IP address. It does not use browser fingerprinting.

The identifier is eligible for attribution for 30 days after capture. The temporary session copy is removed on registration or expires with the session, normally after two hours of inactivity. A daily cleanup clears expired identifiers from account records and from delivered or failed outbox records. A pending delivery may retain its identifier until its retry state is resolved; event records may remain for delivery and audit after an identifier is removed. Protected backups expire on their normal retention cycle.

You can change your promotional measurement choice at any time on the Cookie Notice page. Declining or revoking acceptance stops future GetTraffic365 event creation for your account and clears current attribution, without affecting TestiFollow's core functions or deleting completed audit records. A later acceptance applies only to future valid promotional visits; it does not reconstruct past attribution.

How information is used

We use information to provide accounts and projects, receive and moderate testimonials, publish approved content, operate billing, understand which acquisition sources lead to registrations and product milestones, send verification and password-reset messages, respond to support requests, prevent abuse, and maintain service reliability and security.

Acquisition measurement does not use browser fingerprinting. First-touch campaign information is held temporarily in the session before registration and is attached to an account only if the visitor later registers, as described above.

Account holders decide which submitted testimonials they approve and publish. A testimonial submitter’s information is shared with the business that requested the testimonial, as explained on the collection form.

Service providers

Stripe processes subscription checkout, payment details, invoices, and the customer billing portal. TestiFollow stores Stripe customer and subscription references and billing status, but does not receive or store full payment card details.

Microsoft 365 is used to deliver transactional messages from support@testifollow.com, including email verification and password-reset messages. Hosting, database, Redis, storage, logging, and backup providers may process information solely as needed to operate the service.

Lawful basis and choices

Depending on the context, information is processed to perform the service contract, pursue legitimate interests in operating and securing the service, comply with legal obligations, or act on consent. Testimonial publication relies on the submitter’s required publication permission and the account holder’s approval.

You may request access, correction, deletion, restriction, or a portable copy of personal information where applicable, and may object to certain processing or withdraw consent for future publication. Contact us using the address above. We may need to verify your identity and may retain information where legally required or necessary to establish or defend claims.

Retention and security

We retain account and project data while an account is active and for a reasonable period afterwards for support, security, backup, dispute, and legal purposes. Testimonial content remains until the relevant account holder deletes it, the account is closed, or a valid deletion request is completed. Backups expire on their normal protected retention cycle.

We use access controls, encrypted HTTPS transport, password hashing, signed billing webhooks, restricted uploads, and other proportionate safeguards. No internet service can promise absolute security; please report suspected issues promptly.

International processing and updates

Some service providers may process information outside the United Kingdom. Where required, appropriate contractual or legal safeguards will be used. We may update this policy as the service or legal requirements change and will publish the revised date on this page.