Privacy

Creator accounts. Your email address, name if you provide one, and authentication details handled by our identity provider. We never see your password.

Uploaded schedules. Files you upload are stored privately. Files belonging to a personal calendar are only accessible to your account. Files belonging to an Organisation calendar are accessible to current members of that Organisation, according to their role. They are used to extract event details and to let you re-check what a date came from.

Calendar and event data. The calendars, events, locations and settings you create. Published calendars are public to anyone with the link or QR code.

Event resources. Files you attach to an event become available to people viewing that published calendar.

Recipient change alerts. If a recipient chooses to be told when dates change, we store only their email address and the calendar it relates to, with an unsubscribe option.

Aggregate counts. We count public page views and add-to-calendar clicks per calendar. These are totals only — we do not profile or fingerprint recipients.

To run the service: extracting events from your files, letting you review and correct them, publishing your calendar, generating the QR code and feed, and sending service-related messages. We do not sell your data and we do not use it for advertising.

CalRound runs on Lovable Cloud, which uses Supabase for the database, authentication and file storage. Event extraction is performed by an AI model provider on the content of the file you upload. Place and address suggestions use Google Maps Platform. These providers process data on our instructions.

When you type a location we send only what you type to Google to return suggestions. If you select a suggestion we store the place name, formatted address, coordinates and place identifier so we do not have to look it up again. Nothing else from Google is retained.

Uploads and account data are held in private storage with row-level access rules. Personal calendars, their uploads and their attachments can only be reached by your own account. Organisation calendars, their uploads and their attachments can be reached by current members of that Organisation. Anything on a published calendar — including files you attach to a public event — is intended to be public to anyone with the link or QR code. Traffic is encrypted in transit. No online service can promise absolute security, and we make no certification claims.

If your plan includes an Organisation workspace, calendars created in that workspace belong to the Organisation rather than to one person. Current members can view and work on those calendars, their events, uploads and attachments, according to their role — admins can additionally invite members, remove members and delete Organisation calendars.

Being removed from an Organisation, or leaving it, immediately ends your access to that workspace and everything in it. It does not delete the Organisation's calendars or files, and it does not affect your own personal calendars. Moving a personal calendar into an Organisation is always an explicit action, and afterwards that calendar is accessible to the Organisation's members.

Your data is kept while your account is active. Deleting a calendar deletes its events, uploads and attachments. You can ask us to delete your account and its content and we will do so. Calendars that belong to an Organisation are not deleted when an individual member's account is deleted, because they belong to the Organisation rather than to that member.

If you are in the UK or EU you have rights to access, correct, export or delete your personal data, and to object to certain processing. Contact us and we will help.

We use essential storage only — a sign-in session for creators. There are no advertising or tracking cookies, and recipients do not need an account or a cookie to add a calendar.

Questions or requests: [email protected]