Privacy
Draft for the public beta. This page has not been reviewed by a lawyer yet.
This page describes what upTake collects and why, in plain words. Last updated: 29 October 2026.
Visitors of a site that uses the upTake script
- The script sets no cookie.
- For each page view, upTake records the page address, the page title, the referring site, campaign parameters, the country and city, the type of device and the browser.
- IP addresses are never stored. They are used once, combined with a secret that changes every day, to compute an anonymous identifier that cannot be linked to the same visitor the next day.
- A random identifier is kept in the browser tab for the length of the visit, to link the pages of one visit together. It is erased when the tab closes.
- Off by default: the site owner can turn on an option that keeps a second random identifier in the browser's local storage for 90 days, to link a first visit to a payment made on a later day. It is not shared between sites. A site owner who turns it on is responsible for telling their visitors and for asking for their consent where the law requires it.
- Signups: when a site tells upTake that someone signed up, it may pass that person's email address. The address travels encrypted (HTTPS) and is never stored: upTake keeps only a fingerprint of it, computed with a secret key that is different for every site, so the same address gives a different fingerprint on two sites and cannot be read back. The same applies to the email of a customer received from the site's payment provider, or from its sign-in service (Supabase Auth, Clerk). The only purpose is to credit a payment made on a later day to the post or the link that first brought that person.
- Visits are deleted automatically after 13 months (395 days). A signup fingerprint is deleted after 13 months without any visit, signup or payment linked to it.
- For this data, the site owner is the data controller and upTake acts as their processor, under the data processing agreement. To use your rights, contact the site you visited.
Makers who use upTake
- Your account: your email address, and your name, email address and profile picture from Google or Discord if you sign in with one of them.
- Your project: its address, the description you confirm, your tracked links, the actions you log, your posts and drafts, and your reports.
- The keys and access you provide when you connect a service are stored encrypted and are never sent back to your browser. upTake only reads what is listed below, and only for the project you connected the service to.
Services you can connect
- Payments (Stripe, Paddle, Lemon Squeezy, Polar, Gumroad, Ko-fi, Tebex, RevenueCat): with read-only access, or through the webhook you set up, upTake imports the amount, currency, date and identifiers of your payments. It never reads card data. The email address of a customer is read only to compute its fingerprint, as described above, and is never stored.
- A payment is linked to a visit by an identifier your site passes to the payment provider, or by the fingerprint of the customer's email when the same person signed up on your site (shown as “linked by email at signup”), or by time: the visitor seen on your site in the 30 minutes before the payment. Revenue linked by time is always shown as estimated.
- Sign-in services (Supabase Auth, Clerk): each new user of your app counts as a signup. Their email address is only used to compute a fingerprint, as described above.
- GitHub: on the repositories you pick, upTake reads release notes, pull request titles and commit messages. It never reads or stores your code.
- Social networks and communities (X, Bluesky, Mastodon, Dev.to, Product Hunt, Hacker News): upTake reads your posts, articles or launches with their public numbers (views, likes, replies, votes). On a network that allows it, upTake posts a draft only when you press Send, or at the time you scheduled it.
- Newsletter tools (Kit, beehiiv, Buttondown): upTake reads your sent emails with their recipients, opens and clicks. Nothing is ever sent to your subscribers.
- Analytics tools (Plausible, Umami): upTake reads 12 months of daily visits by source.
- Discord server stats: upTake reads the member and online counts of your server from the invite link you provide.
- Discord, Slack, Telegram and email: if you connect one, your weekly report and alerts (a first payment from a new source, a new release) are sent to the destination you provide, and on Discord your announcements when you press Send. Nothing is read from these services.
- Reddit, Indie Hackers and newsletters without a connected tool are measured with tracked links only: nothing is read from them.
Google services and YouTube
- Sign in with Google: upTake receives your name, email address and profile picture from Google, to create and open your account. Nothing else is read from your Google account.
- Google Search Console, if you connect it: with read-only access, upTake reads the list of your Search Console properties, to pick the one that matches your project, then the search queries and the pages of your site that appeared in Google over the last 90 days, with their impressions, clicks and positions, and the state of the sitemaps you sent to Google (errors and warnings).
- YouTube, if you connect it: upTake uses the YouTube API Services. With read-only access, it reads the name of your channel and your last 100 videos with their title, description, publication date, views, likes and comment counts. Each video is added to your project's action log, so that the visits it brings through your tracked links can be credited to it.
- This data is used only to show you these numbers inside upTake (your overview, releases and links), in your weekly report, your alerts and milestones, and in the drafts, ideas and answers upTake writes for you. Search queries, page addresses and their numbers, and video titles, descriptions and numbers, can be part of the context sent to our AI provider for these features (see “AI” below). It is not sold, not shared with anyone else, not used for advertising, and not used to train or improve AI models, by upTake or by its AI provider.
- The access Google gives upTake is stored encrypted and is used only on your request or by the automatic refresh of your connected services, every few hours. Imported search queries and videos stay in your project until you delete them, the project or your account. Disconnecting a service in the Integrations page stops all reading at once. To have the data already imported deleted too, write to support@upTake.me: it is deleted within 7 days.
- You can also remove upTake's access at any time from your Google account, in Third-party apps & services.
- By connecting YouTube, you agree to the YouTube Terms of Service. Google's use of your data is described in the Google Privacy Policy.
upTake's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- LinkedIn profile, if you connect it: upTake receives your LinkedIn member identifier and your name, to show which account is connected.
- LinkedIn Pages, if you connect it: upTake reads the list of the company pages you administer, with their names, so you can pick the pages of your project.
- In both cases, upTake posts on your profile or on the pages you picked only when you press Send on a draft or at the time you scheduled it, with the text you approved and your tracked link. It keeps the text and the address of each post it published, to measure the visits it brings. It does not read your feed, your connections or your messages.
- The access LinkedIn gives upTake is stored encrypted. Disconnecting LinkedIn in the Integrations page removes it. You can also remove upTake from your LinkedIn account, in Settings → Data privacy → Permitted services.
Cookies and browser storage
- upTake's app uses cookies only to keep you signed in and to check a connection to a service while it is being made (15 minutes).
- The app keeps a few display preferences in your browser (width of the sidebar, posts already read) and your current Ask upTake conversation in the browser tab, erased when the tab closes.
- No advertising or tracking cookie is set, by upTake or by the services below.
Where the data is
- The database is hosted by Supabase in the European Union (Ireland).
- The application is hosted by Vercel.
Other services we rely on
- PostHog (hosted in the European Union): how upTake's own website and app are used. On the public pages of this site: pages opened, buttons clicked, sections seen, loading times and the site you came from. In the app: pages opened and features used. No cookie is set and nothing is kept in your browser, no session is recorded, nothing you type is captured, and IP addresses are not kept. A visitor of the public pages is anonymous. If you create an account, the identifier of that visit is passed along in the address of the sign-up page, so that the visit is linked to your account; from then on you are identified by an account number, not by your email. This never covers the visitors of your site.
- Paddle: sells upTake subscriptions as merchant of record. Paddle collects your payment details and invoices you; upTake never sees your card, and only receives the status of your subscription.
- Resend: sends the emails upTake addresses to you (reports, alerts, getting-started messages).
- Sentry: receives error reports from the app, with emails, keys and addresses removed first.
- Google Safe Browsing: checks the destination of a redirect link when you create one.
AI
To prefill your project, write your weekly report, draft announcements and answer your questions, upTake sends the text of your homepage, your aggregated numbers, the Google searches and pages that bring you clicks, and the titles and text of your posts, videos and releases to Anthropic's Claude API. No visitor-level data is sent. Anthropic does not use this data to train its models. A screenshot you import is sent to the same API to be read, then discarded: upTake does not keep it.
Posts, public conversations and images
- The post studio saves your messages, selected context snapshots, generated versions and manual edit history until you delete the project or account. Selected context and recent conversation are sent to our AI provider when you request generation. These records are included in your data export.
- With your connected accounts, upTake keeps your published post text to prepare adaptations and measure its results. You decide every publication and reply.
- Listening uses official public APIs to find your product name, domain and chosen keywords or competitors. A mention contains its public source, URL, author and up to 500 characters. Mentions are deleted after 90 days; alert history after 7 days.
- Images you attach to posts are stored in a public image bucket so social networks can display them. Anyone with the image address can view it. Images no longer attached to a draft are removed by daily retention, after a one-day cleanup delay.
- When you request a website screenshot, the configured screenshot provider receives your public website address. This option is hidden unless that provider is configured.
Your rights and your data
- You can export all your data, and delete your account, from Settings. Deleting a project deletes its visits, payments, links, actions, imported data and reports.
- You can ask to access, correct or delete your personal data, or object to its use, by writing to support@upTake.me.
- If you are in the European Union, you can also complain to your data protection authority (in France, the CNIL).