Legal

Privacy Policy

This policy explains how BryskBits handles personal data connected to the website, orders, services, support, abuse reports, and legal requests.

Last updated: 2026-11-12Version: 2.1

Read alongside your written order and the related policies below.

Questions & answers

Privacy in practice

Browse all topics
Does BryskBits routinely inspect customer content to decide whether it is legal?

No. BryskBits does not routinely screen customer content or traffic solely for that purpose. It may investigate credible abuse reports, security incidents and threats to the network, enforce its terms or respond to legally valid requests.

Does a cryptocurrency payment remove all account records?

No. A payment method does not change the need for order, billing, security and support records. Do not assume that offshore hosting or a particular coin makes an account anonymous.

Should I send logs with personal information?

Share only what is needed to identify the incident. Remove unrelated addresses, personal identifiers and access tokens while preserving relevant timestamps and error codes.

Is the physical server location enough to establish privacy compliance?

No. Consider what data the application collects, who can access it, where backups go and the contractual requirements for your use case.

How can I identify my account for a privacy request?

Use the contact channel in your agreement and identify the relevant service or invoice. Do not send passwords or identity documents through an unverified channel.

When is my account data deleted?

Three calendar months after the last service becomes inactive, not after your last login. We delete the account data; a specific record must be kept separately only if the law requires it.