Who is responsible for your data
Calliops is published by Max Barbet, sole trader operating under the trade name 201dustries, 10 rue des Lilas, 69008 Lyon, France, SIREN 885 291 799. For any question about this page or about your data, write to [email protected]. No data protection officer has been appointed at this stage.
We act in two capacities. For this site, the waitlist, your account and billing, we are the controller: we decide. For the content of your meetings — calendar, attendees, transcripts and what we extract from them — we are a processor within the meaning of Article 28 of the GDPR: your organisation, our customer, decides, and we act only on its instructions. A data processing agreement is available on request at the same address.
If you took part in a meeting analysed by Calliops without being a user yourself, the organisation that held the meeting decided on that processing. Address your requests to it first; if you do not know who it is, write to us and we will point you to it.
What we collect when you create an account
If you sign in with Google, we ask only for the identity scopes openid, email and profile, and we read five things from Google’s answer: your Google identifier, your email address, whether it is verified, your name and the address of your profile picture. No access token is kept for this sign-in: it exists to recognise you, not to read your account. It is separate from connecting your calendar, described below, and revoking one does not revoke the other.
If you create an account with a password, we keep your email, your name and a hash of the password. In both cases we log sign-ins — timestamp, success or failure — so that an account under attack can be locked.
Which Google data we ask for, and why
When a member connects their Google Workspace account in Settings, Calliops asks for the permissions below, all read-only. The connection is personal: each member grants their own, and a calendar rule only ever reads meetings the person who wrote it attended. We ask for neither Gmail, nor your contacts, nor any write permission on your Google account.
The Drive scope is requested only on deployments where the customer’s Workspace administrator has blocked access to Meet transcripts; it is then used to read the transcript document Google attaches to the event, and nothing else in your Drive.
| Google permission | What we read | Why |
|---|
| calendar.readonly | The list of your calendars and the event colour palette | Let you choose which calendars Calliops follows, and map an event colour to a meeting tag |
| calendar.events.readonly | For events your rules select: title, description, dates, attendees (name and email), organiser, Meet conference id, Drive attachments | Find the meetings to process each night and know who was there |
| meetings.space.readonly | Meet conference records: the speaker-attributed transcript and the participant list | Feed the product-knowledge extraction |
| userinfo.email | The address of the connected account | Show which account is connected in Settings, and nothing more |
| drive.readonly (optional) | The text content of transcript documents attached to the event | Fallback when Meet cannot provide the transcript |
GOOGLE_BASE_SCOPES and GOOGLE_DRIVE_SCOPE in google-auth.service.ts; SSO_SCOPES in google-sso.service.ts.
What we do with that data
Every night, Calliops walks the calendars you chose and creates one record per selected meeting: title, dates, attendees, tag. When a Meet transcript exists, it fetches it and splits it into passages, then submits those passages to a language model that extracts product knowledge from them: decisions, needs, pain points, quotes. Every item keeps the exact quote it came from, verified word for word against the transcript.
Those items land in a review queue. Nothing is written to a third-party tool — Notion, GitHub, GitLab — until someone on your team has approved the item, and only to tools your organisation has itself connected. Rejected items are not resubmitted.
From the attendee lists we derive a directory of the people and organisations you meet: name, email, domain, date last seen. It is used to prepare your next meetings and to attach each meeting to the right client. When external tools query Calliops through its MCP server, the raw transcript is never part of the answer and attendees are reduced to a count.
What we never do with that data
Calliops’ use of information received from Google APIs adheres to the Google API Services User Data Policy, available at https://developers.google.com/terms/api-services-user-data-policy, including its Limited Use requirements. Concretely:
- We use Google data only to provide and improve the user-facing features of the application that you have explicitly requested.
- We do not use it for advertising, targeted or otherwise, and we neither sell nor rent it to anyone, data brokers included.
- We do not transfer it to any third party other than the sub-processors named below, except where the law requires it, or to investigate abuse or a security incident.
- We do not use it to develop, improve or train generalised artificial-intelligence or machine-learning models — neither our own nor our providers’, who are contractually barred from doing so.
- No human at Calliops reads your transcripts, unless you ask us to for support, or a security incident requires it; in both cases the access is logged and time-limited.
- We do not use it to assess or monitor any individual participant, nor for any credit or eligibility decision.
Who else has access to that data
We run Calliops ourselves, with no employee or contractor who has access to the data. The only third parties that see any of it are the technical sub-processors below, each for the function stated and nothing else. Which language-model provider is actually used depends on how your workspace is configured; by default it is Scaleway, in France. None of these providers is allowed to train its models on your content.
Transfers outside the European Union, where they happen, rest on the European Commission’s standard contractual clauses or on the EU–US Data Privacy Framework. We may also disclose data when a legally empowered authority requires it; we then inform the customer concerned unless the law forbids it.
| Sub-processor | Role | Location |
|---|
| Scaleway | Hosting of the application and databases, transactional email, default language model | France (EU) |
| Anthropic, OpenAI, Google (Gemini API) | Language models, only if your workspace is configured to use them | United States |
| Notion, GitHub, GitLab | Receive approved items, only if your organisation connected them | United States / EU depending on the provider |
| Google Analytics | Audience measurement on this site only, with your consent (see below) | United States |
How we protect that data
Google access tokens are encrypted before being stored, with AES-256-GCM and a key that does not live in the database. They are never written to logs. Each Google connection belongs to one member and is never lent to another.
All communications — between your browser and Calliops, and between Calliops and Google — are encrypted in transit with TLS, and the site enforces HTTPS permanently. In the database, each organisation is isolated from the others by row-level security rules enforced by Postgres itself, and the application connects with a role that has no power to bypass them.
Session tokens are stored as hashes, never in clear text. Every connection, disconnection and deletion is written to an audit log. Data is hosted at Scaleway, in the European Union. In the event of a data breach affecting a customer, we notify them without undue delay, with what they need to meet their own notification duty.
Cipher: apps/api/src/common/crypto. Isolation: FORCE ROW LEVEL SECURITY, application role NOBYPASSRLS.
How long we keep it, and how to delete it
Nothing is kept beyond what the service needs, and you can delete everything yourself or on request. The list says how to act; the table that follows gives the rule per kind of data.
- Disconnect Google: in Settings → Integrations, the “Disconnect” button immediately revokes our access at Google, destroys the stored tokens and disables your calendar rules. An administrator can do the same for a member who has left the team.
- Revoke from Google: at https://myaccount.google.com/permissions, remove Calliops from the list of third-party apps. Our access stops at once, even if you never come back to our settings.
- Delete a meeting: from the meeting page, deletion takes the transcript, the extractions and the items that exist only because of it. The operation asks you to retype the meeting title and is written to the audit log.
- Delete your account or your organisation: write to [email protected]. We delete or anonymise everything about you within thirty days and confirm it to you.
| Data | Kept | Deleted |
|---|
| Google access tokens | While the connection is active | On disconnect: revoked at Google and destroyed on our side |
| Meeting records, attendees, transcripts and extracted items | For the duration of the contract | Thirty days after the contract ends, during which you can export everything; sooner if you delete the meeting or ask us to |
| Account, identity, sign-in logs | For the duration of the contract | On request, or at the latest twelve months after the contract ends |
| Waitlist | Until your access opens | On request, or after twenty-four months without interaction |
| Analytics cookies | 13 months | On expiry, or as soon as you withdraw consent |
Your rights
You have the rights of access, rectification, erasure, restriction, objection and portability over the data concerning you, and the right to withdraw consent at any time. To exercise them, write to [email protected]; we answer within one month, extendable by two months for complex requests.
If you took part in a meeting analysed by one of our customers, address your request to that customer, who alone decides on the processing; we help them answer it. You may lodge a complaint with the CNIL, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, or with the supervisory authority of your country of residence.
What this site measures, and what it stores
This site uses Google Analytics 4 to count its visitors: pages viewed, the order they are viewed in, the country and the kind of device. None of these measurements is matched against a name, an email address or an account. There is no ad network, no social buttons, no retargeting pixel, and Google’s advertising signals — ad_storage, ad_user_data, ad_personalization — are denied permanently, including when you accept analytics.
If you accept, Google Analytics stores two cookies. If you refuse, neither is stored and Google’s library is not even downloaded. Your answer to the banner is kept in your browser’s local storage and sent to nobody; the “Cookies” link at the foot of every page reopens the banner so you can change your mind.
The waitlist form sends four things: your email, your company name, your team size and the language of the site. They are used to tell you when the next wave opens, start no sales sequence and go to nobody else.
| Cookie | Role | Duration |
|---|
| _ga | Tell one browser from another | 13 months |
| _ga_V5XDFBM5BB | Group page views into one visit | 13 months |
Set to 13 months, the ceiling the French regulator asks for, rather than the 2-year default.
When this page changes
The date at the top of the page is that of the version in force. Any change to what we do with your Google data or your content is notified to customers by email before it takes effect, and earlier versions are available on request.
Writing to us
For any question about this page, to ask what we hold about you, or to ask us to delete it, write to [email protected]. We answer within thirty days, which is the window the GDPR gives us.