Privacy policy

Who we are

ClippingAlpha is operated by Momentist, Inc., 169 Madison Ave STE 38364, New York, NY 10016, USA, the controller of your personal data.

The short version

• We do not sell personal data for money. California law may count our ad events to Meta and Google as sharing, and you can turn them off.
• The site loads no Meta, Google or other third-party tracking script. Our server sends ad measurement events to Meta and Google itself, and only with your consent where your region asks for it.
• With ad measurement on, our server sends Meta your IP address with each ad measurement event. We keep it for 7 days at most, then delete it. Nothing else we store holds your IP address. Microsoft Azure's edge logs record it, and we keep those logs for 30 days.
• We never keep the access tokens of TikTok, X, Google or Discord sign-in. The tokens we keep are Instagram's and the one from Connect TikTok (audience), encrypted, and only while that account is connected for an audience check.
• You can export or delete everything tied to your account from Profile. See how to delete your data.

What we collect

Visits

The page you open (its path, never the query), the site that sent you (its host only), campaign tags in the link (utm and ad ids), browser and system family, and the country and network looked up from your IP address. The IP address is used in memory for that lookup and for bot and abuse checks, then dropped. With ad measurement on, a copy is kept for your ad measurement events until Meta has them, 7 days at most.

Events

Taps and views on the site, such as a card view, Join, Save, Share, a filter change or grid or table view. Never the text you type.

Account

Your display name, your email address when you enter one or your sign-in provider gives one, the provider's id for you, which provider you used and when. Sign-in drops profile pictures. An Instagram account connected for an audience check keeps a copy, see Audience check. There are no passwords. Each session keeps your browser's user agent, never your IP address. With ad measurement on, an account that signed up but has not confirmed an alert channel yet keeps the IP address and user agent of its signup for the signup event Meta gets, 7 days at most.

Age

For an account made before 1 October 2026, that you confirmed you were 18 or older, and when. Signup no longer asks.

Alert channels

Your email address, your Telegram chat id, or your browser's push subscription, for each channel you turn on.

Preferences

Time zone, country (looked up from your IP address when you sign up by email, or set by you), profile answers (views, platforms, niches, languages, audience countries and payout method type, never an account number), saved campaigns, alert rules, the daily cap and quiet hours.

Alert history

Which campaign we alerted you about, on which channel, when it was sent and whether you tapped it, with the message id from Resend or Telegram. When an account you connected fits the campaign, the alert names it and its audience share, such as Fits @you: 62% US, and the history keeps that line until you remove the account. Alert emails carry no tracking pixel.

Connected apps

When you connect an AI agent to our MCP server: the app's own name, what it may do, when you connected it and when it was last used. Its codes and tokens are stored only as hashes. The agent can read and change your saved campaigns and alert rules and see which kinds of channel get alerts, never your email address or chat id.

Audience check

Only if you connect an account to verify its audience, or sign in with Instagram while the Instagram check is open, up to 10 per platform. For each account: its handle (the Instagram username, the YouTube @handle or channel title, the TikTok display name), follower count, and shares only, never the raw report. YouTube and the TikTok viewer proof: views, the share of views from the US, UK, Canada and Australia, and the top 5 countries. Connect TikTok (audience): the account type (business or personal), and from 100 followers, for its followers the top 5 countries, the share from the US, UK, Canada and Australia, the age groups and the gender split, as percentages. Instagram: the account type (business or creator), the display name, a copy of the profile picture (kept on our servers and shown only to you, never the link Instagram gives), the number of posts, followers and accounts it follows, the account insights of the last 28 days (reach, views, accounts engaged, interactions, likes, comments, shares and saves), and for its followers and its engaged audience the top 5 countries, the top 3 cities, the age groups and the gender split, as percentages. One TikTok account connected more than one way is one row with the latest numbers. For the audience tier we also keep the share of every country the platform lists and, for YouTube, the average country mix of the last 3 videos, with the tier they give (US verified, Tier 1, Tier 2 or Tier 3). See how audience tiers work at clippingalpha.com/audience-tiers. We keep a keyed hash of each platform account id, never the id itself.

Consent records

Each consent you give: which one, a hash of the exact words you saw, the form version, the channel, the page and the time.

Cookies and storage

Every cookie is first-party, set by our own server. None is readable by page scripts.

ca_consent

Your cookie banner choice and a random id, for 400 days. Set when you choose.

ca_vid

A random visitor id that links your visits, for 400 days. Only with visit counting on.

ca_vis

The current visit. It ends after 30 minutes without activity.

_fbp and _fbc

Meta ad measurement ids, made by our server, for 90 days. Only with ad measurement on. _fbc is set only when you arrive from a Meta ad.

ca_gclk

The Google ad click id from the link you arrived by, for 90 days. Only with ad measurement on.

Session

ca.session_token keeps you signed in for 60 days, renewed each day you use the site.

Sign-in steps

ca_signup_intent carries your choices through a sign-in, for 30 minutes. ca_verify and ca_link_intent carry an audience check or a Connect, for 10 minutes.

Local storage

Your browser keeps the theme, grid or table view and the platform you post on. On the first visit it also stores a design test group, old or new card, which card events report so we can compare the two designs.

In the EEA, the UK, Switzerland and wherever we cannot tell your country, no visit or ad cookie is set until you choose. We still count the visit itself, with no id that links it to other visits. In Brazil, ad measurement waits for your yes. Elsewhere both are on and the banner lets you turn ad measurement off. A browser that sends Global Privacy Control turns ad measurement off everywhere.

How we use it

• To sign you in and keep your account, preferences and saved campaigns.
• To send the alerts you ask for, within your daily cap and quiet hours, and to stop them when you unsubscribe.
• To show you your own audience and tier, and to choose which campaign alerts fit an account you connected. Only you see these numbers.
• To count visits and see which pages, campaigns and ads work.
• To send ad events to Meta and Google: a landing view, a Join tap, a signup and an activation. Meta and Google may use these events to measure ads and to target and deliver ads, including on their own services. Turn this off with the banner, Global Privacy Control, aboutads.info/choices or youronlinechoices.eu.
• To keep the site safe: bot checks and rate limits. Rate limit counters hold keyed hashes, never an IP address.
• To answer you when you write to us.

We never share your audience numbers or tier with boards, brands or anyone else, and they never decide who may join a campaign. They sort the alerts you asked for. Your tier also sets the value of your signup event, a plain number Meta and Google receive, never the tier itself.

Who receives it

Microsoft Azure

Hosts the site, the database, files and logs in its East US 2 region (Virginia, United States). Database backups are copied to its Central US region (Iowa, United States). Its Front Door edge service runs worldwide, and it logs each request with the IP address. Azure Speech, in East US 2, can transcribe public campaign videos.

Resend

Sends our email: your address and the sign-in code or alert. An alert can name your connected account and its audience share, such as Fits @you: 62% US. Resend keeps its own delivery logs.

Meta

If you sign in with Instagram, which takes Creator and Business accounts only, Instagram sends us your username, account type, follower and post counts and two Instagram ids, never an email address or a password. Sign-in keeps the username and one id. The same consent covers the audience check, so while that check is open, signing in with Instagram or connecting it in Profile also connects the account as follows. If you connect an Instagram professional account for an audience check, Instagram gives us the account's username, account type, follower and post counts and its audience demographics (countries, cities, age groups and gender, as counts we turn into percentages), and an access token we keep encrypted to read them again once a day. With ad measurement on, our server sends Meta the event (a landing view, a Join tap, a signup or an activation), its time and page, a hashed email address, hashed account and visitor ids, your IP address, your browser's user agent and the _fbp and _fbc values. If you sign up with Google, the signup events also carry the first and last name Google gave us, hashed. We keep the IP address and the hashed names only until Meta has the event, 7 days at most, then delete them. A verified signup also carries a value in US dollars, higher when your best connected account reaches a better audience tier, or set by your country when none does. Meta may use these events to measure ads and to target and deliver ads, including on Facebook and Instagram.

Google

If you sign in with Google, Google sends us your name, email address and Google id. With ad measurement on, our server sends Google a verified signup with a hashed email address, the Google ad click id, its time, its value and your consent state. Google may use it to measure ads and to target and deliver ads, including on Search and YouTube. If you check a YouTube audience, Google gives us the numbers above and we revoke its token right away.

TikTok

If you sign in with TikTok, TikTok sends us your display name and TikTok id. It gives no email address. A TikTok audience check reads your follower count. If you connect a TikTok account with Connect TikTok (audience), Business or Personal, TikTok gives us its display name, username, follower count, whether it is a Business or Personal account and, from 100 followers, its followers by country, age group and gender, as percentages, and a refresh token we keep encrypted to read them again once a day. We keep the display name, or the username when there is none, and otherwise use the username only to match the account to one you already connected. When you remove the account we ask TikTok to end our access.

X

If you sign in with X, X sends us your name, username, X id and the email address X has confirmed for your account, when it has one. It never lets us post for you or read your direct messages.

Discord

If you sign in with Discord, Discord sends us your name, email address and Discord id.

Telegram

If you turn on Telegram alerts, Telegram receives each alert for your chat id. An alert can name your connected account and its audience share, such as Fits @you: 62% US. Telegram keeps its own delivery logs, and each alert stays in your chat until you delete it.

Push services

If you turn on push, your browser's push service (from Google, Mozilla, Apple or Microsoft) carries each alert to your device, encrypted.

Fireworks AI

Reads public campaign briefs, board listings, transcripts of public campaign videos and public brand pages to pull out rules and moments. It never receives account, visitor or alert data.

If you choose the Vouch method for a TikTok audience check, Vouch runs the proof and sends us only the derived numbers. Country and network lookups use a copy of MaxMind's GeoLite2 database on our own servers, so nothing is sent to MaxMind. Services outside Azure may handle data in other countries.

Public campaign data

Campaign data comes from the public pages of clipping boards, the ones a signed-out browser can open. We honor robots.txt and never sign in. We collect the title, rates, budget, platforms, counts, brand name and logo, the links the board gives, and public brief documents.

For a board's top clips we keep the platform, the view count the board shows, the link to the public post and the clipper's handle when the board shows one. We use them to study what works on a campaign and to show a top clip as the platform's own embed. We never download those videos, and the handles never reach our MCP server or our logs. Apart from them, we never collect clippers' names, handles, email addresses or links. An automatic check rejects any other record that holds one, and email addresses, phone numbers and handles in brief contact lines are masked before we store the text. Public source videos named in a brief may be downloaded to find moments. Their audio is deleted after 3 days, frames after 7 and transcripts after 30.

How long it stays

Account

Until you delete it. Then erased within 7 days.

Sessions

60 days from your last day of use. Expired sessions are deleted every hour.

Sign-in codes

Valid for 15 minutes, stored as hashes, deleted within 2 hours of expiry. Telegram sign-in links are deleted a day after use or expiry.

Visits and clicks

400 days.

Events

90 days.

Alert history

90 days, then daily counts only.

Ad events

The hashed email, hashed names, ids, IP address, user agent and click ids are removed once the event is sent, or after 7 days at most. Landing and Join events are deleted after 90 days. Signup events stay without those details.

Connected apps

Access tokens last 1 hour and refresh tokens 30 days. A disconnected app's record is deleted after 30 days.

Audience check

YouTube and TikTok numbers expire 90 days after the check. Instagram numbers, and TikTok numbers from Connect TikTok (audience), are read again every day while the account stays connected. Instagram's encrypted token lasts 60 days, we renew it before then, and it is deleted the moment you remove the account, remove ClippingAlpha in Instagram's settings or delete your account. TikTok's encrypted refresh token lasts a year, and it is deleted the moment you remove the account or delete your account, or at the next daily read once you remove ClippingAlpha in TikTok's settings. Remove any account any time from Profile. A connected account is never deleted for inactivity. It stays, with its numbers, until you remove it in Profile or delete your data, or, for Instagram, until you remove ClippingAlpha in Instagram's settings.

Logs and backups

Azure logs 30 days. Database backups 14 days, in East US 2 and Central US, so erased data can remain in a backup for up to 14 days. Deleted files can be restored for 7 days, then they are gone.

Kept on purpose

Consent records, the banner choices and a one-way hash of any address that unsubscribed, bounced, complained or said it is under 18. They prove what was agreed and make sure we never message that address again.

Your choices

• Export everything tied to your account as one JSON file: Profile, Export my data.
• Delete your account: Profile, Delete my data. The steps also cover what happens if you cannot sign in.
• Stop alerts with the unsubscribe link in any alert email, one click, with /stop on Telegram, or in Alerts.
• Change your answers, time zone and country in Profile.
• Change your cookie choice any time: tap Your privacy choices at the foot of any page to open the banner again, or send Global Privacy Control from your browser.
• Disconnect an AI agent or remove a connected audience account in Profile. Removing ClippingAlpha in Instagram's settings (Apps and websites) deletes that account's numbers and token here too. Removing it in TikTok's settings (Security, Manage app permissions) deletes the token at the next daily read.

Where you live may give you more rights. California, the EEA and the UK are below. Write to us from anywhere and we will help.

California privacy rights

If you live in California, the California Consumer Privacy Act gives you the rights below. In the last 12 months we collected these categories of personal information, each described in What we collect:

• Identifiers: your name, email address, sign-in provider ids, Telegram chat id, IP address and cookie ids.
• Internet activity: the pages you open, the site that sent you, and taps and views on the site.
• Geolocation: the country and network looked up from your IP address, never a precise location.
• Account details: your preferences, profile answers, saved campaigns, alert rules and alert history.
• Audience data: for an account you connect, its handle, counts and audience shares, and the audience tier we infer from them.

We collect them from you, your browser, your sign-in provider and the platforms you connect, for the purposes in How we use it, and keep them as long as How long it stays says. We disclose them for business purposes to the services in Who receives it.

We do not sell personal information for money. With ad measurement on, our server sends Meta and Google identifiers and internet activity in ad events. California law calls that sharing for cross-context behavioral advertising, and may also call it a sale, so the same opt-out covers both. We do not knowingly sell or share the personal information of anyone under 16.

• Right to know: ask what we collect, use and disclose about you, and get a copy. Profile, Export my data gives you everything at once.
• Right to delete: Profile, Delete my data, or email us.
• Right to correct: change your details in Profile, or email us.
• Right to opt out of sharing: tap Your privacy choices at the foot of any page and choose the ad opt-out. A browser that sends Global Privacy Control opts out on its own, and we honor it.
• No discrimination: using these rights never changes what ClippingAlpha gives you or costs you.

To use a right, use Profile or email privacy@clippingalpha.com. We confirm the request comes from you through your signed-in account or the email address on it, and answer within 45 days. Someone you authorize can ask for you, with your signed permission.

EEA and UK rights

If you live in the EEA, the UK or Switzerland, the GDPR or your local law applies. We rely on these legal bases:

Contract

Your account, sign-in, saved campaigns, the alerts you ask for and the AI agents you connect.

Consent

Ad measurement and visit cookies, and the audience check. Withdraw it any time with Your privacy choices, Global Privacy Control or by removing the account in Profile. Withdrawing does not undo what happened before.

Legitimate interests

Keeping the site safe with bot checks and rate limits, and counting visits without an id where your region asks first.

Legal obligation

Consent records and the list of addresses we must never message again.

Momentist, Inc. and its hosting are in the United States. Data from the EEA and Switzerland goes there under the EU Standard Contractual Clauses, and data from the UK under the same clauses with the UK Addendum.

You can ask to access, correct, delete or port your data, and to restrict or object to how we use it. You can also complain to a supervisory authority, such as the data protection authority where you live or work. Write to our data protection contact: dpo@clippingalpha.com

People under 18

ClippingAlpha accounts are for people 18 or older. If you think someone under 18 signed up, email us and we will delete the account.

How we protect it

• Sign-in codes, link tokens and agent tokens are stored only as hashes.
• Sign-in provider tokens are dropped before anything is saved. The exceptions are the Instagram token of an account connected for an audience check, by sign-in or from Profile, and the TikTok refresh token from Connect TikTok (audience): each is encrypted with AES-256-GCM before it is stored, kept once, and never written to a log. TikTok's day-long access token is never stored.
• The database and file storage accept only Microsoft Entra identities, never a shared password.
• The site redirects every plain HTTP request to HTTPS.

Changes and contact

When this policy changes, the date at the top changes with it.