Privacy

This page covers the Tidsoptimist website and the app. Timesheets are personal data about employees. We do not sell that data.

When you submit the form, Supabase Auth stores the email and company name, and the market, on an unconfirmed user. The company and the admin role are created when you open the link. The email is a sign-in link, not marketing. We do not send newsletters.

Once the account exists, company name and email can be sent to an internal inbox, if one is configured. That happens after the link is opened, not before, and not if no inbox is set. It is not a mailing to you.

In the app we process name, email, and the hours, absence, kilometres, per diem, and project information you enter. That is time data, not a payroll register. Employees see their own time. An admin sees the company’s.

A clock punch can, if the browser has already granted location, store latitude, longitude, and accuracy. It is optional and not required. Those rows are removed when the user is deleted.

Not decided, to be filled in: the controller’s company name and organisation number. Intended roles, which also need confirmation: the customer is controller of employees’ timesheets, and Tidsoptimist is the processor. Legal basis is not filled in.

You can complain to the Swedish Authority for Privacy Protection (IMY) or to Datatilsynet in Norway. Which authority applies depends on the controller, which is not filled in here.

Cookies we set: Supabase sign-in (names starting with sb-, necessary for the session). timlistan-market is set only when you choose a country in the language menu. It lasts one year and remembers that choice. It is not set from the first visit or from the browser language. It is not analytics. timlistan-signup-company and timlistan-signup-locale last two hours and are needed to create the company after the email link. timlistan-invite-hash lasts ten minutes and is needed to finish an invite. tidsoptimist-theme, tidsoptimist-tint, and tidsoptimist-font are set only if someone chooses appearance, last one year, and are not tracking. We set no analytics, advertising, or session-recording cookies.

The last chosen hours can be stored locally in the browser under the name timlistan.lastHours. That is not a cookie and is not sent to us.

Processors: Supabase (sign-in and database), Railway (the app and feature flags), Cloudflare (the domain goes through Cloudflare, which sees visitor traffic), Resend (email from Tidsoptimist). OpenRouter receives what is written to the Assistant, including time data the tools fetch, and forwards it to the model provider (a sub-processor, for example OpenAI or Anthropic). Stripe is not used yet. When billing is switched on, Stripe becomes the processor for payment.

Not decided, to be filled in: where the data is stored, and whether it is transferred outside the EU/EEA. No retention period is set in the product, and one must be filled in. Data processing agreements are not published here, and this text does not claim they are signed.

The page does not load fonts, maps, video, or scripts from other domains. An IP address used to limit repeated attempts is not stored in clear text. It is stored as HMAC-SHA-256 with a secret key on the server. If the key is missing in production, the attempt is refused instead of saving a weak hash. The email address is part of the counter name for signup, invites, and creating the company. The counters are deleted after three hours at the latest. That is not a customer register.

Export: an admin can download submitted timesheets as Excel. An API key with read access can fetch CSV. An employee has no download of their full record.

Deletion: an admin can remove another user. Time rows, clock punches, and the Assistant’s conversations and keys go with them. Assistant audit rows can remain without a user id. Archive closes access but does not delete the data. An admin cannot delete their own account that way. There is no control that deletes the whole company. For correction or deletion beyond that: [email protected].