Skip to content

Security

How we handle your data.

What we keep, what we don't, and where the limits are.

Your numbers go in. A sealed link comes out.
  • AES-256-GCMEvery link made now is encrypted with it.
  • About 30 secFor an off switch to reach every server.
  • 13 monthsThen link stats and activity are deleted.
  • Your choiceLinks open forever, 30 days, 90 days or 1 year.
How data moves

From your device to their phone.

  1. Your side

    Your device

    Spreadsheets and notes are read here, in your browser. Emails and phone numbers stay here.

    Not uploaded to us
  2. Our server

    Making the link

    It gets each person’s first name and numbers, and seals them into a link. The numbers are not saved.

    Sealed, not saved
  3. The link

    Sealed

    Encrypted with AES-256-GCM. The web address shows only random characters.

    Private link
  4. Their side

    Their phone

    They open the link and see their recap. Our servers open it only to draw the page.

    You send it, not us

We keep, per link

  • A random id
  • Your company
  • The campaign
  • When it was made
  • The first name

We never keep

  • Their numbers
  • Their emails
At a glance

What happens to each kind of data.

  • Spreadsheets and pasted notes

    Stays on your device

    Read in your browser, on your own device. Excel and CSV files aren’t uploaded to us, and the reader that sorts out messy notes runs in the page too, with no AI service.

  • Making the links

    Numbers not saved

    Only each person’s first name, their numbers and, if you add one, their job or team are sent to our server to be sealed into a link. The numbers and job or team are not saved. We keep only a short record per link (see Recap links). Emails and phone numbers stay in your browser, unless an admin chooses “Email everyone from Recapply” (next row).

  • Emailing your people (optional, off by default)

    Address used once, not saved

    Only when a company admin taps Send on “Email everyone from Recapply”. Each person’s email address and first name go from the admin’s browser to our server for that one send, and our email service (Resend) delivers the message. We use the address once and don’t save it. It isn’t in our database, our activity log or our own logs; the activity log keeps only how many were sent, skipped or failed. Each email holds only that person’s own recap link and is sent without a tracking pixel or open or click tracking. The email service keeps its own delivery records for a time. A company can send at most 500 at once and 2,000 a day. We only email links your own company made.

  • Tools you connect

    Kept only if you ask

    When you import from a tool like Google Sheets, Stripe or Postgres, our server reads just the people and numbers you asked for. The key or password you type is used for that one import, then thrown away, and it is never logged. The one exception is automatic recaps, which are optional: if an admin switches them on, we keep those connection details, scrambled with a secret key, only to make the recaps. They are never shown again and are erased when the admin deletes the connection or the company’s data.

  • AI lines (optional)

    Off unless chosen

    Off unless a company switches it on. Then each person’s first name, their top numbers and the company’s own text are sent to Vercel’s AI Gateway and the model provider behind it to write one short line, and nothing else. We don’t store the request or the answer; only the finished line goes into that person’s link. If the owner saves an AI key in the owner console, it is stored scrambled and only its last four characters are ever shown.

  • Your users’ own apps

    Nothing stored

    If you let users connect an app of their own, the sign-in pass from that app is used for one request to read their stats, then cancelled where the app allows it. Nothing is stored.

  • Recap links

    Encrypted

    Each link carries its own recap inside it: first name, numbers and your brand settings. They are encrypted, 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. We also keep a short record per link: a random id, your company, the campaign, when it was made and the first name you put on it. We use it for the People page and so you can switch the link off. Never numbers or emails.

  • Link stats

    Counts only

    When a recap is opened, read to the end, shared or saved, we count it at most once per link per day. We keep the counts and the times against that link’s record. No cookies, no stored IP addresses, no device details.

  • Activity log

    Admins only

    Company admins can see who changed what: links made, campaigns, API keys, brand and plan. Each entry keeps an account id, the action, an id or a count, the time, and a scrambled (hashed) form of the IP address. Never names, emails or recaps.

  • Old stats and activity

    Deleted at 13 months

    A daily job deletes link stats and activity entries once they’re older than 13 months.

  • Your account and team

    Handled by Clerk

    Sign-in, company accounts and teammates are handled by Clerk. Your brand settings are saved with your company account there.

  • API keys

    Hash only

    Shown to you once, when you make one. After that we keep only a fingerprint (a hash) of the key, never the key itself. You can make a key stop working by itself after 30, 90 or 365 days, and turn any key off.

  • Links for your developer

    Ends after 7 days

    A link you send a teammate to add your users stops working by itself after 7 days.

  • Messages to our team

    Kept until deleted

    What you send through our contact form (name, email, company, website and message) is kept in our database and also emailed to our team inbox. Our server and our named staff can read it. We keep it until we delete it.

Honest limits

Who can see what, honestly.

What we cannot promise

The plain truth.

  • Our servers must open a recap to draw it. So while they do, we can technically read the first name and the numbers inside it.
  • 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.

How we limit access

True today.

  • Our database tables are locked, so the public cannot reach them.
  • Each company can only see its own data.
  • Our staff tools never show your users’ names or numbers. They show company names, plans, sales inquiries and an activity trail.
  • We sell nothing. We use no analytics or tracking scripts, and no cookies for tracking.
Your controls

What your admins can do.

  • Link expiry

    Pick Forever, 30 days, 90 days or 1 year in your brand settings. New links stop opening after that time.

  • Off switches

    Turn off one link or a whole campaign from your dashboard. It takes effect within about 30 seconds.

  • Activity log

    Admins can see the last 100 changes in their company: who, what and when. Entries are kept 13 months.

  • Delete all company data

    Admins can wipe the company’s link records, link stats, campaigns, past usage, activity, saved brand and API keys from Settings, after typing the company’s name.

Deleting data

What “delete all” keeps, and why.

What stays

Kept on purpose.

  • Your company account, team and plan (they live at Clerk).
  • The list of links and campaigns you switched off, so they stay off.
  • This month’s usage, so plan limits can’t be reset by deleting.
  • One activity entry saying the delete happened, who did it and how many links went.

What to know

The limits of a delete.

  • Links you already sent still open: each recap lives inside its own link. Switch links off before you delete if you want them to stop.
  • Messages you sent our team through the contact form aren’t part of it. Ask us and we’ll delete them.
Website protections

Guards on every page.

  • HTTPS, always

    Browsers are told to use only HTTPS with our site for the next two years, so a connection can’t quietly fall back to plain HTTP.

  • No framing

    Our pages refuse to be shown inside another website, so nobody can dress them up to trick you into clicking.

  • Links stay put

    Recap and campaign pages send no referrer, so the link isn’t passed on when someone clicks out.

The basics

The everyday things.

  • No ad trackers, nothing sold

    Cookies only keep things working, like keeping you logged in. Your users’ data is only used to make the recaps you asked for.

  • Your data, your call

    Ask to see, fix, download or delete your data at any time.

  • A team inbox for named staff

    Our own team inbox only opens for named staff accounts. Everyone else gets a “not found” page. A second sign-in step is supported, but we do not require it yet.

Where we are

Limits we want you to know.

  • No certifications yet

    We’re a young company. We haven’t been through a security audit like SOC 2, so we don’t claim one. This page is how we show our work instead.

  • We rely on trusted services

    Clerk for sign-in, Vercel to host the site, Supabase for link records, activity and contact messages, and Resend to email those messages to us and, only when a company admin taps Send, to deliver recap emails to the people in a recap. The full list is on our sub-processors page.

  • A content policy, with a known limit

    Our pages tell your browser which sites they may load scripts, images and frames from, and nothing else is allowed. It still permits inline scripts, which the framework we build on needs, so it limits where code can come from rather than blocking every kind of injected code.

  • No system is perfect

    If something goes wrong that affects your data, we’ll tell you, and the authorities where the law requires it.

Found a problem? Tell us through our contact form, or use the address in our security.txt. Please give us a chance to fix it before you share details. A real person reads every message.

Questions about data? Ask us.

Bring your security questions.

Create an account