Legal
Privacy policy
What this site does with the one piece of information it asks you for, and what it puts in your browser.
TODO(policy)
This document is a structural draft. It is not in force, it has no effective date, and nothing in it is a commitment by TechRoom360 until the policy pass is finished. Each section below states only what the site actually does today; everything still to be decided is marked.
What we collect
One thing, and only when you type it in: the email address you enter into a subscribe form. Alongside it the form sends a short label naming which page it was submitted from — “home”, “about”, “newsletter-hero” — so subscriptions can be told apart by where they came from. There is no account, and nothing else is asked for anywhere on this site.
Delivery is not connected yet. Today an address you submit is checked for validity and then goes no further: it is not stored by this site, which has no database, and it is not sent to anyone. That changes the moment an email provider is wired up, and this section has to change with it.
TODO(policy)
- Rewrite the second paragraph when email delivery is connected. Leaving it in place after that would make it false.
Why we collect it
To send you the newsletter. That is the only purpose an address is used for anywhere in this codebase.
TODO(policy)
- Confirm the address will never be used for anything else — a second publication, an announcement, a survey. If it might be, it has to be said here before it happens, not afterwards.
Who else handles it
Email is delivered by a third-party provider rather than by this site. That provider is not connected yet, so no address has ever been passed to one.
TODO(policy)
- Name the provider, state that it acts on our instructions, and say which country it processes data in.
- Name every other processor that ends up handling reader data — the host above all, plus anything added later such as error reporting or a search service.
- Say whether data crosses a border, and on what basis.
How long it is kept
This site stores nothing. There is no database in it, and no reader data is written to disk anywhere in this codebase.
TODO(policy)
- Once delivery is wired, state how long a subscriber record is kept.
- State what unsubscribing does to it — deleted outright, or kept as a suppression entry so the address is not re-added by mistake. These are different answers and a reader is entitled to know which.
- State the retention of anything the host logs (see “Hosting and server logs”).
Cookies and browser storage
This site sets no cookies. The only thing it writes to your browser is a single session-storage entry, “tr360:opened”, recording that the opening animation has already played once in this tab. It holds the value 1, contains no identifier, is cleared when the tab closes, and is never sent to our server.
Two things are read from your browser without being stored: whether your system asks for reduced motion, and whether your connection reports itself as slow or in data-saver mode. Both decide how much animation to run. Neither leaves your device.
Fonts are served from this domain rather than from a font network, so loading a page here does not tell a third party that you visited.
One exception, and it is a real one: an issue can embed third-party media — a video or a demo — in a frame. Where an issue does that, your browser requests the embedded content directly from whoever hosts it, and what they do with that request is theirs, not ours.
TODO(policy)
- Settle the position on embedded media: whether embeds are allowed at all, whether they are loaded only after a click, and whether the providers used need naming here.
- Re-check this whole section against the build before launch, and again whenever anything is added that talks to a third party.
Analytics and measurement
There is none. This codebase contains no analytics script, no tag manager, no tracking pixel and no measurement of any kind.
TODO(policy)
- Whether analytics is adopted at all is still an open question. If it is, this section must name the tool, say what it records, say whether it can identify a person, and say whether it uses cookies — and it must be written before the tool ships, not after.
Hosting and server logs
TODO(policy)
- Name the host. Until that is settled nothing truthful can be said in this section.
- State what its request logs contain — an IP address, a user agent and a timestamp are typical — how long they are kept, and whether anyone here can read them.
- Confirm whether the subscribe endpoint records anything beyond whatever the platform logs by default. As written it records nothing itself.
Unsubscribing
Every issue will carry an unsubscribe link, and using it is the whole process — no form, no reason required, no email to write.
TODO(policy)
- Confirm whether the unsubscribe link is the provider's own, and describe what pressing it does to the record.
- Say how someone asks for a copy of their address, or for it to be deleted. That needs somewhere to send the request, and no contact address is decided yet.
Your rights, and the legal basis for holding an address
TODO(policy)
- Decide which regimes apply. This follows from where readers are as much as from where we are, so it cannot be answered by looking only at our own location.
- State the lawful basis for holding an address. Consent, evidenced by the confirmation email, is the likely answer — but it has to be decided rather than assumed.
- Name the data controller: a named person or a registered entity, with an address that can receive correspondence.
- Name the supervisory authority a reader can complain to, where one applies.
Changes to this policy
TODO(policy)
- Decide how a change is announced — a dated line at the top, a note in an issue, an email to subscribers — and whether material changes are treated differently from corrections.
- Set the effective date. This draft deliberately has none.
Contact
TODO(policy)
- Publish an address for privacy questions. None is decided yet, and inventing one here would be worse than leaving the section empty.