Security & trust

How we handle your clients' conversations.

Who can see your data, where it is kept, what our AI providers receive, and how it is deleted. Every statement here describes how the product works today and was checked against it on 22 October 2026.

Routenna

Our controls, in plain words · checked 22 Oct 2026

Who can see what

  1. Other organizations cannot read your data

    Every table that holds customer data is limited to your organization by row-level security in the database itself, not by the application remembering to filter. A cross-organization test suite tries to read and change another organization's data, and it runs on every code change.
  2. Inside your organization, a meeting can be kept to the person who recorded it

    A meeting you record and do not file under a client is visible only to you. A meeting filed under a client follows that client's sharing: a client is shared with the team unless it is made private, and a single meeting can be made private on its own. The same database rules apply to administrators: an admin cannot read a colleague's private meeting.
  3. Two-factor sign-in

    Anyone can add an authenticator app to their account, and an admin can require it for every member. Anyone can sign out all their other devices from their security settings.

Where your data is kept

  1. Stored with our database provider, served by our hosting provider

    Transcripts, takeaways, recordings and the search index are stored with Supabase. The database and recordings storage are hosted in the us-east-1 region, US East (North Virginia), in the United States. The application is hosted on Vercel. Both are listed with every other provider in the table below.
  2. Recordings sit in private storage

    The recordings store is private. A recording opens only through a link that expires after five minutes, and each link issued to a person is written to your audit trail.
  3. Connected account keys are encrypted

    When you connect a calendar, the key that lets Routenna read it is encrypted with AES-256-GCM before it is stored, using a key held only on our servers. No one signed in to the app can read it back, including your own admins.
  4. Encrypted in transit

    Routenna is served only over HTTPS, and it sends data to your own systems only to HTTPS addresses.

What our AI providers receive

  1. What is sent, and why

    To produce takeaways, summaries, follow-up drafts, agendas and answers, Routenna sends Anthropic the meeting transcript, your notes, earlier takeaways about the same client and what you ask the Advisor. When you prepare for a meeting it also sends the calendar invite's title, description and attendee names, your notes on the client and any email you add to the preparation. Passages of the transcript and the questions you ask are sent to Voyage AI to build the search index. Audio is sent for transcription: to Recall.ai for meetings the notetaker attends, and to AssemblyAI for recordings made in the browser or the iPhone app, or uploaded.
  2. Routenna does not train AI models

    We do not train or fine-tune any model, on your data or anyone else's, and nothing from one organization is used to answer another's questions. Questions about a client are answered only from that client's meetings, which a dedicated test checks.
  3. What providers may do with it is set by their agreements

    Voyage AI's agreement forbids using the data for anything other than providing the service to us. Our agreements with Anthropic and AssemblyAI do not include a separate no-training clause, so we do not make that promise on their behalf. Each provider keeps data under the terms of its agreement with us; we do not claim any of them keeps nothing.

AI takeaways: a person decides

  1. What the AI picks out stays the AI's finding

    Takeaways are stored as the AI's findings, with the meeting they came from; none is written into a client's record. Commitments it is confident about are counted in your follow-ups automatically. Marking one done, received or dismissed is recorded under the name of the person who did it and can be undone from the Activity page.
  2. Every takeaway carries its evidence

    Each one records the moment in the meeting it came from, a confidence score, and whether it is a fact, an inference or a recommendation. The database refuses a takeaway without them. Takeaways below the confidence threshold are dropped rather than shown.
  3. AI output is checked before it is stored

    Everything the model returns is validated against a strict format. Output that fails is rejected, retried once, and then set aside rather than partly saved.
  4. Changes you ask an assistant to make are yours, and reversible

    If you connect an AI assistant to your account and ask it to make a change, the change is made, recorded under your name, and can be undone from the Activity page.
  5. The advisors point to what to check, not what the law says

    The advisors that comment on a meeting are instructed to name what is worth checking and who to check it with, and never to state what the law requires. Treat their output as a prompt for your own professional judgement.

Retention and deletion

  1. Audio is deleted after transcription, unless you choose to keep it

    By default a recording is deleted about 3 days after its transcript and takeaways are ready. While either is still being worked on, or has failed and may be retried, the audio is kept, for at most 30 days after the meeting. An organization can choose instead to keep recordings for a set number of days, up to a year. Deletion removes the file from storage; it is not archived. A change to the setting applies to meetings recorded afterwards, and shortening the number of days also applies to recordings already kept that way.
  2. Transcript-only mode

    An organization can choose to keep transcripts and no audio. Then the notetaker's audio is never copied into Routenna, and the notetaker service deletes its copy once the transcript is in, within 72 hours at most. A recording made in the browser or uploaded is queued for deletion as soon as it is stored and is not kept.
  3. Deleting a meeting removes everything derived from it

    An admin can delete a meeting. That removes its recording, transcript, search index entries and takeaways, including accepted ones. The deletion job then checks storage, the database and the search index again, records what it found, and fails visibly rather than reporting success if anything is left.
  4. Export and close your account yourself

    Any member can download the data their own account holds. An admin can export the whole organization (the file is deleted after 7 days) and can delete the organization from settings, which runs through the same deletion job.
  5. What deletion cannot reach

    Copies held by our providers are deleted under the terms of their agreements with us, not instantly. Anything you have already sent elsewhere, such as an email or a CRM record, stays there.

What leaves, and only when you connect it

  1. Nothing goes to your own systems until an admin adds them

    Meeting notifications go to an address on your own systems only after an admin in your organization adds it in settings, and only an admin can add or remove one.
  2. Notifications carry the outline of a meeting, not the transcript

    A notification to your own systems carries the meeting's title, its length, how many takeaways it found and a link. It does not name the client or include transcript lines. The title is free text you choose, so a title naming a client will appear.
  3. Requests to your systems are signed

    Each request carries a signature you can check, tied to a timestamp so it cannot be replayed later. Addresses on private or internal networks are refused, and redirects are not followed.

The audit trail

  1. Sensitive actions are recorded

    Opening a recording, viewing a transcript, saving AI takeaways, marking a follow-up done, received or dismissed (and undoing that), deletions, invitations, two-factor sign-in changes and policy changes each write an entry. A check on every code change fails if a listed action loses its entry.
  2. Entries cannot be changed from the app

    Signed-in users can read and add entries but cannot edit or delete them.
  3. Admins can answer “who opened this?”

    Admins can read the trail in settings and export it as a spreadsheet. The export itself is recorded.

09

Our providers

Every company that processes customer data for us. Agreement details are on the subprocessor register.

Providers that process customer data for Routenna
ProviderWhat it does for us
Supabase Pte. LtdDatabase, authentication and storage
Hyperdoc Inc. (Recall.ai)Meeting capture and transcription (the notetaker bot)
AssemblyAI Inc.Transcription of uploaded files and browser recordings
AnthropicAI extraction and analysis of transcripts
Voyage AI Innovations Inc.Embeddings for transcript chunks and Ask queries
Vercel Inc.Application hosting
Plus Five Five, Inc. (Resend)Transactional email
Stripe, LLCSubscription billing and credit purchases on the website

Certifications

Routenna does not hold a third-party certification, and has no SOC 2 report of its own. If certification matters for your review, ask us and we will answer plainly.

Found a vulnerability?

Please tell us directly. How to reach us is published at /.well-known/security.txt: use our contact form and put “security” in the message. Please give us a reasonable time to fix what you find before publishing it.