Privacy Policy

Preview notice: CielLogic is in development. This page describes the data handling of the current pre-release build; it will be superseded by the full policy published before general availability.

What we collect via Google

When you sign in with Google, CielLogic requests:

openid, email, profile — to identify your account and display your name.
calendar.freebusy — the free/busy status of your Google Calendar. We only ever see when you are busy, never the title, description, attendees, or any other detail of an event.
calendar.events — used only to create, update, or remove calendar events that CielLogic itself created (e.g. a confirmed assignment), identified by their event id. We do not read the content of events we did not create.

How it's used

Free/busy data is used to compute worker availability for the architects and projects you're connected to within your organization. It is not shared outside that organization and is not used for any purpose beyond scheduling.

Storage

Your Google OAuth tokens are encrypted at rest (AES-256-GCM) and are only ever decrypted by CielLogic's own backend and sync service to make the calendar calls described above.

Retention & deletion

You can disconnect your Google Calendar at any time, which revokes CielLogic's access with Google and deletes the stored tokens. Account data can be exported or deleted on request.

Contact

Questions about this policy: privacy@ciellogic.com