QUINAPSE LEGAL
Cookies Policy
Last updated: 2026-05-18 Effective date: 2026-05-18
This Cookie Policy explains how Quinapse uses cookies, local storage, and
similar device-storage technologies on the Quinapse website
(quinapse.com, admin.quinapse.com, docs.quinapse.com). It is a
companion to our Privacy Policy.
The Quinapse mobile application does not use browser cookies. This policy applies only to the website surfaces listed above.
1. What are cookies?
A cookie is a small text file that a website places on your device. "Local storage" and "session storage" are similar technologies built into your browser. Together we refer to them as "device-storage technologies."
Cookies can be:
- first-party (set by the website you are visiting) or third-party (set by another domain embedded on the page);
- session (deleted when you close the browser) or persistent (kept until they expire or you clear them);
- strictly necessary (required to operate the site), functional (remember preferences), analytics (measure usage), or advertising (track you across sites for ads).
2. What Quinapse uses, and what it does not
| Surface | Technology | Type | Purpose | Retention |
|---|---|---|---|---|
admin.quinapse.com |
localStorage key quinapse_admin_token (self-hosted JWT, not a cookie) |
Strictly necessary | Keep an admin user signed in across page reloads | 24 hours from sign-in; cleared on sign-out or browser storage clear. AWS Cognito is not used. |
admin.quinapse.com |
Local storage (TanStack Query cache, UI preferences) | Strictly necessary / functional | Reduce duplicate API calls; remember last-opened tab | Until you clear browser storage |
docs.quinapse.com |
None at this time | — | — | — |
quinapse.com (marketing / legal) |
None at this time | — | — | — |
We do not use:
- third-party analytics cookies (no Google Analytics, no Mixpanel, no Hotjar);
- advertising or retargeting cookies;
- cross-site tracking pixels;
- social-media sharing trackers;
- any cookie or storage that profiles you for marketing purposes.
If this changes — for example, if we add a self-hosted privacy-respecting analytics tool — we will update this policy and, where required by the ePrivacy Directive (2002/58/EC) as transposed by your member state, request your prior consent through a cookie banner.
3. Legal basis under EU law
Under Article 5(3) of the ePrivacy Directive and your national implementation (for example, §25 TTDSG in Germany or Article 82 of the French Data Protection Act):
- Strictly necessary cookies and equivalent storage technologies do not
require consent. We rely on this for the session token listed in §2 (stored
in
localStorage, not as a cookie). - All other categories require your prior, informed, freely given consent — which we currently do not need to request because we do not set any cookies in those categories.
4. Managing cookies
You can:
- block or delete cookies in your browser settings (Chrome, Firefox, Safari, Edge all support per-site cookie control);
- use private / incognito mode to limit persistent storage to the session;
- sign out of
admin.quinapse.comto remove the session token.
Blocking the strictly necessary cookies on admin.quinapse.com will sign
you out and prevent the admin app from working. The reader experience in
the Quinapse mobile app is unaffected by browser cookie settings.
5. Do Not Track
We honour the "Do Not Track" signal in the only way that is currently meaningful: we do not perform cross-site tracking regardless of the signal.
6. Changes to this policy
We will update this policy when the cookies set by our surfaces change. Material changes will be reflected in the table above and called out via the "Last updated" date.
7. Contact
Questions about cookies or device-storage: legal@quinapse.com.
This Cookie Policy is informational and reflects the current technical state of the Quinapse website surfaces. The authoritative list of cookies that your browser is actually storing is always the one shown in your browser's developer tools.