COOKIE EN
Cookie
Policy
Necessary cookies. Secure operation. No tracking.
Language notice
This Cookie Policy is a translation of SIMINEO's German Cookie Policy. The German version is the primary and authoritative version. This translation is provided to make information about SIMINEO's use of cookies and browser storage available in English.
1. Purpose of this Cookie Policy
This Cookie Policy explains which cookies and other browser-side storage technologies SIMINEO uses in connection with the operation of the service.
The purpose of this Policy is to explain in a clear and understandable manner:
- which cookies SIMINEO uses;
- for what purposes and for what storage periods they are used;
- which browser-side storage technologies, such as localStorage and sessionStorage, are used;
- which of these technologies are used for the operation, security, or functions expressly used by the user;
- whether analytics, marketing, advertising, or tracking technologies are used;
- how cookies and browser-stored data can be managed through browser settings.
2. What are cookies and browser-side storage technologies?
A cookie is a small data file that a website stores on the user's terminal device through the browser and can read again during later visits. Cookies may serve, in particular, session management, security, or other technical functions.
In addition to cookies, websites can store technical information in other browser-side storage areas such as localStorage or sessionStorage. These storage technologies are technically distinct from cookies but can likewise store information on the user's terminal device.
Not every form of browser-side storage serves analytics, advertising, or tracking purposes. SIMINEO currently uses browser-side storage only for the technical, security-related, and functional purposes described below.
3. Use by SIMINEO
SIMINEO currently uses its own first-party cookies and, to a limited extent, localStorage and sessionStorage for the operation, authentication, security, and certain functions of the service used by the user.
Under the current technical setup, SIMINEO does not use analytics, marketing, advertising, or tracking cookies on its own pages and does not use corresponding browser-side analytics or advertising identifiers.
In particular, SIMINEO currently does not use:
- Google Analytics cookies;
- user tracking based on Google Tag Manager;
- Meta (Facebook) Pixel tracking;
- Hotjar or comparable external services for individual-level behavioural analysis;
- advertising or marketing cookies;
- tracking pixels or comparable browser-side tracking identifiers for analytics or advertising purposes.
Independently of this, SIMINEO creates its own server-side, data-minimised reach, usage, and performance statistics. No analytics or marketing cookies and no analytics or advertising identifiers stored in localStorage or sessionStorage are used for this purpose. Further details are provided in the Privacy Policy.
Where the storage of information on a terminal device or access to information already stored there is strictly necessary to provide a digital service expressly requested by the user, consent may not be required under the applicable statutory conditions. If SIMINEO introduces technologies in the future whose use requires consent, they may only be used in compliance with the applicable consent requirements.
4. Cookies used by SIMINEO
SIMINEO currently uses three of its own first-party cookies:
| Cookie name | Purpose | Storage period | Category |
|---|---|---|---|
seeme_auth |
Authentication and management of the logged-in user session | Regular browser: session cookie; PWA use: up to 72 hours, and again up to 72 hours after successful session renewal | Necessary |
seeme_csrf |
Protection against unauthorised state-changing requests (CSRF protection) | Regular browser: session cookie; PWA use: up to 72 hours, and again up to 72 hours after successful session renewal | Necessary, security-related |
seeme_admin_gate |
Additional protection of administrative API access | Session cookie | Necessary, administrative |
These cookies are not used for advertising, marketing, or individual-level behavioural analysis.
5. Login cookie (seeme_auth)
The seeme_auth cookie serves the authentication and management of a logged-in user session.
The cookie:
- is protected by HttpOnly and therefore cannot be read by ordinary JavaScript;
- is transmitted exclusively over a secure HTTPS connection in the production environment;
- is used with SameSite Strict;
- applies to the
/path; - is set as a session cookie during a regular browser login;
- may be set persistently for up to 72 hours for a session operated as a PWA;
- may be set again for up to 72 hours following a successful PWA session renewal.
In a regular browser session, the authentication token used in the cookie has a technical validity period of generally up to six hours. For a PWA session, a technical validity period of up to 72 hours is provided.
The authentication JWT is not stored in either localStorage or sessionStorage.
6. CSRF protection cookie (seeme_csrf)
The seeme_csrf cookie forms part of the protection against unauthorised state-changing requests that could be triggered on behalf of a user.
This cookie:
- serves security purposes;
- does not contain login credentials or an authentication JWT;
- is readable by JavaScript for the intended browser-side security checks and is therefore not protected by HttpOnly;
- is transmitted exclusively over HTTPS in the production environment;
- is used with SameSite Strict;
- applies to the
/path; - is used as a session cookie during a regular browser session and with a duration of up to 72 hours during a PWA session;
- may be set again for up to 72 hours as part of a successful PWA session renewal.
7. Administrator cookie (seeme_admin_gate)
The seeme_admin_gate cookie serves exclusively as additional protection for administrative access and is not required during the normal use of an ordinary user account.
This cookie:
- is protected by HttpOnly;
- is transmitted exclusively over HTTPS in the production environment;
- is used with SameSite Strict;
- applies exclusively to the administrative API path
/api/admin; - is used as a session cookie;
- contains a technically signed administrative security value;
- is not used for advertising, marketing, or individual-level behavioural analysis.
8. localStorage and sessionStorage
In addition to cookies, SIMINEO uses, to a limited extent, the localStorage and sessionStorage areas provided by the browser.
8.1 localStorage
Currently, the following keys may in particular be used:
| Key | Purpose |
|---|---|
seeme_lang | Storage of the selected language |
seeme_auth_state_event | Technical synchronisation of authentication state changes between browser tabs |
simineo_pending_logout_v1 | Technical support for a logout process that still needs to be completed |
simineo_company_posts_view | Storage of a functional view setting for company posts |
seeme_follow_mode | Storage of a functional view setting in the Follow area |
Data in localStorage generally remains stored until it is overwritten or removed by the application, the user deletes the relevant website data, or the browser removes it for other technical reasons.
8.2 sessionStorage
Currently, the following keys may in particular be used:
| Key | Purpose |
|---|---|
simineo_guest_return_to | Temporary storage of a navigation destination so that a user can return to the intended location after a technical process |
admin2faChallengeId | Temporary technical identifier within the technically provided administrative two-factor login process, insofar as that process is used |
sessionStorage is generally limited to the respective browser-tab session and is discarded by the browser no later than when that session ends, unless the application removes the relevant value earlier.
8.3 No storage of the login token in browser storage
SIMINEO does not store the authentication JWT in localStorage or sessionStorage.
SIMINEO also does not store there:
- bank card data;
- complete payment data;
- analytics or advertising identifiers.
9. Paddle payment service
SIMINEO uses the Paddle payment service for subscriptions, payments, invoices, and the customer portal. Parts of a payment process or subscription management may take place on interfaces provided by Paddle.
SIMINEO itself does not store bank card numbers, complete card data, or other payment instrument data in its own localStorage or sessionStorage.
Paddle may use its own cookies and similar technologies on its own websites and payment interfaces. Paddle's own information and choices apply to such technologies set or read by Paddle itself.
10. External services
The following external services, among others, are used in the broader technical and business operation of SIMINEO:
- Paddle – payment, subscription management, and customer portal;
- Google Workspace – sending transactional emails;
- Hetzner Cloud – server and hosting services;
- Google Search Console – management of website indexing and visibility in Google Search.
The mere use of such an external service does not mean that the service sets cookies in a SIMINEO user's browser. In particular, SIMINEO uses Google Search Console as an administrative tool and not as a browser-side tool for individual-level behavioural analysis or advertising tracking on SIMINEO.
Where a user directly accesses an external interface of a third-party provider, that third party's own privacy and cookie rules may apply there.
11. Analytics, marketing, and tracking technologies
Under the current technical setup, SIMINEO does not use analytics, marketing, advertising, or tracking cookies on its own pages.
In particular, SIMINEO currently does not use:
- analytics cookies;
- marketing cookies;
- advertising cookies;
- tracking pixels for analytics or advertising purposes;
- external browser-side services for individual-level behavioural analysis;
- browser-side analytics or advertising identifiers in localStorage or sessionStorage.
SIMINEO's own server-side, data-minimised reach, usage, and performance statistics are created independently of such browser-side analytics or marketing technologies. Further details on the data processed, purposes, legal bases, and retention periods are provided in the Privacy Policy.
If additional analytics, marketing, advertising, or tracking technologies requiring consent are introduced in the future, SIMINEO will implement the necessary legal and technical measures before their use and update this Policy accordingly.
12. Significance of technically necessary and functional storage
The cookies and browser-side storage described in this Policy support, in particular:
- authentication and management of logged-in sessions;
- protection of the user account;
- CSRF protection;
- security of administrative access;
- technical synchronisation of authentication status;
- storage of the selected language and certain functional view settings;
- technical navigation and return within the service;
- temporary technical processes, insofar as they are actually used.
If necessary cookies or necessary browser-side storage functions are blocked or deleted, login, session management, security checks, or individual expressly used functions of the service may in particular be impaired.
13. Management in the browser
Users can generally manage cookies and other stored website data through their browser settings. Depending on the browser, they may in particular:
- view stored cookies and website data;
- delete cookies and local website data;
- block the use of some or all cookies;
- configure how the browser handles cookies and website storage.
Deleting or blocking technically necessary data may result in SIMINEO's login, security, session management, or other functions not working or not working fully.
14. Updates and status of this Policy
SIMINEO updates this Cookie Policy in particular where the cookies, browser-side storage technologies, or their purposes actually used materially change or where new legal requirements make this necessary.
This applies in particular to the introduction of new analytics, marketing, advertising, or tracking technologies or new browser-side identifiers.
Status of this Cookie Policy: 30 August 2026.
15. Official external references
The following links refer to official information or information provided by the respective provider that may be relevant in connection with this Cookie Policy.
16. Contact
If the user has questions regarding this Cookie Policy, they may contact the provider using the contact details provided on SIMINEO's contact page.