A plain description of how Calynq protects your data today, and what we have not done yet.
Data is encrypted in transit with TLS and encrypted at rest by our database provider.
Every table that holds customer data is protected by row-level security, so a signed-in user can only read and change what their account, organization and role allow.
Google and Microsoft calendars connect through the providers' OAuth flows. You choose which calendars count toward your availability, and you can disconnect at any time.
We keep personal data while your account or organization is active and delete it afterwards unless the law requires us to keep it, for example billing records. Some operational records are removed on a schedule: message logs and routing-form responses after 90 days, audit logs after 24 months.
Data processing and subprocessors
You can download a copy of your data yourself under Settings, Account, Privacy and data, and delete bookings and calendar connections whenever you like.
The service providers that help us run Calynq, and how we process data on behalf of business customers, are listed on our data processing page. If your organization needs a signed addendum, contact us.
Read the data processing page
If you believe you have found a security problem in Calynq, email support@calynq.com with "Security" in the subject line and enough detail to reproduce it. Please give us a reasonable time to fix it before sharing it publicly, and do not access other people's data. We will acknowledge your report and keep you informed.
Calynq does not hold a SOC 2 report or ISO 27001 certificate today. An independent SOC 2 audit is on our roadmap. If your procurement process needs one, tell us so we can prioritise it.