01What we collect
When you upload a recording or paste a transcript, we process the audio or text to extract action items, owners, and deadlines. We store the actions you review and the calendar events you approve. Raw recordings are deleted after processing finishes.
02How long we keep it
Your recording is deleted after processing finishes, whether it succeeded or failed. If processing is interrupted before it reaches either outcome, the recording is cleared by the cleanup that runs when the service next starts. The transcript, the actions extracted from it and the approvals you make are kept in your workspace so they are still there when you come back — they are not cleared at the end of a session. To have them removed, email hello@cadenva.com. We will confirm and complete deletion from the live Cadenva service within 48 hours. Copies of your data may remain in our off-site backups after that point; backups are taken as whole snapshots and cannot have individual records removed from them, so they are instead expired automatically 30 days after they are created.
03We do not train on your data
Your meeting content is never used to train any AI model — ours or anyone else's. We do not sell or license your data and we do not use it for advertising. The only parties that receive it are the service providers listed below, and only so they can run Cadenva.
04Third-party processors
We use the following services to operate Cadenva. Each receives only what it needs to do its job — none receive your meeting data beyond what is necessary for processing.
OpenAI
Transcribes the recordings and notes you submit and extracts action items from them. Processes data under a DPA that prohibits training on API-submitted content. Cadenva does not use Google Calendar event data to train or improve artificial intelligence models.
Reads your upcoming events so we can show what is coming next, and creates the events you approve. If you separately enable Google Meet transcript access, also supplies the transcript Google Meet has already produced for a meeting you chose to capture. See “Google Workspace API data” below.
Microsoft
If you connect Microsoft Calendar, reads your upcoming events so we can show what is coming next, and creates the events you approve. We store your Microsoft credentials, the connected account's email and name, and the identifier of each event Cadenva created so it can update or remove it later.
Railway
Runs the Cadenva backend and hosts its database, so it holds everything we store — including encrypted Google credentials and the calendar identifiers we keep.
Backblaze B2
Stores off-site backups of everything Railway holds. A backup set contains the database — including the same encrypted credentials and identifiers — your meeting transcripts, and any raw recordings still present when the backup was taken. Backup sets expire automatically 30 days after they are created.
Vercel
Hosts the web application and serves web traffic. Does not process meeting content.
Sentry
Receives error diagnostics when something fails. Reports carry error types and request identifiers, not credentials or meeting content.
Stripe
Handles payments and subscriptions. Your card details are entered on Stripe's own checkout and never reach Cadenva. We store the Stripe customer and subscription identifiers for your workspace and the subscription's status, because that status is what decides which plan the workspace is on. Stripe receives no meeting content, recordings, action data, or Google data.
Resend
Delivers the emails Cadenva sends you — account verification, password resets, follow-up reminders and the morning digest. Receives your email address and the contents of those messages, which can include commitment text and dates. It receives no recordings and no transcripts.
05Where your data is processed
The service providers listed above are established outside the European Economic Area, principally in the United States, so running Cadenva involves transferring your data outside the EEA. Each one receives only what the list above says it receives.
If you use Cadenva as a business and we process personal data on your behalf, our Data Processing Agreement sets out what we commit to for those transfers, and we will tell you on request which transfer mechanism applies to a given provider.
06Google Workspace API data
What we access
If you connect Google Calendar, Cadenva asks for access to your calendar events and for your Google account email and basic profile. The calendar permission covers both reading and writing events — it is a single permission Google does not split. It does not ask for any Google Meet permission at that point. Read-only access to your Google Meet conference records and transcripts is a separate, optional permission: Cadenva requests it only when you enable Google Meet transcript import in Cadenva, and Google adds it to the same sign-in. You can decline it, or never enable it, and keep using Google Calendar. Cadenva records which permissions Google reports as granted and reads nothing from Google Meet unless that permission is among them.
Why we use it
We read your upcoming events so the app can show what meeting is next and let you start a capture from it. We create, update and delete calendar events only for actions you have explicitly approved. We use your email and profile to show which Google account is connected. If you have enabled Google Meet transcript access and a meeting is set to be captured, we read the transcript Google Meet has already produced for that meeting so its action items can be extracted. Cadenva does not start transcription or recording in Google Meet and cannot: Google Meet's own transcription is turned on in Google Meet, not by Cadenva, and if no Google Meet transcript exists nothing is imported. Cadenva does not change any Google Meet setting — its Meet permission is read-only, so it cannot turn transcription or recording on or off, or alter how a meeting is configured. We do not use Google data for advertising, and we do not sell or license it.
What we store
We store your Google credentials, the email and name of the connected account, and the event identifier and link for events Cadenva created so it can update or remove them later. If you start a capture from a meeting, we store that meeting's title and event identifier alongside it. We also store which Google permissions you granted. When a Google Meet transcript exists for a meeting Cadenva is set to capture, and you have enabled Google Meet transcript access, we store that transcript in your workspace — its text, its timestamps and the participant names Google Meet attached to each line — together with the meeting's title, in the same way we store a transcript you paste. We do not store Google Meet's internal identifiers for the call, and we do not read Google Drive or Google Docs. We do not keep a copy of your calendar: events we read to show your next meeting are fetched when you open the app and are not written to our database.
How it is protected
Google credentials are encrypted by the application before they are written to the database, and the service refuses to start in production without its encryption key configured. All traffic runs over HTTPS. Google data is reachable only through the workspace it belongs to: every request is checked against the workspace the caller is authenticated for, so one workspace cannot read or write another's calendar data. Credentials are held in server-side configuration rather than in our source code, and our logs and error reports record error types and identifiers rather than tokens, calendar contents or account emails.
Who else receives it
Google data is not sold, and it is not shared for advertising. It is disclosed only to the service providers listed above that run Cadenva — Railway, which hosts the backend and database, and Backblaze B2, which stores encrypted off-site backups of everything Railway holds — and to Sentry if an error report is generated. Google data is never sent to Microsoft, and Microsoft calendar data is never sent to Google: each connection is read and written only through its own provider. Cadenva does not use Google Calendar event data to train or improve artificial intelligence models. We may also disclose data where we are legally required to.
Your control
You can disconnect Google from within Cadenva, which deletes the stored credentials — the calendar connection and any Google Meet permission on it, since they are one sign-in — but does not revoke the permission on Google's side; you can revoke access at any time in your Google Account settings. Google Meet transcript access is not a separate token, so it cannot be withdrawn on its own from within Cadenva: removing Cadenva's access in your Google Account withdraws it, and also disconnects Google Calendar until you reconnect. Cadenva reads a Google Meet transcript only for a meeting set to be captured, so the Meeting capture setting and each meeting's Capture or Skip decision control which meetings are read while the permission stands. Events Cadenva already created stay in your calendar and are yours to keep or delete. To have the remaining records we hold removed, email hello@cadenva.com.
Limited Use
The use and transfer of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
07Shared workspaces
Your data lives in a workspace, and a workspace can be shared. If several people sign in to the same one — which is how a team uses Cadenva — all of them see the same meetings, the same transcripts, the same commitments and the same source evidence, and any of them can review, correct, approve and schedule any of it. There are no permission levels inside a workspace: being a member is the permission. Decide who to add on that basis.
A connected calendar belongs to the workspace rather than to the person who connected it. A workspace has at most one Google connection and at most one Microsoft connection, so every event anyone in the workspace approves is written to that one connected account.
Different workspaces are separated. Every request is checked against the workspace the signed-in session belongs to, so one workspace cannot read or write another's data. Joining an existing workspace requires that workspace's own join code, which is never valid for another. Members are added and removed by writing to hello@cadenva.com; a removal ends that person's access immediately and signs them out everywhere, and it does not delete the work they already did.
When a workspace is deleted, it is deleted for everyone in it. The accounts themselves are not deleted, because a person may belong to another workspace; ask us if you want an account removed too.
08Cookies and browser storage
Cadenva sets no cookies. Our public pages and the app store a small amount of data in your browser's own storage, and all of it is there to make the product work rather than to observe you:
Signing in
cadenva.session holds the signed session token that keeps you logged in, and the temporary workspace a visitor is given before they create an account. Without it you would be signed out on every page load. If your browser blocks durable storage, the same value is kept for the tab only.
Your preferences
cadenva.theme remembers light or dark, cadenva.locale remembers the language you chose, and cadenva.account_seen records only that this device has signed in before, so the form offers to sign you in rather than to create a second account.
Work in progress
Notes you are typing and captures that are running are kept on the device so a refresh or a closed tab does not lose them — cadenva.capture_sessions_v1 and its per-capture drafts, cadenva.live_session_active_v1, cadenva.active_upload, and the notes you paste on the homepage before signing in, which are handed to the app once and then removed.
Not repeating itself
cadenva_processed_meetings_v1 remembers which meetings this device already sent, so the same recording is not processed twice, and cadenva_remind_after_meeting records when a reminder was last offered so it is not offered again straight away.
The public demo
cadenva-demo-theme and cadenva-demo-watch-t remember how you left the sample walkthrough on /demo. The demo uses sample data and no account.
We run no analytics, no advertising and no third-party tracking on this site, so there is nothing here that would require a consent banner and we do not show one. Everything above stays on your device — it is not sent to us as a profile and is not shared with anyone. Clearing your browser's site data removes all of it; the effect is that you are signed out and your preferences return to their defaults. If we ever add analytics, we will change this section before we turn it on, and ask for consent where consent is required.
09Your rights
You can request deletion of all your data at any time by emailing hello@cadenva.com. We will confirm and complete deletion from the live Cadenva service within 48 hours. Off-site backups taken before that request still hold earlier copies; they expire automatically within 30 days. You may also ask what data we hold, request a copy, or ask us to correct anything inaccurate.
10Contact
Questions? Email hello@cadenva.com. We respond within one business day.