Privacy Policy
This page describes PrimeCal's general data-handling architecture. The formal Privacy Policy for your specific deployment must be published by the organization that operates your PrimeCal instance — this may be your employer, a hosted provider, or your own organization if you run a self-hosted instance.
What Data PrimeCal Stores
PrimeCal stores the following categories of user data:
| Category | Examples |
|---|---|
| Account identity | Username, email address, first name, last name, profile image |
| Calendar data | Events, titles, descriptions, locations, attendees, dates/times, recurrence rules |
| Preferences | Timezone, language, theme color, display settings |
| Shared access | Which users have access to which calendars, at what permission level |
| External sync tokens | OAuth tokens for connected Google Calendar / Microsoft 365 accounts (stored encrypted) |
| Automation rules | Rule definitions, audit logs of automation execution history |
| Subscription and billing | Plan information, subscription status, payment records (if applicable) |
Where Data Is Stored
PrimeCal data is persisted in a PostgreSQL database. For cloud deployments, the database host is set by your provider. Self-hosted deployments may configure their own database host via the DB_HOST environment variable.
Data is accessed over authenticated API connections using JSON Web Tokens (JWT). Data at rest is protected by database-level access controls managed by the database host.
How to Request Data Deletion
Contact your PrimeCal system administrator to request account deletion and data removal. Administrators can deactivate accounts and, where necessary, permanently delete user data through the admin panel.
For Self-Hosted Deployments
If your organization operates a self-hosted PrimeCal instance, you are the data controller and are responsible for:
- Publishing a Privacy Policy compliant with applicable law (GDPR, CCPA, etc.)
- Configuring appropriate data retention and deletion processes
- Managing consent for data processing
This documentation page describes PrimeCal's technical data architecture, not a binding legal Privacy Policy. A formal Privacy Policy must be drafted by qualified legal counsel and published for your specific deployment context.
Contact
For questions about how your data is used, contact your system administrator or the organization that provides your PrimeCal account.