Your data
Privacy policy: what this site receives, and what it never sees
No accounts, no forms, no analytics. Three records exist at all, and one of them never leaves your browser.
In short
There are no accounts here, no forms and nowhere to upload anything. The site’s own code sets no cookies, runs no analytics and loads nothing from a third party. Three records about you exist at all: the technical record the host makes when it serves you a page, whatever you choose to write in an email, and the age confirmation your browser keeps to itself.
The person responsible for what reaches this side is the editor, Venios Volden, acting as an individual rather than a company; anything to do with data goes to [email protected]. What the site publishes is the reviews this policy covers.
What is processed
Three records, and who holds each one
Nothing outside this table is collected: there is nowhere for it to arrive.
| Record | What it contains | What it is for | Who holds it |
|---|---|---|---|
| Access log | IP address, time, the address requested, browser details. | Delivering the page and absorbing attacks. | Cloudflare, as processor for the site. This site does not download those logs or build statistics from them, and sets no retention period of its own — how long they live is Cloudflare’s rule. |
| Your email | The address you write from and the text you send. | Reading, checking and replying. | The editor’s mailbox; deleted once the matter is closed, unless it has to be kept. |
| Age confirmation | A single age_ok entry in your browser’s localStorage. | So the 18+ notice does not reappear on every page. | Your browser only. It is never sent to a server, and clearing site data removes it. |
The site is static and hosted on Cloudflare Pages. Under Cloudflare’s privacy policy it is a data processor for the logs and traffic passing through its network, handled on the site operator’s instructions.
How long, and who decides
Retention, record by record
Two of the three are out of this desk’s hands, in opposite directions.
| Record | How long it lives | Who decides that | How it is removed |
|---|---|---|---|
| Access log | Under the host’s own retention rule. This site sets no period, never downloads the logs and builds nothing from them. | Cloudflare, acting as processor for the traffic it serves. | Not something this side can delete on request; it is governed by the host’s policy rather than by this page. |
| Your email | Until the matter it is about is closed. | The editor, who is the only person who reads the mailbox. | Ask in the same thread. It is deleted unless there is a reason it has to be kept. |
| Age confirmation | Until you clear site data — or until the window closes, in a private session. | Your browser, entirely. The entry is never sent anywhere. | Clear site data for this site, and the 18+ notice returns on the next visit. |
What never arrives
The parts that are missing on purpose
Most of what a privacy policy explains has no entry point here.
Photos and files
There is no upload field anywhere on this site.
- No form, no file picker, no drag-and-drop area, on any page.
- Email with an image attached is deleted unopened.
- If an image of you is circulating, the desks that can act on it are in what happens to what you send us.
Cookies and tracking
The site’s code sets no cookie of any kind.
- No analytics, no advertising network, no social buttons, no embedded players.
- The content security policy allows the browser to load files from this site only.
- Outbound links are sent with a referrer policy that passes the domain, not the page you were reading.
- Once you leave, the other operator’s own rules apply — see what the reviewed services keep.
Accounts and payment
Nothing here can be logged into or paid for.
- No account, no password, no newsletter, no notifications.
- The site charges readers nothing, so it never asks for card details.
- An advertising link passes a referral code and nothing about you — the terms this policy sits in.
After you leave
Where this policy stops
One click out, and a different set of rules takes over.
What travels with the click
Very little, and none of it is about you:
- the referrer policy sends the domain rather than the page you were reading;
- an advertising link carries a code identifying this site, not the person following it;
- no identifier, no session and no reading history goes with you;
- from that moment the operator’s own document applies — the services this policy stops at.
What they ask for instead
The contrast is the point of this site:
- one operator lists email, IP address, device identifiers, operating system, approximate location, wallet addresses and transaction hashes;
- another keeps registration data, IP addresses, payment records and moderation decisions for at least seven years;
- none of them can be asked to delete anything through this page, only through their own mailbox;
- the clauses are quoted in full in what each operator writes down.
An installed build asks for more than any web page is able to: storage, notifications and whatever else its manifest declares — the permissions an install file asks for.
Your rights
What you can ask for, and how
The Personal Data (Privacy) Ordinance (Cap. 486) applies to this site as it does to any other.
What you can ask for
The data access and correction principle gives you three things.
- Confirmation of whether any data about you is held here.
- A copy of it, and correction of anything inaccurate.
- Deletion, once there is no longer a reason to keep it.
- Where data was disclosed to harm someone, the Commissioner has separate powers — cessation notices and personal data.
How to make the request
Write from the address the request is about; no form and no fee.
- Say which right you are exercising in the first line.
- No identity document is asked for: there is no account to match you to.
- If you have never written to this site, there is nothing held about you to release or erase.
- The mailbox and what to expect from it are described in how to ask for your data.
The Privacy Commissioner publishes the six data protection principles and handles complaints where a request is refused.
Questions
About your data here
Answers describe the code this site actually runs.
Is the age check a cookie?
No. A cookie travels to the server with every request; the age_ok entry stays in your browser’s storage and is read by a script on your own device. In a private window it disappears when you close it.
Do you know which pages I read?
No. Without analytics there is no page-level record on this side at all, and the host’s technical logs are never turned into reader statistics or joined to anything else. What you send to a service after leaving is another matter entirely — what a bot keeps in the chat log stays there until both sides delete it.
Who answers for this policy?
The editor, in person: no data protection department, no third party reading the mail. The rest of the arrangement is in who is behind this site.