1. Controller and contact
In short: Your data is processed by David Zákoucký (StormHost). Write to us at [email protected].
1.1The controller of personal data is David Zákoucký, a self-employed natural person registered in the Czech Trade Register, company ID (IČO) 19217200, registered address Děčínská 552/1, 180 00 Prague 8, Czech Republic, phone +420 777 436 340 (calls in Czech only), the operator of the StormHost services (“we”).
1.2For personal data matters, contact us at [email protected] or at our registered address.
1.3Data protection officer. We have not appointed a data protection officer. Under Art. 37(1) GDPR we are not required to: we are not a public authority, and our core activities do not consist of large-scale regular and systematic monitoring of individuals or large-scale processing of special categories of data. Please contact us directly in all personal data matters.
1.4If we transfer the services to another person (for example to a company we set up), we will tell you in advance by e-mail. The new controller will process the data under this policy.
2. Who this policy covers
In short: This policy covers customers, website visitors and other people whose data we process. Data you store in your service belongs to you – we only host it.
2.1This policy describes how we process the personal data of:
- customers and people acting on behalf of a customer;
- members with shared access to a service and game panel users added to a server by the customer;
- operators of VIP shops and players who buy in a VIP shop;
- subscribers to service status notifications;
- visitors to stormhost.eu and users of our free tools;
- people who contact us and people who report illegal content.
2.2Data in customers' services. This policy does not cover data that customers store in their service themselves or that the service processes on their instructions. Examples are data on a VPS, game server or Discord bot, website content and databases on web hosting, access logs of visitors to the customer's website, service backups, traffic passing through the txAdmin gateway, and players' data in a VIP shop during a sale. The customer is the controller of that data. We are a processor under Art. 28 GDPR and follow clause 16.2 of the Terms or a separate data processing agreement. The customer is responsible for having a legal basis for the processing and for informing its own users (e.g. players or website visitors). The sub-processors we use for this data are listed in clause 6.4.
2.3We also process some data about a service in our own name, because we need it to perform the contract, keep records or protect the services. Examples are payment records in a VIP shop, domain data or audit logs. These are described in clause 3.
3. Purposes, legal bases and retention periods
In short: We mainly process data so that we can provide the service and issue documents. We keep it only as long as necessary, accounting documents for 10 years.
3.1The purposes of processing are divided into six groups. For each purpose we state which data we process, on what legal basis and how long we keep it. Who we share data with is summarised in clause 6.
Account and services
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Customer account and registration | e-mail, password (stored only as a one-way hash), first name, last name, phone, billing details (company, company ID, VAT ID, address, country), language, e-mail verification, time and version of acceptance of the Terms | performance of a contract (Art. 6(1)(b) GDPR) | for as long as the account exists; then the data needed to defend legal claims for another 3 years |
| Verification of company ID and billing details | company ID, company name and registered address from the public ARES register | performance of a contract; legitimate interest in accurate documents (Art. 6(1)(f) GDPR) | as for the account |
| Orders and provision of services | orders, configuration and status of services, IP addresses and service names, access credentials to services (encrypted), history of actions in services | performance of a contract | for the duration of the contract and 3 years after |
| Sharing and transfers of services | e-mail of the invited member or transfer recipient, permissions, status of the invitation or transfer | performance of a contract; legitimate interest of the service holder | for the duration of the service and 3 years after |
| Game panel, subdomains and DNS | e-mail of the customer and of users the customer added to the server, in the game panel (our own infrastructure), subdomain names (DNS at Cloudflare or on our DNS server) and reverse DNS records (these are public) | performance of a contract; for added users, legitimate interest in operating the service the customer made available to them | for the duration of the service |
| Web hosting | website domain, hosting account name, database and SFTP user names, plan and usage (disk space, data transfer); passwords are generated and shown to you only once and are not stored by us (the web hosting server only has their one-way hash); website content, databases and visitor access logs are processed by us as a processor (clause 2.2) | performance of a contract | for the duration of the contract and 3 years after; website access logs 30 days |
| txAdmin gateway (FiveM) | the domain you verify for txAdmin, the server port and identifier, a record of verifying and removing the domain; the gateway terminates the encrypted connection and forwards the traffic to the game server, including the logins of your server's administrators, but does not store or log the content; IP addresses are kept only in memory to limit the number of requests | performance of a contract | settings for the duration of the service; the domain verification record as audit logs; IP addresses only in memory for minutes |
| Customer API | key name, its public prefix and a one-way hash of the secret part (SHA-256; you see the full key only once), permissions, selected services, allowed IP addresses, expiry, time and IP address of last use; actions performed via the API are recorded as account actions | performance of a contract; legitimate interest in account security | until the key is deleted or the account is closed; actions as audit logs |
| Domains (registration, transfer to us, renewal and management) | domain name; holder details that we pass from the billing profile to the registrar and the registry (first name, last name, where applicable company, company ID and VAT ID, address, e-mail, phone), and the first and last name of the person who consented to the registry rules; domain and contact identifiers at the registry, domain status and expiry, name servers, DNS records in the zone on our DNS servers; for a transfer to us the AUTH-ID (stored encrypted) | performance of a contract | service data for the duration of the contract and 3 years after; the zone on our DNS servers is deleted when the contract ends; the AUTH-ID is deleted after the transfer is completed or rejected or the order is cancelled, at the latest after 60 days; data in the registry is kept by the registry under its own rules |
| Player management and player graph (Minecraft) | player nicknames you add to the whitelist, operators or bans in the Players tab (for servers with account verification we send them to Mojang to verify the account and look up the UUID); every 5 minutes the number of connected players, without names | performance of a contract | player lists are in your server; player count measurements 35 days, can be turned off and deleted in the Players tab |
| Server crash alerts (only if you turn them on) | alert settings, the address of your Discord webhook (stored encrypted), alert history (time, type, exit code, likely cause); server log lines only go into the sent message, after hiding IP addresses, e-mails, tokens and passwords, and we do not store them | performance of a contract (feature at your request) | settings until turned off or the service is transferred; alert history 12 months |
| Discord notifications (only if you turn them on) | Discord ID, username, private channel identifier, language and chosen notification topics, content of notifications (service name, type of event, time); when linking we only ask Discord for the account's basic identity and, only if you tick it, for adding you to the StormHost Discord server; we do not keep Discord access tokens | performance of a contract (feature at your request) | until unlinked in Account settings → Notifications or until the account ends (support can also delete them on request); the link record in the audit log 12 months |
Customer account and registration
- Data
- e-mail, password (stored only as a one-way hash), first name, last name, phone, billing details (company, company ID, VAT ID, address, country), language, e-mail verification, time and version of acceptance of the Terms
- Legal basis
- performance of a contract (Art. 6(1)(b) GDPR)
- Retention
- for as long as the account exists; then the data needed to defend legal claims for another 3 years
Verification of company ID and billing details
- Data
- company ID, company name and registered address from the public ARES register
- Legal basis
- performance of a contract; legitimate interest in accurate documents (Art. 6(1)(f) GDPR)
- Retention
- as for the account
Orders and provision of services
- Data
- orders, configuration and status of services, IP addresses and service names, access credentials to services (encrypted), history of actions in services
- Legal basis
- performance of a contract
- Retention
- for the duration of the contract and 3 years after
Sharing and transfers of services
- Data
- e-mail of the invited member or transfer recipient, permissions, status of the invitation or transfer
- Legal basis
- performance of a contract; legitimate interest of the service holder
- Retention
- for the duration of the service and 3 years after
Game panel, subdomains and DNS
- Data
- e-mail of the customer and of users the customer added to the server, in the game panel (our own infrastructure), subdomain names (DNS at Cloudflare or on our DNS server) and reverse DNS records (these are public)
- Legal basis
- performance of a contract; for added users, legitimate interest in operating the service the customer made available to them
- Retention
- for the duration of the service
Web hosting
- Data
- website domain, hosting account name, database and SFTP user names, plan and usage (disk space, data transfer); passwords are generated and shown to you only once and are not stored by us (the web hosting server only has their one-way hash); website content, databases and visitor access logs are processed by us as a processor (clause 2.2)
- Legal basis
- performance of a contract
- Retention
- for the duration of the contract and 3 years after; website access logs 30 days
txAdmin gateway (FiveM)
- Data
- the domain you verify for txAdmin, the server port and identifier, a record of verifying and removing the domain; the gateway terminates the encrypted connection and forwards the traffic to the game server, including the logins of your server's administrators, but does not store or log the content; IP addresses are kept only in memory to limit the number of requests
- Legal basis
- performance of a contract
- Retention
- settings for the duration of the service; the domain verification record as audit logs; IP addresses only in memory for minutes
Customer API
- Data
- key name, its public prefix and a one-way hash of the secret part (SHA-256; you see the full key only once), permissions, selected services, allowed IP addresses, expiry, time and IP address of last use; actions performed via the API are recorded as account actions
- Legal basis
- performance of a contract; legitimate interest in account security
- Retention
- until the key is deleted or the account is closed; actions as audit logs
Domains (registration, transfer to us, renewal and management)
- Data
- domain name; holder details that we pass from the billing profile to the registrar and the registry (first name, last name, where applicable company, company ID and VAT ID, address, e-mail, phone), and the first and last name of the person who consented to the registry rules; domain and contact identifiers at the registry, domain status and expiry, name servers, DNS records in the zone on our DNS servers; for a transfer to us the AUTH-ID (stored encrypted)
- Legal basis
- performance of a contract
- Retention
- service data for the duration of the contract and 3 years after; the zone on our DNS servers is deleted when the contract ends; the AUTH-ID is deleted after the transfer is completed or rejected or the order is cancelled, at the latest after 60 days; data in the registry is kept by the registry under its own rules
Player management and player graph (Minecraft)
- Data
- player nicknames you add to the whitelist, operators or bans in the Players tab (for servers with account verification we send them to Mojang to verify the account and look up the UUID); every 5 minutes the number of connected players, without names
- Legal basis
- performance of a contract
- Retention
- player lists are in your server; player count measurements 35 days, can be turned off and deleted in the Players tab
Server crash alerts (only if you turn them on)
- Data
- alert settings, the address of your Discord webhook (stored encrypted), alert history (time, type, exit code, likely cause); server log lines only go into the sent message, after hiding IP addresses, e-mails, tokens and passwords, and we do not store them
- Legal basis
- performance of a contract (feature at your request)
- Retention
- settings until turned off or the service is transferred; alert history 12 months
Discord notifications (only if you turn them on)
- Data
- Discord ID, username, private channel identifier, language and chosen notification topics, content of notifications (service name, type of event, time); when linking we only ask Discord for the account's basic identity and, only if you tick it, for adding you to the StormHost Discord server; we do not keep Discord access tokens
- Legal basis
- performance of a contract (feature at your request)
- Retention
- until unlinked in Account settings → Notifications or until the account ends (support can also delete them on request); the link record in the audit log 12 months
Payments and documents
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Payments | amount, payment method, payment identifier and status at GoPay or PayU, for a recurring payment its identifier; for a bank transfer the variable symbol, amount, payer's name and account number from the bank statement; we do not see card details | performance of a contract; legal obligation (Art. 6(1)(c) GDPR) | 10 years from the end of the year of payment |
| Invoicing and tax records | billing details, proforma invoices, invoices, corrective documents, payment receipts; for customers with a recurring invoice kept outside the customer account, also an overview of their invoices and payments | legal obligation (Income Tax Act, Tax Code, where applicable the VAT Act and the Accounting Act) | 10 years from the end of the year of issue |
| Credit | credit movements (top-ups, spending, refunds) | performance of a contract; legal obligation | for as long as the account exists and then 10 years from the end of the year of the last movement; until then movement records are not changed or deleted (erasure on request is therefore not possible, Art. 17(3)(b) GDPR) |
| VIP shop (selling perks to players on a game server) | for the shop operator: shop name and address, seller details (name or company, company ID, address, e-mail), acceptance of the terms, commission and settlement; for the player: nickname, e-mail, purchased item, price, status of payment, delivery and refund, consents (time, IP address, browser identification, terms version, language) | for the sale we are the operator's processor (clause 2.2); in our own name performance of the contract with the operator, legal obligation (payments and documents) and legitimate interest in proving the purchase and preventing fraud | payment and settlement records 10 years from the end of the year of payment; other purchase data and consents for as long as the shop exists and 3 years after |
Payments
- Data
- amount, payment method, payment identifier and status at GoPay or PayU, for a recurring payment its identifier; for a bank transfer the variable symbol, amount, payer's name and account number from the bank statement; we do not see card details
- Legal basis
- performance of a contract; legal obligation (Art. 6(1)(c) GDPR)
- Retention
- 10 years from the end of the year of payment
Invoicing and tax records
- Data
- billing details, proforma invoices, invoices, corrective documents, payment receipts; for customers with a recurring invoice kept outside the customer account, also an overview of their invoices and payments
- Legal basis
- legal obligation (Income Tax Act, Tax Code, where applicable the VAT Act and the Accounting Act)
- Retention
- 10 years from the end of the year of issue
Credit
- Data
- credit movements (top-ups, spending, refunds)
- Legal basis
- performance of a contract; legal obligation
- Retention
- for as long as the account exists and then 10 years from the end of the year of the last movement; until then movement records are not changed or deleted (erasure on request is therefore not possible, Art. 17(3)(b) GDPR)
VIP shop (selling perks to players on a game server)
- Data
- for the shop operator: shop name and address, seller details (name or company, company ID, address, e-mail), acceptance of the terms, commission and settlement; for the player: nickname, e-mail, purchased item, price, status of payment, delivery and refund, consents (time, IP address, browser identification, terms version, language)
- Legal basis
- for the sale we are the operator's processor (clause 2.2); in our own name performance of the contract with the operator, legal obligation (payments and documents) and legitimate interest in proving the purchase and preventing fraud
- Retention
- payment and settlement records 10 years from the end of the year of payment; other purchase data and consents for as long as the shop exists and 3 years after
Consents, withdrawals and complaints
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Proof of consents and requests | acceptance of the Terms, confirmation of whether you order as a business, confirmation of a plan deviation, request for immediate start of the service, withdrawal from the contract, consent to recurring payment (incl. the maximum amount), consent to a service transfer, consent to the registry rules for a domain – always with time, IP address, browser identification, document version and language | legitimate interest in proving consent and defending legal claims | for the duration of the contract and 3 years after; for a recurring payment at least 12 months after it ends |
| Withdrawal from the contract and refunds | name, e-mail, contract details, text of the statement or request, time of sending, IP address, browser identification, reason (category and optional text), the chosen refund method and consent to it, bank account number and account holder's name (stored encrypted), messages about the request, the decision and its justification, progress of the refund | legal obligation (confirming the withdrawal and refunding under sections 1829 to 1836 of the Civil Code); legitimate interest in proving and defending legal claims; for the reason for withdrawal, legitimate interest in improving the services | for the duration of the contract and 3 years after; the free text of the withdrawal reason 12 months after sending; the bank account number 90 days after the refund; records of refunded payments and credit as for payments and credit |
| Handling complaints | name, e-mail, contract and service details, description of the defect and since when it has lasted, the remedy requested, the chosen refund method and consent to it, bank account number and account holder's name (stored encrypted), messages about the complaint, records of the service's operation used for the assessment (monitoring, incidents), the decision and its justification, progress of the refund or service extension | legal obligation (confirming and handling a complaint under section 19 of the Consumer Protection Act, rights for defective performance under the Civil Code); performance of a contract; legitimate interest in proving and defending legal claims | for the duration of the contract and 3 years after; the bank account number 90 days after the refund; records of refunded payments and credit as for payments and credit |
| Prevention of abuse of services | records of withdrawals, complaints, refund requests and payments reversed through the bank (chargebacks) and their outcomes; any measure concerning new orders (reason, validity, who decided) | legitimate interest in assessing repeated abuse of services; a person always decides and we do not share the data with anyone outside StormHost | for the duration of the contract and 3 years after; for the assessment we only use the last 12 months; a measure is valid for at most 12 months |
Proof of consents and requests
- Data
- acceptance of the Terms, confirmation of whether you order as a business, confirmation of a plan deviation, request for immediate start of the service, withdrawal from the contract, consent to recurring payment (incl. the maximum amount), consent to a service transfer, consent to the registry rules for a domain – always with time, IP address, browser identification, document version and language
- Legal basis
- legitimate interest in proving consent and defending legal claims
- Retention
- for the duration of the contract and 3 years after; for a recurring payment at least 12 months after it ends
Withdrawal from the contract and refunds
- Data
- name, e-mail, contract details, text of the statement or request, time of sending, IP address, browser identification, reason (category and optional text), the chosen refund method and consent to it, bank account number and account holder's name (stored encrypted), messages about the request, the decision and its justification, progress of the refund
- Legal basis
- legal obligation (confirming the withdrawal and refunding under sections 1829 to 1836 of the Civil Code); legitimate interest in proving and defending legal claims; for the reason for withdrawal, legitimate interest in improving the services
- Retention
- for the duration of the contract and 3 years after; the free text of the withdrawal reason 12 months after sending; the bank account number 90 days after the refund; records of refunded payments and credit as for payments and credit
Handling complaints
- Data
- name, e-mail, contract and service details, description of the defect and since when it has lasted, the remedy requested, the chosen refund method and consent to it, bank account number and account holder's name (stored encrypted), messages about the complaint, records of the service's operation used for the assessment (monitoring, incidents), the decision and its justification, progress of the refund or service extension
- Legal basis
- legal obligation (confirming and handling a complaint under section 19 of the Consumer Protection Act, rights for defective performance under the Civil Code); performance of a contract; legitimate interest in proving and defending legal claims
- Retention
- for the duration of the contract and 3 years after; the bank account number 90 days after the refund; records of refunded payments and credit as for payments and credit
Prevention of abuse of services
- Data
- records of withdrawals, complaints, refund requests and payments reversed through the bank (chargebacks) and their outcomes; any measure concerning new orders (reason, validity, who decided)
- Legal basis
- legitimate interest in assessing repeated abuse of services; a person always decides and we do not share the data with anyone outside StormHost
- Retention
- for the duration of the contract and 3 years after; for the assessment we only use the last 12 months; a measure is valid for at most 12 months
Security
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Account and login security | IP address, device type, browser and operating system, network country derived from the IP address, time and method of login, failed attempts, identifier of a known device (stored by us only as a one-way hash); if you turn on two-step verification (2FA), also the secret key for your authenticator app (stored only in encrypted form, AES-256-GCM), backup codes (only as a one-way fingerprint, HMAC-SHA256, so they can't be read from the database), when you turned 2FA on and when you last used a code; if you add a passkey, only its public key, identifier, name, the type of password manager (if known), and when it was added and last used (your fingerprint, face or PIN never reach us, verification happens on your device); account settings show the devices you're signed in on (taken from the sign-in record) | legitimate interest in protecting the account against misuse; for 2FA and passkeys also performance of the contract | the IP address and device and network data are removed 12 months after the login (known devices are recognised using the last 180 days); the 2FA key and codes are deleted as soon as you turn 2FA off or close your account, a passkey as soon as you remove it or close your account; records relating to an incident being handled until it is resolved |
| Audit logs and abuse prevention | records of important actions in the account and services (who, when, from which IP address, what changed) and of administrator interventions | legitimate interest in security, traceability and resolving disputes | routine actions in services (power on and off, files, backups, databases, firewall, restore, crash alerts, webhook deliveries) 12 months; for logins, logouts, failed attempts and password resets the IP address and device data are removed after 12 months; records of orders, payments, credit, consents and transfers for the same period as the related documents; other records (account and security changes, API keys, reinstalls, administrator interventions) for as long as the account exists and 3 years after; relating to an incident or dispute until it is resolved |
| Account preview by an administrator | who started and ended a preview of your account, when and for what reason; with full access also every action performed; passwords, keys and tokens are never shown in a preview | legitimate interest in support, checking that services work correctly and traceability of interventions | as audit logs (other records) |
| Protection of forms and the website | IP address and technical browser data (Cloudflare Turnstile, bot protection), number of requests from an IP address | legitimate interest in protection against bots and attacks | not stored by us; request counters only in memory for minutes |
| Leaked password check | when a password is set, we send only the first 5 characters of the password hash to the Pwned Passwords service; neither the password nor the full hash leaves us (not personal data) | legitimate interest in account security | not stored |
| Web server logs | IP address, time, page address, browser, result of the request | legitimate interest in security and fixing website errors | 14 days |
| Error reports from the website and customer account | time, page address without parameters, type of error and a cleaned message (without e-mails, IP addresses, tokens and passwords), identifier of your account, service or order; we do not store the IP address or browser | legitimate interest in detecting and fixing errors | 30 days |
| Database backups | the data listed above | legitimate interest in recovery after a failure (Art. 32 GDPR) | 14 days, then automatically overwritten |
Account and login security
- Data
- IP address, device type, browser and operating system, network country derived from the IP address, time and method of login, failed attempts, identifier of a known device (stored by us only as a one-way hash); if you turn on two-step verification (2FA), also the secret key for your authenticator app (stored only in encrypted form, AES-256-GCM), backup codes (only as a one-way fingerprint, HMAC-SHA256, so they can't be read from the database), when you turned 2FA on and when you last used a code; if you add a passkey, only its public key, identifier, name, the type of password manager (if known), and when it was added and last used (your fingerprint, face or PIN never reach us, verification happens on your device); account settings show the devices you're signed in on (taken from the sign-in record)
- Legal basis
- legitimate interest in protecting the account against misuse; for 2FA and passkeys also performance of the contract
- Retention
- the IP address and device and network data are removed 12 months after the login (known devices are recognised using the last 180 days); the 2FA key and codes are deleted as soon as you turn 2FA off or close your account, a passkey as soon as you remove it or close your account; records relating to an incident being handled until it is resolved
Audit logs and abuse prevention
- Data
- records of important actions in the account and services (who, when, from which IP address, what changed) and of administrator interventions
- Legal basis
- legitimate interest in security, traceability and resolving disputes
- Retention
- routine actions in services (power on and off, files, backups, databases, firewall, restore, crash alerts, webhook deliveries) 12 months; for logins, logouts, failed attempts and password resets the IP address and device data are removed after 12 months; records of orders, payments, credit, consents and transfers for the same period as the related documents; other records (account and security changes, API keys, reinstalls, administrator interventions) for as long as the account exists and 3 years after; relating to an incident or dispute until it is resolved
Account preview by an administrator
- Data
- who started and ended a preview of your account, when and for what reason; with full access also every action performed; passwords, keys and tokens are never shown in a preview
- Legal basis
- legitimate interest in support, checking that services work correctly and traceability of interventions
- Retention
- as audit logs (other records)
Protection of forms and the website
- Data
- IP address and technical browser data (Cloudflare Turnstile, bot protection), number of requests from an IP address
- Legal basis
- legitimate interest in protection against bots and attacks
- Retention
- not stored by us; request counters only in memory for minutes
Leaked password check
- Data
- when a password is set, we send only the first 5 characters of the password hash to the Pwned Passwords service; neither the password nor the full hash leaves us (not personal data)
- Legal basis
- legitimate interest in account security
- Retention
- not stored
Web server logs
- Data
- IP address, time, page address, browser, result of the request
- Legal basis
- legitimate interest in security and fixing website errors
- Retention
- 14 days
Error reports from the website and customer account
- Data
- time, page address without parameters, type of error and a cleaned message (without e-mails, IP addresses, tokens and passwords), identifier of your account, service or order; we do not store the IP address or browser
- Legal basis
- legitimate interest in detecting and fixing errors
- Retention
- 30 days
Database backups
- Data
- the data listed above
- Legal basis
- legitimate interest in recovery after a failure (Art. 32 GDPR)
- Retention
- 14 days, then automatically overwritten
Free tools on the website
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Queries in the tools | queries entered into the tools (IP address, domain, game server address), with the “my IP” option your IP address; for game servers also publicly available data the server itself publishes (e.g. nicknames of players online) | legitimate interest in providing the tool you used | not stored permanently; server cache for at most 1 hour; for player heads the UUID-to-skin mapping for at most 6 hours, head images and plugin icons (not linked to the visitor) until evicted from the cache |
| Spark profile analysis | the server profile you submit as a link or file; the analysis result without the profile author's name or UUID and without JVM system properties; the profile code; your IP address only in server memory to limit the number of analyses | legitimate interest in providing the tool you used | we do not keep the profile itself; analysis result 30 days; profile code at most 24 hours; request counters only in memory for minutes |
Queries in the tools
- Data
- queries entered into the tools (IP address, domain, game server address), with the “my IP” option your IP address; for game servers also publicly available data the server itself publishes (e.g. nicknames of players online)
- Legal basis
- legitimate interest in providing the tool you used
- Retention
- not stored permanently; server cache for at most 1 hour; for player heads the UUID-to-skin mapping for at most 6 hours, head images and plugin icons (not linked to the visitor) until evicted from the cache
Spark profile analysis
- Data
- the server profile you submit as a link or file; the analysis result without the profile author's name or UUID and without JVM system properties; the profile code; your IP address only in server memory to limit the number of analyses
- Legal basis
- legitimate interest in providing the tool you used
- Retention
- we do not keep the profile itself; analysis result 30 days; profile code at most 24 hours; request counters only in memory for minutes
- The history of recent queries is stored only in your browser.
- The "Minecraft player" tool: the nick or UUID you enter is sent to Mojang (Microsoft) to look up the UUID and skin. We do not store the result, it is only kept in server memory for up to one hour.
- A FiveM server banner loads only after you click it, directly from the address the server published – your browser connects to it and it sees your IP address. Other images (FiveM server owner avatar, player heads, plugin icons) are downloaded by our server; your browser does not connect to third-party servers.
- We process a Spark profile on our server. For a link, your browser downloads the profile directly from spark's storage (spark-usercontent.lucko.me); if that fails, our server downloads it. Of the JVM options, only -X and -XX switches (such as memory size and garbage collector) remain in the result, without paths or addresses. The result contains technical details about the server (software and versions, plugins and mods, selected settings, world names) and anyone with its link can view it; search engines do not index it. Our server remembers the profile code so it does not download the same profile again.
Communication and other obligations
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Communication and support | e-mail, Discord username, content of communication | performance of a contract; legitimate interest in handling the request | 3 years after resolution |
| Service e-mails | e-mail address, content of messages (confirmation of the contract, documents, login alerts, service status) | performance of a contract; legal obligation; legitimate interest in security | we do not keep the service e-mails themselves (we only record that a document was issued and sent); copies of correspondence in our mailbox 3 years |
| Operational notices (maintenance, outages, changes to the Terms and prices) | e-mail and language of the service owner and, depending on the notice, also of members with shared access and game panel users added to the server by the customer; content of the notice; delivery record | performance of a contract (information about the service and changes to the contract); for members and panel users, legitimate interest in informing them about an outage or maintenance of a service they use | the e-mail in the delivery record and the content of the notice 12 months, for changes to the Terms and prices 3 years |
| Service status notification subscription (where available on the Status page) | e-mail, language, one-way hash of the confirmation link, time of subscribing and confirming | consent (Art. 6(1)(a) GDPR), which you confirm via the link in the e-mail | until you unsubscribe via the link in every e-mail (unsubscribing deletes the record); an unconfirmed subscription 48 hours |
| Internal notifications | notifications about orders, payments, logins, services, errors and refund requests for our operations; e-mails, names, IP addresses and cities in them are masked (e.g. j…@s….cz, 1.2.x.x); for refund requests and complaints we only send the request number, the amount and the reason category (for a complaint, the remedy requested), never the text of the reason, the description of the defect or messages | legitimate interest in operating the services | until the message is deleted, at most 12 months |
| Review invitation (clause 3.3) | e-mail address, language, whether a service has been running and paid for at least 21 days; record of sending or declining the invitation | legitimate interest in customer feedback; sending to our own customer under section 7(3) of Czech Act No. 480/2004 Coll. | record of sending or declining for as long as the account exists (so the invitation is not sent again) |
| Notices of illegal content | name and e-mail of the notifier, content of the notice, decision | legal obligation (Digital Services Act) | 3 years after resolution |
| Other legal obligations and defence of legal claims | data needed for a specific proceeding or authority request | legal obligation; legitimate interest | for the duration of the proceeding |
Communication and support
- Data
- e-mail, Discord username, content of communication
- Legal basis
- performance of a contract; legitimate interest in handling the request
- Retention
- 3 years after resolution
Service e-mails
- Data
- e-mail address, content of messages (confirmation of the contract, documents, login alerts, service status)
- Legal basis
- performance of a contract; legal obligation; legitimate interest in security
- Retention
- we do not keep the service e-mails themselves (we only record that a document was issued and sent); copies of correspondence in our mailbox 3 years
Operational notices (maintenance, outages, changes to the Terms and prices)
- Data
- e-mail and language of the service owner and, depending on the notice, also of members with shared access and game panel users added to the server by the customer; content of the notice; delivery record
- Legal basis
- performance of a contract (information about the service and changes to the contract); for members and panel users, legitimate interest in informing them about an outage or maintenance of a service they use
- Retention
- the e-mail in the delivery record and the content of the notice 12 months, for changes to the Terms and prices 3 years
Service status notification subscription (where available on the Status page)
- Data
- e-mail, language, one-way hash of the confirmation link, time of subscribing and confirming
- Legal basis
- consent (Art. 6(1)(a) GDPR), which you confirm via the link in the e-mail
- Retention
- until you unsubscribe via the link in every e-mail (unsubscribing deletes the record); an unconfirmed subscription 48 hours
Internal notifications
- Data
- notifications about orders, payments, logins, services, errors and refund requests for our operations; e-mails, names, IP addresses and cities in them are masked (e.g. j…@s….cz, 1.2.x.x); for refund requests and complaints we only send the request number, the amount and the reason category (for a complaint, the remedy requested), never the text of the reason, the description of the defect or messages
- Legal basis
- legitimate interest in operating the services
- Retention
- until the message is deleted, at most 12 months
Review invitation (clause 3.3)
- Data
- e-mail address, language, whether a service has been running and paid for at least 21 days; record of sending or declining the invitation
- Legal basis
- legitimate interest in customer feedback; sending to our own customer under section 7(3) of Czech Act No. 480/2004 Coll.
- Retention
- record of sending or declining for as long as the account exists (so the invitation is not sent again)
Notices of illegal content
- Data
- name and e-mail of the notifier, content of the notice, decision
- Legal basis
- legal obligation (Digital Services Act)
- Retention
- 3 years after resolution
Other legal obligations and defence of legal claims
- Data
- data needed for a specific proceeding or authority request
- Legal basis
- legal obligation; legitimate interest
- Retention
- for the duration of the proceeding
3.2We do not currently send commercial communications (newsletters, offers, discounts). If we start, we will only send them with consent, or to existing customers about our similar services under section 7(3) of Czech Act No. 480/2004 Coll. You will be able to refuse this already at registration and then easily and free of charge in every message. Service e-mails and operational notices (documents, login alerts, service status, maintenance, changes to the Terms) are not commercial communications.
3.3Review invitation. Once per service lifetime we may send you a request to review us on Trustpilot. You can decline it when registering by ticking the box, via the link in the e-mail or at any time by e-mail to [email protected]; after that we will not send you any more. We send it to customers whose service has been running and paid for at least 21 days, to everyone equally and regardless of how satisfied they are; we offer nothing in return for a review. We do not pass any of your data to Trustpilot – you only write a review if you sign in there yourself, and Trustpilot then processes the data as an independent controller under its own policy.
3.4After the retention period ends we delete or anonymise the data. Deleted data disappears from backups through their regular rotation within 14 days at the latest. To close your account, send a request by e-mail from your account address. We close an account with no active services and no credit and delete or anonymise data we are not required to keep within 30 days.
3.5Why these periods. We keep documents, payments and credit movements for 10 years because, under section 148(5) of the Czech Tax Code, tax can be assessed for up to 10 years; section 35 of the VAT Act sets the same period for VAT payers. We keep contract data and proof of consents for 3 years after the contract ends because that is the general limitation period (section 629 of the Civil Code). If a dispute or proceeding starts earlier, we keep the necessary data until it ends.
3.6Legitimate interest. Where processing is based on legitimate interest, we have assessed in advance whether our interest is overridden by your rights (balancing test). The interests are: security of accounts and services, proof of contracts and consents, defence of legal claims, operating and fixing the services, protection against fraud and abuse, and customer feedback. The processing is necessary for them and limited to the data needed. We mask data or limit how long we keep it, we do not sell it to anyone and we do not use it for advertising or profiling. We will send you a summary of the balancing test on request.
4. Obligation to provide data
In short: We cannot provide the service without registration and billing details. Other data is voluntary.
4.1We need the registration and billing details to conclude and perform the contract and to issue documents as required by law. Without them we cannot provide the services. The phone number is a required field in the billing profile. We only use it to contact you in urgent cases (security incident, outage, payment problem). We do not pass it to the payment gateway. Only the domain registrar and registry receive it as holder details if you order a domain from us (clause 6).
4.2Other data (for example linking Discord, notifications, passkeys, API keys or the status notification subscription) is voluntary. Without it, only the related feature will not work.
5. Where we get the data from
In short: We get most data from you. Some comes from payment gateways, registries or other customers.
5.1We get most data directly from you. We also obtain:
- the e-mail of an invited member, transfer recipient or game panel user from the customer who invited them;
- company name and registered address from the public ARES register;
- payment status and method from GoPay or PayU (for refunds, possibly also the account number a bank transfer came from) and, for a bank transfer, the payer's name and account number from our bank statement;
- for customers with a recurring invoice kept outside the customer account, an overview of invoices and payments from the Fakturoid service;
- domain status, expiry and name servers from the registrar;
- the Discord ID and username from Discord when you link your account;
- the nickname and e-mail a player enters when buying in a VIP shop;
- the network country derived from the IP address from public statistics of the regional internet registries (we process them on our own systems and do not send the IP address anywhere);
- data from notices of illegal content from the people who report it.
6. Recipients and processors
In short: We do not sell data. We only share it with those who need it – payment gateways, invoicing, e-mail delivery, the domain registrar and website protection.
6.1Overview by purpose. Details of the data and retention periods are in clause 3, details of the recipients in clause 6.2.
| Purpose | Legal basis | Retention | Recipients |
|---|---|---|---|
| Account, orders and provision of services (including sharing, game panel, web hosting, txAdmin gateway and API) | performance of a contract | for the duration of the contract and 3 years after | Cloudflare (delivery and protection of the website, DNS); Let's Encrypt (only the domain name for a certificate); Mojang (verifying players in the Players tab) |
| Domains | performance of a contract | for the duration of the contract and 3 years after | WEDOS (registrar); the domain registry |
| Discord notifications and crash alerts | performance of a contract (at your request) | until turned off or unlinked | Discord |
| Payments and refunds | performance of a contract; legal obligation | 10 years from the end of the year of payment | GoPay (until 23 December 2026); PayU; our bank |
| Invoicing, tax records and credit | legal obligation | 10 years from the end of the year of issue or last movement | Fakturoid; the tax office on request |
| VIP shop | processing for the operator; in our own name performance of a contract, legal obligation and legitimate interest | payments 10 years, other data for as long as the shop exists and 3 years after | payment gateway; shop operator (seller); e-mail delivery |
| Consents, withdrawals, complaints and prevention of abuse | legal obligation; legitimate interest | for the duration of the contract and 3 years after | no one outside StormHost (refunds are carried out by the payment gateway or bank) |
| Account security, audit logs and account preview | legitimate interest; for 2FA and passkeys performance of a contract | 12 months, other records for as long as the account exists and 3 years after | Cloudflare (Turnstile); Have I Been Pwned (only an anonymous part of the password hash) |
| Web server logs, error reports and database backups | legitimate interest | 14 days, 30 days and 14 days | no one (our internal Discord channel only gets a summary without personal data) |
| Free tools | legitimate interest | not stored, Spark analysis result 30 days | internet registries, PeeringDB, DNS resolvers, Mojang |
| Communication, support, service e-mails and operational notices | performance of a contract; legal obligation; legitimate interest | 3 years after resolution; notices 12 months (changes to the Terms and prices 3 years) | Seznam.cz (e-mail delivery); Discord (communication on Discord, notices in the channel) |
| Service status notification subscription | consent | until you unsubscribe | Seznam.cz (e-mail delivery) |
| Review invitation | legitimate interest | for as long as the account exists | no one |
| Notices of illegal content and other legal obligations | legal obligation | 3 years after resolution or for the duration of the proceeding | public authorities, only where the law requires it |
Account, orders and provision of services (including sharing, game panel, web hosting, txAdmin gateway and API)
- Legal basis
- performance of a contract
- Retention
- for the duration of the contract and 3 years after
- Recipients
- Cloudflare (delivery and protection of the website, DNS); Let's Encrypt (only the domain name for a certificate); Mojang (verifying players in the Players tab)
Domains
- Legal basis
- performance of a contract
- Retention
- for the duration of the contract and 3 years after
- Recipients
- WEDOS (registrar); the domain registry
Discord notifications and crash alerts
- Legal basis
- performance of a contract (at your request)
- Retention
- until turned off or unlinked
- Recipients
- Discord
Payments and refunds
- Legal basis
- performance of a contract; legal obligation
- Retention
- 10 years from the end of the year of payment
- Recipients
- GoPay (until 23 December 2026); PayU; our bank
Invoicing, tax records and credit
- Legal basis
- legal obligation
- Retention
- 10 years from the end of the year of issue or last movement
- Recipients
- Fakturoid; the tax office on request
VIP shop
- Legal basis
- processing for the operator; in our own name performance of a contract, legal obligation and legitimate interest
- Retention
- payments 10 years, other data for as long as the shop exists and 3 years after
- Recipients
- payment gateway; shop operator (seller); e-mail delivery
Consents, withdrawals, complaints and prevention of abuse
- Legal basis
- legal obligation; legitimate interest
- Retention
- for the duration of the contract and 3 years after
- Recipients
- no one outside StormHost (refunds are carried out by the payment gateway or bank)
Account security, audit logs and account preview
- Legal basis
- legitimate interest; for 2FA and passkeys performance of a contract
- Retention
- 12 months, other records for as long as the account exists and 3 years after
- Recipients
- Cloudflare (Turnstile); Have I Been Pwned (only an anonymous part of the password hash)
Web server logs, error reports and database backups
- Legal basis
- legitimate interest
- Retention
- 14 days, 30 days and 14 days
- Recipients
- no one (our internal Discord channel only gets a summary without personal data)
Free tools
- Legal basis
- legitimate interest
- Retention
- not stored, Spark analysis result 30 days
- Recipients
- internet registries, PeeringDB, DNS resolvers, Mojang
Communication, support, service e-mails and operational notices
- Legal basis
- performance of a contract; legal obligation; legitimate interest
- Retention
- 3 years after resolution; notices 12 months (changes to the Terms and prices 3 years)
- Recipients
- Seznam.cz (e-mail delivery); Discord (communication on Discord, notices in the channel)
Service status notification subscription
- Legal basis
- consent
- Retention
- until you unsubscribe
- Recipients
- Seznam.cz (e-mail delivery)
Review invitation
- Legal basis
- legitimate interest
- Retention
- for as long as the account exists
- Recipients
- no one
Notices of illegal content and other legal obligations
- Legal basis
- legal obligation
- Retention
- 3 years after resolution or for the duration of the proceeding
- Recipients
- public authorities, only where the law requires it
6.2We share data only to the extent necessary with these recipients:
| Recipient | Role and purpose | Data | Location |
|---|---|---|---|
| GOPAY s.r.o. – operator of the GoPay payment gateway (until 23 December 2026) | processing payments, recurring payments and refunds; an independent controller for payment data | first name, last name, e-mail, address (street, city, postcode, country), amount and order description; you enter card details directly at GoPay | Czech Republic / EU |
| PayU S.A., ul. Grunwaldzka 186, 60-166 Poznań, Poland, KRS 0000274399 – payment institution | processing payments by card, Apple Pay, Google Pay and bank transfer and refunds of them; an independent controller for payment data | first name, last name, e-mail, language, IP address, amount and order description; you enter card details directly at PayU | Poland / EU |
| The bank where we hold the account for bank transfers | receiving bank transfers and refunds to an account; an independent controller | the data in the payment (payer's name and account number, amount, variable symbol); for refunds the account number and the account holder's name | Czech Republic |
| Fakturoid s.r.o., company ID 04656679, Prague | processor – invoicing | billing details, e-mail, items and payments | Czech Republic |
| Seznam.cz, a.s., company ID 26168685, Prague | processor – sending e-mails | e-mail address, content of service e-mails and notices | Czech Republic |
| WEDOS Internet, a.s., company ID 28115708, Hluboká nad Vltavou | domain registrar – registration, transfer, renewal and management of the domain at the registry (clause 21 of the Terms) | holder details (first name, last name, where applicable company, company ID and VAT ID, address, e-mail, phone), the first and last name of the person who consented to the registry rules, domain name, name servers, for a transfer to us the AUTH-ID | Czech Republic |
| Domain registries – CZ.NIC, z. s. p. o. (.cz), EURid vzw (.eu) and the registries of the other extensions we sell | recording the domain and its holder; the registry is an independent controller for the registry data and under its rules may publish some of it in the public domain database (WHOIS / RDAP) | holder details, domain name, name servers | CZ.NIC Czech Republic; EURid Belgium; others depending on the extension, for some extensions outside the EU (clause 7) |
| Cloudflare, Inc. | processor – delivery and protection of the website and customer account (CDN, protection against attacks and bots), DNS for the stormhost.eu domain including game server subdomains; for Turnstile partly an independent controller (improving bot detection) | IP address, technical data about the browser and request, Cloudflare cookies, content of customer account pages (encrypted); for subdomains the subdomain name and the server's IP address | USA and global network |
| Internet Security Research Group (Let's Encrypt) | issuing a certificate for a web hosting or txAdmin gateway domain; an independent controller | only the domain name; every issued certificate is recorded in the public Certificate Transparency logs | USA |
| Discord Inc. | independent controller of the community and support on Discord; we also receive internal notifications via Discord; crash alerts to the webhook you enter and private message notifications you turn on yourself | username and messages on Discord; in internal notifications only masked data (e.g. j…@s….cz, 1.2.x.x); in notifications for you the service name, type and time of the event, for a crash possibly log lines without IP addresses, e-mails, tokens and passwords; never amounts, passwords or account numbers | USA |
| Internet registries (RIPE NCC, ARIN, APNIC, LACNIC, AFRINIC, top-level domain registries), PeeringDB and public DNS resolvers (Cloudflare, Google, Quad9) | answers to queries you entered yourself in the free tools: registration of an address, range or domain (RDAP of the registry that manages it), BGP routes in the Looking Glass (RIPE NCC), network operator details (PeeringDB only receives the AS number) and DNS | the IP address, prefix, AS number or domain entered; with the “my IP” option your IP address | RIPE NCC Netherlands; ARIN, PeeringDB, Cloudflare and Google USA; APNIC Australia; LACNIC Uruguay; AFRINIC Mauritius; Quad9 Switzerland; domain registries depending on the domain |
| Mojang (Microsoft Corporation) | public Minecraft API – player profile and skin by UUID or nickname (api.minecraftservices.com, api.mojang.com, sessionserver.mojang.com, textures.minecraft.net) for the head image in the Minecraft Status tool, the Minecraft player tool and verifying players in the Players tab; the list of servers blocked by Mojang | UUIDs of players from the server's public list, the nick or UUID entered in the Minecraft player tool and nicknames added in the Players tab; no other data about website visitors | USA |
| Have I Been Pwned (Pwned Passwords) | leaked password check | only the first 5 characters of the password hash (anonymous) | worldwide |
| VIP shop operator (the customer running the shop) | the seller in the VIP shop; the controller for players' data | player's nickname, purchased item, status of payment and delivery; the player's e-mail only to the extent needed to handle the purchase | depending on the operator |
| Data centre operator TTC Teleport, Prague | physical premises, power and connectivity for our servers; has no access to data | – | Czech Republic |
| Public authorities (courts, Czech Police, Czech Trade Inspection Authority, tax office, Office for Personal Data Protection) | compliance with legal obligations | depending on the specific request or the law | Czech Republic |
GOPAY s.r.o. – operator of the GoPay payment gateway (until 23 December 2026)
- Role and purpose
- processing payments, recurring payments and refunds; an independent controller for payment data
- Data
- first name, last name, e-mail, address (street, city, postcode, country), amount and order description; you enter card details directly at GoPay
- Location
- Czech Republic / EU
PayU S.A., ul. Grunwaldzka 186, 60-166 Poznań, Poland, KRS 0000274399 – payment institution
- Role and purpose
- processing payments by card, Apple Pay, Google Pay and bank transfer and refunds of them; an independent controller for payment data
- Data
- first name, last name, e-mail, language, IP address, amount and order description; you enter card details directly at PayU
- Location
- Poland / EU
The bank where we hold the account for bank transfers
- Role and purpose
- receiving bank transfers and refunds to an account; an independent controller
- Data
- the data in the payment (payer's name and account number, amount, variable symbol); for refunds the account number and the account holder's name
- Location
- Czech Republic
Fakturoid s.r.o., company ID 04656679, Prague
- Role and purpose
- processor – invoicing
- Data
- billing details, e-mail, items and payments
- Location
- Czech Republic
Seznam.cz, a.s., company ID 26168685, Prague
- Role and purpose
- processor – sending e-mails
- Data
- e-mail address, content of service e-mails and notices
- Location
- Czech Republic
WEDOS Internet, a.s., company ID 28115708, Hluboká nad Vltavou
- Role and purpose
- domain registrar – registration, transfer, renewal and management of the domain at the registry (clause 21 of the Terms)
- Data
- holder details (first name, last name, where applicable company, company ID and VAT ID, address, e-mail, phone), the first and last name of the person who consented to the registry rules, domain name, name servers, for a transfer to us the AUTH-ID
- Location
- Czech Republic
Domain registries – CZ.NIC, z. s. p. o. (.cz), EURid vzw (.eu) and the registries of the other extensions we sell
- Role and purpose
- recording the domain and its holder; the registry is an independent controller for the registry data and under its rules may publish some of it in the public domain database (WHOIS / RDAP)
- Data
- holder details, domain name, name servers
- Location
- CZ.NIC Czech Republic; EURid Belgium; others depending on the extension, for some extensions outside the EU (clause 7)
Cloudflare, Inc.
- Role and purpose
- processor – delivery and protection of the website and customer account (CDN, protection against attacks and bots), DNS for the stormhost.eu domain including game server subdomains; for Turnstile partly an independent controller (improving bot detection)
- Data
- IP address, technical data about the browser and request, Cloudflare cookies, content of customer account pages (encrypted); for subdomains the subdomain name and the server's IP address
- Location
- USA and global network
Internet Security Research Group (Let's Encrypt)
- Role and purpose
- issuing a certificate for a web hosting or txAdmin gateway domain; an independent controller
- Data
- only the domain name; every issued certificate is recorded in the public Certificate Transparency logs
- Location
- USA
Discord Inc.
- Role and purpose
- independent controller of the community and support on Discord; we also receive internal notifications via Discord; crash alerts to the webhook you enter and private message notifications you turn on yourself
- Data
- username and messages on Discord; in internal notifications only masked data (e.g. j…@s….cz, 1.2.x.x); in notifications for you the service name, type and time of the event, for a crash possibly log lines without IP addresses, e-mails, tokens and passwords; never amounts, passwords or account numbers
- Location
- USA
Internet registries (RIPE NCC, ARIN, APNIC, LACNIC, AFRINIC, top-level domain registries), PeeringDB and public DNS resolvers (Cloudflare, Google, Quad9)
- Role and purpose
- answers to queries you entered yourself in the free tools: registration of an address, range or domain (RDAP of the registry that manages it), BGP routes in the Looking Glass (RIPE NCC), network operator details (PeeringDB only receives the AS number) and DNS
- Data
- the IP address, prefix, AS number or domain entered; with the “my IP” option your IP address
- Location
- RIPE NCC Netherlands; ARIN, PeeringDB, Cloudflare and Google USA; APNIC Australia; LACNIC Uruguay; AFRINIC Mauritius; Quad9 Switzerland; domain registries depending on the domain
Mojang (Microsoft Corporation)
- Role and purpose
- public Minecraft API – player profile and skin by UUID or nickname (api.minecraftservices.com, api.mojang.com, sessionserver.mojang.com, textures.minecraft.net) for the head image in the Minecraft Status tool, the Minecraft player tool and verifying players in the Players tab; the list of servers blocked by Mojang
- Data
- UUIDs of players from the server's public list, the nick or UUID entered in the Minecraft player tool and nicknames added in the Players tab; no other data about website visitors
- Location
- USA
Have I Been Pwned (Pwned Passwords)
- Role and purpose
- leaked password check
- Data
- only the first 5 characters of the password hash (anonymous)
- Location
- worldwide
VIP shop operator (the customer running the shop)
- Role and purpose
- the seller in the VIP shop; the controller for players' data
- Data
- player's nickname, purchased item, status of payment and delivery; the player's e-mail only to the extent needed to handle the purchase
- Location
- depending on the operator
Data centre operator TTC Teleport, Prague
- Role and purpose
- physical premises, power and connectivity for our servers; has no access to data
- Data
- –
- Location
- Czech Republic
Public authorities (courts, Czech Police, Czech Trade Inspection Authority, tax office, Office for Personal Data Protection)
- Role and purpose
- compliance with legal obligations
- Data
- depending on the specific request or the law
- Location
- Czech Republic
6.3We run our own servers (customer account, database, game panel, web hosting, txAdmin gateway, reverse DNS, backups) ourselves in the TTC Teleport data centre in Prague. DNS for the stormhost.eu domain is managed by Cloudflare.
6.4Sub-processors for data in customers' services (clause 2.2): Cloudflare, Inc. – content you view in the customer account or upload to the service (file manager, console, database panel) passes through its network in encrypted form; USA and global network, on the basis of the EU–US Data Privacy Framework and standard contractual clauses. We do not currently use any other sub-processors for this data. We inform customers of an intended change at least 30 days in advance (clause 16.2 of the Terms).
7. Transfers outside the EU
In short: Data only leaves the EU where necessary (Cloudflare, Discord, Mojang, some domain registries and tool queries), and always on a GDPR basis.
7.1We transfer data to third countries only in these cases:
- Cloudflare, Inc. (USA) – on the basis of the Commission's adequacy decision (EU–US Data Privacy Framework) and the standard contractual clauses in the data processing agreement with Cloudflare;
- Discord Inc. (USA) – on the basis of the EU–US Data Privacy Framework; crash alerts and private message notifications are only sent at your request;
- Mojang (Microsoft Corporation) (USA) – UUIDs of players from the server's public list in the Minecraft Status tool, the nick or UUID in the Minecraft player tool and nicknames added in the Players tab, on the basis of the EU–US Data Privacy Framework;
- Let's Encrypt (USA) – only the name of the domain you have a certificate issued for; the transfer is necessary for the performance of the contract (Art. 49(1)(b) GDPR);
- Domain registries outside the EU / EEA – only for a domain with an extension whose registry is based outside the EU / EEA (for example, some generic extensions such as .com, .net or .org are managed by registries in the USA): the registrar passes the holder details to the registry because the domain cannot be registered or managed without them (Art. 49(1)(b) GDPR). For .cz and .eu domains no data is transferred outside the EU / EEA.
- Free tools – the query you entered (with the “my IP” option your IP address) is also sent to the registry that manages the address and to resolvers outside the EU (ARIN, APNIC, LACNIC, AFRINIC, Cloudflare, Google, Quad9), otherwise the tool could not answer. This transfer is necessary to provide the tool you used (Art. 49(1)(b) GDPR); for Cloudflare and Google on the basis of the EU–US Data Privacy Framework.
7.2The EU–US Data Privacy Framework is Commission adequacy decision (EU) 2023/1795. It only covers US companies that are listed in it. The EU General Court dismissed an action against it on 3 September 2025 (case T-553/23); the Court of Justice has not yet ruled on the appeal (case C-703/25 P). If the decision ceased to apply, we would base the transfers on standard contractual clauses or stop them. We will send you a copy of the safeguards on request.
8. Automated decision-making
In short: No computer makes decisions about you. Only protective measures run automatically, and you can always turn to a person.
8.1We do not make decisions with legal effects based solely on automated processing. Only protective measures run automatically: bot protection on forms (Turnstile), rejection of disposable e-mail addresses at registration, rate limiting, temporarily blocking further login attempts to a given account from a given IP address (after 5 failed attempts within 15 minutes), requiring a Turnstile check when traffic looks suspicious, and alerts about a login from a new device. We process withdrawals from the contract automatically (confirmation of receipt, calculation of the proportionate part of the price using a fixed rule in clause 9.4 of the Terms, and the refund); a withdrawal takes effect by itself and is never rejected automatically – an objection to a withdrawal is always assessed by a person. Complaints are always assessed and handled by a person. Prevention of abuse: we keep records of withdrawals, complaints, reversed payments and their outcomes so that we can assess repeated abuse. A person always decides; the records are only a basis and do not restrict anything by themselves. Exercising the statutory right to withdraw from the contract or to complain about a defect is not in itself a reason for any measure. You can object to this processing (clause 9.2). If such a measure restricts you or you disagree with the calculation, write to us – a person will look at it.
8.2We do not carry out profiling for advertising or any other evaluation of personal characteristics.
9. Your rights
In short: You can ask for access, correction, erasure, restriction or portability of your data and you can object. We handle it free of charge within a month.
9.1You have the right:
- of access to your data and to a copy of it, including information on who we have shared it with;
- to rectification of inaccurate data (you can change most of it yourself in your account settings);
- to erasure, if we no longer need the data and are not required by law to keep it (for example, we must keep documents and credit movements);
- to restriction of processing, for example while we verify the accuracy of the data;
- to data portability for data you provided to us that we process by automated means on the basis of a contract or consent;
- to withdraw consent, where processing is based on consent (withdrawal does not affect processing before it);
- to lodge a complaint with the Office for Personal Data Protection (Úřad pro ochranu osobních údajů), Pplk. Sochora 27, 170 00 Prague 7, Czech Republic, uoou.gov.cz, or with the supervisory authority of the EU country where you live or work;
- to go to court if you believe your rights have been infringed.
9.2Right to object. You can object at any time, on grounds relating to your particular situation, to processing based on legitimate interest (marked as “legitimate interest” in the tables in clause 3). We will then stop processing the data unless we demonstrate compelling legitimate grounds that override your interests, or the processing is for the defence of legal claims. You can object to commercial communications at any time and without giving a reason.
9.3Send your request to [email protected], preferably from your account e-mail (so we can verify it is you). If we have reasonable doubts about your identity, we may ask for additional information. We will handle it free of charge within one month; in complex cases we can extend this by a further two months and will let you know. For manifestly unfounded or excessive requests, in particular repeated ones, we may charge a reasonable fee or refuse the request (Art. 12(5) GDPR); we will always tell you why.
9.4We inform the recipients we shared the data with about any rectification, erasure or restriction, unless this proves impossible or involves disproportionate effort.
10. Children
In short: The services are for adults. A minor customer needs the consent of a legal guardian.
10.1The services are intended for adults. We provide services to customers under 18 only with the consent of their legal guardian (clause 4.2 of the Terms); we process their data on the basis of the contract, as for other customers.
10.2Where processing is based on consent (for example the service status notification subscription), a child can give consent in relation to an information society service on their own only from the age of 15 (section 7 of Czech Act No. 110/2019 Coll. and Art. 8 GDPR). For a younger child, consent is given by the legal guardian.
10.3If we find that a child has given us data without the required consent of a legal guardian, we will ask for it. If we do not receive it, we will delete the data we are not required to keep by law. A legal guardian can write to us at [email protected].
11. Security
In short: We protect data with encryption, password hashes, two-step verification and backups. We will tell you and the authority about a serious breach.
11.1We protect data with appropriate technical and organisational measures: an encrypted connection (HTTPS), storing passwords only as a one-way hash (Argon2id), encryption of stored access credentials to services and of sensitive data (such as bank account numbers), mandatory two-step verification for administrators, two-step verification for customers (we will never ask you for a code from the app or for backup codes), login with a passkey (verification happens on your device), logging of administrator interventions, protection of login against password guessing, and regular backups. Our servers and backups are in the Czech Republic; recipients outside the EU are listed in clauses 6 and 7.
11.2Personal data breach. If a personal data breach occurs, we will notify the Office for Personal Data Protection without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to your rights (Art. 33 GDPR). If the breach is likely to result in a high risk, we will also inform you without undue delay (Art. 34 GDPR). We notify customers of a breach of data we process for them in their services under clause 16.2 of the Terms.
13. Changes and effective date
13.1We may update this policy, for example when our services or the law change. We will inform you of significant changes by e-mail or in the customer account. We will send you earlier versions on request.
13.2This policy takes effect on 11 November 2026 (version 2026-11-11).