Quinn wird geladen...
Cookie notice
Cookies and local storage
In the base setup, Quinn mainly uses technically necessary cookies for login and protected app areas. Analytics or marketing services may only become active after final review and suitable consent logic.
Last updated: May 2026
Login
Sessions and protected areas
Security
Abuse protection and stability
Settings
Browser controls local storage
Cookies
No marketing cookies in the base setup
Categories
Which storage is intended.
Necessary cookies
- Purpose
- Login session, authentication, protection of protected areas and technical provision.
- Examples
- Supabase Auth cookies with sb prefix, Next.js/session and security mechanisms
- Basis
- Required to provide the service
Security and error analysis
- Purpose
- Detection of technical errors, abuse protection, stability and operational security.
- Examples
- Sentry only if ENABLE_SENTRY is enabled and finally configured
- Basis
- Legitimate interest in secure operation, where permitted
Analytics
- Purpose
- Product metrics and usage analysis only when the function is enabled and a suitable legal basis exists.
- Examples
- Currently prepared as a feature flag; add provider and consent logic before use
- Basis
- Consent or another basis to be reviewed
Notes
Control remains transparent.
No marketing cookies in the current base setup
No classic marketing or tracking pixels such as gtag, PostHog or Meta Pixel are actively integrated in the visible code. If such services are added later, banners, provider lists and consents must be adjusted.
Technically necessary storage
Cookies are used for protected app areas to recognise users and keep sessions secure. Without these cookies, the application cannot be used properly.
Browser settings
Users can delete or block cookies in the browser. This may mean that login, upload, export or other protected functions no longer work.
Changes
This notice must be updated as soon as new analytics, marketing, support or payment providers are integrated.