CalendarConnect™ combines encrypted transport and storage, per-user authorization, database access controls, and deliberately limited calendar-data processing.
HTTPS/TLS
Encrypted in transit
Encrypted at rest
Managed cloud storage
AES-256-GCM
Calendar credentials
Row-level security
Database-enforced access
For availability matching, CalendarConnect™ calls the providers' scheduling endpoints and keeps only busy status and start/end times. The application does not retrieve or display meeting titles, descriptions, locations, attachments, or attendee lists.
Each person authorizes their own Google or Microsoft connection through OAuth 2.0. CalendarConnect™ never collects a calendar-provider password, and it does not request mail, contacts, organization-directory, or administrator access. Access can be revoked by the user at any time.
CalendarConnect™ is served over HTTPS, with TLS protecting data sent between browsers, the application, calendar providers, and payment services. The managed database encrypts stored data at rest. Calendar connection credentials receive an additional application-level layer of AES-256-GCM encryption before storage.
Row-level security is enabled on application tables and policies restrict signed-in users to records they are permitted to access. Administrative roles are stored separately and checked on the server, rather than trusted from browser storage. Calendar connection records are not directly exposed to browser users.
A user can disconnect a calendar in CalendarConnect™ or revoke access in Google or Microsoft. Disconnecting revokes the provider connection and removes the stored connection record. Project owners can also remove a participant's access to a project.
Availability is shared in the context of a specific project and its invited participants. The database and server checks enforce project membership and ownership boundaries, rather than relying only on what is hidden in the website interface.
Subscription checkout, billing details, invoices, and card processing are handled by Stripe. Full payment-card numbers do not pass through or remain in the CalendarConnect™ database. Incoming Stripe updates are accepted only after their signed webhook is verified.
Application data is hosted on managed cloud infrastructure. Access is authenticated, sensitive work runs on the server, and production secrets are kept outside browser-delivered code. CalendarConnect™ does not sell personal information or calendar data.
CalendarConnect™ maintains a public Privacy Policy describing collection, use, sharing, retention, security, and user rights, plus Terms & Conditions covering service use, subscriptions, calendar authorization, and acceptable use.
Organizations can review the exact permissions on the Google or Microsoft consent screen before approval. CalendarConnect™ can respond to security questionnaires and vendor-review requests at security@calendarconnect.net. No certification is claimed unless it has been completed.
The concrete practices behind the promises above — for security questionnaires and vendor reviews.
Evaluating CalendarConnect™ for your organization? Send your security questionnaire, vendor review checklist, or IT questions to security@calendarconnect.net and we will respond directly.
Exactly what CalendarConnect™ can and cannot see.
| Data | Access |
|---|---|
| Free/busy status and time ranges | Used for availability |
| Create calendar events | Used only for one-click booking |
| Meeting titles | Never accessed |
| Meeting descriptions | Never accessed |
| Attendee lists | Never accessed |
| Meeting locations | Never accessed |
| Attachments | Never accessed |
| Mail or contacts | Never accessed |
| Admin/directory access | Never requested |
Review our published policies, or contact us for a security questionnaire and vendor assessment.