TemplateTrends Back to the app →

Privacy Policy

Last updated: 16 October 2026

TemplateTrends ("TemplateTrends", "we", "us") operates the TemplateTrends Android app and the website at templatetrends.cloud, which help people find trending CapCut templates. This policy explains exactly what we collect, why we collect it, who we share it with, and how you can get it removed.

We have tried to write this in plain language rather than boilerplate. If anything here is unclear, email us at support@templatetrends.cloud and we will answer.

TemplateTrends is an independent service. We are not affiliated with, endorsed by, or operated by CapCut or ByteDance.

1. The short version

  • You can use TemplateTrends without creating an account. Guests get an anonymous session that holds nothing but a daily search counter.
  • We do not sell your personal information, and we do not share it for cross-context behavioural advertising.
  • We do not collect your precise location, contacts, photos, camera, microphone, call logs, SMS, or installed-app list.
  • We show ads. On Android those come from Google AdMob; on the web from Google AdSense. Both may use advertising identifiers and cookies — section 6 explains how to turn personalised ads off.
  • Deleting your account from inside the app removes your data; the final purge runs 30 days later.

2. Information you give us

Nothing, if you stay a guest. Signing in is optional.

If you choose to sign in with Google, we receive and store:

  • your email address
  • your name and profile picture, if your Google account exposes them

If you edit your profile we also store the display name, language and theme you choose, and whether you opted in to marketing email. Marketing email is off unless you turn it on, and every message has an unsubscribe link.

If you contact support, we keep that correspondence so we can answer it.

3. Information created when you use the service

Searches. The words you search for are stored, in normalised form, together with how many results they returned. Search text is also sent to our search providers (section 7) to fetch fresh results. Searches are stored as queries, not as a personal history: we keep "how many people searched this phrase", not "here is everything this person looked for". Please do not type personal or sensitive information into the search box.

Activity events. When you open, favourite or share a template we record the event, the template, your platform (Android or web), the app version and your language. These events are attached to a device hash — an irreversible salted hash of a device identifier, not the identifier itself — or to your user id if you are signed in. We use this to work out which templates are actually trending and to stop the same person inflating a count.

Usage counters. A per-day count of searches made and rewarded ads watched, so free limits and bonuses work. These counters reset daily.

Subscription state. If you subscribe, we store which entitlement is active and when it expires, plus the events our payment processor sends us.

Push tokens. If you allow notifications we store the push token for that install, with its platform, app version and language, so we can send the notification and stop sending it once the install goes away.

Technical logs. Our hosting and database providers keep short-lived operational logs, including IP addresses, for security, abuse prevention and debugging. We do not build profiles from them.

4. Why we are allowed to use it

Where the GDPR or UK GDPR applies, our legal bases are:

  • Contract — running your account, applying free limits, delivering a subscription you paid for.
  • Legitimate interests — keeping the trending index accurate, preventing abuse and fraud, keeping the service secure, and understanding in aggregate which features are used.
  • Consent — personalised advertising, push notifications and marketing email. You can withdraw any of these at any time without losing access to the rest of the service.
  • Legal obligation — tax, accounting, and responding to lawful requests.

5. What we do not do

  • We do not sell personal information, and we have not in the preceding twelve months.
  • We do not share personal information for cross-context behavioural advertising as defined by the CPRA.
  • We do not use your data to train machine-learning models about you.
  • We do not read, upload or scan files on your device. Videos you preview are streamed from their source; videos you share are produced on our servers from the public template, not from anything on your phone.

6. Advertising

Ads pay for the free tier. Pro subscribers see no ads at all.

In the Android app ads are served by Google AdMob. AdMob may use your device's advertising ID to limit how often you see the same ad and, where permitted, to personalise ads.

  • Android: Settings → Google → Ads lets you delete or reset your advertising ID and opt out of personalisation.
  • In the European Economic Area, the UK and Switzerland we show Google's consent form on first launch. Choosing "do not consent" switches the app to non-personalised ads. You can reopen that choice from the app's settings.

On the web ads are served by Google AdSense, which sets cookies and similar identifiers.

We never pass your email address, name or account id to an ad network.

7. Who we share data with

We use a small number of processors. Each gets only what it needs to do its job.

  • Supabase — database, authentication and server functions. Holds your account, searches, events and subscription state.
  • Vercel — serves the website.
  • Google Play billing and RevenueCat — subscription purchases and receipt validation. They receive a pseudonymous app user id and your purchase. We never see or store your card details.
  • Google AdMob and Google AdSense — advertising, as described above.
  • Firebase Cloud Messaging — delivers push notifications to your device.
  • ValueSERP and SerpApi — fetch public search results for the phrases you search. They receive the search text and a country or language hint, not your identity.
  • Cloudinary — optional media processing when a shareable video is generated.
  • Google Workspace (Gmail) — sends transactional and, if you opted in, marketing email.

We also disclose information when the law requires it, to enforce our Terms, or to protect the rights and safety of our users — and, if TemplateTrends is ever sold or merged, to the acquirer under the same commitments made here.

Opening a template hands you off to CapCut. What CapCut does then is covered by CapCut's own privacy policy, not this one.

8. Cookies and local storage

The website stores a small amount of data in your browser:

  • your signed-in or guest session, so you are not logged out on every visit
  • your language, theme and remaining free searches
  • cookies set by Google AdSense, as described in section 6

The Android app uses local app storage for the same purposes and sets no cookies. You can clear everything from your browser settings, or by clearing the app's storage.

9. How long we keep it

  • Activity events — 90 days, then deleted automatically.
  • Operational health checks — 14 days.
  • Usage counters — reset every day; historical rows are not retained.
  • Account data — for as long as the account exists. After you request deletion the account is locked immediately and permanently purged 30 days later.
  • Search queries — kept in aggregate, with no link to who searched them.
  • Billing records — as long as tax and accounting law requires.

10. Your rights

Whoever and wherever you are, you can:

  • See and get a copy of the data tied to your account.
  • Correct anything inaccurate.
  • Delete your account and its data — Profile → Delete account in the app, or by email.
  • Withdraw consent for notifications, marketing email or personalised ads, separately and at any time.
  • Object to or restrict processing based on legitimate interests.
  • Complain to your data protection authority. In the EEA that is your national DPA; in the UK, the ICO.

Under the CPRA, California residents additionally have the right to know, to delete, to correct, and to opt out of sale or sharing — and because we do neither, there is nothing to opt out of. We will not discriminate against you for exercising any of these rights.

Email support@templatetrends.cloud and we will respond within 30 days. We may need to confirm you control the account before acting on a request.

11. International transfers

Our processors operate globally, so your data may be processed in countries other than your own. Where data leaves the European Economic Area or the UK we rely on the European Commission's Standard Contractual Clauses, or on an adequacy decision where one covers the destination.

12. Children

TemplateTrends is not directed at children. You must be at least 13 years old to use it — and at least 16 in countries where 16 is the minimum age for consenting to this kind of processing. We do not knowingly collect data from children below that age. If you believe a child has given us data, email support@templatetrends.cloud and we will delete it.

13. Security

Access to the database is restricted by row-level security, so one account cannot read another's data. Administrative access is limited to named accounts and is logged. Traffic is encrypted in transit, and credentials and API keys are held in managed secret storage rather than in the app. No system is perfectly secure; if a breach ever affects you, we will tell you and the relevant authority as quickly as the law requires.

14. Changes to this policy

If we change this policy we will update the date at the top, and for anything material we will tell you in the app before it takes effect. Continuing to use TemplateTrends after that means you accept the updated policy.

15. Contact

TemplateTrends — privacy enquiries: support@templatetrends.cloud

For anything that needs a postal address, ask by email and we will provide the registered address of the operating entity.