The short version
No first-party cookies. No analytics. No retargeting. Fonts are loaded from a third-party CDN (Fontshare); see below for what that means in cookie terms.
01What a cookie is
A cookie is a small piece of data a website asks your browser to store, so it can recognise you on a return visit. Cookies are also used by analytics scripts to count visitors, by marketing pixels to track you across sites, and by login systems to remember you're signed in. The same machinery powers helpful UX and invasive tracking — what matters is what's actually being set, by whom, and for what.
"Similar technologies" — local storage, session storage, fingerprinting, server-side identifiers — fall under the same rules in the EU. We treat them as cookies for the purposes of this notice.
02What this site sets today
The static landing page at nuya.io does not set any first-party cookies. There is no analytics integration, no marketing pixel, no session, no login — just HTML, CSS, fonts, and three small images. You can verify this in your browser's developer tools (Application → Cookies should show nothing under nuya.io).
What third parties might set
The site loads two kinds of third-party requests:
| Origin | What it does | Cookies? |
|---|---|---|
api.fontshare.com |
Serves the General Sans and JetBrains Mono web-fonts. | Fontshare's published policy is that it does not use cookies for tracking; CDN-cache cookies may be set by their infrastructure for performance reasons. See fontshare.com/legal/privacy. |
fonts.googleapis.com & fonts.gstatic.com |
Pre-connect hint declared in the page <head> for browsers that may resolve Google Fonts. We do not actually load fonts from Google Fonts; the pre-connect is residual and will be removed in the next site update. |
Google's own policy applies if your browser opens the connection. We're removing the hint to make this moot. |
We do not control either third party. If you block third-party cookies in your browser, the site continues to function (font fallback to system sans-serif and mono).
03What we'd add later — and how
We may add a small set of cookies once the platform launches and we have a customer-facing app:
- Strictly necessary — for the platform's authenticated session (the cookie that keeps you signed in to
app.nuya.io). These don't need consent under the ePrivacy Directive because they are essential to deliver a service you've explicitly requested. - Privacy-respecting analytics — likely a self-hosted Plausible or Umami instance. These do not set persistent cookies and don't collect personal data; we'll list them here when we add them.
- Nothing else. We don't plan to add advertising cookies, retargeting pixels, social-share tracking, or third-party heatmaps. If we ever do, this page changes first and a clear consent banner appears before anything is set.
04How to control them
Every modern browser lets you inspect, accept, refuse, and delete cookies on a per-site basis. The exact menu name varies; the location is usually Settings → Privacy:
- Firefox — clear cookies and site data
- Chrome — manage cookies
- Safari — manage cookies
- Edge — delete cookies
Because this site doesn't set first-party cookies today, blocking cookies for nuya.io changes nothing about how the site behaves.
05Updates & contact
We'll update this notice when our cookie use changes. Material additions get a new "Last updated" date at the top and (if consent is required) a banner on first visit. Questions: contact@nuya.io. The fuller data-handling story lives in the Privacy policy.