Security and trust
Where your meetings go, and who touches them
ForgeNotes records on the device in front of you and processes meetings on a server we operate. This page lists every company that handles ForgeNotes data, what each one receives, and what is still in progress. Updated 5 November 2026.
Data flow
From your device to your notes
- You press record on your device. Nothing joins the call. The recording uploads over an encrypted connection to file storage in Supabase, in the United States, and a job is queued.
- Our processing server, which TheContentForge operates, picks up the job, fetches the audio over an encrypted connection, transcribes it and writes the notes with an AI model that runs on that server. No outside AI service receives it unless you connect one yourself (step 5).
- The transcript and notes are written back to the database. The working copy of the audio on the processing server is removed when processing finishes.
- Your apps read your notes from the database. Only people you share a meeting with can read it.
- Content leaves ForgeNotes only for a destination you turn on yourself: Slack, a webhook, Notion, HubSpot, Asana, Linear, Jira, an AI agent you connect, a recap email or a share link.
- A daily job deletes audio and text when each meeting reaches its expiry date. You can delete any meeting, or your whole account, sooner.
Subprocessors
Companies that process ForgeNotes data
None of them is an AI service working on your meetings. We will update this list before adding a company that receives meeting content.
| Service | What it does | What it receives | Where |
|---|---|---|---|
| Supabase | Database, sign-in, file storage and the server functions the apps call | Your account, recordings, transcripts, notes and everything else ForgeNotes stores | United States (AWS us-east-2, Ohio) |
| Netlify | Hosts the website and web app, and forwards the AI agent (MCP) address to Supabase | Web requests, including the pages and app files your browser loads | Global network |
| TheContentForge processing server | Transcription and the AI that writes notes, answers questions and writes coaching notes | A meeting's audio and text while it is being processed | A server TheContentForge operates. Not a third party |
| Resend | Sends recap emails, team invitations and account emails such as trial reminders | The recipient's address and the message. A recap is the summary, decisions and action items, never the transcript | United States |
| Apple | App Store billing | Whether your subscription is active. We never see your card | Apple |
| Google Play | Billing for the Android app, which is coming soon to Google Play | Whether your subscription is active. We never see your card | |
| PostHog | Optional product analytics, only after you accept analytics in the cookie prompt | Generalized page visits, feature actions and technical errors. Never audio, transcripts, notes, questions, names or email addresses | United States (us.i.posthog.com) |
| Google Analytics | Website analytics, only after you accept analytics in the cookie prompt | Page visits on the website | |
| Cloudflare and Google public DNS | Checks a domain a team admin asks to verify | Only the domain name | Global network |
Your choice
Sent only where you send it
These receive content only after you, or your team admin, connect them. Each can be disconnected in Settings. What was already sent stays in that service until you delete it there.
| Destination | What it receives |
|---|---|
| Slack | Each meeting's summary, decisions and action items, posted to the channel you picked. Never the transcript |
| Webhooks (Zapier, Make or your own server) | The same summary, decisions and action items, signed. Never the transcript |
| Notion | A meeting's notes, when you export it. Never the full transcript |
| HubSpot | The summary, decisions and action items as a note on the matching contacts, company and deal, with a task per action item |
| Asana, Linear and Jira | Each action item as a task or issue, with a link back to the meeting. Never the transcript or the summary |
| AI agents you connect (MCP), such as Claude or ChatGPT | What you let that connection read, which can include transcripts. Each agent gets its own connection, and you can revoke it |
| Recap email recipients | One meeting's summary, decisions and action items, sent to the people you list. Never the transcript or the audio |
| Share links | The one meeting or clip you share, for anyone with the link, until you revoke it |
Practices
What is in place, and what is not yet
- Encryption in transitIn place
- Every network connection ForgeNotes makes, between the apps, the website, Supabase and the processing server, uses TLS.
- Encryption at restPartly verified
- Stored data lives in Supabase, which states that it encrypts customer data at rest. On the processing server, a recording is held only while it is processed and removed when processing finishes. Disk encryption on that server is being verified and will be stated here once confirmed.
- BackupsPartly in place
- The database is backed up daily by Supabase. Stored audio and video files are not backed up separately yet; that work is in progress, and this page will say when it is done.
- RetentionIn place
- Audio and text are deleted on a stated schedule by a daily job. Each meeting carries its own expiry dates, set from the plan it was recorded on. You can delete any meeting sooner.
- No trainingIn place
- Your recordings, transcripts and notes do not train AI models, ours or anyone else's. A data processing agreement that puts this in the contract is in progress.
- Access and auditIn place
- Access to production systems is restricted and audited. Team plans have an audit log of every team change that admins can read and export, and that cannot be edited.
- Single sign-onComing
- Single sign-on through Okta or Microsoft Entra ID is built and switched off while its account checks are reviewed. This page will say when it is available.
- Penetration testPlanned
- An external penetration test is planned and has not happened yet. When it is done, its summary (the firm, dates, scope and findings by severity) will be published here.
- Incident responseIn progress
- A written incident-response and breach-notification commitment is being drafted. Until it is published: if a security incident affects your data, we will tell you without undue delay and as the law requires.
- Reporting a vulnerabilityIn place
- Email support@thecontentforge.io with "Security" in the subject. We read every report and reply to the address it came from. Please give us a chance to fix an issue before you publish it. Our security.txt is at /.well-known/security.txt.
Retention by plan: Audio is kept for 1 year (2 years on Pro Plus and above). Transcripts and notes are kept for 2 years (4 years on Pro Plus and above). The full detail is in the privacy policy.