An honest account of how your data is handled — this page will grow as the product does.
Your data — meeting transcripts, summaries, action items, and account information — is stored in Supabase (PostgreSQL), a managed database provider. All connections to the database and between FollowUp's services are encrypted in transit (HTTPS/TLS).
Access tokens for Google Calendar, Gmail, and Notion are stored encrypted at rest. They're used only for the specific actions you've explicitly connected — reading calendar events to detect meetings, and sending follow-up emails you've reviewed and approved — never for anything else.
Meeting transcripts are sent to Anthropic's Claude API to generate summaries and action items. Anthropic does not use this data to train its models. FollowUp does not share transcript content with any other AI provider.
Your data is only accessible to your own account, or — if you're on a Team plan — to other members of your specific team. Row-level access controls in the database enforce this at the data layer, not just in the application code.
FollowUp is an early-stage, actively developed product. It does not currently hold formal certifications like SOC 2 — that's a realistic goal for later, once the product and company are further along, not something claimed prematurely. If security compliance is a hard requirement for your use case right now, this is worth knowing upfront.
If you find a security issue, please reach out directly rather than disclosing it publicly — it'll be looked at and addressed as quickly as possible.