Privacy Policy

This calit instance is operated by https://booking.nikigre.si.

What calit is

calit is open-source scheduling software the operator hosts themselves. It stores all data in a database the operator controls. The maintainers of the project do not operate a central service, do not receive your data, and have no access to any deployment's database.

Data calit stores

• Account data — your username, email address, display name, timezone, and an argon2id hash of your password (never the password itself).
• Scheduling data — your meeting types, availability rules, and the bookings made by invitees (invitee name, email, and any answers to custom booking questions you configure).
• Google account data — when you connect Google Calendar (optional): the Google account's email and stable subject identifier, and the OAuth access and refresh tokens. Tokens are encrypted at rest.
• CalDAV account data — when you connect a CalDAV calendar (optional): the server URL, your username, and the app password, which is encrypted at rest like Google tokens.

Booking details on the host's calendar

When a host has connected a calendar account and selected a calendar to write bookings to, calit copies each booking to that calendar as an event. The event is stored by the host's calendar provider — Google, or the CalDAV server the host connected. It carries:

• the title "meeting title with invitee name" and the booking's description;
• the start and end time, and the meeting location (or a generated Google Meet link);
• the email addresses of the invitee, the host(s) and any active guests. On Google they are added as event attendees, so Google stores them and emails them invitations. On a CalDAV server they are written into the event description, and the server stores them.

If you book a meeting, your name, email address and these booking details are therefore stored by the host's calendar provider as well as by calit. If you are a host, this is the copy on your own calendar. That copy is held under the provider's own privacy policy and retention. calit deletes the event when the booking is cancelled or erased, but it cannot remove copies the provider keeps in its trash or backups. When a host deletes their account, calit cancels their upcoming bookings first, which deletes those events; events of past bookings remain on the provider's calendar until the host removes them. No such event is created when the host has no connected calendar or no write calendar selected.

How CalDAV data is used

When you connect a CalDAV account, calit fetches the full event objects from the CalDAV calendars you select, within the booking window. It uses only their times to compute busy intervals and discards the rest: the content of events calit reads is never stored. When bookings are made, rescheduled, or cancelled, calit creates, updates, and deletes the event on the calendar you chose as write target; that event carries the booking details listed above.

How Google user data is used

When you connect a Google account, calit requests the Google Calendar scope and uses it only to provide scheduling: it reads free/busy information from the calendars you select to compute available slots, and creates, updates, and deletes events on the write-target calendar you choose when bookings are made, rescheduled, or cancelled. calit reads only free/busy information from Google, never the content of your calendar events (the events calit writes for bookings carry the booking details listed above), and does not use Google data for advertising, profiling, or any purpose other than the scheduling features you initiated.

Limited Use disclosure

calit's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not sold, not transferred to third parties except as needed to provide the scheduling features, not used for advertising, and not read by humans except where required for security, to comply with law, or with your explicit consent.

Data sharing

calit does not sell or share your data.

This deployment sends data to:

• The CalDAV server you connect, if you connect one, for the calendar operations above, including the booking details copied to your calendar.
• Google, for the calendar operations above, including the booking details copied to your calendar.
• The SMTP server mail.nikigre.si, which delivers booking and notification emails.

Retention and deletion

• Disconnecting a calendar account in Settings → Calendars deletes its stored credentials and calendar selections from this site. For Google this does not withdraw the grant at Google — revoke calit's access in your Google account to do that.
• Deleting your account at Settings → Delete my account removes your account, settings, meeting types, availability, bookings, connected calendar accounts and notification channels.
• A hash of a deleted account's username is kept permanently, so that name can never be re-registered and used to take over a stale login.
• If you booked a meeting here, the manage link in your confirmation email lets you download your data or erase it from that booking. Bookings are not linked to each other by email address, so erasure reaches only the booking whose manage link you used — not any other booking you may have made.
• This deployment sets no automatic retention window, so booking details are kept until removed by the host or the operator. A host may still set their own window, up to 36,500 days.
• Emails queued for sending are deleted about 30 days after they are sent (or after they were queued, if never sent). Password-reset, invitation and sign-in tokens are deleted about a day after they expire.

Security

Passwords are hashed with argon2id; Google OAuth tokens and CalDAV app passwords are encrypted at rest. Production deployments run behind TLS with secure cookies. The operator is responsible for securing the host and database.

Contact

For questions about a specific deployment, contact that deployment's operator. For questions about the calit software itself, open an issue at github.com/asm0dey/calit.