# Privacy policy

What ClippingAlpha collects, why, who receives it, how long we keep it, and how to export or delete it yourself.

As of 11:10 UTC on 27 Oct 2026. Page: https://clippingalpha.com/privacy

Last updated 26 October 2026

This policy covers clippingalpha.com, its alerts by email, push, Telegram and Whop, its app inside Whop, and its MCP server for AI agents. It says what we collect, why, who receives it and how long we keep it.

## 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, Google, OpenAI and X as sharing, and you can turn them off.
- If you sign up, we may share a hashed copy of your email address with Google and Meta to build advertising audiences of clippers like you. In the EEA, the UK and Switzerland only after you say yes. Elsewhere you can turn it off any time and you leave the lists within a day.
- The site loads no Meta, Google, OpenAI, X or other third-party tracking script. Our server sends ad measurement events to Meta, Google, OpenAI and X 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, Discord or Whop 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](https://clippingalpha.com/data-deletion).

## 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. With visit counting on, also the browser and system versions, the app whose browser opened the page, the screen and window size, and your color scheme and reduced motion settings, never the full user agent. 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. When you sign up or sign in, we also note the steps of that attempt (form shown, method picked, code sent, code wrong, sign-in error, account created) under a random id that lives only in the page, to find where signup breaks. With visit counting on, these steps are linked to your visit, and through it to its source, campaign, ad and device. Where your region asks first and you have not said yes, they are counted only and never linked to a visit, a browser or an account.
- **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.
- **Page speed**: On about half of page views, the page measures how fast it loaded and responded: load time, response time to taps and how much the layout shifted. We keep those numbers with the kind of page, the country looked up from your IP address, whether it was a phone or a computer, and whether the page opened in a browser of its own or inside an app such as Instagram or TikTok. Never a visit id, a browser id, a cookie or the IP address, so they cannot be tied to you. Because nothing identifies you, they are collected without asking, also before you choose in the banner, and nothing is stored on your device.
- **Device setup**: With visit counting on, your browser's setup: screen size and pixel ratio, time zone, languages, processor cores, memory, platform, graphics chip, touch support and the browser's own hints, plus short hashes of a drawn image, a sound and a list of fonts. We keep only a keyed hash of it and a few flags for a setup that does not match the browser it claims, never the values. It helps us tell people from bots across visits and networks. It is never used for ads, never sent to Meta, Google or OpenAI, and never used to identify you by name.
- **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, your browser's push subscription, or your Whop id, 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, social apps, 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 app. 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 app 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 app account id, never the id itself.
- **Handle check**: Only if you connect a handle with a bio code, up to 10 across TikTok, Instagram, YouTube and X. For each handle: the platform, the handle, the code we gave you, and from its public profile its platform id, follower count and creation date when the profile shows them, and the Alpha Points it earned. We read the public profile through Apify to find the code, never with a login, and never keep the bio. For a post you add to an AP campaign: its link, when it was posted and its views, read the same way when you add it and again 7 days later. We keep a keyed hash of each handle that earned Alpha Points, so a handle earns them once.
- **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 we set is first-party, set by our own server. Only ca\_member 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.
- **ca\_club**: When your AlphaClub founding offer started on this browser, signed so it cannot be moved, for 180 days. A time only, no id. It keeps the 48 hours from restarting.
- **ca\_member**: Set when you sign in or sign up, for 365 days, and kept when you sign out. The value 1 only, no id and no account data. It stops the AlphaClub founding offer from showing again on this browser, and it is removed when you delete your account.
- **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.
- **Video players**: A clip's player loads only when you press play. Then YouTube, TikTok, Instagram or Google Drive may set their own cookies under their own privacy policies. If you are signed in to YouTube, YouTube sees it is you.
- **Local storage**: Your browser keeps the theme, grid or table view and the app you post on, whether it is signed in to AlphaClub and, for the browser session, a dismissed AlphaClub strip. 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. The device setup is read only where visit counting is on, and never after you turn ad measurement off or send Global Privacy Control.

## 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 verify a handle you connect by its bio code, count the posts you add to AP campaigns and award Alpha Points for them.
- To count visits and see which pages, campaigns and ads work.
- To see how fast our pages load and respond in each country, on phones and computers, and fix the slow ones.
- 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. A verified signup also goes to OpenAI, to measure ChatGPT ads and improve their delivery, and to X, to measure X ads and improve their delivery. Turn this off with the banner, Global Privacy Control, [aboutads.info/choices](https://optout.aboutads.info/) or [youronlinechoices.eu](https://www.youronlinechoices.eu/).
- To build advertising audiences: a hashed copy of a verified clipper's email address goes to Google and Meta, so their ads reach more clippers like you, and fewer ads reach people who already use ClippingAlpha. See Advertising audiences.
- To keep the site safe: bot checks and rate limits. One bot check runs in the page by itself and shows nothing: whether a tap, a key or a scroll came, how long the page was open, a small calculation, and signs of an automated browser. We keep only its result (passed, no input, or failed) on the visit, never what you typed or where you tapped, and nothing on your device. 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 clipping platforms, 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, Google, OpenAI and X receive, never the tier itself. With advertising audiences on, your tier also decides which of our lists your hashed email joins (all verified clippers, US verified, or US verified and Tier 1), so Google and Meta learn which list you are in, never your numbers.

## Advertising audiences

Once you sign up and confirm an alert channel, we may add a hashed copy of your confirmed email address to advertising audiences at Google (Customer Match) and Meta (Custom Audiences). Google and Meta use these lists to show our ads to people like our clippers, to measure those ads and to leave out people who already use ClippingAlpha. This is not a sale for money. California law may call it sharing for cross-context behavioral advertising.

- **What leaves**: Only a SHA-256 hash of your email address, made on our servers: lowercased, spaces removed, and for Gmail addresses without dots or a plus part, as Google asks. Never the address itself, your name, your connected accounts or your numbers. Google and Meta match the hash against their own users and then delete the hashes they cannot match, under their own terms.
- **Which lists**: All verified clippers, US verified, and US verified with Tier 1. Your audience tier decides which of them you join, so Google and Meta learn the list, never your numbers. Google keeps a member for up to 540 days, and we send you again while you stay.
- **Where you live**: In the EEA, the UK, Switzerland, Brazil, and wherever we cannot tell your country, only after you tick the box at signup or turn on Ad audiences in Profile. Everywhere else you are included by default, and you can turn it off any time.
- **How to turn it off**: Profile, Your data, Ad audiences. Or Do Not Sell or Share My Personal Information (Your privacy choices) at the foot of any page and the ad opt-out, or Global Privacy Control in your browser, which we record on your account the next time you visit signed in. Deleting your account turns it off too.
- **When it takes effect**: At the next daily update, within a day, we ask Google and Meta to remove your hash from every list. We keep the hash we sent only while you are in a list, so we can remove it, and delete it when you leave.

## 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.
- **Apify**: Reads public pages for us, never with a login: the public profile of a handle you connect, to find its bio code, its follower count once a month, and the posts you add to AP campaigns. Apify gets the handle or the post link only, never your name, email address or ClippingAlpha account.
- **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. With advertising audiences on, a hashed email address joins our Custom Audiences, see Advertising audiences.
- **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. With advertising audiences on, a hashed email address joins our Customer Match lists, see Advertising audiences. If you check a YouTube audience, Google gives us the numbers above and we revoke its token right away.
- **OpenAI**: For ChatGPT ads. With ad measurement on, our server sends OpenAI a verified signup: the event, its time and page, a hashed email address, hashed account and visitor ids, the ChatGPT ad click id from the link you arrived by, and a value in US dollars. No IP address, user agent or name goes to OpenAI. In the EEA, the UK, Switzerland, Brazil and wherever we cannot tell your country, only after a yes on a banner that names OpenAI. OpenAI uses it to measure ChatGPT ads and improve their delivery, and says it does not use these events to personalize ads today.
- **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. For X ads, with ad measurement on, our server sends X a verified signup: its time, a hashed email address, the X ad click id from the link you arrived by, and a value in US dollars. No IP address, user agent or name goes to X. In the EEA, the UK, Switzerland, Brazil and wherever we cannot tell your country, only after a yes on a banner that names X. X may use it to measure ads and to target and deliver ads on X.
- **Discord**: If you sign in with Discord, Discord sends us your name, email address and Discord id.
- **Whop**: If you sign in with Whop, Whop sends us your name, username, Whop id, profile picture and the email address Whop has verified for your account, when it has one. Sign-in drops the picture and keeps your name, username, Whop id and that address. It never lets us see your purchases, memberships or payments on Whop.
- **Whop alerts**: If you turn on alerts in Whop, we send Whop your Whop id and the text of each alert (the campaign, its pay per 1K views and its budget), and Whop shows it to you as a notification. To check that Whop can deliver it, we ask Whop whether your Whop account can open the ClippingAlpha app. When you open ClippingAlpha inside Whop, Whop tells us your Whop id with each page you open. Whop keeps its own notification history.
- **ClippingAlpha inside Whop**: We count the pages you open in ClippingAlpha inside Whop as visits from Whop, with the same facts as any visit (the page, the time, your country from the network address, your device type) and a code we make from your Whop id with a secret key, never the id itself, so we can tell a returning member from a new one. Nothing is stored on your device there, and nothing of it goes to Meta or Google. If you tap Turn on alerts there, that tap makes your ClippingAlpha account: your Whop id, the name and username your Whop profile shows, and your alert picks. Whop gives us no email address for it. Sign in with Whop on clippingalpha.com opens the same account.
- **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, clipping platform 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 platforms, the ones a signed-out browser can open. We honor robots.txt. The one place we sign in is Content Rewards, where our own ClippingAlpha account reads the campaign material the platform shows to signed-in creators. We use that material only for our own summaries and analysis and never publish it. We collect the title, rates, budget, social apps, counts, brand name and logo, the links the platform gives, and public brief documents.

For a clipping platform's top clips we keep the app, the view count the platform shows, the link to the public post and the clipper's handle when the platform shows one. We use them to study what works on a campaign and show them as the platform does: on the campaign page, as the app's own embed with the handle and the views, and in our MCP server's answers about that campaign. We never download those videos, and the handles never reach 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 and frames after 7. Their transcripts and the brief text we read are kept in private storage for our own analysis, and never published.

For our market news we read public articles and posts about clipping found through GDELT, Perplexity search, X and LinkedIn search results (through Apify, never with a login), keep only the link, outlet, date, the author's public name and role and our own short summary, and delete LinkedIn records after 180 days.

## 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.
- **Signup steps**: 90 days.
- **Page speed**: 30 days.
- **Device setup**: The keyed hash goes 90 days after a browser with that setup was last seen, and with your visits when you delete your data.
- **Alert history**: 90 days, then daily counts only.
- **Campaign material**: Audio from public source videos 3 days, frames 7 days. Transcripts and brief text are kept privately for analysis and never published.
- **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.
- **Advertising audiences**: The hash we sent stays with us only while you are in a list, and goes at the next daily update after you leave. Google keeps a list member for up to 540 days unless we send them again.
- **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.
- **Handle check**: A code you never checked expires after 24 hours. A verified handle and its numbers stay until you remove it in Profile or delete your data, and its follower count is read again once a month. Removing a handle within 7 days of its Alpha Points takes them back. The keyed hash of a handle that earned Alpha Points stays after you remove it, so it never earns twice. Our record of each Apify read is deleted after 90 days.
- **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](https://clippingalpha.com/data-deletion) 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, with Turn off in our app inside Whop, 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.
- Leave our advertising audiences: Profile, Your data, Ad audiences. Do Not Sell or Share, the banner's ad opt-out and Global Privacy Control take you out too. You leave every list within a day.
- 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 apps 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, Google, OpenAI and X identifiers and internet activity in ad events, and with advertising audiences on, a hashed email address for our ad audiences. 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 Do Not Sell or Share My Personal Information (Your privacy choices) at the foot of any page and choose the ad opt-out, or turn off Ad audiences in Profile. A browser that sends Global Privacy Control opts out on its own, and we honor it, for the ad events and the advertising audiences alike.
- 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](mailto:privacy@clippingalpha.com?subject=California%20privacy%20request). 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, visit cookies and the device setup, the audience check, and advertising audiences (only after your yes at signup or in Profile). Withdraw it any time with Your privacy choices, Global Privacy Control, the Ad audiences switch or by removing the account in Profile. Withdrawing does not undo what happened before, and it takes you out of the advertising audiences within a day.
- **Legitimate interests**: Keeping the site safe with bot checks and rate limits, counting visits without an id where your region asks first, and noting the steps of your own signup attempt to fix where it breaks.
- **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](mailto:dpo@clippingalpha.com?subject=Data%20protection)

## 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.

Privacy questions, requests and complaints: [privacy@clippingalpha.com](mailto:privacy@clippingalpha.com?subject=Privacy)

Data protection contact: [dpo@clippingalpha.com](mailto:dpo@clippingalpha.com?subject=Data%20protection)

By post: Momentist, Inc., 169 Madison Ave STE 38364, New York, NY 10016, USA