The data position is small because the product here is reading

What arrives anyway

Incoming requests create ordinary server logs: IP, time, path, user agent. Those logs exist to keep the host up, not to build a profile.

The desk does not name an analytics vendor because it will not invent one.

The contact widget

Messages typed at /contact/ are handled by that widget's script. Do not put passwords or full identity numbers there.

A published privacy contact address is not yet available. That absence is stated rather than filled with a fake inbox.

Server logs, ordinary and limited

IP, time, path, user agent. Hosting, not profiling. No named analytics vendor.

The outbound click

After PLAY NOW, the destination policy applies. This desk does not see the lobby.

Chat caution

Do not send passwords or full identity numbers to /contact/.

Controller identity

Being finalised. Not published. Absence is stated.

No accounts here

No newsletter. No comment log on the articles. The product is reading.

A small data position, written without a fake officer

These pages are static files. They do not create an account, a newsletter list or a payment record on this host. Ordinary web server logs still appear because the internet works that way: an address, a time, a path, a user agent. Those logs keep the host running. They are not a marketing profile and no analytics vendor is named because none is documented.

The one outbound commercial click is PLAY NOW, which leaves through /Login/playnow. After that click the destination's rules apply. This desk does not receive a copy of the lobby session and cannot describe it.

The chat widget at /contact/ is a separate script. Treat it as a narrow inbox for notes about these pages. Do not put passwords, one-time codes or full identity numbers there. A reset control on that widget, if present, starts a new thread. It is not a statutory erasure portal because a controller identity has not been published.

Controller identity, a postal address and a dedicated privacy email are being finalised. They are not listed. Inventing them would make this note look complete and false. When they exist they will be added with a date.

No first-party marketing cookie is documented. Third-party scripts on the contact widget follow that widget's own behaviour. The rest of the public pages load fonts, a stylesheet and a small menu script. That is the honest inventory.

If you want an operator to delete an account, that request belongs in the product and on the delete-account note. This privacy note cannot press a button inside an unseen client. It can only describe what this static host actually holds, which is little, and what it refuses to invent, which is a lot.

Closing field notes

You can read these pages without creating an identity here. That is the point of a static host. The cost is ordinary server logs. The benefit is no newsletter to leak. If you need a named officer, you will have to wait until one is published. Waiting is better than a invented inbox.

Fifteen data-position lines

1. Static files. No account on these articles.
2. No newsletter list exists to leak.
3. Ordinary server logs: IP, time, path, agent.
4. Logs are for hosting, not profiling.
5. No analytics vendor is named.
6. PLAY NOW leaves. Destination policy then applies.
7. Chat widget is a narrow inbox. Do not feed it secrets.
8. Controller identity is not published yet.
9. A fake inbox would look complete and be false.
10. No first-party marketing cookie is documented.
11. Fonts, CSS and menu.js are the honest inventory.
12. Operator deletion is a product problem, not this host's button.
13. You can read without creating an identity here.
14. Waiting for a named officer beats inventing one.
15. Smallness is the policy.

More checks, said another way

1. No account on the articles means no password to leak from the articles.
2. No newsletter means no list to sell.
3. Logs exist because hosts log. They are not a profile product.
4. No vendor name is not a secret vendor. It is no vendor documented.
5. After PLAY NOW the other policy applies. This desk cannot see it.
6. Do not feed PAN or OTP to /contact/.
7. Controller unpublished. Wait. Do not invent an inbox.
8. Cookie claims without a named cookie are refused.
9. Inventory: fonts, CSS, menu, widget, logs, one exit click.
10. Operator erasure is a product button, not this host's button.
11. You can read unnamed. That is the design.
12. A fake officer would complete the template and break the ethics.
13. Smallness is not unfinished. Smallness is the position.
14. The widget reset starts a thread. It is not a statutory portal.
15. If you need more rights language, you need a named controller first.

Checks restated for tired readers

1. Static reading is the default identity: none.
2. A list that was never built cannot leak.
3. Boring logs should stay boring.
4. Unnamed vendors are not secret vendors.
5. We cannot quote a policy we cannot see after the exit.
6. PAN and OTP stay out of /contact/.
7. An imaginary officer is worse than a wait.
8. Cookie novels without cookie names are refused.
9. Short inventories are honest inventories.
10. Their erasure button is theirs.
11. Unnamed reading is intended.
12. Template-complete privacy pages often invent officers.
13. Smallness is chosen.
14. Thread reset is not a statute.
15. Rights speeches wait for a named controller.
16. Fonts and CSS are not trackers by themselves.
17. The widget is a narrow inbox. Keep it narrow.
18. No newsletter means no unsubscribe theatre.
19. After the click, their rules. Before the click, these.
20. Wait, then date the officer. Do not sketch one.