Recipheon Cookie Policy
| Service | Recipheon - website and mobile app |
|---|---|
| Operator / Controller | FIAMEKSO SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ |
| Contact | support@recipheon.com |
| Effective date | 30.08.2026 |
This Cookie Policy describes how Recipheon uses cookies and similar technologies in connection with the use of the Service. In particular, this document covers the Recipheon website, the mobile app, and other digital interfaces where analogous technologies are used.
To the extent that information collected through cookies or similar technologies constitutes personal data, it is also processed under the rules described in the Recipheon Privacy Policy.
1. What cookies and similar technologies are
Cookies are small text files or other data stored on, or read from, the user’s device while they use the Service. Similar technologies include local storage, session storage, and technical session identifiers in the web interface, as well as secure local storage mechanisms in the mobile app, such as SecureStore or equivalent system-provided secure storage, where these are used to maintain sessions, secure sign-in, or remember settings.
2. Legal basis and consent model
Recipheon uses cookies and similar technologies in line with the applicable electronic communications privacy rules, in particular Article 399 of the Polish Electronic Communications Law of July 12, 2024, and, where personal data is involved, also in line with the GDPR. Cookies other than strictly necessary cookies are activated only after valid user consent has been obtained. Consent may be withdrawn or changed at any time.
3. Categories of technologies we use
Necessary – used for the proper operation of the Service, maintaining the user session, ensuring security, remembering privacy settings, handling sign-in, protecting against abuse, and delivering a function explicitly requested by the user.
Analytics – used to understand how users interact with the Service, which features are used, where difficulties appear, and how to improve the interface and performance. This category is optional and requires prior user consent.
4. Solutions currently in use
As of the publication date, in the MVP version Recipheon uses the following categories of tools and technologies:
- technical cookies or analogous mechanisms required for the Service to operate, including session handling, sign-in, storing the cookie decision, preventing abuse, and protecting account security;
- Microsoft Clarity in the web layer and, where implemented, Clarity for Mobile Apps in the mobile app, as analytics tools used to analyze user behavior, detect interface issues, and improve the usability of the Service. In the web layer, Microsoft Clarity is activated only after consent for analytics cookies has been obtained, and in the mobile app in accordance with the adopted consent model for similar technologies and analytics tools.
5. Categories and retention table
| Category | Name | Provider | Purpose | Retention period |
|---|---|---|---|---|
| Necessary | accessToken (secure storage in the mobile app) | Recipheon | maintain the authenticated mobile session and authorize API requests | until token expiry or logout; generally up to 30 minutes |
| Necessary | refreshToken | Recipheon | maintain the sign-in session (httpOnly cookie on web / secure storage in the mobile app) | until token expiry or logout; generally up to 30 days on web and up to 365 days in the mobile app |
| Necessary | recipheon.language | Recipheon | remember the interface language in the web version | 365 days |
| Necessary | recipheon.theme | Recipheon | remember the interface theme on web and in the mobile app | until the setting is changed; on web generally up to 365 days |
| Necessary | cookie_prefs (local storage / secure storage) | Recipheon | store cookie consent settings | until changed or removed by the user |
| Necessary | isGuest (local storage / secure storage) | Recipheon | remember guest mode status | until sign-in, logout, or user data removal |
| Analytics | Microsoft Clarity cookies and identifiers (including _clck, _clsk, CLID, ANONCHK, MR, MUID, SM, and mobile Clarity identifiers) | Microsoft | heatmaps, session replay, UX analytics | according to the current Microsoft Clarity documentation and browser or device settings |
6. How the consent mechanism works
On the first visit, the user receives a cookie banner with a real choice between at least: “Accept”, “Reject optional”, and “Settings”. The acceptance, rejection, and settings options are available directly in the banner.
A user’s failure to take action does not constitute consent.
Optional categories are disabled by default.
Withdrawing consent or changing settings is as easy as giving consent and is available at all times from within the Service.
Until the appropriate consent is obtained, analytics cookies and scripts are not set or activated.
The system stores the user’s decision, the date it was made, the notice version, and the scope of consent to demonstrate compliance with applicable rules.
7. Microsoft Clarity
Microsoft Clarity may collect, once consent has been granted to the extent required for the relevant technical layer, information about how the Service is used, including page views, transitions between screens, interface interactions, errors, and technical data of the browser, device, or app. The scope of the data and the way the tool operates depend on the current Clarity configuration, the implemented web or mobile variant, and the settings of the Service operator.
Clarity is implemented in a way that respects the user’s consent choice. If the user refuses analytics consent or later withdraws it, the script remains inactive and does not collect analytics data.
8. Managing cookie settings
The user may at any time:
- accept optional cookies;
- reject optional cookies;
- change a previously selected decision;
- delete cookies in browser or device settings, bearing in mind that this may affect the operation of some Service functions.
Detailed information about managing cookies in a browser can be found in the browser or device manufacturer documentation.
9. Changes to the Cookie Policy
The Cookie Policy may be updated, in particular, in the event of changes in law, technological changes in the Service, implementation of new tools, or a change of providers. The current version is published in the Service together with its effective date.
Effective date: 30.08.2026.