Privacy

What we store

The Google identity you sign in with: the stable identifier Google provides, the email address, and a display name and picture when there is one.

For each connected calendar account: the Google authorization, stored encrypted, and the record of when it was connected and whether it still works.

Your preferences: calendar order and visibility, language, first day of the week, hour format, default event duration, and the time zones you chose to see.

Technical records of operations in flight — a transfer of an event between accounts that stopped half-way, for example — for as long as you need to finish or undo it.

What we do not store

We keep no copy of your events, guests or calendars in our databases. Events are read from Google on every request, and the cache on your device can be deleted at any time without losing anything.

We do not store your password, because we never receive it.

We use no tracking cookies, no third-party pixels, and no advertising profiles.

Google data and how it is used

Cuco asks for permission to see and edit the calendars of the accounts you connect. That permission is used only to show and change your events when you ask — never to train models, never for advertising, and never shared with anyone else.

You can revoke it at any time, either in Cuco or on your Google Account’s permissions page. Revoking stops Cuco’s access immediately.

For how long

For as long as your account exists. Deleting your account erases the identity, the authorizations, the sessions and the preferences; minimal security audit records may remain without identifying you, where security requires it.

Contact

Privacy questions: privacidade@cuco.com.vc.