Policy version 2026-08-06
Emberly Privacy Policy
This page explains the privacy rules enforced by the current Emberly build. It is written for members in plain language and does not replace advice from a qualified attorney for a public commercial launch.
Return to EmberlyAge requirement and consent
Emberly is available only to people age 13 and older. Registration requires an age entry and Privacy Policy agreement. Existing accounts that have not accepted the current policy version are blocked from normal app actions until they complete the consent screen.
Information Emberly stores
Emberly may store account profile information, device and login security records, server and group memberships, messages and attachments, support requests, reports, moderation history, call-signalling records, and limited diagnostic events needed to operate and protect the service.
Safety and diagnostic retention
Restricted message context captured for a safety review is configured for approximately 14 days unless it becomes part of an active case or must be retained for legal or safety reasons. Owner runtime diagnostic events are configured for approximately 30 days. Provider backups and infrastructure logs may follow separate retention periods configured with the hosting providers.
How information is used and protected
Information is used to provide messaging and community features, secure accounts, prevent abuse, respond to reports, troubleshoot failures, and comply with legitimate legal obligations. Access is restricted using authentication, database Row Level Security, staff permissions, audit logs, and owner-only server functions.
Your controls
The Account Security Center lets members review devices and login history, sign out other sessions, download an account-data export, manage recovery and sign-in methods, and request permanent account deletion after fresh authentication. Some safety, fraud-prevention, backup, or legal records may remain for a limited period where required.
Questions and policy changes
Questions can be submitted through Emberly Support. When the policy version changes, members are required to review and accept the updated version before continuing to use protected features.