PRIVACY / SERVICE DATA
Privacy, in plain language.
Trends Fast is operated by Top of the World Reizen, handelend onder de naam Trends Fast. This page describes how the service handles your data. For privacy, access or deletion requests, contact meestierolff@gmail.com.
What we need
We store your submitted product URL, proposed website profile, confirmed product context, permitted research excerpts, Daily Trend Briefs, generated drafts, saved edits and feedback. We also keep the usage, trial, subscription and security records needed to operate your account and enforce its limits. If you explicitly join the historical product-interest form, 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. Trends Fast stores the corresponding authentication ID, normalized email address, and—when supplied by the identity provider—a bounded display name and HTTPS avatar URL. When you choose Google, we request only your identity, email address and basic profile to sign you in and associate you with your account. Supabase manages the authentication session, which may temporarily include a Google provider token. We do not use that token to read Gmail, Drive, calendars or Search Console, or store it as a connected data-source credential. You can revoke Google access in your Google Account settings; account deletion is available through the verified support process described below.
Private by default
Project profiles, briefs and drafts require access to the owning account or a scoped project key. Historical 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.
Analytics and cookies
Vercel Web Analytics counts visits to public pages without cookies, from cleaned page addresses only.
Google Analytics runs only if you allow it. On public pages a banner asks first, and nothing is sent to Google until you accept. If you accept, Google Analytics 4 sets the cookies _ga and _ga_KDWJQJJ6KG, which last up to two years after your last visit, and receives the public page you open with only its campaign parameters, the page title, the referring site, your browser and device type, and an approximate location that Google derives from your IP address. We keep its advertising features, ad personalisation and Google signals off, and it never runs on the dashboard, sign-in, scan, billing or shared-result pages. If you accepted, our server also tells Google Analytics about three moments in your account: that you created it, that you created an API key and whether it was your first, and that you started a checkout, with the plan and its price. Each report carries the identifiers in those cookies and nothing else about you or your account: no dashboard address, no account or project ID and no email address.
Google processes this data for us under its data processing terms for Google Analytics; data that reaches Google in the United States is covered by Google's certification under the EU–US Data Privacy Framework. Google keeps the event-level data for at most 14 months; aggregated counts, such as page views per day, remain. Change your choice here at any time. Turning it off also deletes the Google Analytics cookies from this site.
If you accept analytics, your browser also remembers where your first visit came from: the address of the referring page without its query, the page you landed on, its campaign parameters (utm_source, utm_medium and utm_campaign) and the time. It stays in your browser's storage and reaches us only when you set up your account, together with your optional answer to “How did you hear about TrendsFast?”. We keep the two with your account to learn which channels bring people, and delete them with your account. Without your consent the browser remembers nothing, and the answer alone is kept if you give one.
Reading your choice in this browser…
Public MCP planning tools
When you use the public planning connection in an MCP client such as ChatGPT, that client sends your selected tool arguments to TrendsFast. These include observation counts and times, available time, content preferences, or Reddit account counts and optional public rule text. The calculator processes them for that request and returns the result to the client; it does not save the inputs or results to an account or database, send them to AI or research providers, or log request bodies. Do not include usernames, credentials or sensitive personal information. Your client may retain the conversation and tool results under its own settings and privacy policy.
Vercel processes the network request and may retain operational metadata such as the requesting client IP, route, timestamp and response status under the hosting service's configured log retention. This supports delivery and troubleshooting. Contact support for information or a deletion request relating to identifiable service records. You can stop sending tool requests by disconnecting the plugin in your client.
Trend API, MCP server, CLI and agents
When you or your agent call TrendsFast through the REST API, the MCP server, the CLI, an SDK or a connector in an assistant such as Claude or ChatGPT, we receive the request: the product or question, your brand's confirmed context or a niche you describe, any filters, a request ID and a spending limit. For billing and security we keep a usage record of each call: who made it, its request ID, a hash of the request, the operation, the credits charged and the time, but not the request in full. The saved result stays in your workspace until it expires, at most 30 days after the call and sooner if a source's permission for its evidence ends. Your assistant may keep the conversation and the results under its own settings and privacy policy.
Results hold public posts from public sources: a link, the title or an excerpt where the source permits it, the public name or handle of the account that posted it, its public counts and the labels TrendsFast computes. We collect these into a shared index that every customer's results read from, and keep each post only as long as its source's permission allows. Daily statistics derived from the index stay longer, without the identifiers of individual posts once that time has passed. We do not read private accounts or private messages. For a question about a public post of yours in the index, or to ask us to remove it, use the address above.
To collect and read this evidence we use ScrapeCreators for public social posts and video transcripts, the YouTube Data API, Algolia's Hacker News search, the GitHub API, and DataForSEO for Google Trends and for what ChatGPT, Claude, Gemini and Perplexity answer, searching the web, to the question a buyer in your brand's category would ask. That question is built from the category and audience you confirmed and never names your brand, its website or a competitor. Anthropic's Claude drafts your brand's context from your website's public text, labels the opening lines of videos, and reads community rules and the form of top posts. Research providers receive the search terms and public handles a call needs, which can come from your brand's context, and never your account details.
Shared result links
If you share a saved result, we publish a copy at a link shown to you once, and anyone who has the link can read it without signing in, including anyone it is passed on to. The copy holds public posts' links, titles where their source permits public excerpts, creators, public counts and TrendsFast's labels, with a headline and caveats we write. It never holds your brand's context, relevance scores, hooks, AI answers, playbooks, IDs or credit cost. We store the copy and a hash of the link, not the link itself.
A link stops working when you end it, after at most 30 days, when its result expires or is redacted, or when the brand is removed, and every view drops a post that may no longer be shown publicly. Ended links are then deleted. Shared pages are not cached and ask search engines not to index them.
Free trend analysis
The free analysis needs no account. If you paste in a website, we read its public homepage once and match it against public posts already in our index; nothing is sent to an AI or research provider. We keep the website address, what we read from the homepage and the result for 24 hours. To apply the daily limits we set a cookie, tf_fa_visitor, for up to seven days, and keep keyed hashes of it and of your network address rather than the address itself. If you create an account and claim the analysis, it becomes part of your workspace.
Retention and deletion
Marketing results have a 30-day retention deadline; access to a trial or subscription does not promise permanent storage. Source restrictions can require earlier removal. The current scan and analytics policy uses a 90-day retention target. Historical launch-interest consent expires after 180 days unless renewed.
You can export your retained marketing data from the dashboard. Forget marketing memory removes the saved marketing context and dependent drafts; it does not delete your account or the underlying product record. Minimal usage, billing and security records remain where needed, including records of unresolved requests. Full account or project deletion requires a verified support request and may be subject to lawful retention requirements.
YouTube API Services
Trends Fast uses YouTube API Services to collect public video trend data. By using the parts of Trends Fast that return YouTube data you agree to be bound by the YouTube Terms of Service. Google's handling of data it receives is described in the Google Privacy Policy.
What is requested. Trends Fast calls the YouTube Data API v3 videos.list endpoint for the public mostPopular chart of a region, requesting only the snippet and statistics parts. From each returned video it records the video identifier, the title, the publication date, the public view count, the region the chart was requested for and, when one was requested, the video category. It does not read comments, captions, subscriber counts, private or unlisted videos, or any data belonging to a viewer's account.
How requests are authenticated. Requests use a server-side Google API key. Trends Fast does not request, hold or use any YouTube OAuth authorization. Signing in with Google uses Google's identity scopes only — your name, email address and account identifier — and gives Trends Fast no access to your YouTube account, channel, uploads or watch history. The API key is never sent to your browser and is redacted from logs and stored receipts.
Why it is collected. Repeated public chart readings are what let the service report whether attention on a topic is rising or falling, rather than only what is popular right now. Collection is scheduled at most once per day.
Retention, refresh and removal. Every stored observation carries an expiry taken from the recorded source permission for that collection, and an observation is filtered out when the index is read once that expiry has passed. A collection is refused outright if the recorded permission has already lapsed. Removal before expiry is handled through a verified support request: there is currently no scheduled job that physically deletes expired rows, and this page does not claim one.
Third parties. YouTube-derived observations are stored in the same hosted infrastructure described under Providers below. They are not sold, and they are not sent to advertising networks. Where a request returns results to a customer through the API or MCP server, the stored permissions for that source determine what may be returned.
Derived metrics and storage. Google has approved Trends Fast's use of YouTube API data for derived metrics, such as how attention on a topic changes over time. Stored YouTube observations still expire within the 30 days the YouTube API Services terms permit by default; any longer retention would require a further approval from Google, and this page does not claim one.
Contact. To ask what YouTube-derived data is held, or to request its removal, email meestierolff@gmail.com. You can also remove data Google holds about you through Google's security settings.
Providers
Necessary product context, permitted source excerpts and rules, writing assignments, drafts and review findings are sent to the configured AI and research providers to produce your profile and marketing. Do not submit secrets, payment details or sensitive personal information as marketing context. Provider credentials stay on the server. Research access does not grant permission to republish source material or post in a community.
Vercel hosts the application, Supabase handles authentication and storage, and our configured email provider delivers sign-in links. Stripe handles Checkout and billing; Trends Fast stores the customer, subscription and payment-status references needed for access, not your full card details. Purchases are sold through Link, Stripe's merchant of record service, which processes your payment details, billing address and tax location for the sale under its own privacy policy.
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; Trends Fast 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. Contact us if you need information about a provider's handling of data associated with your account.