SEC MAIL
RU EN
No magical promises

What we protect.
What data we need.

A technical description of the current service and how website requests are handled.

Website and forms

Your manually selected website language is saved in the secmail_lang cookie for one year. Automatic selection uses your browser’s primary language.

The website has no advertising trackers, external analytics or third-party CAPTCHA. Forms use a necessary session cookie for CAPTCHA and request-forgery protection. A submission stores its category, reply email, subject, text, reported address, IP address and time. Staff handling the request can access it; administration messages are restricted to the administrator.

Handling requests

A reply address does not prove ownership of a mailbox. By submitting the form you provide data for us to review and respond. Do not include passwords, private keys or information that is unnecessary to resolve the issue.

Closed requests are removed from the register 90 days after their last update. Unresolved requests remain until handled. Email notifications contain only the reference number and category, not the message text. Separate support correspondence and technical logs have their own retention periods.

Mail encryption

Storage uses mail-crypt. This is encryption at rest, not end-to-end encryption: the running server processes messages. Client connections use TLS; encryption during delivery to another mail server also depends on the receiving side.

PGP and public information

Senders and recipients can use end-to-end encryption to protect message content from mail operators. It does not hide all metadata. Donor names are published manually and only with consent.

Send questions about data handling and deletion through the administration form. Before public launch, this description will be supplemented with operator details and final retention periods for logs and correspondence.

Contact the administration ↗