Privacy policy

    LAST UPDATED · 2 OCTOBER 2026

    This policy explains what data SUDODMCA processes when you use the site, an account, the software tools, and the Telegram bot. There is no public chat on the site.

    Data operator

    The site operates under the SUDODMCA name. Data questions and formal requests to the operator are accepted at legal@dmca.su.

    What data is processed

    • Technical data: IP address, user-agent, request details, a browser identifier, and interaction signals needed for security and to limit automated requests.
    • Notice generators: what you enter into the DMCA notice generators stays in the browser only and is not sent to the server.
    • Telegram bot: messages, replies, and voice attachments if you write to the assistant in Telegram. This is a separate processing path, not a site page.
    • Account: email or Telegram profile data, sign-in details, account links, and authorization sessions.
    • Requests: messages and materials you send yourself in Telegram.
    • Site events: visits, article and video views, downloads, and other limited technical counters.

    The server receives an IP address on connection. In application statistics and rate limiters it is stored as a hash with a private salt. Infrastructure may briefly process the original IP in technical logs.

    Local storage and cookies

    • The generator on the DMCA page saves nothing by default. If you turn on “Remember details on this device”, assembling a notice stores your name, email, address, nickname and original link in the browser — until you untick it, press “Delete saved details”, or clear site data.
    • The English §512 template keeps its notice draft in the browser, the claimant details when you save them, and a list of sent notices (platform, recipient address or form, number of links, date) when you mark a notice as sent. The recu.me complaint helper keeps the profiles you create. This data stays on the device until you clear site data or delete it in the tool where that is available.
    • The “read later” list stays on the device until the user deletes it.
    • The browser also stores technical flags for visits, interface reloads, and warning display. They do not contain messages or contacts.
    • Necessary cookies support sign-in and CSRF protection.

    Advertising cookies and third-party ad analytics are not used. Deleting local data or cookies may end the session and reset settings stored on the device.

    Why, and on what basis

    • To run the chosen feature, reply to a request, and perform an agreed service.
    • To sign in to an account and restore a user session.
    • To protect the site, limit abuse, diagnose errors, and keep aggregated statistics.
    • On the basis of consent, pre-contract steps, contract performance, or legal requirements — depending on the situation.

    External services and data transfers

    Data is not sold. It is transferred only to the extent needed for the chosen feature, infrastructure operation, or a lawful request. Some providers’ infrastructure is outside Russia, so a chosen feature may include a cross-border transfer.

    • Telegram-bot messages are sent to OpenRouter and the selected model provider. For text requests, providers that collect user data are excluded from routing. Voice messages are sent to OpenRouter and the selected speech-recognition provider to convert audio to text. OpenRouter stores technical request metadata; content may be stored only if the account owner separately turns that setting on.
    • Telegram sign-in receives the data shown in the authorization window.
    • One-time links are sent through mail infrastructure. Hosting and related technical providers process the data needed to deliver the site and messages.
    • When error monitoring is enabled, technical details are sent to Sentry. Sensitive request bodies, authorization headers, and cookies with tokens are excluded from those events.
    • Embedded videos load from YouTube only when you open a page with that material. YouTube may receive an IP address and browser details.

    Retention periods

    • RAG queries — up to 90 days.
    • Visits and article views — up to 180 days; download events — up to 365 days.
    • One-time sign-in records — up to 90 days; the link itself is valid for 30 minutes.
    • Account data is kept while the account is used, or until a justified deletion request, unless the law requires keeping it longer.

    Server technical logs are usually kept about 7 days. Sentry event retention is set in the account and is usually 30–90 days.

    Rights and data deletion

    • Learn what data is processed and obtain a copy.
    • Ask to correct, restrict, or delete data, or withdraw consent.
    • Delete the DMCA-page generator data by unticking “Remember details on this device” or with “Delete saved details”; other local data and cookies through browser settings.

    Send the request to legal@dmca.su. To protect the data we may need to confirm identity or a link to an identifier, account, or request.

    Data protection

    We use HTTPS, access limits, hashing of sensitive identifiers, and protected cookies. Absolute security of transmission and storage cannot be guaranteed.

    Policy changes

    The policy is updated when site features, providers, or legal requirements change. The date of the current version is shown at the top of the page.


    When processing requires consent, the site asks for it separately. This policy itself does not replace that consent.