Cookie Policy

Last updated: 2 August 2026

1. Introduction

Hoppa is a product of HandyHop, a sole proprietorship registered in the Netherlands under KVK number 91394066 and VAT number NL004888439B24.

This Cookie Policy explains how Hoppa uses cookies and similar browser technologies when you visit hoppa.cc or use the Hoppa application.

Hoppa currently uses only technologies needed to secure user authentication, maintain login sessions, protect authentication requests, complete authentication redirects, remember limited dashboard interface choices, and display onboarding and trial-related interface messages correctly.

Hoppa does not currently use advertising cookies, tracking cookies, behavioural profiling, session-replay tools or third-party website analytics.

If Hoppa introduces optional tracking technologies in the future, this policy will be updated and consent will be requested where legally required before those technologies are used.

2. What are cookies?

Cookies are small text files stored on your device by a website. Hoppa also uses first-party browser storage (localStorage and sessionStorage) for limited interface preferences. Browser storage is not the same as a cookie; it is described separately below.

3. Cookie inventory

On production HTTPS, Hoppa uses NextAuth (Auth.js) authentication cookies. The public homepage does not set cookies. Exact Max-Age values for CSRF and callback cookies were not confirmed on the Set-Cookie header in safe runtime checks.

Cookie or storage nameProviderPurposeTypeDurationConsent requirement
__Host-next-auth.csrf-tokenHoppa / NextAuthProtects authentication forms and requests against cross-site request forgery (CSRF).Essential / security · First-party · HttpOnly: Yes · Secure: Yes · SameSite: Lax · Path: /Persistent while used for authentication. Max-Age: Not confirmedNot required (essential)
__Secure-next-auth.callback-urlHoppa / NextAuthRemembers where the user should return after authentication.Essential / authentication · First-party · HttpOnly: Yes · Secure: Yes · SameSite: Lax · Path: /Persistent while set for the authentication flow. Max-Age: Not confirmedNot required (essential)
__Secure-next-auth.session-tokenHoppa / NextAuthKeeps the user securely logged in (JWT session).Essential / authentication · First-party · HttpOnly: Yes · Secure: Yes · SameSite: Lax · Path: /Persistent. NextAuth default session lifetime: 30 days. Max-Age on login Set-Cookie: Not confirmedNot required (essential)
next-auth.session-token (and non-prefixed CSRF/callback names)Hoppa / NextAuthSame authentication purposes as above when the app runs over HTTP (for example local development).Essential / authentication · First-party · HttpOnly: Yes · Secure: No (HTTP) · SameSite: Lax · Path: /Same as production session defaults when used locallyNot required (essential)

4. Browser storage and similar technologies

Hoppa uses first-party localStorage and sessionStorage only for application interface state in the logged-in dashboard. These keys are not advertising or analytics identifiers.

Storage keyTechnologyWhat it remembersNecessary for the interface?Personal information?Expiry / removal
hoppa_migrated_{organizationId}localStorageWhether you skipped or completed the invoice migration prompt for that organisation.Yes — avoids repeatedly showing the same setup prompt.The key includes an internal organisation ID. The value is only “true”.Until you clear site data in your browser, or the key is overwritten by the app.
hoppa_onboarding_{organizationId} or hoppa_onboarding_defaultlocalStorageWhether the onboarding checklist is visible, minimized, or skipped.Yes — keeps the checklist in the state you chose.The key may include an internal organisation ID. The value is a UI state string only.Until you clear site data in your browser, or the app updates the key.
past_due_drafts_snoozelocalStorageA timestamp used to snooze the past-due drafts reminder modal.Yes — prevents the same reminder from reappearing immediately.No personal data in the value (timestamp only).The app treats the snooze as active for about 3 days. Clear site data to remove it sooner.
overdue_snoozelocalStorageA timestamp used to snooze the overdue invoice reminder modal.Yes — prevents the same reminder from reappearing immediately.No personal data in the value (timestamp only).The app treats the snooze as active for about 3 days. Clear site data to remove it sooner.
trial-banner-dismissedsessionStorageWhether you dismissed the trial status banner in the current browser tab.Yes — keeps the banner hidden for the rest of that tab session.No.Removed when the browser tab or session ends, or when you clear site data.

You can clear cookies and browser storage for hoppa.cc through your browser settings (often under Privacy, Cookies, or Site data). Essential authentication cookies will be set again when you sign in. Clearing storage may reset dashboard prompts and banners.

5. Third-party hosted pages

Hoppa may redirect you to externally hosted payment or subscription pages operated by providers Hoppa uses in the application:

Mollie — used so Hoppa users can connect a Mollie account and so customers can pay invoices through Mollie-hosted checkout. Hoppa does not embed Mollie tracking scripts on the Hoppa public homepage. Mollie may use cookies on its own hosted pages under Mollie’s own privacy and cookie terms.

Lemon Squeezy — used for Hoppa subscription checkout and billing portal redirects. Hoppa does not embed Lemon Squeezy tracking scripts on the Hoppa public homepage. Lemon Squeezy may use cookies on its own hosted pages under Lemon Squeezy’s own privacy and cookie terms.

Hoppa has not independently verified the exact cookies set on those external domains. Please review each provider’s documentation for details.

6. Managing cookies

Because Hoppa currently only uses essential authentication cookies and first-party interface storage, Hoppa does not show a cookie-consent banner.

You can block or delete cookies in your browser. If you block essential authentication cookies, you may not be able to sign in or stay signed in.

For more information about personal data processing, see our Privacy Policy.

7. Contact

Questions about this Cookie Policy can be sent to info@hoppa.cc. Hoppa is a product of HandyHop · KVK: 91394066 · VAT: NL004888439B24.