Privacy Notice

Information you provide

Account information includes your email address, username, password credentials handled by our authentication provider, profile details, profile artwork, preferences, and settings.

At signup, we process your self-reported date of birth to calculate your age. We retain only the calculated age and declaration time in a private eligibility record, not your full date of birth. This is not identity verification. These details are not part of your public profile or our usage analytics. The active eligibility record is removed when your account is deleted.

If you request beta access before creating an account, we store your email, request time, invitation status, and email-notification status in a private owner queue. We use these to review your request and contact you about access, not to enroll you in marketing. Request notifications are delivered to our administrative inbox through our transactional email provider. You can ask us to delete your request.

Content includes server messages, threads, replies, direct messages, reactions, reports, uploaded files, server membership, roles, friendships, blocks, and other actions you choose to perform. Issue reports can include your description, reproduction steps, expected result, and the Revelog page and app version that generated the report.

Information created while operating the service

Revelog records security and operational information such as account events, moderation actions, abuse signals, notification state, call participation, connection quality, and limited diagnostics. Voice, video, and screen-share media are transmitted for live communication and are not recorded by Revelog unless a future recording feature clearly asks for consent.

Attachments enter private quarantine and are checked for file type, size, integrity, and malware before they can become readable.

How information is used

Information is used to provide accounts and communication, personalize settings, deliver notifications, secure the platform, enforce community controls, investigate reports, prevent abuse, recover from failures, and understand reliability.

Revelog does not sell personal information or sell access to private messages. When monitoring is configured, selected usage events help us understand signup, entry into the app, return visits, and participation. We do not send message or attachment contents, names, email addresses, birthdays, search text, server or channel names, authentication credentials, page URLs, raw error text, or session recordings to product analytics.

Before sign-in, usage events use a random identifier stored for the current browser tab. After sign-in, a separate random analytics identifier can link those events to the same account across visits and devices. This is pseudonymous, not anonymous: Revelog keeps the account mapping in a private backend table, but does not send your internal account ID to PostHog. We collect limited categories such as browser or desktop, whether an action included an attachment, and whether a signup link came from Reddit, X, or another source. We do not collect the full link or its other parameters. The temporary signup link between identifiers is removed after successful delivery, or on the next analytics session after seven days. Deleting an account removes its local analytics mapping; it does not automatically erase events already sent to a provider. Contact us before deleting your account if you want help removing those records.

Analytics do not run on password-reset or desktop-authorization pages. Client tracking and the optional server verification event honor browser Do Not Track and Global Privacy Control signals. No session replay or automatic page-content capture is enabled. Providers necessarily receive network information when a request reaches their servers; analytics disable IP-based location enrichment. Earlier beta clients sent account IDs, email addresses, and usernames to analytics. The current client does not send those fields, but updating the app does not erase previously collected records.

For the owner’s aggregate activity board, Revelog also records whether a signed-in account interacted with the app on a given UTC day. This first-party record contains only the account identifier and date, not typed text, visited pages, or message content. It respects Do Not Track and Global Privacy Control and is removed on account deletion. Records older than seven days are cleared when new daily activity is recorded; if activity stops, cleanup resumes with the next record. The owner board shows totals, not individual activity histories. Counts reconstructed from records needed to operate Revelog, such as posts, votes and server joins, remain available without this optional interaction measurement.

You can contact privacy@revelog.com about access to or deletion of analytics records.

Service providers

Revelog relies on a small number of service providers: a managed platform for authentication, database, realtime delivery, and storage; a live media provider for voice, video, and screen sharing; a content delivery and security network; an attachment malware scanning service; a transactional email provider for account email; an error monitoring service configured to minimize personal data; and a product analytics service for limited usage and reliability measurements.

These providers process information only to deliver their services under their own security and privacy commitments.

Retention and deletion

Active content is retained while the account or community remains active. Deleted content may leave a protected moderation record or limited snapshot for appeals, abuse prevention, legal obligations, and conversation integrity. Reviewed safety metadata follows bounded internal retention periods. Backups can retain prior data until they expire.

You can export your account data and request account deletion from settings. Some security, moderation, transaction, and legal records may remain when retention is necessary to protect other users or satisfy legal obligations.

Your choices and contact

Settings control profile visibility, direct-message access, presence, notifications, sounds, blocks, mutes, and other privacy boundaries. You can request access, correction, export, or deletion through the controls provided in Revelog.

Privacy questions and requests can be sent to privacy@revelog.com. We may need to verify that a request comes from the account owner before acting on it.