Skip to content
DE

What your browser stores

This website stores two entries, the application a few more depending on what you use. The two here never leave your device. In the application the session goes to our server, because signing in would not work otherwise. Anything else that reaches the server is noted below with the entry concerned.

Why there is no banner to click away

German law (§ 25 Abs. 1 TDDDG, implementing the ePrivacy Directive) requires consent for anything stored on your device that is not strictly necessary. Tiveo stores only what is strictly necessary, and the full list is below. We could show a banner anyway. It would ask permission for something that does not happen, which amounts to a false claim. It would also get people used to clicking permissions away unread, and that habit is what the rule was written against.

Colour scheme

Key "tiveo-theme", value "light" or "dark". It is only there if you have used the switch; otherwise we follow your system setting and store nothing at all. It stays until you clear site data and is never sent to a server.

Opting out of analytics

Key "tiveo-analytics", value "off". It is only there if you have opted out. So it is the opt-out, of all things, that stores something. Without this entry we would not know on your next visit that you do not want to be counted.

The application on app.tiveo.de

The application runs on its own address and therefore in its own storage. What is kept there is invisible to these pages, and the other way round. If you have never signed in, none of it exists in your browser. The session ("sb-…-auth-token") is kept there, as otherwise you would have to sign in again on every page. It expires, and it is removed when you sign out. Of what every user has in the browser, it is the only thing that reaches a server at all, because a sign-in cannot work any other way. Alongside it there are three conveniences that never leave your device. "tiveo-sprache" holds your language choice and "tiveo:farbschema" the colour scheme (with a different key and different values from above, because it is a different storage). "tiveo-firma" remembers which company you last had open. If you only work in one company, you will never notice it. Also kept in the browser only: "tiveo:schulferien", value "aus" (off). It is present only if you have switched school holidays off in the calendar. They are shown by default, and that needs no entry. Switch them back on and it disappears. It is necessary because otherwise that choice would be lost on every page load. It belongs to the view rather than to you as a person, which is why it lives in the browser and not in your profile. It reaches no server, and nobody can be recognised by it; all it says is that a calendar should be narrower. If you administer a company, there is also "tiveo:einrichtung". It records whether the setup guide is open, minimised or hidden on this device and which step you were on last, per company. Like the colour scheme it is a preference of this screen and reaches no server. What the company has decided, such as its industry or skipped steps, is stored with the company in the database instead. Once you have opened What’s new, there is "tiveo:neuigkeiten" with two points in time: when the page was last open and from when an entry counts as unread there. The dot next to "What’s new" in the menu depends on it. It applies to this browser only and reaches no server. Once you have collapsed or expanded the sidebar on the left, there is "tiveo:leiste" with "schmal" (narrow) or "breit" (wide); the sidebar also remembers which of its groups you collapsed. Both are stored per signed-in person under their own name (with your ID after the colon). Without it, the sidebar follows the width of the window. It applies to this browser only and reaches no server. Only on a phone or tablet, and only if you dismissed the hint "Get Tiveo as an app on your phone": "tiveo:app-hinweis" with the date of that click. It keeps the hint from coming back on this device. It applies to this browser only and reaches no server. Only for the operator of Tiveo, on the dashboard of the platform administration: "tiveo-dashboard" with two points in time, namely when the dashboard was last open and from when things are marked as new there. Customers never have this entry. Only while you look at the app as another person ("View as" in the account menu): "tiveo-ansicht" in this tab's session storage, holding that person's ID, name and role, so the view survives a reload. It is gone after "Deactivate", when you sign out or when you close the tab. Only if your company has switched on automatic clocking on the PC and you switch it on for this PC in the clock at the top: "tiveo:pc-stempeln:…" with the ID of your membership in the company and the work location. While it exists, Tiveo checks in from this PC every minute so that clocking in and out is recorded. Switching it off in the clock deletes it. Only if you start a trip in the vehicle logbook: the database "tiveo-fahrten" (IndexedDB). "Start trip" and "End trip" wait in it while there is no network and, only for business trips with recording switched on, the route's location points. The application sends them to our server as soon as it can and deletes them here once they are sent and the trip has ended. Whatever could not be sent disappears after 30 days at the latest. Without the logbook it does not exist. Only when switching from Excel, if you look at your workbook under /umstieg: the database "tiveo-umstieg" (IndexedDB) with that file, so that you need not look for it again after creating your account. It only reaches a server if you explicitly take it over in the import. It is deleted after the import and otherwise no longer used after seven days. Only on a tablet that your company has set up as a terminal for clocking in: "tiveo:terminal" holds this device's access key and its name. On that device it replaces a person's sign-in and can be revoked in the administration at any time; the device then deletes it itself. If the network fails there, the terminal keeps entries in "tiveo:terminal-warteschlange", with the time, clock number and PIN or badge code, because the person can only be checked when the entries are sent later. Clock number, PIN and badge code are stored encrypted so that only our server can open them; the terminal keeps the public key for this in "tiveo:terminal-schluessel". Once the entries are sent, the queue is empty. If the terminal reads badges with the camera, it remembers in "tiveo:terminal-kamera" which of the tablet's cameras it uses. Only the camera's ID is stored, never an image. Other devices have none of these entries.

Sign-in page and payment pages

On the sign-in page of the application (when you sign in with a password, register or request a sign-in link) and on the contact form, Cap checks whether a person is using the page. For this, your browser loads a small check page from cap.tiveo.de as an invisible frame. It runs on our own server and stores nothing in your browser. Tiveo itself stores nothing for it either: the result of the check is kept only in the memory of the open page and disappears with it. The privacy policy has the details. Payment takes place on Stripe’s pages (checkout.stripe.com and billing.stripe.com). What is stored in your browser there is up to Stripe; Stripe’s own information applies.

The analytics itself

We run Matomo ourselves on our web space at Serverprofis GmbH and share nothing with third parties. It runs without cookies: the instruction "disableCookies" comes before the first page view in the source, so the usual Matomo cookies (_pk_id, _pk_ses) are never set in the first place. Nor does the measurement read device properties such as screen size; "disableBrowserFeatureDetection" is there for that as well. If you send "Do Not Track" or a Global Privacy Control signal, you are not counted, and the measurement file is not even loaded. You can also opt out explicitly on the privacy page.

How to get rid of all of it

Clear site data for tiveo.de and app.tiveo.de in your browser. Until then the entries stay; the session is also removed when you sign out. Afterwards nothing is left, your opt-out included, so you would have to opt out again.