Third Party Index

Snapshot 25955

Document
Security page
URL
https://www.teamoclock.com/legal/security
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
78526 bytes
SHA-256 (raw)
6f0917db74b975834f63e5408836080c06b9c2a9b93b7c3a85ae7efe52c309d6
SHA-256 (normalized text)
0c07eb8b4b26a96497280c02855e93b0fff62678169b00f9f860ecf6661578ad

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Features Meetings
Retrospective
Daily standups
Planning poker
Tools
Icebreaker Add-on
Metrics
Hill Charts
AI-Assist
Agility Cards
Integrations
Solutions Features Retrospectives
Daily standups
Planning poker
Icebreaker Add-on
AI-Assist
Metrics
Hill Charts
Agility Cards
Slack
Microsoft Teams
Atlassian Jira
Asana
Linear
Basecamp
Pricing Login Get StartedStart
By Industry
Finance and Banking
Healthcare and Pharmaceuticals
Retail and E-commerce
Manufacturing
Telecommunications
Media and Entertainment
Automotive Industry
Education
Consulting Services
Government and Public Sector
Real Estate and Construction
By Use Case
Engineering Manager
Tech Lead
Product Manager
DevOps Team
Remote Team
Hybrid Team
Security
Last modified: May 28th, 2024
Data center
Team O'clock is hosted on render.com, a PaaS owned by Render Services, Inc. Our data centers operate on the Europe (Frankfurt) region of Amazon Web Services, being accredited under ISO 27001, SOC 1 and SOC 2/SSAE 16/ISAE 3402, PCI Level 1, FISMA Moderate and Sarbanes-Oxley (SOX).
Learn more about Render's security here.
Data encryption,
in transit and at rest
All internal or external service communications (including third parties, such as Slack, Microsoft Teams or Jira) are encrypted via SSL using TLS1.2+ protocols. Data is encrypted at rest with AES-256, block-level storage encryption.
Data sharing
Data sharing occurs when integrations are enabled. Team O'clock may retrieve user account details (name, email and avatar), only when a user is using the integration. No Team O'clock data is shared with the integrations, unless for updating data on the integration's side, such as standup notes, retrospective action items, and estimations.
Data retention
Application data is retained until the termination of the account. When a Team O'clock organization or user account is deleted, no data is retained. Server logs are retained for 7 days, with all personal data anonymized before storage. Audit logs, used for storing application actions, are retained for a year, with all personal data anonymized before storage.
User authentication
Users are authenticated through Slack, Microsoft or Google social logins, or by using passwordless email authentication. No passwords are stored on our servers. In the case of passwordless authentication, the user is sent an one-off expiring token to the provided email address, that can be used over a very limited amount of time in order to enter the platform.
Single Sign On (SSO)
Per organization SSO is supported using SAML 2.0, such as Okta. Additional SSO options include authentication through Slack, Microsoft and Google accounts.
Confidentiality
All employees are restricted by regulations to maintain confidentiality. Access to data is restricted, unless required in order to provide technical support.
Incident management
In the unfortunate event of security breach or unauthorized access to user data, the company will inform you within 72 hours, in compliance with GDPR.
Payments
All payments are processed by our subscription partner Paddle. No credit card information is stored on our servers.
🙏 Special thanks to:
Blackktech
Dava Wardana
for helping us identify issues with our service.
Information
Support
Pricing
Developers
Changelog
Retrospective guide
Company
About us
Blog
Comparisons
Contact us
Status
Free stuff
Remote Scrum Guide
Retrospective ideas
Meeting templates
Simple timer
"Agile" against agility
Lean Tarot
Legal
Security
Privacy policy
Terms of use
Sub-processors
Team O'clock © 2026 Team O'clock
Connect