Partnered communities and private sanction appeals
Connected communities send new BRAVE sanction records to Atlas so affected members can review their own decisions and request community appeal links from another connected BRAVE community. Records include an encrypted Root account identifier, local case number and member-visible reason, plus sanction type, category, date, expiry and active status. Private staff notes, internal reports and unrelated Atlas evidence are not included. Each community controls whether it accepts sanction appeals and can close appeals for selected categories. An appeal goes to that community's staff, not Atlas global reviewers. A 15-minute private link can be copied from the member's authenticated BRAVE profile; no Root password is requested on the website. Appeal text is encrypted at rest. A link holder can submit or view the corresponding appeal, so keep the link private.
Partner ban sharing starts off. Both communities must enable matching categories and explicitly agree to a targeted invitation. Only new human-issued bans after agreement propagate; automatic moderation, Atlas bans and partner-imported bans do not create chains. Partners receive the affected Root account, category, source community and expiry, but not the original private reason or reports. BRAVE protects staff and exemptions, preserves independent local bans and records imported decisions. Ending the partnership, withdrawing the source decision or disabling an agreed category releases only bans that BRAVE can confirm it owns. Staff may override an imported ban locally. Native Root bans use Other unless staff assign a category. Missing permissions or outages can delay enforcement and restoration; the app records and retries work rather than claiming an unsuccessful action happened.
Sanction and appeal records expire after 180 days unless needed for an active ban. Active permanent bans remain until withdrawn; their appeals remain with that decision. Expired website links are removed by scheduled maintenance. Disconnecting Atlas ends partnerships and hides the community's sanction records from member queries; retained records follow the same schedule. Contact imbrave@wdym.site for an access, correction or deletion request.
Optional member verification
Community administrators can choose off, optional verification, or required verification for all newcomers, selected newcomers, or everyone. Selected rules use account age and whether the Root profile has a custom photo. Unknown selected facts require verification rather than assuming the member qualifies. Existing members are included only with the Everyone setting. Verification takes place at www.wdym.site after a member creates a private link inside their authenticated Root account. The website displays the collection notice before the member agrees. Completion also requires pasting a code back into the same Root account; a website visit alone cannot verify an account.
After agreement, the website sets a first-party, Secure, HttpOnly browser cookie for up to 90 days and processes the request's public IP address. The website sends keyed fingerprints of the cookie identifier and IP to Atlas through an authenticated server request. It also sends the hosting provider-observed IP transiently for any required CAPTCHA or VPN check; that address is not written to verification tables. Atlas scopes fingerprints to the community and keeps account identifiers encrypted, with verification records expiring after 90 days. BRAVE and Atlas do not store raw verification IP addresses or expose them to staff. Vercel and the VPS hosting/proxy infrastructure may retain IP addresses in operational request logs according to their own policies. Verification challenges expire after 15 minutes and are removed no later than one day after expiry.
Staff with review access can inspect related verified accounts and whether the match used the same browser identifier or a shared public network. Matching does not prove a physical device or a person's identity. Shared computers, households and public networks can involve different people. Cookie clearing, private browsing, another browser, VPNs or another network can evade checks. This version does not inspect installed apps, collect hardware serial numbers, use hidden canvas fingerprints, or identify every VPN or alternate account. Associations stay within each community and never create an Atlas misconduct score or global ban.
Admins can choose alerts or a staff-review hold for same-browser matches. Shared-network matches are advisory only. Administrators can also require hCaptcha and block networks classified as VPNs or proxies by Proxycheck. These services receive the current public IP only when their check is required; hCaptcha also handles its widget and challenge data under its own policy. Classification may be incomplete or incorrect. CAPTCHA responses are validated server-side against the configured site key and website hostname, and are not retained. VPN results are cached for six hours under keyed network fingerprints. The free lookup budget is limited: service errors or exhausted checks keep verification pending, with staff approval available. Required verification and holds add no strike. With Airtight mute enabled, BRAVE attempts personal posting restrictions and voice mutes while keeping assigned roles and preserving unrelated staff changes. It sends private instructions and can send a mention in a staff-selected channel visible to the member. Where its Root permissions cannot enforce the gate, or Airtight mute is disabled, it can only remove posts after they reach the app. Owners, staff and configured trusted roles are exempt. Staff can approve access, and separate moderation restrictions remain in force.
Members can delete this community's Atlas verification records from the in-app Verification page. This also clears local verification status and may require verifying again or contacting staff in a community that requires verification. Disconnecting Atlas deletes that community's verification fingerprints. BRAVE retains a local restriction ledger only to restore its access-rule changes and a minimal pending/approved status; it does not locally retain browser or network fingerprints. Contact imbrave@wdym.site if the app is unavailable. To remove the website cookie, clear site data for www.wdym.site in your browser.
Feedback and permission checks
Suggestions and bug reports sent through BRAVE go to a private developer inbox. Feedback text is encrypted at rest and retained for up to 90 days with pseudonymous account and community fingerprints. The endpoint cannot independently verify an author's Root identity; submissions are reviewed. Optional ratings from 1 to 5 are published only as an anonymous average and count after review, including low ratings. One latest approved rating per pseudonymous account contributes to those totals. Text, account identifiers and community identifiers are never published with ratings. A Root app-store review is separate and optional.
Staff can audit the roles, members and channel access rules BRAVE can read. Hidden channels cannot be certified. Supported role repairs require an explicit preview confirmation and are logged locally for 90 days. A staff-selected volunteer test lasts 60 seconds, notifies the member, adds no strike and changes no channel access rules. BRAVE attempts to remove the timeout role it assigned after the test, and retries cleanup after outages. A received post proves Root allowed posting; no received posts alone cannot prove it blocked posting.
Atlas ban review flags
A separate opt-in shares new human community ban decisions confirmed by BRAVE through Root. Atlas keeps keyed fingerprints of the account, moderator and normalized ban reason, plus private similarity signatures, rather than reason text. Ban reports are kept for up to 48 hours. Similar bans from at least three source groups within 30 minutes can produce a 24-hour unverified review flag. Shared moderators and known related sources count together. Automatic BRAVE and Atlas decisions are excluded. These reports do not prove misconduct, increase the punishment score or authorize bans. Unbanning, disabling sharing or disconnecting withdraws active contributions. Review flag records are kept for up to 30 days.
Public Atlas join alerts are optional. They announce explicit operator decisions or clearly labelled test flags in the busiest eligible channel, with cooldowns. AI-only and unverified ban-pattern leads remain in staff logs. Operator test flags expire after 24 hours and carry no punishment or misconduct finding.
At a glance
BRAVE helps Root communities moderate messages and manage safety. It is operated by WDYM Softworks. A community administrator chooses BRAVE’s settings. Local rules work without Atlas or AI; Atlas sharing and AI analysis are separate, optional settings. BRAVE does not sell app data, use it for advertising, or train AI models on it.
This policy covers BRAVE and this legal website. Root separately operates the Root platform under its Privacy Policy.
Data BRAVE handles
Depending on the permissions granted by a community and the features it enables, BRAVE receives Root user and community identifiers, roles, channel identifiers, messages, attachments and event metadata. It reads this information to apply configured rules, detect spam or harmful content, and show relevant results to authorized people.
When a rule matches or someone files a report, BRAVE may save a message excerpt of up to 240 characters, the relevant identifiers, matched rules, timestamps, a report reason, review status, and moderator actions. It also stores cases, appeals and responses, configuration and revision history, and operational notices. Staff-selected log channels on Root may receive action or report details, visible according to that channel’s permissions.
Member insights are enabled by default but administrators can turn them off. When enabled, BRAVE stores per-member message counts, activity by channel and hour, a recent daily series, and—if the separate word setting remains on—frequent words. It does not need to retain every message to produce these summaries.
Why we use it and your controls
We use app data to enforce the community’s chosen rules, show moderation queues and member-facing notices, investigate reports, process appeals, provide member insights, keep the service secure, and diagnose failures. Community administrators can configure rules, notices, logging, insights, Atlas, AI analysis and automated actions. Moderators can review and reverse decisions where the app permits it; members can view their BRAVE standing and submit appeals.
BRAVE’s decisions can affect a member’s access to a community. Automated matches may be wrong. Community staff should review disputed actions and can use BRAVE’s case and appeal tools. Root’s own permissions and community settings still control what BRAVE can do.
Optional Atlas and AI analysis
Atlas is an optional cross-community safety feature. If enabled, BRAVE sends a Root user identifier to our Atlas service, which derives a secret-keyed pseudonym. Atlas stores that pseudonym, the community identifier, a signal category and severity, and a timestamp. Local-rule signals do not include message text. Atlas may return an aggregated risk result from participating communities. Atlas’s risk engine runs in shadow mode: recommendations do not trigger bans. Report counts and AI alone cannot authorize network punishment.
Separate manual Atlas bans require an explicit human operator decision. Their Root account IDs are encrypted at rest, alongside a keyed pseudonym, decision reason, operator identifier and timestamps. Connected BRAVE servers may receive these IDs and reasons through a private authenticated feed. Communities must separately opt in to enforcement; it is off by default. BRAVE checks changes every five minutes and on member joins, exempts owners, managers and configured trusted roles, and records enforcement receipts in Atlas. These decisions affect participating communities, not Root-wide accounts. An accepted Atlas appeal revokes that manual decision; independent local bans remain.
AI analysis is another separate opt-in setting, available only while the community has more than 1,200 members. When enabled, message text up to 5,000 characters is sent through our Atlas service to OpenAI’s Moderations API for classification. The Atlas database stores a content hash and classification for caching, not the submitted plaintext. BRAVE does not train LLMs or other AI models with this feature. OpenAI says API data is not used to train its models by default unless the customer opts in; see OpenAI’s API data controls. AI capacity limits or provider failures do not switch off BRAVE’s local rules.
Atlas and AI are off by default. Disconnecting Atlas stops new sharing. Existing signals expire on the schedule below or can be withdrawn individually after review.
Who receives data
Root hosts BRAVE’s per-community app instance and datastore. Authorized community staff see moderation information according to their Root permissions and BRAVE settings; members see their own standing and appeal information. Connected communities use Atlas for private sanction appeals; optional verification, partner sharing, safety signals and AI use the information described above. If AI analysis is enabled, OpenAI receives submitted text for classification. We may disclose information when required by law or to address security and abuse. We do not sell app data.
This website is hosted by Vercel. General pages do not set first-party cookies or run analytics. The consented member-verification flow sets the browser cookie described above. Vercel may process ordinary request information, such as IP address and browser metadata, to deliver and secure the site; see Vercel’s Privacy Notice.
How long records remain
BRAVE’s scheduled cleanup removes incident records after 30 days. Cases are removed after one year when their action has expired or has no expiry, except active permanent bans, which remain until lifted. Closed appeals are removed after 180 days; open appeals remain until resolved. The daily member-insights series keeps approximately 60 days, while other activity aggregates and the most frequent 200 words per member currently have no automatic expiry. Configuration history keeps the latest 50 revisions.
Atlas removes safety signals and analysis records after 90 days, classification cache entries after one day, and general Atlas audit entries after 30 days. Verification records expire after 90 days. Community sanction and appeal records expire after 180 days unless required for an active ban. Manual global ban decisions, their encrypted account identifiers, operator audit history and community enforcement receipts have no automatic expiry, including after revocation; contact us to request review or deletion. These periods describe the app’s scheduled database cleanup; Root’s hosting, backups and community log channels may have separate retention. A disconnected community’s Atlas connection record is revoked, while prior signals continue to follow their retention schedule unless withdrawn. We may retain information longer when necessary to comply with law or resolve a legitimate dispute.
Access, deletion and questions
Email imbrave@wdym.site to request access, correction or deletion, to contest a BRAVE decision, or to ask a privacy question. Include your Root user ID, the community concerned and enough context to locate the record; do not send passwords or sensitive message content. We may need to verify the request and coordinate with the relevant community administrator or Root. Applicable law may give you additional rights. You can also use BRAVE’s in-app appeal flow for a moderation decision.
Root controls its own account and platform data. For Root-wide requests, use the channels in Root’s Privacy Policy.
Security and updates
We limit access to moderation information, use authenticated connections for Atlas requests, and keep provider credentials out of the client. No security measure is perfect. Processing may occur where Root and our service providers operate. We will update this page when BRAVE’s practices change and show the latest date at the top. Material changes will be communicated through the app or another appropriate channel.
Community showcase and protection totals
Atlas-connected BRAVE installations send a protection heartbeat every five minutes containing their community ID, current member count and whether local protection is enabled. The website publishes aggregate counts for connected installations that reported active protection within the last 30 minutes. These are memberships across communities, which may overlap, rather than unique people. Totals do not include installations that are not connected to Atlas.
Administrators may separately opt in to publish the community's name, small avatar and member count on BRAVE's page. The page shows up to 12 profiles. Names and avatars are not sent for communities that have not opted in. Disabling the showcase clears the stored public name and avatar on the next successful update; cached views can remain briefly. Disconnecting Atlas removes the installation from the public results. Profiles inactive for 30 days are removed. Individual member profiles, IDs, messages and moderation records are never included in this showcase.
Website connection codes and Atlas appeals
At Connect Atlas, the website sends your code to Atlas to approve its specific community request. Codes expire after 15 minutes. Atlas stores a hash of the code; the private community token stays in BRAVE's Root-hosted server.
At Atlas appeals, an appeal code issued for your authenticated Root identity links your explanation to your Atlas case. The code expires after one hour. The website processes the code and explanation through a Vercel function and transmits them to Atlas over HTTPS. Atlas stores the explanation encrypted at rest; senior Atlas reviewers can read it to investigate the appeal. Open explanations remain available until review; closed explanations are removed after 180 days. Your private receipt code can show appeal status for 180 days. Atlas appeals do not automatically reverse local community decisions.
Connection codes confirm requests rather than independently verifying Root community ownership. They do not establish the authenticity of reports. Atlas's evidence engine remains in shadow mode and cannot authorize bans. Separate manual operator bans can be appealed here; accepting an appeal revokes that Atlas decision, and opted-in communities sync the revocation. Independent local decisions remain. Community member reports stay in BRAVE's local Review queue unless separately submitted as Atlas evidence.
Write to imbrave@wdym.site. We’ll point you to the right place.