Privacy
Privacy Policy.
Last updated: May 16, 2026. This policy explains how RENGAL handles the data needed to run accounts, communities, messages, calls, files, safety, billing, and support. RENGAL means the RENGAL service and its operator.
Who to contact
For privacy, account, deletion, export, safety, or support requests, contact support@rengal.app. We may need to verify your account before acting on requests that affect account data, community data, or message access.
Information RENGAL processes
- Account information, including email address, display name, username, avatar, profile settings, verification state, password hash, consent records, and account status.
- Community and social information, including guilds, channels, roles, memberships, friend relationships, blocks, reports, moderation actions, and invitation context.
- Content you provide, including messages, replies, threads, reactions, pins, attachments, file metadata, DMs, group DMs, profile text, support messages, and diagnostic bundles.
- Voice and media information, including call or Hall participation state, room identifiers, connection events, media-session metadata, mute/deafen state, and moderation actions. RENGAL does not need to store the contents of live audio/video streams to route calls.
- Operational information, including request IDs, timestamps, logs, IP-derived security signals, client version, platform, device details, browser details, crash details, and error reports.
- Email and account-security information, including verification tokens, password-reset tokens, email delivery status, and account/security notices.
- Billing information when paid features are introduced, such as plan status, invoices, transaction identifiers, payment-provider references, and billing contact details. Full card data should be handled by the payment provider, not stored directly by RENGAL.
How RENGAL uses data
- Provide and maintain the service, including accounts, login, DMs, channels, replies, reactions, pins, search, attachments, voice/call presence, notifications, and settings.
- Protect accounts and communities through email verification, password reset, abuse prevention, moderation, rate limits, fraud prevention, security monitoring, and incident response.
- Debug issues, investigate support requests, measure reliability, understand whether releases work correctly, and improve product quality.
- Send service emails such as verification links, password reset links, account notices, security notices, billing notices, and important product or policy updates.
- Process subscriptions and billing if paid features are enabled.
- Comply with legal obligations, enforce the Terms of Service, and respond to lawful requests where required.
Legal bases and consent
Where laws such as the GDPR apply, RENGAL processes personal data using legal bases such as providing the service you requested, legitimate interests in operating and securing the platform, consent where required, and compliance with legal obligations. You can withdraw consent-based processing where applicable, but some data is necessary to keep your account and communities working.
Sharing and subprocessors
RENGAL does not sell personal data. We use service providers only where needed to operate, secure, improve, bill for, or support the service. These may include hosting, database, storage, email, push notification, analytics, payment, crash reporting, and support providers.
Community owners and moderators may see content, reports, membership details, and moderation context inside communities they manage. Other users see content you choose to post, send, upload, react to, or share with them.
Cookies, local storage, and client data
RENGAL may use cookies, local storage, secure storage, and similar client-side technologies to keep you signed in, remember preferences, route API requests, protect sessions, and support app behavior across web, desktop, and mobile. You can clear browser storage, but doing so may sign you out or reset local preferences.
Retention
- Account and community data is kept while the account or community exists, unless deleted, removed, or retained for safety, legal, backup, or abuse-prevention reasons.
- Messages, files, pins, replies, moderation records, and reports may remain visible according to product behavior, community settings, safety needs, or legal requirements.
- Verification and password-reset tokens expire and are stored server-side as hashes.
- Operational logs are kept for a limited period for debugging, abuse prevention, security, and reliability.
- Backups may retain data for a limited time after deletion until backup cycles expire.
Security
- Passwords are stored as hashes, not plain text.
- Verification links and reset links are private and should not be shared.
- RENGAL uses technical and operational safeguards appropriate for the service, but no online service can guarantee perfect security.
- If you believe your account or a community is compromised, contact support quickly.
Your choices and rights
You can update account details and change your password inside RENGAL. Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal data. Contact support@rengal.app to make a request.
Some requests may be limited when data is needed for security, fraud prevention, legal compliance, dispute handling, backups, moderation records, or to protect other users.
Children
RENGAL is not intended for children under 13 or for anyone below the minimum age required by their local law. If you believe a child has provided personal data in violation of this policy, contact support.
International operation
RENGAL may process and store data in countries different from where you live. When data moves across borders, we use service providers and safeguards appropriate for operating the platform.
Changes to this policy
We may update this policy as RENGAL changes. If changes are material, we will provide notice through the site, app, email, or another reasonable method. Continued use of RENGAL after an update means the updated policy applies from its effective date.