Sahl/Cal

Security

How we protect your calendar and your guests.

What SahlCal does to keep data safe, where it lives, and what we don't offer yet — stated plainly.

What we do

Encrypted in transit

Every page, booking and API call is served over HTTPS.

Calendar tokens encrypted at rest

Google and Microsoft access tokens are encrypted with AES-256-GCM before they are stored.

Only the calendar access we need

Google: read events to find busy times, and create the events SahlCal makes. Microsoft: read and write calendar events for the same purpose. Nothing else in your account.

Workspace isolation

Every query is scoped to your personal account or your team workspace. Team roles (owner, admin, member) control who can change what.

Web protections

CSRF tokens on form submissions, a strict Content Security Policy and standard security headers on every response.

Guest privacy

Guests never need an account. Reschedule and cancel links use unguessable tokens, and poll voters' emails are never shown publicly.

Where your data lives

SahlCal runs on these providers. Your database is hosted in the European Union (Frankfurt, Germany).

Neon
PostgreSQL database — EU (Frankfurt)
Vercel
Application hosting
Maileroo
Confirmation and reminder emails
Google / Microsoft
Calendar sync, only when you connect a calendar
Groq
AI forms and meeting briefs, only if you use them

Full details are in our privacy policy.

What we don't offer yet

  • We don't hold SOC 2 or ISO 27001 certification today.
  • We don't offer hosting inside the GCC today; data is stored in the EU.
  • Enterprise customers can contact us for security questionnaires and contract terms.

Report a security issue

Found a vulnerability? Email us and we'll respond as quickly as we can. Please don't test against other people's accounts or data.

support@sahlcal.com