Legal
Privacy Policy
This policy explains how BryskBits handles personal data connected to the website, orders, services, support, abuse reports, and legal requests.
We collect only the data needed to answer your inquiry, provide and secure your service, handle payments and meet applicable legal obligations. The email draft on our contact page stays in your browser until you choose to send it through your own email provider.
1. Data we collect
- account and contact details you provide;
- billing, invoice, payment status, and tax-related information;
- service records such as server identifiers, IP allocations, configuration notes, and support history;
- technical logs needed for security, operations, abuse prevention, and troubleshooting;
- website analytics and browser data where configured;
- abuse reports, legal notices, and related correspondence.
2. How we use data
We use data to respond to inquiries, process orders, provision services, operate infrastructure, provide support, prevent abuse, enforce policies, secure accounts, handle billing, comply with legal obligations, and improve the website. We do not sell personal data.
3. No routine content monitoring
BryskBits does not routinely inspect, screen, or monitor customer content or traffic solely to determine legality. We may investigate or act when responding to credible abuse reports, protecting the network, investigating incidents, enforcing terms, complying with applicable law, or responding to legally valid requests.
4. Sharing and processors
Data may be shared with suppliers needed to provide services, such as datacenters, carriers, payment processors, fraud-prevention services, monitoring tools, support systems, professional advisers, or legal authorities where required.
5. Retention
We delete your account data three calendar months after your last service becomes inactive. The clock runs from the end of the last service, not from your last login. You do not need to request deletion. This includes your account profile, contact details, and account-linked provisioning and support records. We do not keep a separate customer profile after deletion.
If applicable law specifically requires preservation of a particular record, such as a tax invoice or a record under a binding preservation order, only that record is kept for the required period and deleted when the obligation ends. This does not extend retention of the rest of the account.
The three-month period is not a server backup or recovery window. Export your files before service ends. Account deletion cannot erase transactions already recorded on a public blockchain.
6. Security
We use reasonable technical and organizational safeguards for account and operational data. Customers remain responsible for securing their own servers, software, credentials, keys, applications, and customer content unless a written managed-service scope states otherwise.
7. Your rights
Depending on your jurisdiction, you may have rights to access, correct, delete, export, restrict, or object to processing of personal data. These rights may be limited by security, abuse, billing, legal, or operational obligations.
8. Contact
Use the contact channel in your service agreement for a privacy request. Include enough information for us to identify the relevant account or service without sending unnecessary sensitive data.
Read alongside your written order and the related policies below.
Questions & answers
Privacy in practice
Browse all topicsDoes 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.
