Chronoo

Provisional document, subject to legal validation

Privacy policy

Last updated: 10 October 2026

This policy describes how Chronoo (“Chronoo”, “we”) processes personal data in connection with its SaaS online appointment booking service and connected calendar management, in accordance with the Swiss Federal Act on Data Protection (nFADP / nLPD, SR 235.1).

1. Controller

The controller is the publisher of the Chronoo platform. For any question relating to data protection: ask@chronoo.ch.

ACN Group Sàrl (company in formation), Chemin du Petit-Bâle 3, 1045 Ogens, Switzerland. UID number: pending. Contact: ask@chronoo.ch

2. Data processed

2.1 Visitors and prospects (appointment booking)

  • Identity and contact: first name, last name, email address, phone number (optional), company (optional).
  • Request content: subject or free-text message, meeting mode, in-person address where applicable.
  • Scheduling data: chosen slot, time zone, language, technical booking identifier.
  • Technical data: IP address (abuse rate limiting), analytics session identifier (if enabled).

2.2 User accounts (self-service offer)

  • Account identity: display name, email address, password (stored as a hash).
  • Profiles and availability settings, public labels, appointment preferences.
  • Mobility addresses, if provided in the account area:
    • Home address: sensitive data; managed solely by the account holder; used server-side to estimate travel. It does not appear on the public booking page or in the configuration sent to the browser.
    • Workplace (office) address: same server-side travel use; not exposed publicly. An organization administrator may set it when creating a seat, without access to the home address.

2.3 Calendar connections (OAuth / CalDAV)

If you connect a calendar via OAuth (Google, Microsoft Outlook, Infomaniak) or via manual CalDAV, Chronoo receives and stores the secrets required (encrypted OAuth tokens, or CalDAV credentials / app password) to read your availability and, where applicable, write appointment events. We only access calendars you explicitly enable. Calendar data remains hosted with the relevant provider; we retain only what is strictly necessary for the service to operate.

2.4 Google user data (Google Calendar)

When you connect a Google account, Chronoo asks for access to Google Calendar and to your Google account email address. This access is used only to provide the booking features you see in your account:

  • Email address: identifies the connected Google account in your Chronoo account and links it to the right booking page.
  • Calendar list (calendar names and identifiers): lets you choose which calendars block slots.
  • Availability and events of the calendars you enable: start and end times, “busy” or “free” status and, for in-person appointments, the event location used to estimate travel time between two appointments. Event titles are read only when you open the availability diagnostic with titles enabled, and are shown to you only.
  • Appointment events: when a visitor books, Chronoo creates the appointment in the calendar you chose (date, time, subject, visitor contact details, video link such as Google Meet where applicable), and removes or updates it if the appointment is cancelled or moved.
  • “Travel” blocks: for an in-person appointment, Chronoo adds a “Travel” event marked free before it and, when needed, after it, and removes it on cancellation. If you turn on the option in “Meeting modes”, it does the same around in-person meetings you enter yourself, using only their time and location. Chronoo keeps the identifier and times of these blocks, not the content of your events.

Storage: we store the OAuth tokens (encrypted), the account email address, the list of your calendars with your choices, and the identifiers of the events Chronoo created. The content of your other events is not stored: availability is computed on the fly and kept at most a few minutes in a temporary cache.

Sharing: Google user data is not sold, not used for advertising, not used to train artificial intelligence models, and not shared with third parties, except the processors needed to run the service (hosting in Switzerland) or where the law requires it. Visitors of your booking page only see free slots. Nobody at Chronoo reads this data, except with your explicit consent for support, for security reasons, or to comply with the law.

Deletion: disconnecting the calendar in your account, or deleting your account, revokes the access with Google and deletes the tokens and the stored calendar information. You can also remove access at any time at myaccount.google.com/permissions, or ask for deletion at ask@chronoo.ch.

Chronoo's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Purposes and legal bases

  • Service performance: schedule, confirm, remind, or allow modification/cancellation of an appointment (Art. 6 nFADP).
  • User account: create and administer your space, connect calendars (Art. 6 nFADP).
  • Security and anti-abuse: rate limiting, security event logging (overriding interest, Art. 31 nFADP).
  • Product improvement: aggregated booking-journey statistics, if analytics is enabled on the instance (overriding interest or consent, as applicable).
  • Legal obligations: limited retention of technical traces where the law requires it.

4. Recipients and processors

Data may be processed by (depending on features actually enabled on the instance or account):

  • Host: Infomaniak Network SA (Switzerland), for hosting the application, data files and technical logs.
  • To be completed: payment provider (Payrexx), once card and TWINT are open.
  • To be completed: provider of the Chronoo Assistant.
  • Calendars (CalDAV / OAuth): Google LLC, Microsoft Corporation, Infomaniak, or any CalDAV server you configure (URL and credentials provided by you). Chronoo reads busy periods to compute which slots to offer. Visitors only see free slots. Appointment details stay in your calendar. Chronoo may write appointment events for calendars you enable.
  • Travel calculation (mobility option): swisstopo first (address check, Swiss Confederation) and Open Journey Planner (travel time, Federal Office of Transport). OpenRouteService (HeiGIT, Germany) is called only if the matching Swiss service does not respond. Home, company and in-person addresses are checked. Trip coordinates are sent when an in-person meeting is booked.
  • Video conferencing: depending on the chosen mode: Google Meet, Microsoft Teams, kMeet (Infomaniak), Zoom. Zoom may use a configured fixed link or, if Server-to-Server credentials are present on the instance, meeting creation via the Zoom API.
  • Microsoft search connector (Enterprise opt-in): if the account turns it on, indexing of appointment metadata (generic title, time slot, mode, profile). No prospect email, phone or company in that index.
  • Messaging: transactional email (confirmation, reminder, cancellation) sent through the mail server configured for the instance.

We do not sell your personal data. Any processor is selected to ensure an adequate level of protection under the nFADP. The list above describes integrations provided by the software; only those actually configured process data.

5. Transfers abroad

The main infrastructure is located in Switzerland (Infomaniak). Travel calculation asks swisstopo and Open Journey Planner first, in Switzerland. OpenRouteService (Germany) is used only as a fallback. Use of calendars or video conferencing via US or European services, or Microsoft Graph, may involve a transfer of data outside Switzerland. Such transfers rely on the contractual and technical safeguards of the relevant provider and on your choice to enable those integrations.

6. Retention periods and anonymisation

We apply storage limitation. The periods below reflect the instance’s technical configuration and may be adjusted by the administrator.

6.1 Booking log

Identifying data linked to a past booking (name, first name, email, phone, company, request subject, meeting address, management token) is automatically anonymised 365 days after the end of the booked slot, by a scheduled task.

After anonymisation, only non-identifying metadata may remain (dates, meeting mode, internal statistics).

6.2 Appointment management link

The token allowing a prospect to reschedule or cancel an appointment expires 30 days after the end of the appointment, or is cleared when the log is anonymised.

6.3 User account and OAuth

  • Account data: retained while the account is active, then deleted within a reasonable time after account deletion.
  • Calendar OAuth tokens: revoked when the calendar is disconnected or the account is closed.
  • Technical logs and analytics: limited duration (rotation or aggregation), generally under 12 months.

7. Security

We implement appropriate technical and organisational measures: encryption of secrets and OAuth tokens, access control for sensitive files, CSRF protection on booking, rate limiting, security event logging. No measure, however, provides absolute security.

8. Your rights

Under the nFADP, you have in particular the following rights, within the limits of the law:

  • right to information about the processing;
  • right of access;
  • right to rectification;
  • right to erasure or anonymisation when the data is no longer needed;
  • right to withdraw consent where applicable;
  • right to lodge a complaint with the Federal Data Protection and Information Commissioner (FDPIC / PFPDT).

Exercise your rights by writing to ask@chronoo.ch. We may ask you to prove your identity.

9. Cookies and local storage

The booking flow may use browser local storage (language, analytics session). The account area relies on a session cookie strictly necessary for authentication. No advertising cookies are set by default by Chronoo.

10. Changes

We may update this policy to reflect changes to the service or to regulation. The update date appears at the top of the document. In case of a material change, we will inform account users by email or via the interface where appropriate.

11. Contact

Questions or requests relating to data protection: ask@chronoo.ch.