Corteza
Privacy Policy
Last updated: October 12, 2026
Corteza (“Corteza”, “we”, “us”) is a decision log for teams that use Google Workspace. It reads the transcripts and Gemini notes of your Google Meet meetings and keeps the outcomes in them: decisions, action items, open questions and risks. This policy explains what data Corteza uses, why, who it shares it with, and the choices you have. Corteza is operated by Cristian Tumani. Contact: cristian@corteza.app.
In short: we read your meetings to find their outcomes, and we keep only those outcomes, never the transcripts. Meeting content is encrypted with a key for your workspace. Colleagues never see each other’s personal data. We don’t sell data, show ads or use your Google data to train AI models.
1. Data we collect
Your account
When you sign in with Google we receive your name, email address, profile picture and your Google Workspace domain (the hd claim), which decides which Corteza workspace you belong to. We also keep your settings: language, time zone, email preferences and the “morning partner” you pick.
Data from Google, only after you connect it
Signing in gives Corteza no access to your meetings. In Settings → Google Meet you can choose to connect Google, and Google asks for your consent to each permission below. You can disconnect at any time.
| Permission (scope) | What Corteza does with it |
|---|---|
meetings.space.readonly | Lists the Google Meet meetings you attended (conference records) and their participants, transcripts and Gemini notes, so new meetings are read automatically and past ones can be imported when you ask. |
drive.meet.readonly | Reads the transcript and notes files that Google Meet saves in your Google Drive. |
drive.readonly | Reads the Gemini “Take notes for me” document of a meeting when Google stores it in a way the permission above doesn’t cover. Corteza opens only the notes documents Google Meet links to a meeting; it doesn’t browse, list or read other files in your Drive. |
calendar.events.readonly (optional) | Reads today’s events in your calendar to prepare your morning summary and the “Prepare your day” section on Home: each meeting with what is still open from its earlier sessions. Calendar events are read when the summary or Home is prepared, kept only in the server’s memory for up to 10 minutes, and never saved. |
drive.file (optional) | Lets you pick specific documents in Google Drive (through Google’s file picker) to give the AI context about your company or your role. Corteza can open only the files you pick. |
What we keep from a meeting
- Outcomes: the text of each decision, action item, open question and risk; its owner and due date; the reasoning and a short quote from the meeting as evidence; the meeting’s title and date; and the topic it belongs to.
- Not the transcript. Transcripts and notes are read, sent to our AI provider to find the outcomes, and then discarded. We keep only a fingerprint (hash) of the transcript, so the same meeting isn’t processed twice, plus its file name and counts.
Content you add
Outcomes you write or edit, transcripts you upload (read and discarded the same way), the context you give the AI (company description, glossary, role, documents you pick), your search questions, and the feedback you give on outcomes (confirm, dismiss and why).
Usage and technical data
Server logs and product analytics with counts, types and identifiers (for example “3 action items captured”, “search used”). Logs and analytics never include meeting content, transcripts, outcome text or search questions. A session cookie keeps you signed in (up to 7 days); we use no advertising cookies.
2. How we use data
- To provide Corteza: find the outcomes of your meetings, show them to you, answer your searches, prepare your morning summary and weekly digest, link outcomes across meetings, propose which open items a decision you type settles, and remind owners of their action items.
- To improve results in your own workspace: outcomes you confirm or dismiss become examples for future meetings of your workspace only.
- To run the service: security, preventing abuse, AI usage limits, fixing errors and understanding which features are used (with no meeting content).
- To contact you about your account and the service.
We don’t sell personal data, use it for advertising, or build profiles for anyone else.
3. Google API Services: Limited Use
Corteza’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- We use Google user data only to provide and improve the user-facing features described above.
- We transfer it to others only as needed to provide those features (the AI and infrastructure providers listed below), for security, to comply with the law, or as part of a merger or acquisition with notice to you.
- We don’t use it for advertising, and we don’t sell it.
- People don’t read it, unless you ask us to (for example for support) and give us permission, it’s needed for security or abuse investigations, or the law requires it.
- We don’t use Google user data to develop, improve or train generalized AI or machine-learning models. Our AI providers process it under terms that don’t allow them to train their models on it.
4. Who can see your data
- Your workspace: outcomes live in spaces. Your own captures go to your personal space, which only you can see; colleagues, including workspace admins, can’t open it. An action item assigned to a colleague is shown to that colleague.
- Sensitive topics (dismissals, people leaving, performance, pay, health, legal matters about a person) are detected automatically or marked by you, and stay visible only to you, even when they name colleagues or assign them work.
- Service providers that process data for us, under contracts that limit what they can do with it:
| Provider | What for | Data |
|---|---|---|
| Anthropic | AI that finds outcomes in meetings and writes search answers | Transcript and notes text, outcomes, AI context, search questions and decisions you type |
| OpenAI | Embeddings for semantic search | Outcome text and search questions |
| MongoDB (Atlas) | Database | Everything Corteza stores (meeting content encrypted) |
| Railway | Application hosting | Data in transit through the app, server logs |
| Resend | Sending email | Your email address and the content of the emails we send you |
| PostHog | Product analytics | Identifiers, counts and feature usage; no meeting content |
| Sentry (EU) | Error monitoring | Error type and stack trace, with internal workspace and user ids; no meeting content, email addresses or request data |
| GitHub | Storing our nightly backups | An encrypted copy of the database that only Corteza can decrypt |
| Sign-in and the integrations you connect | As described in section 1 |
If you connect Slack or Jira, the data you send through them is shared with those services as you choose. We may disclose data if the law requires it, to protect the rights and safety of people or the service, or to a successor in a merger or acquisition, which would remain bound by this policy.
5. Security
- All traffic is encrypted in transit (HTTPS).
- Meeting content (outcome text, reasoning, quotes, meeting titles, AI context and documents) is encrypted in the database with a key unique to your workspace. Google access tokens are encrypted too.
- Access is checked on every request, and data is always filtered to what you are allowed to see.
6. Retention and deletion
- Outcomes are kept while your workspace uses Corteza, so the log stays useful. You can delete outcomes and action items at any time.
- Transcripts and calendar events are not saved (see section 1).
- An encrypted backup of the database is made every night and kept for 30 days, so we can recover from a failure. Deleted data leaves the backups within those 30 days.
- Disconnecting Google (Settings → Google Meet) revokes Corteza’s access with Google and deletes the stored tokens. You can also remove access from your Google Account.
- To delete your account or your workspace’s data, write to cristian@corteza.app. We delete it within 30 days. When a whole workspace is deleted, its encryption key is destroyed, which makes any remaining copy, including in backups, unreadable.
7. Your rights
Depending on where you live (for example under the GDPR or your country’s data protection law), you may have the right to access, correct, delete, or receive a copy of your personal data, and to object to or restrict its processing. Write to cristian@corteza.app and we’ll answer within 30 days. If your organization manages your Corteza workspace, we may refer your request to them. You can also complain to your data protection authority.
8. International transfers
Our providers may process data outside your country, including in the United States. We rely on their contractual safeguards, such as standard contractual clauses where they apply.
9. Children
Corteza is a work tool and isn’t meant for anyone under 16.
10. Changes
If we change this policy we’ll update the date above, and for important changes we’ll tell you by email or in the app before they apply.
11. Contact
Cristian Tumani, Corteza: cristian@corteza.app