01Who we are and our role
Recapply is run by [COMPANY LEGAL NAME], [ADDRESS]. This policy explains how we handle personal data when you visit our website or use Recapply.
There are two kinds of people here, and our role is different for each:
- Visitors and customers. For people who visit our site, fill in our contact form, or use a Recapply account (and their teams), we decide how the data is used. We're the controller (under the GDPR and UK GDPR) or the business (under California law).
- End users. These are the people our customers make recaps for, including people who connect their own app through a customer's campaign link. The customer decides how their data is used, and we only process it on the customer's instructions. We're the customer's processor or service provider, under our Data Processing Addendum. If you're an end user, the business that sent you a recap is the best first contact for questions about your data.
02What we collect
Your account. When you sign up: your name, email address, and login details (handled by Clerk, our login provider), plus your company name and who's on your team.
Your brand settings. The colors, app name, headline, words, and template you choose. These are saved with your company account at Clerk, along with your plan and a fingerprint (hash) of each API key, never the key itself.
Your users' data. When you upload a spreadsheet (CSV or Excel), paste text, or use sample data, the file is read in your browser. We don't store it on our servers. To create links, the browser (or your server, if you use our API) sends each person's first name, their numbers for the year or month the recap covers, and (if you add one) their job or team to our server, which seals them into a link and sends it back. We keep a short record per link: a random id, your company, the campaign, when it was made, the first name you put on it, and counts and times of opens, shares and saves. It never holds numbers or emails. Email addresses and phone numbers in your file stay in your browser and are only used to open your own messaging apps, unless an admin uses "Email everyone from Recapply" (next paragraph).
Emailing the people in your recaps (optional, off unless we switch it on). Recapply emails the people in your recaps only when a company admin taps Send on "Email everyone from Recapply". At that moment the admin's browser sends each person's email address and first name, with their own recap link, to our server. We use the address once, to send that one email through our email service, Resend, which handles it while the email is on its way. We don't store the address, put it in our activity log or write it to our own logs. The activity log keeps only how many emails were sent, skipped or failed. The email says which company made the recap, holds only that person's own link, is sent without a tracking pixel or open or click tracking, and has a "Report this" link to us. A company can send at most 500 at once and 2,000 a day. Resend keeps its own delivery records for a time, under its own policy. Recapply never emails anyone otherwise: automatic recaps and the API email only your company's admins, or no one.
Share links. Each link contains that person's first name and numbers (plus your brand settings) inside the web address, encrypted with AES-256-GCM, so nobody reading a web address or a request log can read them or change them. Our servers can open them, because they have to draw the recap. Links made before we added encryption are signed instead, so their name and numbers can be read from the address. If you choose an expiry time (30 days, 90 days, or a year), the link stops opening after it. When someone opens a link or saves its image, our host processes that address to show the recap, like any web request.
Connected tools. If you connect a tool (like Stripe, HubSpot, or your own database), our server uses the key you give it once to read your users' numbers and sends them straight to your browser. We don't store the data, and we never log the key.
Automatic recaps (optional). If a company admin switches on "Run this by itself", we keep the connection details they typed (for example an API key), scrambled with a secret key. They are used only to make that company's recaps on the schedule the admin chose, are never shown again, and are erased when the admin deletes the connection or the company's data. Each time the recaps are made, we email only that company's admins to say they are ready. These admin emails never go to the people in your recaps (they only get an email when an admin taps Send, see below), and the email holds no names or numbers of any person. If nobody switches this on, nothing like this is kept.
Apps your users connect. If you share a campaign link, each person can type a first name (optional) and connect an app of their own (like GitHub, Strava, or Spotify), or give a public username for apps that work that way. We read their totals for the year once to make their recap, then cancel our access where the app allows it. We don't store their sign-in pass or their numbers; the recap lives inside their link. Fitness trackers (Oura, WHOOP, Withings) give numbers like steps, workouts, sleep score, strain, and recovery, which some laws treat as health data. They're only read if the person connects that app.
Link stats. When someone opens a recap, finishes it, opens their card, shares it, or saves its image, the page tells our server. We count each kind once per link per day, and add up daily totals per campaign, so you can see how your campaign is doing. We don't set cookies for this and don't store IP addresses.
Activity log. When someone in your company (or an API key, or billing) makes a change, like making links, switching a link off, making an API key, or saving the brand, we record who did it (an account id), what they did, an id or a count, the time, and a scrambled (hashed) form of their IP address that can't be turned back into the address. It holds no names, emails, or recaps. Only your company's admins can see it.
Contact and demo requests. If you fill in our contact form, we keep what you type (your name, work email, company, website, rough number of users, and your message) in our database and email it to our team inbox through Resend, so we can reply. Our server and our named staff can read it.
Payments. Once paid plans launch, our payments provider (Cash App, Square, Stripe, Paddle or Lemon Squeezy) handles checkout and your card details. We receive your plan, its status, and an id that links the payment to your company, never your full card number. If you pay through Cash App, you pay our Cash App account yourself and we check the payment by hand; we keep only the plan, the amount, a short note code and the time you told us you paid.
Technical data. Like any website, our host receives your IP address, browser type, and the pages you request, and keeps short-term logs for security and to fix problems.
03Why we use it, and our legal bases
- To run the service (log you in, set up your company, save your brand, make recaps and share links, bill you): because it's needed for our contract with you.
- To keep it safe (stop abuse, fake recaps, and attacks; keep the activity log): our legitimate interest in a safe, reliable service.
- To show you link stats: our legitimate interest, and yours, in seeing how a campaign does, done without cookies or stored IP addresses.
- To reply to contact requests and send important account updates: our legitimate interest in answering business questions, or steps you asked for before a contract.
- To follow the law, like tax records: a legal obligation.
For end users' data, we act on our customers' instructions, and the customer is responsible for having its own legal basis, and consent where needed. When a person connects their own app, they choose to sign in and allow access.
We don't sell personal data, don't use it for advertising, don't use it to train AI models, and don't use your users' data for anything except making the recaps you asked for and keeping the service safe.
04Who helps us run it
We share data only with services that help us run Recapply, and only what they need:
- Clerk — logins, user accounts, team accounts, and your brand settings.
- Vercel — hosts the website and app, and handles every request, including opening share links.
- Supabase — our database. It holds contact requests, link records, link counts, campaign names, the off switches, plan usage, and the activity log. Only our servers can reach it.
- Resend — sends contact requests to our team's inbox, ready or failed notices for automatic recaps to your company's admins (their work email address, your company name, and recap counts; no end-user names or numbers), and, only when an admin taps Send and we have switched it on, the recap emails to the people in a recap (their email address, first name and own recap link; used once, not stored by us).
- Google Fonts — when a recap image is saved, our server downloads lettering from Google. Google sees our server's request, not your users' details. The fonts on our own pages are bundled with the site, so your browser doesn't contact Google.
- Cash App, Square, Stripe, Paddle or Lemon Squeezy (whichever we use) — payments, once paid plans launch. They handle card details; we never see your full card number.
Optional AI (off unless a company switches it on): if a company switches on AI-written personal lines, then for each person we send their first name, their top two or three recap numbers with plain labels (for example "Commits: 214"), and the company's name, description, cover headline, sign-off, recap type and language to Vercel's AI Gateway and the AI model provider behind it, only to write that one line. We send nothing else (no email, phone number or logo). Recapply does not store the request or the answer; only the finished line is kept in that person's link. Companies that do not switch it on send nothing. The optional AI assistant on the Data page, if we switch it on and you use it, sends what you type and the data you ask it about to the same services.
The full list, with what each one sees and where, is on our sub-processors page. We may also share data if the law requires it, or with a new owner if Recapply is ever sold (they'd have to follow this policy).
05Where it's processed
We're based in the United States and our providers mainly process data in the US. When personal data comes from the EU, EEA, UK, or Switzerland, we rely on safeguards the law accepts: the European Commission's Standard Contractual Clauses (with the UK Addendum for UK data) in our providers' data processing terms, or a provider's certification under the EU-U.S. Data Privacy Framework where it has one. You can ask us for a copy of the relevant safeguards through our contact form.
06How long we keep it
- Account and brand settings: while your account is open. We delete them within 30 days after you delete your account.
- Spreadsheets you add: never stored on our servers. They're gone when you close or refresh the page.
- Share links: the data lives in the link itself, so it lasts as long as people keep the link, until the expiry time you chose, or until the link is switched off. We can't delete copies people have saved, but you (or we, on request) can switch links off. Links made before link records existed can't be switched off.
- Link records, campaign names, and daily campaign totals: while your account is open, or until an admin deletes all company data.
- Link stats (opens, shares, saves): deleted automatically after 13 months.
- Activity log: deleted automatically after 13 months.
- Contact requests: kept until we delete them, or until you ask us to. Our server and named staff can read them. We are adding a time limit.
- App-connection cookie: 10 minutes at most, and cleared as soon as the connection finishes.
- Server logs: kept for a short time by our host, then deleted.
- Billing records: once billing launches, kept as long as tax law requires.
07Deleting your company's data
A company admin can delete all of the company's data from Settings, after typing the company's name to confirm. This deletes its link records, link stats, campaigns, past usage, activity log, saved brand, and API keys.
We keep, on purpose: the company account, its team and plan (at Clerk); the list of links and campaigns it switched off, so they stay off; this month's usage, so plan limits can't be reset; and one activity entry saying the delete happened.
Links already sent keep opening, because each recap lives inside its own link. Switch links off first if you want them to stop. Contact requests aren't part of this; ask us and we'll delete them.
09Your rights (GDPR and UK GDPR)
If you're in the EU, EEA, UK, or Switzerland, you can ask us to:
- tell you what data we have about you and give you a copy (access);
- fix data that's wrong (correction);
- delete your data (erasure);
- limit how we use it (restriction), or object to uses based on our legitimate interests;
- send it to you or another service in a common format (portability);
- withdraw consent, where we relied on it, at any time.
You can also complain to your local data protection authority (for example, the ICO in the UK). We'd like the chance to help first.
10Your rights in the US (including California)
If you live in California or another US state with a privacy law, you have the right to know what personal information we collect, use, and disclose; to get a copy; to correct it; and to delete it.
- What we collect (in the last 12 months): identifiers (name, email, account id, hashed IP), business contact details, commercial information (your plan), internet activity on our site (link stats without IP addresses, and short-term server logs), and the activity numbers customers send us to make recaps. The sources and purposes are described above.
- We don't sell or share personal information, as the CCPA defines those words, and we haven't in the last 12 months. We don't share it for cross-context behavioral advertising. We don't knowingly sell or share the data of anyone under 16.
- Sensitive personal information: we don't use it to infer things about people. Fitness numbers a person chooses to put in their own recap are used only to make that recap.
- Opting out: since we don't sell or share personal information, there's nothing to opt out of, so no "Do Not Sell or Share" link or Global Privacy Control setting is needed.
- You can use an authorized agent to make a request. We'll check the request is really from you (or your agent) by asking you to confirm from the email on your account or contact request.
- We won't treat you differently, or charge you more, for using these rights.
11How to use your rights
Write to us through our contact form and say what you'd like. We'll confirm we got it, check it's you, and reply within 30 days (45 days for US state law requests). If we need more time, we'll tell you why.
Company admins can also delete their company's data themselves from Settings (see Deleting your company's data).
If you're an end user, we'll pass your request to the business that made your recap, since they're in charge of your data, and help them answer it. We can also switch off your recap link.
12Children
Recapply is for businesses and isn't meant for children. We don't knowingly collect data about children under 13 (or under 16 in the EU and UK), and our Terms don't let customers add it without verified parental consent. If you think we hold a child's data, tell us through our contact form and we'll switch off the links and delete what we hold.
13What we cannot promise
- Our servers must open a recap to draw it, so we can technically read a first name and numbers while we do.
- People with access to our hosting or database accounts could in principle read what we store. We keep the number of people with that access small, and we are working to require a second sign-in step on those accounts.
- Anyone with a recap link can read it. We cannot delete copies that people saved or shared.
- Our email and hosting providers keep their own logs for a time. Hosting logs hold the web address, which includes the link.
More on our Security page.
14Security
Everything travels over encrypted connections (HTTPS). Logins are handled by Clerk. Our database tables are closed to the public. Share links are encrypted with a secret key, so nobody reading a web address or a request log can read them, change them, or fake them. Recap pages ask search engines not to list them. Our team inbox opens only for named staff accounts. A second sign-in step is supported, but we do not require it yet. More detail is on our Security page. No system is perfect. If a breach affects your data, we'll tell affected customers without undue delay, and the authorities as the law requires.
15Changes to this policy
We'll update this page when Recapply changes, for example when payments launch. We'll change the date at the top, and for important changes we'll tell you by email or in the app. See also our Terms of Service.
16Contact us
Questions or requests about your data? Reach us through our contact form or write to [COMPANY LEGAL NAME], [ADDRESS].