Last updated 8 November 2026
Cookie Policy
eTime uses a small number of first-party cookies and browser storage that are needed for it to work. On the public pages we ask before counting your visit with AppHelm, our own analytics. We don't use advertising or cross-site tracking cookies.
Cookies we set
| Cookie | What it does | How long |
|---|---|---|
| Session cookie (better-auth.session_token) | Keeps you signed in. | 12 hours, renewed while you use eTime; removed when you sign out |
| Passkey cookie (better-auth.better-auth-passkey) | Holds the one-time challenge while you make or use a passkey. | A few minutes |
| Workplace (etime_org) | Remembers which workplace you're working in, if you belong to more than one. | 1 year |
| Unit (etime_unit) | Remembers which unit you're looking at, in a workplace with more than one. | 1 year |
On secure connections the eTime cookies' names may start with __Secure-. None of these cookies are used on other sites.
Browser storage
- Layout choices (etime.side.collapsed, etime.view.…, local storage): whether the side menu is collapsed and which screens you've expanded.
- Location answer (etime.location-consent, local storage): your yes to the location check at clock-in, if your workplace uses one. Stop sharing removes it.
- Your shifts offline (etime.offline.v1, local storage): your own shifts for the next four weeks, so you can see them without a connection. No colleagues. Removed when you sign out.
- Kiosk pairing (etime.kiosk.device, local storage): only on a tablet set up as a clock-in kiosk, the device token from pairing.
- Menu caches (etime.nav, etime.units, session storage): so the menu doesn't flicker between screens. Gone when you close the tab.
- App shell (service worker cache): the offline page, icons and app files, so eTime can be installed and opens without a connection. Pages with your data are never cached.
- Push subscription: if you turn on notifications, your browser keeps the keys it made for them.
- Examples (etime.demo, local storage): on the public pages, the kind of workplace and country you picked for the examples.
- Analytics choice (etime.analytics, local storage): your yes or no to visit counting on the public pages.
The eTime phone app keeps your sign-in token and push token in your device's secure storage (Keychain on iOS, Keystore on Android).
Third parties
We don't load advertising scripts. These outside services are involved:
- Google Fonts. The web app loads its typeface, Geist, from Google's font service (fonts.googleapis.com and fonts.gstatic.com). Your browser then sends Google your IP address and browser details to fetch the font files. Google says the service doesn't set cookies.
- Cloudflare, which hosts eTime, may set a cookie needed for security and bot protection.
- AppHelm (apphelm.dev, made by Sansavision, as eTime is), only on the public pages and only after you say yes. It records the pages you view, where you came from and where you click, never what you type or the text on the page, and keeps an anonymous id in local storage. No recordings and no ad measurement. Change your mind any time with Privacy choices at the foot of the page.
When you pay or manage billing you're taken to pages run by Stripe, which sets its own cookies under its own policy.
When we ask, and when we don't
The Swedish Electronic Communications Act (lagen om elektronisk kommunikation) lets a service store information on your device without consent only when it's needed to provide a service you asked for. Everything above except AppHelm falls in that group. Visit counting isn't needed, so on the public pages we ask first, and AppHelm isn't even loaded until you say yes. Where cookies involve personal data, our Privacy Policy applies.
Your choices
You can clear cookies and storage in your browser at any time. Blocking the session cookie will sign you out, and blocking the others will limit some features, such as remembering your workplace or seeing your shifts offline.