What we collect, what becomes public, and why.

• Account and authentication information, including email and the identity provided through supported OAuth providers.
• Profile information such as username, display name, country, bio, avatar, onboarding status, and accepted terms version.
• Story drafts, submissions, revisions, public-credit choices, classifications, screening results, and editorial decisions.
• Comments, replies, reactions, story votes, bookmarks, reading progress, highlights, notes, and notification state.
• Security, moderation, request, and technical logs needed to operate and protect the service.

If Opinions are introduced later, their drafts, submissions, reactions, and conversations would also be covered by an updated policy before use.

Information is used to authenticate accounts, maintain profiles, save private work, publish approved content, provide reading and community features, deliver notifications, enforce platform rules, investigate safety concerns, prevent abuse, and improve reliability.

Public profile fields can include display name, username, and avatar. Published stories expose only their screened publication copy and selected public credit. Visible comments expose screened public text and safe public-profile identity fields.

Email, account identifiers, original private drafts, original submission text, moderation flags, private notes, bookmarks, reading progress, highlights, and account notifications are not intended for public display.

An "Anonymous" story credit means the public does not see the account identity. RELEC still keeps the private ownership record needed for moderation, revision handling, and account security.

Supabase provides authentication, database, storage, and Edge Function infrastructure. Supported OAuth providers process sign-in information under their own policies. The public website is built as static files and may be served by a web-hosting provider.

Supabase authentication uses browser storage to persist a session. Security services such as CAPTCHA may use browser technologies of their own. RELEC does not currently run a separate advertising-cookie system. Future local reading preferences may require this policy to be updated.

Data may be retained while an account is active and for a reasonable period afterward where needed for publication history, safety, disputes, legal obligations, backups, or abuse prevention. Published and editorial records may need different retention from private drafts.

Version 1 does not currently provide a self-service account-deletion control. Users can edit supported profile fields and remove certain private saved items. Until a verified deletion workflow is available, deletion or privacy requests should be sent to safety@relecmedia.com. RELEC should confirm scope, identity, and any content-retention implications before acting.

RELEC uses account-based access controls and restricted public data projections, but no online service can promise absolute security. Users should protect their sign-in method and avoid including private information in public submissions.

Email safety@relecmedia.com for access, correction, deletion, safety, or privacy questions. The Contact page lists general and technical-support channels.