Cookie notice
Effective date: August 23, 2026
Which cookies exist, what they do, and how long they last.
No cookies are set on public pages
No cookies are written to your device while browsing getrekid.com. There are no advertising cookies, no analytics cookies, and no third-party tracking cookies.
The cookies described below are only created when you log in, and are necessary for the function itself.
On getrekid.com
| Name | What it does | Duration |
|---|---|---|
| `gr_s` | Keeps you signed in after you use the login link sent by e-mail. Sealed value; HttpOnly, Secure, SameSite=Lax. | Until logout |
| `gr_adm` | Admin panel session. Set only for our own staff. | Until logout |
Nothing else is set.
On the child-facing site
On rekid.tr and rekid.uk, a cookie remembers a pairing key, so the device does not have to be paired again every time. It is stored as a sealed value and is flagged HttpOnly and Secure.
If reCAPTCHA is enabled on the pairing screen, Google places its own cookies there; these come from Google and are used to distinguish a human from a script.
Something that is stored but is not a cookie
Your preference from this notice is kept in your browser under the name `rk_cerez`, stored in local storage, not as a cookie. Storing the cookie preference itself as a cookie would be doing exactly the thing being asked about, without asking it.
Fonts
The font is served from our own server. Your browser does not make requests to Google or to any other external address.
The pages do not contain embedded advertising, social media, or measurement code.
Network layer
Cloudflare sits in front of the site. Cloudflare may add a cookieless measurement script that counts page views; it does not create a visitor identifier. We mention this here because it is the kind of detail a cookie notice is expected to be honest about.
Turning it off
You can clear or block cookies from your browser. You can also reopen this notice and change your choice at any time via the Cookie preferences link at the bottom of the pages.
If you block the pairing cookie on the child-facing site, the device will need to be paired again using the device's pairing key.