← Back Login

Privacy Policy

Privacy Policy

Version: 1.0 | Effective from: 31 March 2025

This Policy explains how personal data is handled when a person visits the website, creates an account, places an Order, pays, receives support or uses a Service. It does not govern personal data inside Customer Content processed solely on a customer's instructions; the Data Processing Terms govern that activity.

1. Controller

The controller for contract, account and payment data is the Provider expressly identified in the accepted Order, invoice or payment instructions. Its current identity and contact details are published in the separate Contact Information section. Another entity listed there may process data for support, payment or operations under the appropriate role, agreement and legal basis.

2. Data collected

  • Identity and contact data: name, organization, postal address, email, phone, country, language and verification data.
  • Account and security data: identifiers, password hash, authentication events, sessions, recovery data, roles, consents and audit records.
  • Contract and billing data: Orders, Services, invoices, currency, tax information, payment status, transaction references, balance and refund records. Complete card credentials are handled by payment providers, not stored by the platform.
  • Domain data: registrant and contact details, eligibility documents, nameservers, transfer and verification records, privacy status and registry communications.
  • Technical and usage data: IP address, timestamps, user agent, request, error, security and service telemetry needed to operate and protect the platform.
  • Communications: support tickets, attachments, calls or messages, preferences, complaints and data-rights requests.
  • Data received from payment providers, registrars, registries, identity/fraud services, referrers and public or lawful sources.

3. Purposes and legal bases

  • Form and perform the contract, provision Services, administer domains, authenticate users, bill, support and communicate - contract necessity.
  • Keep tax, accounting, sanctions, fraud, security and regulatory records and respond to authorities - legal obligation.
  • Protect systems, prevent abuse, improve reliability, establish legal claims, manage business and measure essential service performance - legitimate interests balanced against individual rights.
  • Send optional marketing or use non-essential storage - consent where required. Consent may be withdrawn without affecting earlier processing.
  • Protect vital interests or perform a public-interest task only where the circumstances and law support that basis.

If required data is not provided, an Order or legal request may be impossible to complete. Automated controls may flag fraud, abuse or security risk, but a person may request human review of a decision that has legal or similarly significant effect where the law provides that right.

4. Recipients

Data is disclosed only as needed to personnel and contracted providers for hosting, data centers, cloud, communications, support, security, analytics approved in the active cookie settings, payment, banking, accounting, identity/fraud checks, domain registrars, registries, escrow and professional advice. It may also be disclosed to a competent authority, court, claimant or transaction counterparty where lawfully required and appropriately limited.

Domain-registration data may be transferred and disclosed under the selected TLD's rules. Public registration data is minimized or redacted where applicable, but the Provider cannot guarantee anonymity.

5. International transfers

Services may require processing outside the person's country. Where EU/EEA transfer rules apply, the controller uses an adequacy decision, approved contractual clauses with supplementary measures, another lawful mechanism, or a specific statutory derogation. Details relevant to a transfer can be requested, subject to protection of confidential security and commercial information.

6. Retention

Data is kept only as long as needed for the stated purpose, considering the Service term, account status, statutory tax and accounting periods, limitation periods, registry rules, fraud and security risk, dispute or legal hold, and backup replacement cycles. In particular:

  • contract, invoice and payment records remain for mandatory financial and claims periods;
  • domain records remain for registrar, registry, escrow, transfer and dispute requirements;
  • support and operational records remain while needed to provide the Service and resolve reasonably foreseeable claims;
  • security and audit logs follow configured operational retention and may be kept longer for an incident or legal hold;
  • marketing data remains until withdrawal or inactivity criteria, with a minimal suppression record retained to honor opt-out;
  • deleted production data may persist temporarily in protected rotating backups and is not restored except for disaster recovery.

When retention ends, data is deleted, anonymized or isolated from ordinary use.

7. Security

The controller uses proportionate organizational and technical measures such as access control, password hashing, transport encryption, logging, backups where configured, segregation, supplier controls and incident procedures. No system is perfectly secure. The Customer must protect credentials, devices, contacts and Customer Content and report suspected compromise promptly.

8. Individual rights

Subject to applicable law, a person may request access, a copy, correction, deletion, restriction, portability, objection, withdrawal of consent and review of qualifying automated decisions. Authenticated users may submit export or erasure-review requests through the account; a request does not cause automatic deletion because identity, lawful retention and third-party rights must first be reviewed.

A request should identify the person, account, right and relevant data. Identity and authority may be verified. The controller responds within the legally required period and explains any lawful refusal or extension. Manifestly unfounded or excessive requests may be handled as law permits.

9. Complaints and authorities

Questions and requests should first be submitted using a method published in the Contact Information section and marked as a personal data request. Without prejudice to other administrative or judicial remedies, a person may lodge a complaint with a competent data protection supervisory authority, including an authority in the country or territory of habitual residence, place of work or alleged infringement where applicable law permits that choice. The person may also apply to a competent court or other authorized body. Competence and procedure are determined by applicable law and the circumstances of the processing.

10. Children

The Services are not offered for independent purchase by persons under 18. If personal data of a child is processed through Customer Content, the Customer must have a valid legal basis and appropriate safeguards. Suspected unauthorized child data should be reported for review.

11. Incidents and legal requests

The controller investigates suspected personal-data breaches, mitigates harm, documents decisions and notifies competent authorities and affected persons where legally required. Government and claimant requests are reviewed for authority, scope and proportionality; the Customer or person is notified where lawful.

12. Cookies, changes and contact

The Cookie Policy describes browser storage. Material Policy changes will be dated and notified where required. A change does not retroactively legitimize earlier processing. Privacy questions and requests must be submitted using a method published in the Contact Information section and marked as a personal data request.