Privacy Policy
What we collect, why we need it, and who else sees it.
Last updated: 5 November 2026
- support email (environment: SUPPORT_EMAIL)
- data-protection contact (environment: GRIEVANCE_EMAIL)
- refund window (environment: REFUND_WINDOW_DAYS)
Who is responsible for your data
Under India's Digital Personal Data Protection Act, 2023 we are the Data Fiduciary for the personal data described here, and you are the Data Principal. That holds even though we provide these services through an upstream registrar: engaging a supplier to process data on our behalf does not move the responsibility for it onto them. If something goes wrong with your data, the obligation to answer for it is ours.
Our suppliers, and which of them act on our behalf
The distinction matters, because it decides who you can hold to account:
- Our upstream registrar and hosting suppliers process data on our instructions, as Data Processors. We remain responsible to you for what they do with it.
- Domain registries are different. A registry sets its own rules about what a registrant must supply and what it publishes, under its own regulatory framework — ICANN for generic extensions, NIXI for .IN. They are not acting on our instructions, and we cannot overrule them. Once registrant details are lodged with a registry, we cannot withdraw them while the domain exists.
- Payment providers set their own terms for the data they hold about a transaction, and are responsible for it directly.
Some of these suppliers operate outside India, so providing these services involves transferring personal data abroad. We do that only where it is necessary to deliver what you asked for, and only to countries not restricted by the Central Government.
What we collect, and why
Only what a transaction or a service actually requires:
- Account details — your name, email address and password. The password is stored only as a one-way hash; we cannot read it, and neither can anyone who obtains the database.
- Billing details — postal address, phone number, and company name and GSTIN where you supply them. A tax invoice is a legal document and must identify the recipient, so these appear on the invoices we issue to you.
- Registrant details for domains — name, address, email and phone. Domain registries require these from the registrant; a domain cannot be registered without them.
- Service records — which domains and plans you hold, their terms and renewal dates, your orders and invoices, and any support tickets you raise.
- Technical records — server logs produced in the ordinary course of serving the site, used to keep it working and to investigate abuse.
We do not store your card or bank details. Payments are taken on the payment provider's own systems; we receive confirmation that a payment succeeded and a reference to it, and nothing more.
Who your data is shared with
Providing these services is not possible without passing some of this on. We share only what the recipient needs:
- Domain registries and our upstream registrar — registrant details, because a registration cannot be completed without them. Registries have their own publication rules, and some operate a public WHOIS. Where privacy protection is available for an extension and you have it enabled, your details are masked in that public record; it does not hide them from the registry itself.
- Payment providers — the amount, currency and an order reference, so the payment can be taken and reconciled.
- Our email provider — your address and the message, so we can send order confirmations, renewal reminders and replies to tickets.
- Tax and regulatory authorities — where the law requires it.
We do not sell your data, and we do not share it for advertising.
How long we keep it
Most of these periods are not ours to choose. Where the law sets one, it is named below rather than described vaguely, so you can see what we can and cannot delete on request.
| Record | Kept for | Why |
|---|---|---|
| Tax invoices and order records | 8 years | Indian tax law requires books of account and the records supporting them to be preserved for a period measured from the end of the relevant financial year. An invoice is the evidence for a GST return already filed, so deleting it would leave a filed return unsupported. |
| Domain registrant details | While the service lasts | Held for as long as the domain is registered. These sit with the registry, not only with us: a registry will not withdraw them while the domain exists, and a domain whose details are removed can be suspended. |
| Hosting account and service records | While the service lasts | Held while the service is active, and for the tax period afterwards as part of the order record. |
| Account profile (name, email, address, phone) | While the service lasts | Needed to operate the account. Erasable once no service is active and the tax period for the last order has passed. |
| Support tickets and replies | 3 years | Kept so the history of an issue stays available to both sides, then removed. |
| Consent records | 8 years | The evidence that processing was lawful while it ran. Deleting a consent record on an erasure request would destroy the only proof that the data had been handled lawfully - which is why a withdrawal sets a date on the record rather than removing it. |
| Marketing contact permission | While the service lasts | Held on consent alone. Withdrawn at any time from the control panel, with immediate effect. |
| Server and access logs | 1 years | Kept to investigate faults and abuse, then discarded. |
Closing your account does not delete records we are legally obliged to keep.
Cookies
We set a session cookie when you sign in; without it the control panel cannot tell who you are. Your currency preference is stored in your browser so the site does not forget it between visits. Neither is used for advertising or cross-site tracking.
What you can ask us to do
You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Deletion has a limit worth stating plainly: we cannot delete records we are legally required to retain, and we cannot withdraw registrant details already lodged with a registry while the domain exists. We will tell you specifically what we can and cannot action rather than refusing the request as a whole.
Write to us at the address above. If you are not satisfied with how we have handled a request, you can raise it with the relevant data protection authority.
Security
Access to the administrative console requires an authenticated session, passwords are stored only as hashes, and provider credentials are held in the deployment environment rather than in the application's source. No system is beyond compromise; if a breach affecting your data occurs, we will tell you what happened and what it means for you.
Questions, complaints and how to escalate
You can ask us anything about how your data is handled, and you can complain if you are not satisfied with the answer. Write to:
We will acknowledge your request and tell you what we are doing about it. If you are not satisfied with how we have handled it, you may complain to the Data Protection Board of India, and to any other authority with jurisdiction over you.
If there is a breach
If a breach affects your personal data, we will tell you and notify the Data Protection Board of India, in the manner and within the time the law requires. We will tell you what happened, what data was involved, and what it means for you — not simply that an incident occurred.
Children
These services are not offered to children. You must be 18 or over to open an account. We do not knowingly collect data from anyone under 18, and we do not profile or direct advertising at children. If you believe a child has given us personal data, tell us and we will delete it.
Changes to this policy
When this policy changes, the date at the top of the page changes with it. Where a change materially affects how your data is used, we will tell you by email rather than relying on you to notice.
