Privacy Policy

Version 1.5 — effective 2026-11-16.

What we collect

• Account data: username, email, password hash (Argon2id — we never store the password itself), avatar/identicon seed, bio, links you choose to add, theme and preference settings.
• Content: works, chapters, comments, board posts, chat and room messages, project proposals, proposals/jobs listings, pledges, gifts, votes and reports that you create.
• Profile data: every profile on your account (handle, display name, bio, links, avatar seed), profile kind (default/public/private/adult-only/scoped), the realm scope of scoped profiles, and switch/attribution records so content shows the profile it was posted with.**
• Policy-check data: records of automated policy checks on profile/content changes (we call the check Jev) — outcome category, timestamps and the object checked — so blocks can be reviewed and appealed.
• Adult-access records: your account adult preference and per-session adult confirmations (session id, timestamps, decision), so the adult gate can be enforced. Anonymous visitors never receive adult content.
• Contract records: moderation-contract versions for realms/threads and your contract acceptances (version, timestamp, and a salted, truncated hash of the IP — never a raw IP).
• Legal-notice records: legal notices we receive (kind, requester contact details, subject references, decisions, reasons, evidence references and legal-hold state). These are staff-only and never published; only aggregate counts reach the transparency page.
• Availability records: when content is hidden by a provisional geo rule, we record the country code, policy version, path and timestamp for legal evidence; we do not store a geolocation profile or the IP in this audit entry.
• Financial-simulation records: your simulated WAID balances, simulated USD balances, ledger entries, post power, and project escrow. All of it is demo money.
• Technical data: session records (hashed session token, IP address, user agent, timestamps), rate-limit counters, and server logs that may contain request metadata.

What we do not collect

No advertising identifiers, no third-party analytics, no external fonts or CDNs, no payment data, no government ID, and no stored geolocation. It is a v1 limitation and a deliberate choice. Our automated policy checks examine the content/profile text and images you submit; they are not a general surveillance tool and do not build shadow profiles.

Why we keep it

To run the product (sessions, content, balances, notification delivery), to keep the site secure (rate limits, audit logs, moderation), and to satisfy legal obligations.

Public by design

Your username, display name, bio, published works, board posts, projects, pledges (amounts may be shown publicly), kudos and public bookmarks are public. Votes are shown only as aggregates in receipts, never per-person. Private bookmarks are private. Your email is never shown publicly. Preferences (likes/dislikes/mutes) are private.

Sharing

We do not sell data. We share data only with infrastructure providers necessary to serve the site (hosting, database, and the operator's own mail service), or when legally required. Secrets and environment configuration are kept on the server, not in the repository.

A data-protection impact assessment (DPIA) for profiles, automated policy checks, asset uploads and adult gating is pending; it will be referenced here once completed. The trust/legal review flag remains on until the operator and counsel sign off on this policy set — the current status is shown on /admin/trust for staff and summarised honestly on this page: this policy set has not yet completed independent legal review.

Your choices

You can edit your profile, change your email and password, export your account data as JSON from Settings → Account, and delete your account (soft delete; content is attributed to [deleted user]). For data requests, write to support@waidrn.com — see the Contact page. Cookies used: waidrn_session (session, HttpOnly), waidrn_csrf (CSRF protection), waidrn_theme (display preference).

Retention

Ledger transactions, audit logs, receipts, moderation decisions and contract-acceptance records are retained as the system's permanent accountability record. Session records are retained until expiry or revocation. Adult-access session confirmations expire with the session. Legal-notice records and evidence are retained while a hold is active and, after resolution, according to the retention window described in the Legal & trust runbook — evidence references are cleared after the retention period unless a hold applies. Geo availability audit entries are retained for accountability; they contain no IP. Signup/profile policy-check records are retained with the content/moderation record. Logs are rotated.

Support, contributions and communities (v1.4)

• Simulated WAID only. Waidrn does not collect or process card, bank, payment-processor or KYC data; there is no real-money rail. Support/contribution amounts exist only in the simulated ledger.
• We store support receipts and contribution records (amount, sender account, recipient creator/community/org/project, message, transaction id) to run the simulated economy, show aggregate totals to creators, and keep the ledger reconcilable. Public project pages show public-tier contributors by name; amount-only and anonymous contributions are counted but not named. Support receipts for creators show the sender's username and amount to the creator's supporters list as public by default; do not include personal information you do not want shown in the optional message.
• We store membership and role records for communities and organizations, linked boards/projects, and organization verification requests/evidence links you submit. Verification evidence is visible to moderators; never upload sensitive personal documents to a demo verification field.
• External support links are URLs you choose; we do not process their payments and do not receive your data from them.
• Rights-status attestations and claim statements are stored and audited as part of project records; claims may reference an evidence URL you provide.