Data collected
DMOZSTYLE collects only what's needed to run an editorial directory. For editors, that's an account record: email address, hashed password, display name, and an optional bio. Read-only visitors are not asked to sign in and are not profiled.
Submitted links carry the submitter's account reference so editors can attribute and follow up on the queue. No additional fingerprinting or analytics payloads are attached to a request.
Cookies
One session cookie is set on sign-in: dmoz_session. It is HttpOnly, SameSite=Lax, and expires after seven days. It exists solely to keep an editor signed in and is cleared on sign-out.
No advertising, analytics, or third-party cookies are set by the directory.
Logs and metrics
The server records request IPs at the application layer for one purpose: rejecting traffic when the directory is in protected mode. There is no analytics pipeline, no behavioural funnel, and no long-term log retention beyond what's needed to debug an outage.
Third parties
The directory has no third-party data sharing. There are no embedded scripts, no remote fonts, no tag managers, and no advertising partners. The reading experience is fully served from the application binary.
Your rights
Editors can sign in to update their account at any time. Account deletion is handled manually in this slice: contact an admin and your record will be removed. Automated self-service deletion is not yet shipped — we'd rather flag that honestly than imply otherwise.
Contact
For privacy questions or deletion requests, email editorial@dmozstyle.example.