Draft for review with counsel. Not certified legal advice. Effective date and company registration details will be confirmed before sales open. Placeholders in [BRACKETS] must be filled before this policy is final.
Last updated: 6 November 2026 · Product: DataPulse · Panel: dash.datapulse.cc
1. Who we are
DataPulse (“we”, “us”, “our”) provides VPS, game hosting, cloud storage, dedicated servers, and related infrastructure. Orders and server control run through the DataPulse panel.
The controller for account, billing, support, and website data will be:
[LEGAL_NAME][ADDRESS][COUNTRY]
Privacy email: [EMAIL]
Registration: [REGISTRATION_NUMBER]
Until company registration is published, privacy questions can also be raised via Discord support.
If [LEGAL_NAME] has no establishment in the EEA or the UK and still offers services to people there, we will publish the representatives we appoint. Leave these out until the appointment is real:
- EEA representative:
[EU_REPRESENTATIVE_NAME],[EU_REPRESENTATIVE_ADDRESS],[EU_REPRESENTATIVE_EMAIL] - UK representative:
[UK_REPRESENTATIVE_NAME],[UK_REPRESENTATIVE_ADDRESS],[UK_REPRESENTATIVE_EMAIL] - Data protection officer, if appointed:
[DPO_EMAIL]
2. Personal data we process
Depending on how you use DataPulse, we may process:
- Account and profile data (name, email, password hashes, language preferences)
- Billing and tax data (postal address, payment references, invoices)
- Support communications (tickets, Discord tickets you open with us, email)
- Service metadata (product type, IP assignments, usage counters, configuration)
- Security and application logs
- Cookie and consent records as described in section 9
Files a client uploads may contain other people’s personal data. For that content the client decides the purpose of processing. Contact the client first if you are one of those people. If you write to [EMAIL] and we can tell which client it is, we will pass the request to that client.
3. Why we process personal data
We process personal data to create and run accounts, deliver and support services, take payment, prevent abuse, meet legal duties, and—only where allowed—send service or marketing messages.
Legal bases include contract, legal obligation, consent (where required), and legitimate interests (for example securing the platform and improving reliability). Where we rely on legitimate interests, you can ask us to explain the balancing test for your situation. Write to [EMAIL].
We do not make decisions that produce legal or similarly significant effects based solely on automated processing without human involvement, except where the law allows it and you have the rights described in section 10.
4. What staff may ask you
In a billing ticket or a Discord ticket, staff may ask you to confirm:
- first name
- last name
- email address
- postal address
- telephone number
We ask when the task could affect your files, when we need to confirm you own the account, or when we are processing a cancellation or an account move. The request happens in that ticket or by email. It does not happen on a personal call, in a private message, in a public chat, or in any place where other people could collect what you type.
5. Service privacy
We do not open, delete, copy, move, or upload files on your service unless you ask us to, or the malicious-activity rule below applies. If you ask in a ticket, staff may start, stop, or restart the service to see an error and fix it.
If you invite another person into a workspace, that person can see the profile details the product shows to members, and the content you place in shared views.
If we see malicious activity on your service, we may open the relevant files. We may keep a copy or delete the file without asking first, so that other clients on the machine are protected.
Client services are restricted to staff who need access for the two cases above. We take safety backups of game-hosting services every day. Those backups are used when DataPulse caused the loss. A request for a backup for another reason is refused. Safety backups are kept on [BACKUP_LOCATIONS] and only the system team can reach them.
6. Who we share personal data with
We share personal data with staff and contractors of [LEGAL_NAME] who need it to do their job and who are bound to keep it confidential.
We also use processors who handle data only on our instructions:
| Processor role | Identity | What they do |
|---|---|---|
| Application hosting | [HOSTING_PROVIDER] | Host the application, databases, and backups in [REGIONS] |
| Customer panel / control plane | Hostrivo / dash.datapulse.cc | Account, billing flows, and service management |
| Payments | [PAYMENT_PROVIDER] | Take payment and return status to us |
[EMAIL_PROVIDER] | Deliver service and, where allowed, marketing email | |
| Support tooling | [SUPPORT_PROVIDER] / Discord when you open a ticket there | Store support tickets and conversations |
| Analytics, only after consent | [ANALYTICS_PROVIDER] | Measure use of the site or product |
| Error monitoring, if used | [ERROR_MONITORING_PROVIDER] | Receive crash and diagnostic data |
We may share personal data with a professional adviser, an insurer, or an authority when we need to, or with a buyer of the business if DataPulse is sold. A buyer would be told to use the data only for the purposes in this policy.
7. International transfers
[LEGAL_NAME] is established in [COUNTRY]. Personal data is stored in [DATA_RESIDENCY]. Customer services currently run in Germany as described on the site.
If we transfer personal data from the EEA, the UK, or Switzerland to a country that does not have an adequacy decision, we use a transfer tool the law recognises. The tool we rely on is [TRANSFER_MECHANISM] (for example the European Commission’s standard contractual clauses, together with the UK addendum or the UK international data-transfer agreement where the UK GDPR applies). You can ask [EMAIL] for a summary of the safeguards and, where we can share it without revealing security details, the relevant clauses.
8. How long we keep personal data
We keep personal data only for as long as the purpose, the contract, or the law requires. The periods below are the ones to publish once they are confirmed.
| Data | Retention |
|---|---|
| Account and workspace records | For the life of the account, then [ACCOUNT_RETENTION]. An unused account may be closed after 6 months under the Terms of Service |
| Billing and tax records | [BILLING_RETENTION], matching the period required by the law of [COUNTRY] |
| Support and Discord tickets | [SUPPORT_RETENTION] from the last message. A transcript is available to the ticket author after the ticket closes |
| Security and application logs | [LOG_RETENTION] |
| Safety backups | [BACKUP_RETENTION], taken daily for game hosting |
| Cookie-consent records | [CONSENT_RETENTION] |
| Marketing contact details | Until you withdraw consent or opt out, then [MARKETING_SUPPRESSION_RETENTION] on a suppression list so we can honour the opt-out |
When the period ends, we delete the data or irreversibly anonymise it. Backups fall away on their normal cycle. We may keep a limited record for longer when a legal claim, an investigation, or a statutory duty requires it, and we limit access to that record.
9. Cookies and consent
We use cookies and similar technologies (such as local storage and pixels) as follows.
Strictly necessary. These are required to provide the site or the service you ask for: to keep you signed in, to protect the session, to remember a load-balancer, to store this privacy and cookie choice, and to complete a checkout. They do not require consent. The legal basis for any personal data they contain is contract or legitimate interests, as section 3 describes.
Analytics and product measurement. These help us understand which pages and features are used. For visitors in the EEA, the UK, and Switzerland we set them only after you opt in. The legal basis is consent.
Marketing. These track you across sites or build a profile for advertising. We set them only after you opt in. If the product does not use them, we will publish: “DataPulse does not use marketing cookies.” Otherwise we name them under [ANALYTICS_PROVIDER] or a separate [MARKETING_PROVIDER].
The current list, with name, purpose, duration, and provider, is [COOKIE_LIST]. Update that list when a cookie changes.
You can accept or refuse non-essential cookies in the cookie control on the site, and you can change that choice at any time through the same control (labelled cookie settings). Refusing non-essential cookies does not stop you creating an account. You can also control cookies in your browser. Blocking a strictly necessary cookie may stop sign-in or checkout from working.
Withdrawing consent does not affect processing that was lawful before the withdrawal. After you withdraw, we stop the relevant non-essential tools and we will not read those identifiers for the withdrawn purpose.
10. Your rights
If the GDPR or the UK GDPR applies to you, you have the following rights, subject to the conditions and exceptions in the law:
- Access — to receive a copy of the personal data we hold about you, and information about how we use it
- Rectification — to correct inaccurate personal data, and to complete incomplete data
- Erasure — to ask us to delete personal data when the law requires or allows deletion
- Restriction — to ask us to limit processing in the situations Article 18 describes
- Portability — to receive personal data you provided, where we process it by automated means on the basis of contract or consent, in a structured, commonly used, machine-readable format, and to have it transmitted to another controller where technically feasible
- Objection — to object to processing based on legitimate interests, and to object at any time to processing for direct marketing
- Withdraw consent — where we rely on consent, to withdraw it at any time
- Not to be subject to certain automated decisions — as section 3 describes
To use a right, email [EMAIL]. Include the account email and enough detail for us to find the data. We may need to confirm your identity before we act, using details already on the billing profile. We will respond within one month. If a request is complex or numerous, the law allows us to extend that period by two further months, and we will tell you if we do.
You can update much of your account data yourself in the product. You can opt out of marketing with the link in the message or by emailing [EMAIL]. Service messages about the contract and security will still be sent.
If we do not act on a request, we will explain why and remind you of your right to complain and to seek a judicial remedy.
11. Complaints
You may lodge a complaint with a supervisory authority. If you are in the EEA, that is in particular the authority in the member state of your habitual residence, your place of work, or the place of the alleged infringement. If you are in the UK, you may complain to the Information Commissioner’s Office.
The authority we expect to be competent for [LEGAL_NAME], once [COUNTRY] and any EU establishment are confirmed, is [SUPERVISORY_AUTHORITY]. You do not have to complain to that authority first, and you do not have to contact us before you complain. We do ask you to write to [EMAIL] as well, so we can look into the issue. You may also seek a remedy from a court.
12. Security
We use technical and organisational measures appropriate to the risk, including access control, encryption in transit, least-privilege access for staff, and backups as the specifications describe. No online service can promise perfect security. If a personal-data breach affects you and the law requires us to tell you, we will do so.
Staff who can reach personal data are authorised to use it only for the purposes in this policy.
13. Children
DataPulse is not aimed at children. A user under 13 may use a service only when a parent or guardian buys it and is responsible for the account. We do not knowingly create accounts for anyone under [MINIMUM_AGE]. Where we rely on consent and the person is under the digital-consent age in their country (16 under the GDPR, unless that country has set a lower age between 13 and 16), we need authorisation from the holder of parental responsibility. If you believe we hold a child’s personal data and we should delete it, email [EMAIL].
14. Changes and contact
We will post updates on this page and change the last-updated date. If a change materially affects how we use personal data, we will also email the account address or show a notice in the product before the change takes effect, where the law expects us to.
Privacy requests and questions go to [EMAIL]. Postal address: [LEGAL_NAME], [ADDRESS], [COUNTRY]. Data protection officer, if appointed: [DPO_EMAIL]. Until email is published, use Discord support.