Understanding how we use cookies and similar technologies
Last updated: May 9, 2026
Cookies are small text files that are stored on your device when you visit a website. They are widely used to make websites work more efficiently and provide information to website owners. Cookies allow websites to remember your actions and preferences over time.
Session Cookies
Temporary cookies that are deleted when you close your browser
Persistent Cookies
Remain on your device for a set period or until you delete them
These cookies are required to keep sign-in flows secure, preserve authenticated sessions, and protect requests against abuse.
| Identifier | Type | Purpose | Duration |
|---|---|---|---|
| authjs.session-token | Cookie | Maintains your authenticated session | Session / auth lifetime |
| authjs.callback-url | Cookie | Preserves the post-login redirect target during authentication | Session |
| authjs.csrf-token | Cookie | Protects forms and auth flows against CSRF attacks |
Our consent banner already includes optional categories for analytics and marketing. At the moment, the public implementation does not initialize analytics or advertising scripts by default from that consent flow.
Analytics
Reserved for future measurement tooling. We will update this page before enabling analytics cookies or similar tracking scripts.
Marketing
Reserved for future advertising and retargeting tooling. We do not currently list active public marketing cookies in the app code.
When the consent banner is shown, you can accept all categories, accept essential only, or save category-specific preferences. Your decision is stored in browser storage so we can remember it on later visits.
Most web browsers allow you to control cookies through their settings. Below are links to instructions for managing cookies in popular browsers:
Some parts of the platform rely on third-party infrastructure. Based on the current implementation, relevant services may include:
Auth.js / NextAuth
Authentication sessions and login security
Stripe
Payment processing on ticketshop and checkout flows
OAuth Providers
Google or LinkedIn sign-in flows when enabled
Browser Storage
Theme, consent state, and UI preference persistence
We may update this Cookie Policy from time to time to reflect changes in our practices or for legal, regulatory, or operational reasons. We will notify you of any material changes by posting the updated policy on our website and updating the "Last updated" date.
If you have any questions about our use of cookies, please contact us:
privacy@dxpx.eu| Session |
We store your consent choices and interface preferences in browser storage so the product remembers your setup between visits.
| Identifier | Type | Purpose | Duration |
|---|---|---|---|
| cookie_consent | localStorage | Stores whether you have already responded to the cookie banner | Until cleared |
| cookie_preferences | localStorage | Stores the consent categories you accepted | Until cleared |
| theme | localStorage | Remembers your selected theme preference | Until cleared |
| sidebar-collapsed | localStorage | Remembers dashboard sidebar state | Until cleared |
When you arrive with campaign parameters and continue toward checkout, we store attribution data so orders can be matched to the source campaign.
| Identifier | Type | Purpose | Duration |
|---|---|---|---|
| dxpx_order_attribution | Cookie + localStorage mirror | Stores UTM parameters and click IDs such as gclid, fbclid, and msclkid for order attribution | 30 days |
Note: Disabling certain cookies may affect the functionality of our website and your ability to use certain features.
We do not currently initialize public Google Analytics, Meta Pixel, LinkedIn Insights, or Intercom scripts from the cookie banner flow shown in this application code. If that changes, we will update this policy accordingly.