Legal request guide
Requests should identify the service, the information sought and the authority relied on.
1. Send a scoped request
Contact [email protected]. Include the relevant IP or order identifier, a timestamp and timezone, the specific records sought, the legal authority relied on, and a contact for clarification. Provide the applicable documents and their scope.
Requests are assessed for authenticity, scope and applicable requirements. A foreign location, optional contact or crypto payment does not establish immunity from binding legal obligations.
2. Records and limits
The privacy policy describes account, configuration, order, payment and support information. Contact details are optional; they may exist if the customer supplied them. We do not promise the existence of a particular record or an infrastructure-wide absence of all logs.
No identity-document upload is requested in standard checkout. No verified numerical history of requests, disclosures or seizures is published.
3. Response and notification
Requests that are incomplete or unclear may require clarification. Any response must be limited to the relevant request and applicable obligations. Customer notification depends on whether a contact channel is available and notification is permitted.
Urgent threats should be clearly described with the specific risk and affected service. Do not send unrelated sensitive data with an initial enquiry.
4. Published information
The transparency page links current policies and publication status. No signed warrant canary has been issued; its absence is not a statement about any particular request.