Privacy Notice

The Silencers is the commercial name of the platform initially operated from Mexico. Controller identity (individual or legal entity): [PENDING DEFINITION]. Controller address: [PENDING DEFINITION]. Privacy email and alternative contact without an account: [PENDING DEFINITION].

The Legal Center offers an authenticated rights request form, including during suspension. If you cannot sign in, use the official support email when configured and published. These channels do not replace the identity and address the controller must supply.

• Account: name, email, avatar, Discord, Google or GitHub identifiers, username, role, verification and security settings.
• Public profile and activity: biography, status, social links, images, card, followers, achievements, posts, comments, reviews, votes, resources, servers and collections.
• Communications: messages, groups, forums, calls, reactions, attachments and support tickets, including participants and dates.
• Commerce: cart, orders, items, prices, currency, taxes, discounts, invoices, subscriptions, inventory, keys, sales, commissions and payment status. The gateway processes full card details; we normally receive references and status, not the full number.
• Withdrawals: method, destination such as PayPal email or bank account, amount, notes and review.
• Hosting and databases: plans, instances, quotas, status, encrypted credentials, queries made through the console and required technical logs.
• Security and device: IP or IP hash, user agent, known device, sign-in events, attempts, reports, sanctions and audit records.
• Technical data: cookies, local storage, language, theme, push notifications, downloads, visits and operational metrics.

We do not intentionally request sensitive data. Avoid including it in profiles, messages, files, support tickets or AI prompts.

We receive data directly from you when you complete forms, publish, purchase, sell or contact Support; from sign-in providers you authorise; from the payment gateway; from other users when they interact with or report you; and automatically from your browser, device or requests to the service.

We also query public or technical information from game servers and connected platforms when you request verification or display of that information.

Primary purposes: create and authenticate accounts; show your chosen profile and content to its selected audience; provide messages, files, voice, calls and support; process purchases, delivery, balances, transfers, withdrawals and subscriptions; administer hosting; prevent abuse, handle reports and meet obligations and claims. Region, language and declared gender can be used for social discovery; you can decline to disclose gender and edit your profile. We do not ask every user for a birth date or identity document.

In Mexico we apply the relevant LFPDPPP grounds and exceptions to each activity; data indispensable to a legal relationship is not turned into optional consent. Financial or asset data for payments or withdrawals requires review of its function and grounds; acknowledging this notice does not authorize every financial use. European legitimate-interest concepts are not automatically imported into Mexican law.

Optional purposes: cookie-based referral attribution and external media loading when enabled by you. They have separate Privacy Preferences controls. Emails found are transactional and security-related; accepting Terms enables no general marketing campaign. New secondary or sensitive purposes require information and, where applicable, specific prior consent withdrawable without closing your account.

Profiles, posts, resources, servers, reviews, comments, public collections and public groups may be visible without signing in and indexed by search engines. Do not publish information you do not want to make public.

Direct messages, private groups, tickets, private files and account data are restricted to participants and authorised personnel with an operational need. Even so, do not treat them as a vault for secrets or assume end-to-end encryption. Recipients may keep their own copies.

Silentz sends OpenRouter the current message, browser-supplied history, public platform context and, if you attach an image, a processed version of it. OpenRouter routes the request to the configured model provider. Provider and policy may change with the model; we do not assume third-party zero retention or no training arrangements. Your DMs are not automatically sent to the assistant.

Translation sends public prose excerpts from resources, servers and other listings; document attributes and code stay local. Translations are stored in PostgreSQL. Assistant interface history may exist in the browser. For a proposed ticket, the server stores a summary and up to ten redacted context messages in SQLite for a 30-minute confirmation window; expired unconfirmed proposals are cleaned when new ones are generated. Confirmation copies context into the ticket, where it persists. Secret filtering is limited: do not include sensitive information.

The assistant discloses AI use before sending. It does not automatically open a ticket or independently decide a legal outcome, sanction or refund. Responses and translations require checking. Provider retention depends on its terms and actual configuration; we do not promise an unverified deadline.

Integrations depend on enabled features and configuration. Supabase Storage receives files through the public upload flow and serves public URLs; PostgreSQL holds primary data and may be hosted by Supabase. Operator SQLite and disk hold private files, media, stickers, tickets and database metadata. Discord, Google and GitHub exchange identity data for sign-in; Resend receives recipients and transactional email content.

Stripe, PayPal and Mercado Pago receive necessary data for the enabled transaction and return references and status. Cloudflare may provide tunnel/proxy and Turnstile abuse prevention. LiveKit processes room identity, connection metadata and audio or shared screens; we found no enabled call recorder. Sent voice messages and attachments are stored. Web Push uses the browser’s delivery provider. Upstash, if configured, holds expiring rate-limit keys.

OpenRouter and model providers process prompts, images and translation text. VirusTotal may receive hashes or full files in the configured scanning flow; it is not a private secrets repository. YouTube, Spotify and SoundCloud, and music lookup or playback through Deezer/Audius when used, may receive technical data and requests. Hosting panel and infrastructure operators depend on the plan; directory links belong to third parties.

Processors act on the controller’s behalf where that relationship exists; authentication, payments and external services may have their own purposes. We do not label all recipients processors without reviewing contracts. Processing may occur outside Mexico; actual regions and agreements must be confirmed for each integration. Transfers needing consent outside a legal exception require recipient and purpose disclosure and prior consent. We do not sell personal data. Mandatory authority disclosures are limited to valid requests.

We use authentication, security and language cookies; local storage for preferences and interface state; and, with your choice where required, referral or affiliate attribution cookies. We do not currently use Google Analytics or our own behavioural-advertising cookies.

See names, durations and controls in the Cookie Policy.

Accounts and content remain while their feature is provided and until closure or removal requests are resolved. Closure reviews multiple stores rather than performing instant universal deletion. Removing public content does not erase recipients’ downloaded or saved copies. Supabase files, disk and SQLite require separate action; hosting may need its own export and termination.

Email codes expire after 10 minutes; expiry does not mean immediate row deletion. Unconfirmed ticket proposals expire after 30 minutes and are cleaned when new proposals are generated. Attribution cookies last up to 30 days or until claimed or withdrawn. Local preferences remain until changed or browser data is cleared. Legal receipts record version, action, context and time, without full IP or device fingerprint.

Orders, invoicing, withdrawals and dispute evidence require assessment of duties and limitation periods before removal. No general automated purge or uniform verified backup rotation exists; closure responses explain scope and criteria. Mexican contractual breach records have the applicable 72-month statutory limit from breach. Data needing preservation is restricted to that reason without new-purpose reuse. The internal matrix identifies operational periods still requiring controller approval.

We apply reasonable controls such as encryption of selected secrets, salted hashes, permissions, file review, rate limiting, two-factor authentication and audit logs. No system eliminates all risk.

If we identify an incident that significantly affects your rights, we will investigate and notify people or authorities where the law requires it. You must protect your external accounts, devices, recovery codes and service credentials.

You can request access, rectification, cancellation or objection (ARCO), withdraw consent or limit disclosure through the Legal Center rights form. Identify the right, specific data or processing and how to establish ownership; do not publicly share identity papers or card details. Sign-in lets you initiate a request; proportionate identity or representation verification may still be needed.

For Mexico we communicate the determination within 20 business days of receipt and, if granted, implement it within 15 business days after the response. An extension for an equal period requires justification. We explain refusals, necessary retention or third-party rights and review channels. The authority named in current Mexican law is the Secretaría Anticorrupción y Buen Gobierno; we do not list the former INAI as the current channel.

You can edit account data and withdraw optional permissions in Privacy Preferences. Rejection leaves essential features available. Closure requests review balances, orders, services and stores; you receive the scope and reasons for retention. You need not accept new Terms to initiate these requests.

There is currently no age verification or verifiable guardian authorization flow. Discord or other provider sign-in is not proof of adulthood. If you are underage, guardian authorization and supervision must satisfy applicable law and provider rules; do not enter transactions for which you lack legal capacity.

The controller still needs to define a minimum age and specific procedures before offering child-directed services or processing requiring verified authorization. Guardians can use the rights channel to request review or removal of a child’s data. Public posting, messages, files and purchases need particular care; do not share sensitive data or precise location.

A foreign visit alone does not make every law of that country applicable. Where GDPR/UK GDPR covers the service or processing, purposes need specific grounds, applicable access, correction, erasure, restriction and portability rights, objection, authority complaints and transfer safeguards. The same channel accepts these requests; no nonexistent DPO or representative is appointed.

US state privacy duties, California and children’s protections depend on scope and activity. We do not automatically assert CCPA thresholds or a verified COPPA program. We do not sell data and found no own behavioral advertising. Mandatory rights remain available without discrimination for exercising them.