Cookie Policy
Every cookie this service sets, what each one is for, how long it lasts, and what breaks if you refuse it.
Version v2 · In effect since Sep 21, 2026
1What a cookie is
A cookie is a small piece of text your browser stores at a site’s request and sends back every time you open that site. It is how a browser remembers that today’s request comes from the same person as the last one.
2Our position on cookies
This service sets no advertising cookies, no cross-site tracking cookies, and no third-party analytics cookies. No Google Analytics, no social network pixels, no tracker that follows you to other sites.
That is why you find no cookie consent banner here. Banners exist to ask permission for cookies you never needed; we do not set those, so there is nothing to permit. Every cookie below is strictly necessary to deliver a function you asked for yourself.
3The complete list of cookies we set
| Name | What it does | Lifetime | Nature |
|---|---|---|---|
| HADIRIN_SESI | Keeps you signed in as an organizer. It holds a pointer to a session in the database, not your identity. | 90 days, or until the session is revoked. | HTTP-only, unreadable by JavaScript. |
| HADIRIN_MASUK | Marks that you recently proved who you are, for actions that require proving it again, such as changing organization members. | 15 minutes. | HTTP-only. |
| HADIRIN_LOCALE | Remembers the language you chose so your next visit opens in it. | 1 year. | Readable by JavaScript. Holds nothing about you beyond a language code. |
| HADIRIN_BAHASA | Remembers the language you chose on an event registration page. Those pages carry no language in their address — so that a link forwarded to you does not impose the sender's language — which is why your choice is kept here instead. | 1 year. | Readable by JavaScript. Contains nothing about you beyond a two-letter language code. |
| HADIRIN_AKSES | Remembers that you entered the correct event access code, so it is not demanded again on every page. | 2 hours. | HTTP-only, signed. |
| HADIRIN_DAFTAR | Links you to the registration you just submitted, so the confirmation page and its ticket can be shown without signing in. | 60 minutes, matching the lifetime of the verification link in your email. | HTTP-only, signed. |
| HADIRIN_PINTU | Keeps a door steward’s session open on the scanning device for the length of the event. | 12 hours. | HTTP-only, signed. |
| HADIRIN_GOOGLE | Prevents the "sign in with Google" process from being hijacked by another site (CSRF protection). Holds a random code, not your identity or any personal data, and is deleted as soon as sign-in finishes. | 10 minutes, or until sign-in finishes — whichever comes first. | HTTP-only. |
If you find another cookie from our domain that is not in this table, that is a defect we want to know about. Tell us at info@yarnext.com.
4Other storage on your device
Besides cookies, one part of the service stores data inside your browser: the offline check-in scanner.
- The scanner keeps the event attendee manifest and a queue of scans in local browser storage, so that it keeps working when the network at the venue dies.
- That data stays on the steward’s device and is sent nowhere except back to this service once the network returns.
- It is cleared when the door session ends or when site storage is cleared from the browser.
Because the manifest holds attendee names, the scanning device should belong to the organizer, not be a borrowed phone that someone else holds after the event.
5Third-party cookies
We embed no third-party scripts that set cookies. Fonts are served from our own domain, and no outside provider receives a request from your browser merely because you opened this page.
If an organizer links to another site from their event description, that site has its own cookie policy, outside our control.
6Refusing and deleting cookies
Every browser offers a way to block or delete cookies, usually under privacy settings. You are free to use it at any time.
What to expect if you do:
- Without HADIRIN_SESI you cannot stay signed in as an organizer — every page will ask you to sign in again.
- Without HADIRIN_AKSES the event access code will be demanded over and over.
- Without HADIRIN_DAFTAR the confirmation page cannot recognize you; your ticket is still reachable through the link in your email.
- Without HADIRIN_PINTU a door steward must re-enter the join code every time the page reloads.
- Without HADIRIN_LOCALE the language is renegotiated from your browser settings on every visit.
7Changes to this policy
If we add or remove a cookie, the table above is updated on the day the change takes effect, not afterwards. The effective date of this version is shown at the top of the page.