Privacy Policy
Effective 19 September 2026 · Last updated 19 September 2026
Draft — not yet in force. Every HIGHLIGHTED value below has to be filled in by arky.bet before this page is published, and the finished text should be reviewed by a lawyer qualified in your jurisdiction. Until then this document does not bind anyone.
This website collects nothing about you. There are no accounts, no forms, no cookies, no analytics and no tracking pixels. The only thing it stores is a flag remembering that you closed the notice at the bottom of the page. This policy exists to say exactly that, and to be honest about the three third parties your browser contacts when it loads the page.
1. Who is responsible
This site is operated by LEGAL ENTITY NAME, registered in COUNTRY / STATE at REGISTERED ADDRESS ("arky.bet", "we", "us"). For anything in this policy, write to PRIVACY CONTACT EMAIL.
2. What we collect
Nothing that you provide. The site has no sign-up, no login, no contact form, no newsletter box, no comment field and no wallet connection. There is nowhere on this site to enter personal data, so we never receive any.
Almost nothing that we store on your device. The site sets no cookies at all, and writes nothing to session storage or IndexedDB. There is exactly one exception: when you dismiss the privacy notice at the bottom of the page, your browser records a single flag in local storage, arky:notice-dismissed, so the notice does not reappear on every visit. It holds the value 1 and nothing else — no identifier, no timestamp, no history. It never leaves your browser and we cannot read it. Clearing your site data removes it, and the notice returns.
That flag is why you see a notice rather than a consent banner: with no cookies, no analytics and no tracking, there is nothing here to consent to, and a strictly necessary preference like this one does not require consent under the ePrivacy rules.
No analytics and no advertising. We run no analytics product, no heatmaps, no session recording, no A/B testing tool and no advertising or social tracking pixels. We do not build profiles of visitors and we have no visitor identifiers of any kind.
3. What happens automatically when you load the page
Loading any website causes your browser to reveal certain technical information to the servers it fetches files from. That is how the web works, and it applies here to three parties we do not control:
- Our hosting provider. The site is served by HOSTING PROVIDER, e.g. Netlify, which keeps standard server logs. These typically include your IP address, the page requested, a timestamp and your browser's user-agent string, and are retained for a limited period for security and to keep the service running. See HOST'S PRIVACY POLICY URL.
- Google Fonts (
fonts.googleapis.com,fonts.gstatic.com) serves the Anton and Outfit typefaces. Your browser's request exposes your IP address and user-agent to Google. - jsDelivr (
cdn.jsdelivr.net) serves the GSAP animation library. Your browser's request exposes your IP address and user-agent to that CDN.
We do not receive, request or store any of this data ourselves, and none of it is passed back to us in a form that identifies you. If you would rather not contact these services at all, a content blocker or a privacy-focused browser will stop the requests; the page remains readable without them.
4. Why we process anything at all
Where the server logs described above amount to personal data under the GDPR, the legal basis is our legitimate interest (Article 6(1)(f)) in delivering a working, secure website. We do not rely on consent, because we are not doing anything that requires it. We carry out no automated decision-making and no profiling.
5. Sharing and selling
We have no visitor data to share, so we share none. We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are used in the California Consumer Privacy Act as amended by the CPRA. We have never done so.
6. International transfers
The hosting provider and the two CDNs above operate globally and may serve this page from a server outside your country. Because we hold no visitor data ourselves, we make no international transfer of your personal data.
7. Retention
We retain no visitor data. Server logs are held by our hosting provider under its own retention schedule, not ours.
8. Your rights
If you are in the EU, EEA or UK, the GDPR gives you the right to access your personal data, to have it corrected or erased, to restrict or object to its processing, and to data portability. If you are a California resident, the CCPA/CPRA gives you the right to know, to delete, to correct, to opt out of sale or sharing, and not to be discriminated against for exercising those rights.
In practice we hold nothing to disclose, correct or delete, so a request to us will usually be answered by saying so. If you want the server logs described in section 3 addressed, that request has to go to the hosting provider, and we will tell you where to send it. You can reach us at PRIVACY CONTACT EMAIL, and we will respond within the period the applicable law allows.
You also have the right to complain to your data protection authority — in the EU/EEA your national supervisory authority, in the UK the Information Commissioner's Office.
9. Children
This site is not directed at children and we knowingly collect no data from anyone, of any age.
10. Security
The site is static: it holds no database and no visitor records, which removes most of what could be breached. It is served over HTTPS. No method of transmission over the internet is completely secure, and we cannot guarantee absolute security of data handled by the third parties named above.
11. Links out
Any link from this site to somewhere else takes you to a service with its own privacy policy, which governs what happens once you arrive. We are not responsible for those practices.
12. Changes
If this site ever starts collecting something — an email box, an account, analytics — this policy will be updated before that goes live, and the "last updated" date above will change. Material changes will be flagged on the page.
13. Contact
Questions about this policy: PRIVACY CONTACT EMAIL, or write to LEGAL ENTITY NAME, REGISTERED ADDRESS.