Mit vertrauen verbinden
Tausende von Unternehmen und Millionen von Menschen vertrauen Calendly für sichere, sorgenfreie Kalenderverbindungen.
How we keep your data secure
Calendly has a dedicated team of compliance and security experts to help meet our rigorous privacy and security standards. Our policies, procedures, and technologies enable us to comply with and exceed industry standard requirements.
|Google's physical infrastructure is hosted and managed within their secure data centers. Calendly leverages all of the platform’s built-in security, privacy and redundancy features. Google continually monitors its data centers for risk and undergoes assessments to ensure compliance with industry standards. Google’s data center operations have been accredited under: ISO 27001, SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II), PCI Level 1, FISMA Moderate and Sarbanes-Oxley (SOX). Calendly backups are replicated for high redundancy.|
|Encryption||Data that passes through Calendly is encrypted, both in transit and at rest. All connections from the browser to the Calendly platform are encrypted in transit using TLS SHA-256 with RSA Encryption. Calendly requires HTTPS for all services. Calendly uses HSTS to ensure browsers interact with Calendly only over HTTPS and is on the HSTS preloaded lists for both Google Chrome and Mozilla Firefox.|
Security and compliance programs
|Background checks||All Calendly employees go through a thorough background check before hire.|
|Training||While we retain a minimal amount of customer data and limit internal access on a need-to-know basis, all employees are trained on security and data handling to ensure that they uphold our strict commitment to the privacy and security of your data.|
|Confidentiality||All employees sign a confidentiality agreement before they start at Calendly.|
|Reliability and redundancy|
|Business continuity and disaster recovery||We have business continuity and disaster recovery plans in place that replicate our database and back up the data onto multiple cloud providers to ensure high availability.|
|Software development lifecycle|
|Routine audits||Calendly continuously scans the product for service interruptions, performance degradation and security vulnerabilities to immediately alert our engineers and take action when an incident has been detected.|
|New releases||New releases to the Calendly platform are thoroughly reviewed and tested to ensure high availability and a great customer experience. Changes to our codebase are required to include unit tests, integration tests and end-to-end tests. Changes are run against our continuous integration server, which enables us to automatically detect any issues in development.|
|Quality assurance testing||Once a changeset is completed, it is manually peer reviewed by one or more members of the engineering team. The changeset is then evaluated and manually tested by our quality assurance team to thoroughly test areas of expected impact, regression test and further evaluate the user experience.|
|Continual monitoring||After a changeset is released, we continue to monitor application exceptions and log exceptions. These exceptions are regularly reviewed and triaged for resolution. Performance impacts of the changeset are monitored through several monitoring services.|
|Mobile device management (MDM)||We secure our employees' machines and laptops using mobile device management to ensure that each device follows our information security standards, including encryption.|
|Malicious software prevention||Our employees’ equipment is defended by industry-leading, next-generation anti-malware software, and we run routine phishing tests to further educate and train employees.|
|Vulnerability scanning||We keep our systems up to date with the latest security patches and continuously monitor for new vulnerabilities through compliance and security mailing lists. This includes automatic scanning of our code repositories for vulnerable dependencies.|
Application security measures
|Login credential protection||For Google Calendar and Office365 calendar connections, Calendly never collects passwords. Using a secure OAuth connection to sync these calendars only grants Calendly access to your calendar account through a secure token from your email provider. This also enables you to set additional security precautions with that provider including 2-factor authentication (2FA). For iCloud users, we recommend setting up 2FA and application-specific passwords. For organizations with enhanced security requirements, Calendly supports SAML-based Single sign-on (SSO) with the following identity providers: Okta, Ping Identity, Azure, OneLogin, and Auth0.|
|User provisioning and deprovisioning||Calendly offers seamless OAuth through Google Calendar and Office365, calendar connection is eliminated automatically when your account is canceled. For larger organizations, Calendly supports automatic provisioning and deprovisioning via SCIM if using one of our supported identity providers: Okta, Ping Identity, Azure, OneLogin, and Auth0.|
Vertrauen von mehr als 50.000 der weltweit führenden Organisationen
Zertifizierungen und Konformität
SOC 2 Typ 2
SOC 2 ist der Goldstandard für die Einhaltung von Sicherheitsrichtlinien. Wir haben für unsere Verpflichtung, Sicherheitsrichtlinien und -verfahren festzulegen und einzuhalten, die SOC-2-Typ-2-Zertifizierung erhalten.
Wir nehmen Ihnen die Arbeit ab, sich mit anderen zu verbinden, damit Sie mehr erreichen.