Privacy policy · Crenomi

Crenomi keeps your calendars in step: when you are busy in one of them, it adds a “Busy” event to the others. To do that, it needs to know when you are busy, and nothing more. This policy says what Crenomi reads, what it stores, for how long, who else handles it, and how to delete it.

In short:

Crenomi copies only the time of your busy events. Titles, descriptions, locations, attendees and attachments are never stored and never written anywhere.
The events Crenomi adds are titled “Busy” unless you choose another title, and their description says “Synced by Crenomi · crenomi.com”.
Your data is stored in France, on Microsoft Azure. It is never sold, never used for advertising and never used to train AI models.
Disconnecting an account removes every event Crenomi added through it. Deleting your Crenomi account removes every event Crenomi added, then everything it stores about you.

1. Who is responsible for your data

Crenomi is published by ALK Innovations, a SASU with a capital of €1,000, registered with the Nantes Trade and Companies Register under number 983 856 642, whose registered office is at 31 avenue des Korrigans, 44300 Nantes, France (“ALK Innovations”, “we”). ALK Innovations is the controller of the personal data described in this policy.

The legal representative of ALK Innovations is Quentin Georget, its President. He is also the point of contact for any question about the protection of your personal data. You can reach us at contact@crenomi.com or by post at the address above.

2. What Crenomi stores

Your Crenomi account

You sign in to Crenomi with a Google or a Microsoft account. Signing in asks the provider for your basic profile only: on Google, the openid, email and profile permissions; on Microsoft, openid, email and profile. Crenomi stores:

your name, your e-mail address, whether the provider says that address is verified, and, if the provider sends one, the address of your profile picture;
for each sign-in method, the provider’s identifier for your account and the tokens it issues for signing in, which give access to that basic profile and nothing else;
for each signed-in session, a session identifier, its expiry date, the IP address the session was opened from and your browser’s identification string (user agent);
the language your alert e-mails are written in (English or French), as the app last reported it, and when the last alert e-mail was sent to you.

Signing in never gives Crenomi access to your calendars. Connecting a calendar is a separate step, with its own consent screen.

The calendar accounts you connect

When you connect a calendar account, Crenomi asks for the narrowest access that lets it read when you are busy and write its events:

Google: calendar.calendarlist.readonly (the list of your calendars, read only), calendar.events (to read your events and write Crenomi’s events), openid and email (to know which Google account was connected). Crenomi never asks for Gmail, Google Drive or the broader calendar permission.
Microsoft: Calendars.ReadWrite (to read your events and write Crenomi’s events), openid and email (to know which account was connected) and offline_access (so that the access keeps working without you signing in again). Crenomi never asks for access to your mail or your files.
iCloud and other CalDAV servers: the server address, your username (for iCloud, your Apple ID) and a password. For iCloud, this is an app-specific password that you create in your Apple account, never your Apple ID password.

For each connected account, Crenomi stores the provider’s identifier for the account, its e-mail address, the permissions you granted, the server address for CalDAV, and the credentials (access and refresh tokens, or the CalDAV password). The credentials are encrypted (see section 9). Crenomi also stores the health of the connection: its status, when a problem started and a technical error message, which only our team sees.

Your calendars

For each calendar of a connected account that Crenomi can write to, Crenomi stores its name, its colour, its time zone, whether it is yours or shared with you, and your settings for it: whether it blocks your other calendars, whether it receives blockers, the title of its blockers and whether all-day events count. A calendar you can only read is not stored.

To keep up with changes, Crenomi also stores technical markers from the provider (sync tokens, subscription identifiers for change notifications) and the dates of its last reads.

Your busy times

Crenomi reads the events of your calendars from today up to 90 days ahead. To decide whether an event makes you busy, it looks at its start and end, whether it is an all-day event, whether it is marked busy, tentative or free, whether it is cancelled, whether you declined it, and how it repeats.

For each event that makes you busy, Crenomi stores only the provider’s identifier for the event, its start and end time, whether it lasts all day, an identifier of the series it belongs to, and a fingerprint used to detect changes. The title, description, location, attendees, attachments and conference links of your events are never stored. The provider may send some of them along with the event; Crenomi does not keep them and does not write them anywhere.

The events Crenomi adds

For each “Busy” event Crenomi writes into one of your calendars (a “blocker”), it stores the provider’s identifier for that event, the time it was written with, and its state. This is how Crenomi updates or deletes its own events later, and how it remembers a blocker you deleted by hand so that it does not add it again.

A blocker carries only a title (“Busy” by default, or the title you chose for its source calendar), the description “Synced by Crenomi · crenomi.com”, its start and end, and a “busy” status. It is never sent with attendees, so no invitation is ever sent. In a calendar you own, it is marked private where the provider supports it. In a calendar someone shared with you, it is not marked private, because some servers would then hide it from the people the calendar is shared with: everyone who can see that calendar sees that you are busy at that time, and nothing else.

Alert e-mails

When a connected account or a calendar stops working (access withdrawn, a calendar deleted or no longer writable), Crenomi sends one e-mail to the address of your Crenomi account. It names the provider, the account’s e-mail address and, where it applies, the calendar’s name. It never contains anything from your events. Crenomi sends at most one such e-mail a day, and never twice for the same problem. Apart from these alerts, Crenomi e-mails you only to give notice of a change to its terms or to this policy, or of the end of the service, and to answer a request you made: no newsletter, no marketing.

Technical logs

Our servers keep technical logs of the requests they receive and of the synchronisation work they do, to run the service, investigate errors and detect abuse. These logs can include network addresses and identifiers of your account, connections and calendars.

3. What Crenomi does not do

It does not copy the details of your events into any other calendar. Only the time is shared.
It does not sell your data, rent it or share it for advertising.
It does not use your data to train artificial intelligence or machine learning models.
It does not use analytics or advertising trackers, on crenomi.com or in the app.
It does not read your e-mail or your files, and it does not ask for permission to.
Nobody at ALK Innovations looks at your calendar data, except at your request to help you, when it is necessary for security (investigating abuse, for example), or to comply with the law.

4. Why we process your data, and on what legal basis

Providing Crenomi: your account, the calendar accounts you connect, your busy times and Crenomi’s blockers, the alert e-mails and the service notices. Legal basis: performance of the contract between you and ALK Innovations, the terms of service (Article 6(1)(b) GDPR).
Keeping Crenomi secure and working: sessions, rate limits on sign-in, technical logs, database backups, and the list of addresses that e-mails are no longer sent to because they bounced or were reported as spam, which protects the reputation of the addresses Crenomi sends from. Legal basis: our legitimate interest in protecting the service and its users (Article 6(1)(f) GDPR).
Answering your requests about your data and complying with the law. Legal basis: legal obligation (Article 6(1)(c) GDPR).

The data described in section 2 is needed to provide Crenomi under the terms of service, and no law requires you to provide it. Without the profile of a Google or Microsoft account, you cannot have a Crenomi account; without access to a calendar account, Crenomi cannot keep its calendars in step.

Crenomi does not rely on your consent for any processing, and it makes no decision about you based solely on automated processing that has legal or similarly significant effects. Deciding when to add a blocker is an automated step of the service you asked for.

5. How long we keep it

Your account: for as long as you have one.
A session, with its IP address and user agent: until you sign out, or at most a quarter of an hour after it expires.
A connected calendar account: until you disconnect it or delete your Crenomi account.
A calendar: until you disconnect its account, delete your Crenomi account, or the calendar disappears from its account.
Your busy times: while the event is within the 90-day window. Once it is over, it is removed at the next full read of the calendar (about once a day), unless a blocker made from it is still in one of your calendars: it is then kept as long as that blocker.
Blockers: a blocker for an event that is over stays in your calendar, so that your past stays as it was. Crenomi keeps its record so that it can still delete it when you disconnect an account, stop a calendar from receiving blockers, or delete your Crenomi account.
The temporary state of a connection in progress: until the connection is finished. Left unfinished, it expires after ten minutes and is deleted within the next quarter of an hour, or when you delete your Crenomi account.
A synchronisation task that failed for good, with its technical error message: kept for our team to investigate, until the calendar, the connected account or the Crenomi account it concerns is deleted.
An address that e-mails bounced from or that reported one as spam: Amazon SES keeps it on our account’s suppression list, so that nothing more is sent to it, until we remove it. Deleting your Crenomi account does not remove it; ask us and we will.
Technical logs: 30 days.
Database backups: 35 days. Data you delete is therefore gone from backups at most 35 days later.

When you disconnect an account, Crenomi deletes every blocker it added to that account’s calendars, and every blocker those calendars caused in your other calendars, past ones included. It stops change notifications, deletes the account’s credentials, calendars, busy times and blocker records, and revokes its access at Google where that does not affect another connection. Microsoft offers no way for an app to revoke its own access: you can remove it in your Microsoft account. For iCloud, you can revoke the app-specific password in your Apple account.

If a provider cannot be reached, Crenomi keeps trying for a few hours. If it still cannot, it deletes its records anyway and keeps only the names of the calendars that may still hold its events, and the account they belong to, so that it can tell you where to look. You can dismiss that list at any time. Every Crenomi event says “Synced by Crenomi”, which makes them easy to find.

When you delete your Crenomi account, Crenomi disconnects every account as above, then deletes your account, your sessions, your sign-in methods and everything else it stores about you, except an address on the e-mail suppression list (above). The permission you gave Google or Microsoft to sign you in to Crenomi stays listed in that account until you remove it there. For your security, deleting your account requires a recent sign-in. Your own events are never touched.

6. Who receives your data

We use the following service providers, which process data on our behalf and under our instructions:

Microsoft Azure (Microsoft France SAS): hosting of the application, its database, its encryption keys and its logs, in France. Azure Static Web Apps also serves crenomi.com and app.crenomi.com through Microsoft’s global network (see section 7).
Amazon Web Services EMEA SARL (Amazon Simple Email Service): sending the alert e-mails and the service notices, from the Ireland region. It receives your e-mail address, your name and the content of the e-mail, and keeps the addresses that bounced or reported an e-mail as spam on our suppression list (section 5).
Google Workspace (Google Ireland Limited): hosting of our support mailbox, contact@crenomi.com. It receives the messages you send us and our replies.

Crenomi also exchanges data with the calendar providers you connect, because you ask it to: Google (Google LLC), Microsoft (Microsoft Corporation), Apple (iCloud) or the CalDAV server you choose. They receive Crenomi’s requests and the blockers it writes, and they process your data under their own terms and privacy policies.

We may also disclose data when the law requires it, or to a company that takes over all or part of ALK Innovations’ business; you would be told beforehand.

7. Where your data is stored

The database, the application servers, the encryption keys and the logs are hosted by Microsoft Azure in the France Central region. Database backups stay in that region.

Alert e-mails and service notices are sent through Amazon Simple Email Service in the Ireland region, in the European Union.

The website and the web app are served by Azure Static Web Apps, which delivers pages from Microsoft’s global network and passes the app’s requests on to our servers in France. Those requests can therefore travel through Microsoft’s points of presence outside the European Union. These transfers are covered by the European Commission’s standard contractual clauses, incorporated in Microsoft’s Data Protection Addendum.

The calendar providers you connect may store and process your data outside the European Union, under their own terms.

8. Google user data

Crenomi’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 practice:

What Crenomi accesses: the list of your Google calendars (read only), and the events of the calendars you connect, which it reads and in which it writes its blockers. It also receives the e-mail address and the identifier of the Google account you connect.
How Crenomi uses it: only to provide the features you see in Crenomi, that is, to show your calendars and their settings, to find when you are busy, and to add, update and delete its “Busy” events in your other calendars.
What Crenomi stores: from your events, only their timing and identifiers, as described in section 2. The credentials of the Google calendar accounts you connect are encrypted (section 9).
Sharing: Crenomi does not transfer Google user data to anyone, except to the service providers listed in section 6 that host and operate Crenomi, when it is necessary to comply with the law, or as part of a merger, acquisition or sale of assets, with your prior consent. The only thing Crenomi writes into your other calendars is the blocker described in section 2: a title, a fixed description and a time.
No advertising: Crenomi does not use or transfer Google user data for advertising, including retargeting, personalised or interest-based advertising.
No sale: Crenomi does not sell Google user data.
No AI training: Crenomi does not use Google user data to develop, improve or train generalised artificial intelligence or machine learning models.
No human reading: nobody at ALK Innovations reads your Google user data, unless you ask us to in order to help you, when it is necessary for security purposes such as investigating abuse, or to comply with the law.
Deleting it: disconnecting your Google account in Crenomi, or deleting your Crenomi account, deletes the Google data Crenomi stores and revokes its calendar access where that does not affect another connection (section 5). The permission to sign in to Crenomi with Google is not revoked: it stays listed in your Google Account until you remove it. You can remove any of Crenomi’s access at any time from your Google Account’s third-party connections page.

9. Security

The credentials of your connected accounts (tokens and CalDAV passwords) are encrypted in the database with AES-256-GCM. Each value is bound to the connection it belongs to, so it cannot be moved to another one. The encryption key is kept apart from the database, in Azure Key Vault.
The database is reachable only from Crenomi’s private network, never from the internet, and only over encrypted connections.
Every exchange between your browser and Crenomi, and between Crenomi and the calendar providers, is encrypted (HTTPS).
Connecting a calendar is protected against requests forged by another site or another session, and its temporary state expires after ten minutes.
Sign-in is rate-limited to slow down abuse.
Database backups are kept for 35 days.

If a personal data breach is likely to put your rights at risk, we notify the CNIL within 72 hours of becoming aware of it, and we tell you without undue delay when the risk is high.

10. Cookies

Crenomi uses one kind of cookie: the session cookie that keeps you signed in to the app, set when you sign in and removed when you sign out. While you sign in, a short-lived cookie may also protect the exchange with Google or Microsoft. These cookies are strictly necessary for the service you ask for, so they need no consent.

Crenomi uses no analytics, advertising or tracking cookies, on crenomi.com or in the app. The website crenomi.com sets no cookie of its own.

11. Your rights

Under the General Data Protection Regulation (GDPR) and the French Data Protection Act, you have the right to access your data, to have it corrected or erased, to restrict its processing, to object to processing based on our legitimate interest, to receive the data you provided in a structured, machine-readable format, and to set directives on what happens to your data after your death.

Much of this you can do yourself in the app: change the settings of each calendar, disconnect an account, or delete your Crenomi account. For anything else, write to contact@crenomi.com or by post to ALK Innovations, 31 avenue des Korrigans, 44300 Nantes, France. We answer within one month. We may ask you to prove your identity before we act on a request.

You also have the right to lodge a complaint with the French data protection authority, the CNIL (www.cnil.fr), or with the authority of the country where you live.

12. Children

Crenomi is offered to professionals only and is not intended for children. You must be at least 16 years old to create an account.

13. Changes to this policy

We may update this policy, for example when Crenomi changes. The date at the top of this page says when it last changed. If a change affects how your data is used, we will tell you before it takes effect, by e-mail or in the app.

14. Contact

For any question about this policy or your data: contact@crenomi.com, or ALK Innovations, 31 avenue des Korrigans, 44300 Nantes, France.

This English version is provided for convenience. In case of any inconsistency, the French version prevails.