Privacy policy

In short: we don't collect your data. The iPhone app keeps your hours on the phone, or sends them to your workplace's own Timetap server - never to us. No analytics, no advertising, no tracking.

Last updated 31 October 2026.

This policy covers four things: the iPhone app, the Timetap server, the address service (api.timetap.no) and this website. Who is responsible is at the bottom.

1. The iPhone app

On the phone alone

Your hours, projects and settings are stored only on your phone, in the app's own storage (shared with its widgets). Nothing is sent anywhere. Deleting the app deletes them.

Connected to a Timetap server

The app sends to your workplace's own Timetap server - never to us:

• when you clock in and out, and the project;
• the tags it reads;
• the times of days worked away from the office, marked remote - a yes or no, never a place.

The connection's key is kept in the phone's Keychain; the server keeps only a one-way hash of it. Your workplace runs that server and is responsible for the data on it.

What the app never does

• No analytics, no advertising, no tracking.
• No third-party services or SDKs, and no account with us.
• It asks for one permission: NFC, to read Timetap tags.
• It doesn't use your location. The optional automatic clock-in is the iPhone's own Shortcuts automation, which only tells Timetap "clock in".

2. The Timetap server

The server is installed and run by your workplace, not by us. We never see its data; your workplace is responsible for it (the controller). It stores:

• each person's name, login (the password only as a salted hash), roles and weekly hours;
• NFC tag numbers, clock-in and clock-out times, projects and the comments people type;
• absences - the type and the day only, never a reason or diagnosis;
• a history of changes to the hours.

Each person sees their own hours. Admins see everyone's and can comment, but can't change them.

The server contacts nothing on its own. It only reaches out for what the workplace sets up or asks for: Check for updates (asks GitHub, only when pressed), the https certificate (Let's Encrypt), the address service below, and encrypted backups to the place the workplace chooses.

3. The address service (api.timetap.no)

For servers that use a Timetap address such as name.timetap.no. It runs on Cloudflare (Workers and DNS) and stores:

• the name, and the server's local network address (such as 192.168.1.20 - only private addresses are accepted);
• a one-way hash of the name's secret;
• when the name was registered and last used, and which invitation code was used;
• invitation codes, with a note the maintainer writes (for example which workplace it was for).

Public by nature: the name and its local address are in public DNS (kari.timetap.no → 192.168.1.20), and each certificate's name is listed in public Certificate Transparency logs. A local address means nothing outside that network.

A name nobody has used for 180 days is released and its record removed. Cloudflare processes requests, including the requesting IP address, to run the service.

4. This website (timetap.no)

• Static pages: no cookies, no analytics, no tracking, and no fonts or scripts from anywhere else.
• Hosted by Cloudflare (Pages), which processes visitors' IP addresses to deliver the pages and protect against attacks.
• The demo runs entirely in your browser. Nothing you do in it leaves the browser.
• The site remembers your language choice (English or Norwegian) in your browser's local storage. It is never sent anywhere.
• Email to contact@timetap.no and code@timetap.no is handled by Fastmail.

Who is responsible

• For this website, the iPhone app and the address service: Jon-André Hakvåg, Norway - contact@timetap.no.
• For the data on a workplace's Timetap server: that workplace.

Questions about your data, or want something removed from the address service? Email contact@timetap.no. For hours on your workplace's server, ask your workplace.

Changes

• 31 October 2026: first version.