Skip to content

Draft — not yet reviewed by a lawyer. This is a plain-English working draft and may change before launch.

LEGAL · RECAPPLY

Sub-processors

Last updated

The services that help us run Recapply: what each one does, what it sees, and where it is.

The short version

  • These are the companies that process personal data for us to run Recapply.
  • Your users' spreadsheets never go to any of them: they're read in your browser.
  • We'll update this page before we add a new one that handles your users' data.

The full version below is what counts if anything here seems to disagree with it.

01In use today

  • Vercel

    Purpose
    Hosts the website, the dashboard, and the API, and runs our daily clean-up jobs.
    Data
    Every web request, including IP address, browser type, and the page or share link asked for. Short-term logs.
    Location
    United States, served from a global network
  • Clerk

    Purpose
    Sign-in, user accounts, company and team accounts.
    Data
    Names, work emails, login details, company name, team members, brand settings, plan, and API key fingerprints (hashes).
    Location
    United States
  • Supabase

    Purpose
    Our database.
    Data
    Contact requests, link records (random id, company, campaign, time and the first name you put on the link; never numbers or emails), saved connections for automatic recaps (scrambled, only if an admin switches them on), link and campaign counts, off switches, plan usage, and the activity log (with hashed IPs).
    Location
    [REGION: confirm in the Supabase project settings]
  • Resend

    Purpose
    Emails contact requests and sign-up alerts to our team, ready or failed notices for automatic recaps to your company's admins, and, only when a company admin taps Send (off unless we switch it on), a personal recap email to each person in a recap.
    Data
    What you type into the contact form; admin work email addresses, company name and recap counts for automatic recaps. For recap emails an admin sends: the person's email address, first name and own recap link, passed on for that one send and not stored by us. Otherwise no end-user names or numbers. We never email your users except when your admin taps Send.
    Location
    United States
  • Google Fonts

    Purpose
    Lettering for recap images when someone saves one.
    Data
    Our server's request for a font. No personal data about your users.
    Location
    United States, served from a global network

02Set up, but not live

  • Vercel AI Gateway, and the AI model provider it routes to

    Off unless a company switches it on

    Purpose
    Writes the optional AI personal line under a person's name, and answers the Data page assistant if we switch that on.
    Data
    Only if a company switches on AI lines: the person's first name, their top two or three recap numbers with plain labels, and the company's name, description, cover headline, sign-off, recap type and language. For the assistant: what you type and the data you ask it about. No emails or phone numbers. We don't store the request or the answer.
    Location
    Per Vercel and the model provider
  • Cash App, Square, Stripe, Paddle or Lemon Squeezy

    Set up, but not live

    Purpose
    Checkout, subscriptions, and invoices, once paid plans launch, through whichever of them we choose. With Cash App you pay our Cash App account yourself and we confirm the payment by hand.
    Data
    The paying admin's billing details and card (handled by the provider), plus your company id so we know which plan you're on. With Cash App the payment stays in Cash App; we keep only the plan, the amount and a short note code.
    Location
    United States
  • Vercel AI Gateway (and the AI model provider it routes to)

    Switched off. We'll update this page before turning it on.

    Purpose
    The optional setup assistant.
    Data
    What you type into the assistant and the data you ask it about.
    Location
    United States

03Services you or your users choose

Some services aren't our sub-processors, because you or your users pick them and use their own accounts. When they're used, our server talks to them directly and keeps nothing:

  • Tools you connect to import your users (like Google Sheets, Stripe, HubSpot, or your own database). We use the key you give us once, then throw it away.
  • Apps your users connect from a campaign link (like GitHub, GitLab, Strava, Oura, WHOOP, Withings, Spotify, Last.fm, Steam, or Trakt). Each person signs in to their own app; we read their year once and cancel our access where the app allows it.

Their own terms and privacy policies apply. Product names belong to their owners; no endorsement is implied.

04Changes and objections

We change the date at the top when this list changes. Customers with a signed Data Processing Addendum get notice before a new sub-processor starts handling their users' data, and can object through our contact form, as the DPA describes. See also our Privacy Policy and Security page.