Privacy Policy
Preamble
This policy (the "Policy") describes how Atipik SA, a public limited company (société anonyme) registered in the commercial register of the Canton of Geneva, with its registered office at Avenue de la Praille 26, 1227 Carouge, Switzerland, operating the Cassini platform (hereinafter "Cassini", "we", "our" or "us"), processes personal data in connection with the operation of the Cassini platform (the "Platform"), in accordance with the Federal Act of 25 September 2020 on Data Protection ("FADP") and its implementing ordinance.
It is addressed to customer organisations and their employees who use the Platform, to visitors to our website, and to persons who interact with a public chatbot published by a customer. The Platform is intended for organisations established in Switzerland; we do not offer our services to any customer established abroad.
1. Two distinct regimes: read this first
The Platform processes two categories of data that are subject to different regimes. This distinction governs the rest of the Policy.
| Account, billing, support and usage data | Customer Content | |
|---|---|---|
| What it covers | User identity, billing, technical logs, usage metrics | Conversations, uploaded documents, knowledge bases, meeting recordings, voiceprints, assistant configurations, visitors' exchanges with public chatbots |
| Who decides the purposes | Cassini | The Customer |
| Cassini's role | Controller (Art. 5 lit. j FADP) | Processor (Art. 5 lit. k FADP) |
| Applicable document | This Policy | The Data Processing Addendum |
| To whom an access request should be addressed | Cassini | To the Customer concerned |
In practice: when an employee of a customer submits a document to the Platform or asks the assistant a question, it is the customer who decides what data it submits, why and for how long. Cassini processes this data only on the customer's instructions and makes no use of it for its own purposes. By contrast, when Cassini invoices the subscription, responds to a support request or analyses the load on its servers, it acts on its own behalf and is responsible for that processing.
2. Controller and contact
Atipik SA, a public limited company (société anonyme) registered in the commercial register of the Canton of Geneva
Avenue de la Praille 26
1227 Carouge, Switzerland
Contact for any question relating to data protection: dpo@cassini.app
3. Data processed by Cassini as controller
3.1 Account and identification data
Surname, first name, business email address, job title, role and access rights in the Platform, affiliated organisation, profile photo (if any), interface preferences.
3.2 Billing data
Subscription plan, number and type of seats, billing and payment history, payment method (card data being processed directly by our payment service provider, without our having access to it), configured overage cap and overage usage amounts invoiced.
3.3 Technical and connection data
IP address, connection timestamps, session identifier, browser and operating system type, access and operation logs, error logs.
3.4 Support data
Content of exchanges with our support team, including the screenshots and attachments you send us.
3.5 Usage and consumption data
Features used, frequency of use, navigation within the application, performance metrics, as well as consumption metrics for the artificial intelligence features (usage volumes per user, per model and per feature), which are necessary for managing usage allowances, billing overages, preventing abuse and pricing. These metrics relate to volumes and metadata; they do not include the content of conversations.
3.6 Customer Content
Conversations, documents, knowledge bases, meeting recordings and other content submitted to the Platform, including the personal data they contain (where applicable, sensitive data within the meaning of Art. 5 lit. c FADP), are the responsibility of the Customer. Cassini processes them only as a processor and accesses them only in the limited cases described in the Data Processing Addendum, in particular for technical operation, incident resolution and backup. Cassini does not use Customer Content to train artificial intelligence models made available to third parties.
3.7 Google data (Google Drive connector)
When a user connects their Google Drive account, the Platform requests read-only access to their Drive files (drive.readonly scope). This access is used solely to search, within the folders linked to a project by one of its members or to an assistant by an administrator of the Customer, for the files relevant to the question asked, and to read their content in order to answer it. The Platform always acts with the user's own Google permissions: the user sees only the files to which Google already gives them access. Cassini never modifies, creates or deletes files in Google Drive.
Cassini stores:
- the OAuth access tokens, encrypted at rest;
- the email address and identifier of the connected Google account;
- for each linked folder: its identifier, name, path and link.
The content of the files read forms part of the Customer Content (section 3.6). The extracted text is kept in an encrypted cache, specific to each user, for no more than six hours, and is never indexed in a Cassini search engine. The excerpts used to answer are recorded in the conversation and follow its retention period (section 7).
The content of the files is transmitted to the selected artificial intelligence model, solely to respond to the request (section 5.2). Data obtained from Google APIs is neither sold, nor used for advertising purposes, nor used to train or improve any artificial intelligence model whatsoever. No one accesses it, except with the user's agreement, for security reasons or where required by law.
This data benefits from the security measures described in section 8. In particular, exchanges with Google APIs and with the Platform are encrypted in transit (TLS), the tokens and the cache are encrypted at rest, and each search is performed with the token of the user asking the question, never with that of another user.
The user may disconnect Google Drive at any time in their settings: Cassini then revokes its access with Google and deletes the tokens. The user may also withdraw this access from myaccount.google.com/permissions.
Cassini'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.
3.8 Voiceprints (meeting notes)
A user may, if they wish, record a short reading in their preferences so that the Platform recognises their voice in the meetings of their organisation. From this recording, the Platform computes a voiceprint: a series of numbers describing the characteristics of the voice. A voiceprint is biometric data that can identify a person, and therefore sensitive data within the meaning of Art. 5 lit. c FADP.
- Consent. The voiceprint is created only with the user's explicit consent, given in the interface before recording. Recording is optional; declining it has no other consequence on the use of the Platform.
- Data kept. Only the voiceprint is stored, with its creation date, the version of the recognition model and the version of the consent text accepted. The recording is processed in memory to compute the voiceprint and is never stored.
- Use. The voiceprint serves only to recognise the user in meetings recorded within the organisation for which it was created. The user is named in the transcript, or, when they were not one of the meeting's participants, their name is suggested to the person who recorded it. It is never used for another organisation, disclosed to third parties, or used to train any model.
- Location. It is computed and stored in Switzerland.
- Retention. Until the user deletes it from their preferences, which also withdraws their consent. At the latest, it is deleted when the user leaves the organisation, when their account or the organisation is deleted, or when the organisation stops using meeting notes.
- Role. Like meeting recordings, voiceprints form part of the Customer Content (section 3.6). Cassini processes them as a processor on behalf of the Customer, which remains responsible for the lawfulness of the processing, in particular towards its employees. Cassini collects the user's consent through the interface on the Customer's behalf.
4. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Provision of the Services, management of the account and of access | Performance of the contract |
| Invoicing, collection and debt recovery, including usage measurement | Performance of the contract; legal obligation (accounting) |
| Support and assistance | Performance of the contract |
| Security of the Platform, prevention and detection of abuse and of uses contrary to the Acceptable Use and Content Policy | Overriding legitimate interest |
| Capacity management, service balance and pricing | Performance of the contract; overriding legitimate interest |
| Improvement of the Services and aggregated statistics | Overriding legitimate interest |
| Audience measurement for the Site and the Platform | Consent |
| Informing Customers about changes to the service | Performance of the contract; legitimate interest |
| Direct marketing to professionals | Legitimate interest, with a right to object at any time |
| Statutory retention, responses to authorities | Legal obligation |
No Customer Content data is used for marketing, advertising, profiling or resale purposes.
5. Recipients and processors
We neither sell nor rent your data. It is disclosed only to the following categories of recipients.
5.1 Processors
| Processor | Service | Data location |
|---|---|---|
|
Infomaniak Network SA Rue Eugène-Marziano 25 1227 Les Acacias (Geneva), Switzerland |
Hosting of the Platform, document storage, backups, base artificial intelligence model, speech transcription, sending of emails | Switzerland |
| Stripe (Stripe Payments Europe Ltd / Stripe Inc.), Dublin, Ireland | Processing of card payments | International processing, in particular in the EEA and the United States. Transfers from Switzerland are governed in particular by the Swiss-U.S. Data Privacy Framework and, in the alternative, by standard contractual clauses adapted to Swiss law |
|
OpenAI Ireland Ltd. Dublin, Ireland (processing also by OpenAI OpCo, LLC, San Francisco, United States) |
Optional artificial intelligence models, enabled only when a user selects them | Ireland / United States. Transfers governed by standard contractual clauses adapted to Swiss law or by an adequacy decision; contractual commitment not to use content for training purposes |
|
Anthropic Ireland, Limited Dublin, Ireland (processing also by Anthropic PBC, San Francisco, United States) |
Optional artificial intelligence models, enabled only when a user selects them | Ireland / United States. Transfers governed by standard contractual clauses adapted to Swiss law or by an adequacy decision; contractual commitment not to use content for training purposes |
|
SpaceXAI LLC Austin, United States |
Optional artificial intelligence models, enabled only when a user selects them | United States. Transfers governed by standard contractual clauses adapted to Swiss law or by an adequacy decision; contractual commitment not to use content for training purposes |
|
Google Cloud EMEA Limited Dublin, Ireland (Gemini; processing also by Google LLC, Mountain View, United States) |
Optional artificial intelligence models, enabled only when a user selects them | Ireland / United States. Transfers governed by standard contractual clauses adapted to Swiss law or by an adequacy decision; contractual commitment not to use content for training purposes |
|
OpenRouter, Inc. New York, United States |
Gateway to optional artificial intelligence models, enabled only when a user selects them | United States. Transfers governed by standard contractual clauses adapted to Swiss law or by an adequacy decision; contractual commitment not to use content for training purposes |
| Tavily Inc. | Web search, enabled only when the feature is used; only the search query is transmitted | United States |
| Cloudflare Inc. | Anti-bot protection for public chatbots | International processing |
Application error logging is carried out on infrastructure operated by Cassini in Switzerland.
All our processors are bound by a contract imposing on them safeguards at least equivalent to our own and an obligation of confidentiality. The list of processors with access to Customer Content is set out in the Data Processing Addendum.
5.2 Third-party models: a choice that is yours
Cassini's positioning is data sovereignty: Customer Content is hosted in Switzerland and the base model is operated on infrastructure located in Switzerland. Third-party models (for example those of OpenAI, Anthropic, Google, SpaceXAI or via OpenRouter) are optional: they receive data only when a user selects them for a conversation, and only the content strictly necessary to process the request. Each model is identified as Swiss or third-party in the interface, and the Customer's administrators may restrict the models made available to their users. The selection of a third-party model constitutes an instruction from the Customer within the meaning of the Data Processing Addendum.
5.3 Other recipients
Our legal advisers, fiduciaries and auditors, to the extent necessary; the Swiss judicial or administrative authorities where there is a formal request based on law; a potential acquirer in the context of a merger or business transfer, subject to a prior confidentiality undertaking.
6. Disclosure of data abroad
Customer Content is processed and stored in Switzerland.
Data is disclosed abroad only in the following cases:
- when a user selects a third-party model or a feature relying on a third-party provider (web search), the strictly necessary content is transmitted to the provider concerned, according to the locations indicated in section 5.1;
- for payment processing, in accordance with the arrangements indicated in section 5.1;
- for the anti-bot protection of public chatbots.
Depending on the case, these disclosures are based on the Federal Council's recognition of legislation ensuring adequate protection (Art. 16 para. 1 FADP), on the Swiss-U.S. Data Privacy Framework or on standard contractual clauses adapted to Swiss law.
7. Retention periods
| Category | Period |
|---|---|
| Account data, active account | For the term of the contract |
| Account data, after termination | 12 months, then deletion or anonymisation |
| Billing data and accounting records | 10 years, in accordance with Art. 958f CO |
| Customer Content | Term of the contract, then made available for 90 days (Art. 15.6 of the Terms), then deletion |
| Voiceprints | Until deleted by the user, at the latest when they leave the organisation or when the organisation stops using meeting notes |
| Connection and access logs | 12 months |
Data is destroyed or anonymised as soon as it is no longer necessary for the purposes pursued, subject to statutory retention obligations.
Customer Content: the retention period for content within the Platform is determined by the Customer, which is the controller and has the features enabling it to delete its content itself. Cassini retains it for the term of the contract and deletes it in accordance with the Data Processing Addendum.
8. Security
We implement technical and organisational measures appropriate to the risk, in accordance with Art. 8 FADP, in particular:
- encryption of communications in transit and of data at rest, including backups;
- two-factor authentication for access to the Platform;
- role-based access control and the principle of least privilege;
- logical segregation of data between customers;
- strict separation of development, test and production environments;
- prohibition on using real customer data in development and test environments;
- access logging and continuous security monitoring;
- rate limiting and mechanisms protecting against abusive use;
- regular backups and tested restoration procedures;
- a written confidentiality undertaking from every person accessing the data;
- periodic reviews of access rights;
- a documented incident management procedure.
Details of the measures are set out in the Data Processing Addendum.
Data security breaches. We notify the Federal Data Protection and Information Commissioner as soon as possible of any breach resulting in a high risk to the personality or fundamental rights of the data subjects, in accordance with Art. 24 FADP, and inform the data subjects where the law so requires or their protection so demands. Where the breach concerns Customer Content, we inform the Customer concerned, which is the controller, in accordance with the arrangements and within the time limit provided for in the Data Processing Addendum.
9. Your rights
In accordance with the FADP, you have the following rights with regard to the data for which Cassini is the controller:
- Right of access (Art. 25 FADP): to obtain confirmation that processing is taking place and to know its content;
- Right to rectification of inaccurate data (Art. 32 FADP);
- Right to delivery or transmission of your data in a commonly used electronic format (Art. 28 FADP);
- Right to request erasure of data or the cessation of processing, within the limits of our statutory retention obligations;
- Right to object to processing based on our legitimate interest, in particular to direct marketing;
- Right to withdraw your consent at any time, where the processing is based on it, without retroactive effect.
These rights may be exercised by contacting dpo@cassini.app. We generally respond within thirty days. We may request proof of identity where necessary to verify your identity, and refuse, restrict or defer a request in the cases provided for by law.
Requests concerning Customer Content. A person who wishes to exercise their rights over data contained in an organisation's Customer Content (for example an employee regarding conversations held within their employer's workspace, a participant in a recorded meeting, or a visitor to a public chatbot) must contact the organisation concerned, as it is the controller. If such a request reaches us, we forward it without delay to the customer concerned, without responding to it ourselves.
10. Cookies and audience measurement
The Platform and our website use:
- strictly necessary cookies for operation, authentication and security, which cannot be disabled;
- where applicable, audience measurement subject to your consent.
No cookies are used for advertising, individual targeting, cross-site tracking or data resale purposes.
11. Cooperation with authorities
We disclose data to third parties only where there is a binding legal basis or a decision of a competent authority. Where the law permits, we inform the person or Customer concerned of such a request. We oppose requests that appear to us to be unfounded.
12. Audits
Cassini does not accede to on-site or system audit requests made in general terms. Customers may obtain, on request, documentation of our security measures. A defined audit right may be exercised in accordance with the arrangements provided for in the Data Processing Addendum.
13. Changes to this Policy
We may amend this Policy in line with changes in our processing, in technology or in the law. The version in force is published on www.cassini.app. Any material change is communicated to Customers electronically at least thirty (30) days before it takes effect.
Version 1.0, 1 September 2026