Tidpunkt Security
- 1. Hosting and physical security
- 2. Encryption
- 3. Authentication
- 4. Access control within the service
- 5. Access by our staff
- 6. Network security
- 7. Backups and recovery
- 8. Monitoring and logging
- 9. Incident response
- 10. Secure development
- 11. Data minimisation and deletion
- 12. Changes
This document describes the technical and organisational measures SIA "Net service" uses to protect data in Tidpunkt. It is also Annex 2 to our Data Processing Agreement.
It describes what is in place today.
1. Hosting and physical security
- The application, its database and its backups run on Amazon Web Services (AWS) in Frankfurt, Germany.
- Our error-reporting and analytics tools run on servers we operate at Hetzner in Helsinki, Finland.
- Physical security of the data centres is provided by AWS and Hetzner under their own certified security programmes. AWS holds ISO/IEC 27001, SOC 1, 2 and 3 and PCI DSS attestations; Hetzner holds ISO/IEC 27001:2022 certification covering its Helsinki and Falkenstein data centre parks.
- Production and testing run in separate AWS accounts. The testing environment holds no real customer data.
2. Encryption
- In transit. All connections to the web application, the API and the native applications use HTTPS. The web application requires TLS 1.2 or higher.
- Between our systems. Email is handed to our email provider over an encrypted connection, and the connection between the application and its database uses TLS.
- At rest. The database storage and the application server's disk are encrypted by AWS.
- Sensitive fields. Authenticator secrets and recovery codes are additionally encrypted by the application before they are stored.
3. Authentication
- Tidpunkt has no passwords. People sign in with a one-time code sent to their email address, with Google, or with a passkey.
- One-time codes are six digits, valid for 10 minutes, usable once, limited to five attempts, and stored only as a hash.
- A second factor is available to every user: a passkey (WebAuthn) or an authenticator app (TOTP) with single-use recovery codes.
- Sign-in uses the OAuth 2.0 authorisation code flow with PKCE. Access tokens last 15 minutes. Refresh tokens last 30 days, are replaced on every use, and are all revoked if an old one is presented again.
- In the browser, the refresh token is kept in a cookie that scripts cannot read, and the access token is kept in memory only. The native applications keep the refresh token in the operating system's secure storage.
- Deleting an account or turning off two-factor authentication requires a fresh code sent to the account's email address.
- Users can sign out of all other devices.
- A social sign-in is linked to an existing account automatically only when both sides have a verified email address.
4. Access control within the service
- Every workspace is isolated. Each record belongs to one workspace, every query is limited to the workspace of the request, and membership is checked on every request.
- Three roles exist: owner, admin and member. Members can view the workspace and track their own time. Changing projects, customers and rates, viewing other members' time, managing members and managing billing are limited to admins and owners. Only an owner can grant or remove the owner role.
- Requests are rate-limited, with stricter limits on sign-in: three code requests and five code attempts per minute for each email address and network address.
- The API accepts browser requests only from our own web application's addresses.
5. Access by our staff
- Access to production systems is limited to authorised administrators. It is granted through AWS single sign-on and the deployment key, and is removed when the role ends.
- Our employees do not look at the content of customers' workspaces, except at the customer's request, when strictly necessary to operate, secure or repair the systems, or when the law requires it.
- Deployments are made by an automated pipeline that uses short-lived credentials. No long-lived cloud access keys are stored. The production deployment role can be used only from the main branch.
- Application secrets are kept in a dedicated secrets store and delivered to the servers at deployment.
6. Network security
- The database is not reachable from the internet. It accepts connections only from the application server.
- The storage that holds the web application's files is private and reachable only through the content delivery network.
- Infrastructure metrics are exposed only to our monitoring server's address.
7. Backups and recovery
- The production database is backed up automatically by AWS: point-in-time backups for seven days, weekly snapshots kept for 35 days and monthly snapshots kept for 90 days. Backups are encrypted and stored in the same region.
- Deleted data can therefore remain in backups for up to three months.
- The production database is protected against accidental deletion.
- The database runs in a single availability zone in Frankfurt, and backups are kept in the same region.
8. Monitoring and logging
- Application errors are reported to an error-tracking tool we host ourselves. It is configured not to store IP addresses, email addresses or user identifiers. Reports are kept for 365 days.
- Server health (processor, memory, disk and network) is monitored continuously.
- Web server access logs record the network address, browser type and requested address of each request and are kept for 30 days.
- Alerts on server health and application errors are sent to our administrators, who respond.
9. Incident response
- Our administrators are responsible for security incidents. An incident is assessed within 24 hours of our becoming aware of it: what happened, which data and how many people are affected, and what must be done to contain it. Where personal data is affected, we notify the affected customers within 72 hours and the Latvian Data State Inspectorate within 72 hours where the GDPR requires it. Each incident is recorded with its cause and the measures taken.
- We notify affected customers of a personal data breach without undue delay, as set out in the Data Processing Agreement.
- Security reports can be sent to security@tidpunkt.com.
10. Secure development
- Source code is kept in version control on a server we operate.
- An automated pipeline builds every change and runs static checks and the automated test suite. Deployment to production is a separate step started by an authorised employee.
- Releases are deployed without downtime, and the previous version keeps serving requests until the new one is healthy.
- Destructive database commands are blocked in every environment except local development and testing.
- API documentation and debugging output are disabled in production, and error messages do not reveal internal details.
- Payment card data never reaches our systems. It is entered on pages hosted by our payment provider.
- Every change is reviewed in a merge request by a second person before it is merged. Dependency updates are proposed automatically by a bot and go through the same review and test run.
11. Data minimisation and deletion
- The service collects no location, screenshots, keystrokes, or application and website activity.
- Users can delete their own account, and deletion is final.
- Owners can delete their workspace, and users can delete their own account after a seven-day grace period; both remove all personal records. Expired tokens, sessions, invitations and failed jobs are removed on a schedule.
- Workspaces and accounts unused for two years are deleted after a warning.
12. Changes
We may update these measures as the service develops. We will not lower the overall level of protection.
Questions: security@tidpunkt.com