What we hold, and what we will not do with it.
This product reads conversations you had with your clients. That is about as sensitive as business software gets, so this page is specific rather than reassuring.
last updated [EFFECTIVE DATE — not yet published] · [LEGAL ENTITY NAME — business not yet formed]
The short version
- Nothing is sent to anyone on your behalf. Approving a follow-up puts it in your own Gmail drafts, unsent. This is enforced in code, not in a setting.
- Nothing of ours joins your calls. There is no meeting bot and no recording. You bring the transcript afterwards.
- Your transcripts are sent to a language model so it can extract commitments and write drafts. That is the core of the product and there is no way to use it without that happening.
- We do not sell your data, and we do not use your transcripts to train models.
- Another organisation cannot read your rows. That is enforced by the database, not by application code.
What is stored
Grouped by how it got here, because that decides who is responsible for it.
Your account
Your name and email address, and the name and timezone of your organisation. Google sign-in asks for identity scopes only; if you sign in by emailed link instead, we hold the address you typed. No password exists anywhere in this system — there is no password field to store.
What you paste in
The transcripts and notes you bring, exactly as you submit them, together with everything derived from them: the commitments extracted, the sentence each one came from, the follow-up drafts, tasks, and their completion records. A transcript is whatever you paste — if your conversation touched on health, money, or anything else sensitive, that text is stored as-is.
The people you work with
Names and email addresses of clients and prospects, the enquiries prospects send you, and the record of what was promised to whom. You enter this, and it describes people who are not our customers — which is why the section below on responsibility matters.
How your business runs
Retainers and their usage, scope-of-work records, time entries, billing rates and invoices, scheduled sessions and no-show policy, document requirements, and review requests. This is the material the operations view reasons over.
Google access, if you grant it
Drive, Calendar, and Gmail are each granted separately, from Settings, one capability at a time — never bundled into sign-in. If you connect one, we store a refresh token for it and references to the specific files you pick. We do not copy your Drive.
The record of what happened
Every action the agent takes is written to an append-only audit log: who or what acted, what kind of action it was, and what it touched. This is the thing that lets you answer 'what was it allowed to do on the day it did that?' — so it is deliberately hard to erase.
Who is responsible for your clients' data
Your clients are your clients. When you paste a transcript, you decide what goes in, what it is used for, and how long you keep it. In data-protection terms you are the controller and we are your processor: we handle that material on your instructions and for no purpose of our own.
That has a practical consequence worth stating plainly. The people in your transcripts did not sign up here and mostly do not know this product exists. Telling them how you handle their information, and having a lawful basis for putting it in here, is your responsibility, not ours. If one of them asks you to delete what you hold about them, we will help you do it.
Who else processes it
Everyone outside this codebase that your data reaches, and why.
Supabase
Database and authenticationStores everything above. Your rows are isolated from other organisations' rows by row-level security in the database itself, not by application code that could forget to check.
Vercel
HostingRuns the application and serves every page. Sees request metadata — IP address, timing — as any web host does.
Vercel AI Gateway
The model callTranscript text is sent through the gateway to the model that extracts commitments and writes drafts. The model in use is gpt-oss-120b, an open-weights model, not a personal assistant account tied to you.
Identity for sign-in. If you connect Gmail, approved drafts are written into your own drafts folder. If you connect Drive or Calendar, we read what you point us at.
What it cannot do
Claims worth checking. Each is enforced in a named file, not in a policy document.
The assistant cannot send an email to anyone. No Google scope permits creating a draft without also permitting send, so the guarantee is not bought with scopes — it is built. The Gmail module exposes exactly two endpoints, and a test fails the build if the word “send” appears anywhere in it.
Beyond sending, these are refused outright, even if you approve them: change what was agreed, change a price, sign anything, take a payment, delete a record. They sit in the contract's prohibited list, which no setting can override.
Every table carries an organisation id and a row-level security policy that ties reads and writes to the organisations you belong to. A request for another org's row returns nothing, because the database refuses it rather than because a function remembered to filter.
Google refresh tokens are sealed with envelope encryption and stored in a table the ordinary logged-in database role cannot read at all. Each ciphertext is bound to the row it belongs to, so a token copied to another row fails to decrypt rather than working somewhere it should not.
Transcript text is wrapped as data, never as instructions, and passages that look like an attempt to give the model orders are flagged on the transcript and surfaced to you. A transcript is something someone else wrote; it is not treated as trusted input.
Keeping it, and getting rid of it
Your data stays while your account is open. You can delete individual transcripts, commitments, and drafts from the product as you go.
When an account closes, its data is removed within [RETENTION WINDOW — no automated deletion job exists yet]. The audit log is the exception: it is append-only by design, because a record that can be quietly rewritten is not a record. Disconnecting a Google capability in Settings revokes and deletes the stored token for it immediately.
Depending on where you live you may have statutory rights to a copy of your data, to correct it, or to have it erased — [JURISDICTION — to be set once the business is formed] governs which apply. Write to joinconductflow@gmail.com and we will action it.
Something here look wrong?
This page describes a system that changes. If you find a claim on it that the product does not honour, that is a bug worth hearing about — write to joinconductflow@gmail.com.