Privacy Policy

Your public identity can stay out of a story. ReadChief still tells you honestly what the service must retain to keep accounts and communities safe.

Effective 1 September 2026

The privacy principle

Collect what is needed for a specific purpose, keep it only as long as that purpose and applicable law require, restrict access, and give people practical controls. Anonymous posting hides authorship from other readers; it does not make activity untraceable to ReadChief or immune from valid legal process.

Information we process

• Account data: opaque identity-provider identifiers, email managed by Cognito or Google, a keyed one-way email matching value used to prevent duplicate accounts, public pseudonym, display name, profile and account status.
• Activity: posts, comments, votes, saves, follows, Corner memberships, Context Notes, reports, appeals, privacy requests and moderation history.
• Security and operations: session cookies, IP and device/network signals, request logs, timestamps, rate-limit records and diagnostic events needed to prevent abuse and run the service.
• Media and communications: uploaded files and metadata after sanitisation, support messages, legal notices and transactional-email delivery records.

Why we use it

To authenticate accounts; publish and rank content; operate personalised, saved and following feeds; deliver notifications; secure the service; detect fraud and abuse; review reports and appeals; fulfil privacy rights; maintain backups; comply with law; and understand aggregate product reliability. Product telemetry records only an allowed event name, page path, random session identifier, release and bounded technical properties. It rejects content text, raw search queries, email addresses and private identifiers.

Cookies

ReadChief uses secure, HttpOnly cookies for login state, refresh sessions and OAuth protection. These are necessary for authenticated features. We do not describe the current service as cookie-free. If optional analytics or advertising cookies are introduced, this policy and the consent controls must be updated before they are enabled.

Who processes data

Current infrastructure uses Amazon Web Services for identity, compute, media, delivery and transactional email, and Supabase-hosted PostgreSQL for application data. These providers process limited data to supply their contracted services. Public posts and profiles are, by design, visible to anyone and may be indexed or reshared.

International transfers

Infrastructure may process data outside Nigeria. ReadChief must use appropriate contractual, organisational and technical safeguards for cross-border processing and review provider locations as the stack changes.

Retention and deletion

Public content remains until deleted, removed, or no longer needed. Product telemetry is deleted after 90 days, processed delivery jobs after 30 days, read notifications after 365 days, application logs after 30 days and encrypted database backups after 90 days. Incomplete quarantined uploads expire after 30 days. Security, moderation, legal and active dispute records may remain for up to two years or longer where law or a preservation duty requires it. Deletion requests are verified and the completion is recorded; a deleted record may remain in a protected backup until that backup expires.

Controller and contact

ReadChief is the data controller for the service described here. Privacy questions and verified rights requests can be sent through the in-product Privacy workflow or to readchieff@gmail.com. Use the subject “PRIVACY” and do not email passwords, one-time codes or identity documents unless a secure verification channel is provided.

Your rights and choices

Subject to applicable limits, you can request information, access, correction, objection, restriction, portability or deletion, withdraw consent where consent is the basis, seek human review of qualifying automated decisions, and complain to the Nigeria Data Protection Commission. Read the Nigeria Data Protection Act 2023 on the NDPC website ↗

Changes

Material changes will be dated here and, where appropriate, notified in-product or by email before they take effect. Continued use after the effective date is subject to the updated policy.