Privacy, in plain language.

This is an operational summary, not a substitute for founder and legal review before public launch.

What we need

We store the submitted product URL, inferred public product context, bounded source receipts, scan lifecycle and cost metadata, feedback you choose to submit, and the minimum security audit events needed to operate the service. If you explicitly join the paid launch list, we also store the normalized email address and consent record needed to contact you about that launch.

If you sign in, Supabase Auth processes your authentication identifier, email address, session and sign-in metadata. TrendsFast stores the corresponding authentication ID, normalized email address, and—when supplied by the identity provider—a bounded display name and HTTPS avatar URL. If Google sign-in is enabled and you choose it, Google and Supabase also process the minimum identity profile used for that sign-in; TrendsFast does not retain Google access or refresh tokens.

Private by default

Scan links use unguessable tokens and are not made public without explicit consent. We do not send private scan URLs, API keys, emails, free text, prompts, or evidence text to optional external analytics. First-party browser analytics use an HMAC-derived, short-lived session identity and fixed event dimensions rather than raw private URLs or submitted content.

Retention and deletion

The current configuration defaults to a 90-day scan and analytics retention target. Paid-launch interest expires after 180 days unless you consent again. The application includes an authenticated, dedicated-role retention job and an ops-only daily schedule template, but no hosted execution or self-service deletion endpoint is verified yet. A reviewed operator can invoke the exact-project, launch-interest, or expiry-purge procedure; completion and lawful retention exceptions must be verified manually. Public launch remains gated on owned, monitored privacy intake and scheduler workflows.

Providers

Public website content and public source metadata may be sent to configured model/data providers to produce a scan. Managed keys stay server-side. Provider-specific terms and rights remain disclosed in the source-rights matrix.

When abuse protection is enabled, the scan form loads Cloudflare Turnstile. Cloudflare receives browser and network information, including the requesting IP address, to issue and verify the challenge; TrendsFast sends the one-time challenge token—but deliberately omits the optional IP field—for server-side verification. Supabase and Cloudflare may process data in other countries under their own applicable terms and transfer safeguards. The founder and qualified privacy counsel must approve the final processor list, lawful bases, transfers, retention periods, and contact details before public launch.