{"ok":true,"document":"privacy","updated":"2026-01-01","markdown":"# OCMobileX — Privacy Policy\n\n**Effective date:** 2026-01-01\n**Service:** https://ocmobilex.pages.dev\n\nThis policy explains what the OCMobileX backend stores, why, for how long,\nand what control you have over it. It describes the API at https://ocmobilex.pages.dev only.\n\n## 1. Short version\n\n- We store the minimum needed to run accounts, shares, publications and\n  moderation.\n- We do **not** run advertising, analytics or cross-site tracking.\n- We do not sell or rent personal data. Ever.\n- Passwords are stored as PBKDF2-SHA256 hashes, never in plain text.\n- Content you publish is public. Assume anything you publish can be read,\n  copied and archived by anyone.\n\n## 2. What we store\n\n### 2.1 Account data\n\n| Field | Purpose | Notes |\n| --- | --- | --- |\n| username | identity, login, attribution | public |\n| password hash + salt (PBKDF2-SHA256, 100 000 iterations) | authentication | never returned by the API |\n| role (user / mod / admin / owner) | permissions | public |\n| bio, accent colour, links | profile page | public |\n| joined date | account age | public |\n| counters (shared chats, published items, ideas) | profile statistics | public |\n| muted-until / banned flags | moderation | visible to staff |\n| warning and report counters | moderation | staff only |\n\n### 2.2 Content data\n\n- **Shared chats** — the title, the message snapshot you send, the permission\n  flags, your username as owner and the creation time. Public at\n  `/shared/chat/<code>` for anyone holding the code.\n- **Published items** — the payload (HTML text, base64 image or audio), title,\n  description, tags, size, MIME type and your username. Public at `/p/<id>`.\n- **Ideas** — title, description, category, impact, vote count and your username\n  if you were signed in. Public.\n- **Bug reports** — the report fields you fill in, an optional contact, optional\n  logs, your username if signed in, and the IP address the report came from\n  (staff only, used to detect spam).\n- **Moderation reports** — target username, reason, details, evidence, source\n  (user or automated), and the IP address for user-submitted reports.\n\n### 2.3 Technical data\n\n- **IP address** — read from the `CF-Connecting-IP` header for rate limiting and\n  abuse handling. IP addresses are kept in a rate-limit key that expires\n  automatically (60 s – 10 min) and, for bug and moderation reports, alongside\n  the report so staff can spot coordinated spam.\n- **Session tokens** — signed with HMAC-SHA256 and held by your client. They are\n  not stored in a database; the API validates the signature and re-reads your\n  account record on each request. A token is valid for 30 days or until the\n  account is deleted.\n- **Cloudflare logs** — Cloudflare, our hosting and CDN provider, processes\n  requests and may keep short-lived operational logs (IP, user agent, path,\n  status) for security and reliability. See Cloudflare's own privacy policy.\n\nWe do **not** collect: email addresses, phone numbers, precise location,\ncontacts, advertising identifiers, or behavioural analytics.\n\n## 3. Why we process it (legal bases)\n\n- **Contract** — creating your account, authenticating you, storing and serving\n  the content you ask us to store and serve.\n- **Legitimate interests** — keeping the Service online and abuse-free: rate\n  limiting, spam detection, moderation, debugging and security.\n- **Legal obligation** — retaining records needed to answer lawful requests, or\n  to report content that is illegal in the jurisdiction where we operate.\n- **Consent** — where we ever ask for something optional, we ask first and you\n  can withdraw at any time.\n\n## 4. What is public\n\nPublic by design: your username, role, bio, colour, links, join date, counters,\nideas you posted while signed in, published items, and shared chats for anyone\nwith the link.\n\nNot public: your password hash, salt, muted/banned state (staff only), warning\nand report counters (staff only), IP addresses (staff only), bug report contents\n(staff only), moderation report contents (staff only).\n\n## 5. Sharing\n\nWe do not sell personal data. We share it only with:\n\n1. **Cloudflare** — hosting, CDN, Workers KV storage and DDoS protection. Data is\n   processed in Cloudflare's global network.\n2. **The people you share with** — when you create a share link or publish an\n   item, you are publishing it. That is your decision and your responsibility.\n3. **Authorities** — when we receive a valid legal request, or when disclosure is\n   necessary to prevent serious harm, especially harm to a child.\n\nWe do not use third-party advertising or analytics SDKs.\n\n## 6. Retention\n\n- Rate-limit keys: 60 seconds to 10 minutes, then deleted automatically.\n- Session tokens: expire after 30 days; deleting your account invalidates every\n  token immediately.\n- Account record: kept until you delete it.\n- Shared chats and published items: kept until the owner deletes them or\n  moderation removes them.\n- Bug reports and moderation reports: kept up to 24 months so repeat abuse can be\n  recognised, then deleted.\n- Backups: short-lived, overwritten on a rolling basis.\n\n## 7. Your rights\n\nDepending on where you live (for example under the GDPR or CCPA) you may have the\nright to access, correct, export, delete or restrict processing of your personal\ndata, to object to processing based on legitimate interests, and to lodge a\ncomplaint with your local data-protection authority.\n\nIn practice:\n\n- **Access / export** — `GET /api/account/me` returns your profile; your public\n  content is readable through its public URLs.\n- **Correct** — `PATCH /api/account/profile` for bio, colour and links.\n- **Delete** — `POST /api/account/delete` with your password and the\n  confirmation string `DELETE`.\n- **Anything else** — write to legal@ocmobilex.pages.dev and we will respond within 30 days.\n\nWe do not discriminate against you for exercising these rights.\n\n## 8. Security\n\n- Passwords: PBKDF2-SHA256 with a random 16-byte salt and 100 000 iterations.\n- Sessions: HMAC-SHA256 signed tokens with an expiry; the signing secret is a\n  server-side secret and never leaves the backend.\n- Transport: HTTPS only (Cloudflare edge, TLS 1.2+).\n- Access: owner-only endpoints require a separate owner token or the owner role;\n  moderation endpoints require staff roles.\n- No system is perfectly secure. If you discover a vulnerability, report it\n  privately to abuse@ocmobilex.pages.dev instead of publishing it.\n\n## 9. Children\n\nThe Service is not directed at children under 13, and we do not knowingly collect\npersonal data from them. If you believe a child under 13 has created an account,\ncontact abuse@ocmobilex.pages.dev and we will remove it. Content that sexualises minors is\nremoved immediately and reported where the law requires it.\n\n## 10. International transfers\n\nThe Service runs on Cloudflare's global network, so your data may be processed in\na country other than your own. Where required, transfers rely on the European\nCommission's Standard Contractual Clauses or an equivalent safeguard offered by\nour provider.\n\n## 11. Cookies and local storage\n\nThe API itself sets no cookies. The web client may store your session token and\nyour UI preferences in browser local storage; that data stays on your device and\nis removed when you clear site data. No tracking cookies are used.\n\n## 12. Changes\n\nWe will update this policy when our practices change and will change the\neffective date above. Significant changes will be announced in the Service.\n\n## 13. Contact\n\nPrivacy questions, data requests, abuse reports: **legal@ocmobilex.pages.dev**\nAbuse and illegal content: **abuse@ocmobilex.pages.dev**\n"}