BlossomHost1Who we are
Blossom Host is a sole proprietorship in California, United States, operating blossomhost.us. For the purposes of data-protection law we are the controller of the personal information described in this policy.
This policy covers our website, customer dashboard, Discord and Telegram bots, and the hosting services we provide. It does not cover the content you put on a server you rent from us — see section 3.
Contact: ben@blossomhost.us
2What we collect
2.1 Account and identity
How this looks depends on how you sign in. We collect only what the chosen method gives us:
| Sign-in method | What we store |
|---|---|
| Your email address and a hashed password (scrypt). We never store your password itself and cannot read it. Also the time of your last login. | |
| Discord | Your Discord user ID. Not your password, and not your message history. |
| Telegram | Your Telegram user or chat ID, supplied by Telegram's login widget. |
| Legacy payment provider | Your historical membership and provider identifiers. |
Where you link more than one of these, we store the link so your servers follow you between them. We also store the date your account was created, which our fraud controls use.
2.2 Orders and billing
For each order: the plan, operating system, term, add-ons, any coupon or referral code, the amount charged, the payment provider and method, provider-side invoice and checkout identifiers, the order's current state, and its expiry and renewal dates.
We do not collect or store your card number, bank details, wallet credentials, or crypto wallet credentials. Card and supported wallet payments run through Stripe, historical memberships remain with their original payment provider, and crypto runs through BTCPay; we receive provider references, payment status, and the limited payment and fraud signals described in this policy.
2.3 Service and technical data
The identifier and IP address assigned to each server you rent, its specification, its provisioning and lifecycle state, and bandwidth and resource usage measured for allowance enforcement and node capacity planning.
To detect spam, scanning, credential attacks, denial-of-service activity, and similar network abuse, we process limited network-flow metadata such as source and destination addresses, ports, protocol, connection counts, and timestamps. We do not capture packet payloads or intercept encrypted traffic. Ordinary destination addresses are aggregated in memory and not retained; a source address and aggregate counts are retained for up to seven days only when a fixed threshold creates an abuse incident, unless a longer period is required for a complaint, legal claim, or lawful preservation obligation.
2.4 Support
The subject and body of support tickets you open, and the correspondence that follows — including messages you send us on Discord or Telegram in the course of support.
2.5 Audit log
We keep an append-only record of consequential actions on an account: invoices created and paid, renewals, warnings, suspensions, terminations, provisioning, administrative actions, and support events. Each entry records who acted, what they did, which order or service it touched, and when.
This log is deliberately immutable. It is how we resolve billing disputes and payment fraud, and it is the evidence we submit when contesting a chargeback.
2.6 Website usage
When you visit the site we create a first-party session record identified by a random ID in a cookie, containing: any referral (ref) code in the URL, the referring website, UTM campaign parameters, a coarse country derived from your IP address, which site variant you were served, first-seen and last-seen timestamps, and a count of events.
We also record page views and interactions — such as viewing a plan or starting checkout — as a stream of events against that session. If you later sign in, the session is linked to your account, which lets us see which campaign a customer came from.
Our servers and those of our providers keep standard access logs including IP addresses, user agents, and request paths.
2.7 Fraud-prevention signals
When you create an account or place an order, we collect signals used to tell a real customer from an automated or fraudulent one. These are gathered at those two moments — not as you browse — and are used for fraud prevention only. They are never used for advertising, never sold, and never shared with advertisers.
- Device characteristics — your browser and operating system, screen and language settings, timezone, processor and memory class, graphics hardware, installed fonts, and small rendering measurements taken from the graphics and audio systems. Together these form a device fingerprint. We store it as a hash, not as the underlying details.
- Interaction characteristics — how long the order form took to complete, the rhythm and variability of typing, and whether a hidden field no human can see was filled in. We measure timing and pattern, not the content of what you type.
- Request characteristics — your IP address, the network it belongs to, and the shape of the request your browser sends.
We use these to detect automated ordering and to recognise when many different accounts are being created from one machine. A device fingerprint is never treated on its own as proof of anything, and a shared network address is never treated as evidence that two customers are the same person.
We keep the resulting risk assessment — the score, the reasons, and the decision — as part of the audit record described above, because it is the evidence behind any order we hold or refuse.
2.8 Referral and affiliate data
If you join through a referral link or invite, we record which affiliate introduced you as a permanent first-touch attribution. Affiliates see aggregate counts and commissions attributable to them — they do not see your identity, contact details, or what you run.
3What's on your server
The data inside a server you rent is yours, and this policy does not govern it. If you store other people's personal information on it, you are the controller of that information and responsible for it — including for your own privacy notice, lawful basis, security, and breach reporting. We are at most a processor acting on your instructions.
We do not routinely inspect, index, scan, or read the contents of your server. Abuse monitoring begins with network-flow metadata and does not inspect your files, packet payloads, or encrypted communications. Access to server contents is limited to providing or repairing the service at your request, responding to a specific credible incident where content access is necessary and lawful, or complying with legal obligations.
The browser console in your dashboard renders your server's screen output. When our staff assist you through it, they may see what is on that screen.
If you have purchased Backup & Recover, or where we hold operational disaster-recovery copies, those copies are encrypted and are subject to the same restrictions.
4Why we use it
| Purpose | Basis |
|---|---|
| Creating your account, provisioning servers, delivering credentials, taking payment, sending renewal and expiry notices | Performing our contract with you |
| Support | Performing our contract with you |
| Detecting and preventing fraud, chargeback abuse, and breaches of the Acceptable Use Policy; order-velocity and new-account controls | Our legitimate interest in protecting the business, and in some cases legal obligation |
| Keeping the audit log; contesting payment disputes | Our legitimate interest in establishing and defending legal claims |
| Measuring which campaigns and referrals produce customers; improving the site | Our legitimate interest in operating and marketing the business, and consent where required |
| Capacity planning and enforcing transfer allowances | Performing our contract; our legitimate interest in network stability |
| Tax, accounting, and responding to lawful requests | Legal obligation |
We do not sell your personal information, and we do not share it for cross-context behavioural advertising in exchange for money. We do not send marketing email to customers who have not asked for it.
7How long we keep it
| Data | Retention |
|---|---|
| Account and identity records | While the account is open, then up to 3 years, to handle disputes and to recognise a returning or previously terminated customer |
| Order, invoice, and billing records | 7 years — tax and accounting requirements |
| Audit log | Retained indefinitely. It is append-only by design and is our evidence in billing and fraud disputes |
| Support tickets | 3 years from closure |
| Server contents | Destroyed with the server at termination — see Terms section 7.4 |
| Backups (where purchased) | As described in the product; purged after the stated window |
| Website session and event records | Up to 2 years |
| Access logs | Typically 30–90 days, depending on the provider |
| Abuse and fraud records | As long as necessary to protect the business, and longer where a matter is unresolved or referred |
8Security
We take reasonable measures to protect the information we hold: passwords stored only as scrypt hashes, encrypted transport, encrypted offsite backups, token-authenticated internal APIs, network isolation between tenants, restricted administrative access, and an audit trail of administrative action.
No system is perfectly secure, and we cannot guarantee the security of information transmitted to us or stored by us. Securing what runs inside your server — patching, firewalling, credentials, and configuration — is your responsibility; you have full root or administrator access and we do not manage it.
If we become aware of a breach affecting your personal information, we will notify you and any regulator as required by law.
9Your rights
Wherever you live, you may ask us to:
- Access — tell you what personal information we hold about you and give you a copy;
- Correct — fix information that is wrong;
- Delete — erase your information, subject to the limits below;
- Port — provide your information in a portable format;
- Object or restrict — object to processing based on our legitimate interests.
Email ben@blossomhost.us from the address or account associated with your account. We respond within 30 days. We will not discriminate against you for exercising these rights.
9.1 Limits on deletion
We cannot delete everything on request. Order and invoice records must be kept for tax purposes, and audit-log entries are never deleted — they exist precisely so that a record cannot be altered after the fact, and they are our defence in a billing or fraud dispute. Where we must keep records, we will delete or de-identify everything not required and tell you what was retained and why.
10California residents
We are a California business and publish this policy in accordance with the California Online Privacy Protection Act. The categories of personal information we collect, our purposes, and the categories of recipients are described in sections 2, 4, and 6.
We do not sell personal information and do not share it for cross-context behavioural advertising in exchange for money or other valuable consideration.
We do not knowingly collect sensitive personal information, and we do not use or disclose it for purposes requiring a right to limit.
We extend the access, deletion, correction, portability, and non-discrimination rights in section 9 to California residents as a matter of policy, whether or not the California Consumer Privacy Act applies to us by threshold. You may use an authorised agent, who must provide proof of authorisation.
California residents may also request, once a year and free of charge, information about disclosures of personal information to third parties for their direct marketing purposes under the "Shine the Light" law. We make no such disclosures.
11EU, UK and Swiss residents
If you are in the European Economic Area, the United Kingdom, or Switzerland, our legal bases are set out in section 4: performance of a contract, our legitimate interests, consent where required, and legal obligation.
In addition to the rights in section 9 you may withdraw consent at any time where processing is based on consent, and you may lodge a complaint with your local supervisory authority. We would rather you came to us first.
International transfers. We operate from the United States and our infrastructure and providers are primarily in the United States. Using our Services involves transferring your information to the United States, which has not been found by the European Commission to provide an equivalent level of protection. Where required we rely on the European Commission's Standard Contractual Clauses or another lawful transfer mechanism. By using the Services you understand your information will be processed in the United States.
We have not appointed an EU or UK representative under Article 27. Contact us directly at ben@blossomhost.us.
12Children
The Services are not directed to anyone under 18 and we do not knowingly collect personal information from them. If you believe a minor has given us information, tell us and we will delete it and close the account.
13Changes to this policy
We may update this policy. The effective date at the top always reflects the current version. For material changes we will make reasonable efforts to notify you through your account contact route or a notice on the site. Continued use after the effective date means you accept the updated policy.
14Contact
Questions, requests, or complaints about privacy:
- Email — ben@blossomhost.us
- Discord — our server
Please put "Privacy" in the subject line so it gets routed correctly.