The short version
- Zeeroow Limited, trading as Zeeroow, decides how your personal data is used. Our Data Protection Officer answers at help@zeeroow.com.
- We collect what we need to run your Account, bill you, deliver your Services and support you. We use no advertising or tracking tools, and no third-party analytics. We count visits to our website from our own server's logs, without cookies.
- Our servers are in our data centre in Dhaka. Some providers we rely on (payment gateways, domain registrars, Meta, Cloudflare, our off-site backup stores) process data outside Bangladesh, and backup copies sent off-site are always encrypted.
- We keep account data for the life of your Account and 1 year after you close it, then erase or anonymise it. Invoices and payment records are kept as VAT and tax law requires.
- You can see, download, correct and ask us to erase your data, and withdraw any consent you gave. You can complain to us or to the National Data Governance Authority.
1. Who we are and what this policy covers
1.1 This policy explains how Zeeroow Limited ("we", "us"), trading as Zeeroow, collects and uses personal data about you when you visit https://zeeroow.com, use the Client Area at https://zeeroow.com/clientarea, buy or use our Services, contact us, or report abuse to us. Words with capital letters have the meaning given in the Definitions section of our Terms of Service.
1.2 For this personal data we are the data fiduciary under Bangladesh's Personal Data Protection Ordinance 2025 (the "PDPO"). In the language of other laws, we are the "controller".
1.3 Our registered address is H-12, 11th Floor, Razzak Plaza Moghbazar, Ramna Dhaka-1217, Bangladesh. Our trade licence number is TRAD/DNCC/030183/2024, our VAT BIN is 355566145929 and our e-TIN is 355566145929.
1.4 This policy does not cover the content you or your own users store on the Services we host for you (websites, databases, mailboxes, files on a VPS, dedicated server or colocated equipment). For that content you are the data fiduciary and we act only on your instructions, as our Data Processing Agreement explains.
1.5 Our Services are offered to customers in Bangladesh, in Bangladeshi Taka, and to customers abroad, in US dollars. They are not directed at people in the European Union or the United Kingdom. We still give everyone the rights described in section 11, because we think they are good practice.
2. Our Data Protection Officer
2.1 We have appointed a Data Protection Officer. You can reach the Data Protection Officer at help@zeeroow.com about anything in this policy: a question, a request to use your rights, or a complaint.
2.2 Complaints about our Services in general go to our Compliance Officer at help@zeeroow.com, as the Terms of Service describe.
3. The personal data we collect
3.1 Signup and account. Your email address, password (stored only as a one-way hash), display name, and whether you sign up as an individual or a business. If you sign up as a business: the company name and type of entity. In your Account settings: billing email and phone, currency, language (English or Bangla), postal address and country, and your choice of which optional notices you receive.
3.2 Business details. For Business Customers: VAT BIN, e-TIN and trade licence details. Your BIN or TIN is printed on your VAT invoices.
3.3 Contacts and team members. The people you add as contacts (default, billing, technical, registrant or abuse contact): name, email, phone, company and address. People you invite to your team: their email address and role. We confirm a contact's email address by a link and a phone number by a code sent by SMS or WhatsApp. When we send a phone code we record the IP address that asked for it, so that we can review fraud.
3.4 Billing and payments. Your orders, services, invoices, receipts, credit notes, Wallet Credit and payment history. You pay through a payment gateway (bKash or SSLCommerz) on the gateway's own pages, or by bank transfer. We send a gateway only the amount and our own payment reference. We never see or store your card number, card security code, bKash PIN or online-banking password; the gateway or bank collects those directly from you under its own privacy policy. For a bank transfer we record the transfer details you give us.
3.5 Identity documents (KYC). We may ask you to prove your identity or your business before we deliver some services: for example colocation, dedicated servers, high-value orders, or where we suspect fraud. You may upload a national ID card, passport or driving licence; a trade licence, certificate of incorporation or registration; a TIN certificate, a bank statement or another document we ask for. We treat these documents as sensitive personal data. We collect them only with your explicit consent, given when you upload them. We do not check national ID numbers with the Election Commission.
3.6 Support tickets and attachments. What you write in a ticket, the files you attach, and our replies. Every attachment is scanned for malware when it arrives and again from time to time; a file that fails the scan is held in quarantine and not delivered to staff.
3.7 Live chat. Messages you send through the chat on our website or Client Area, including the files you share. If you write to us through Facebook Messenger or WhatsApp, we receive the name on your Messenger or WhatsApp profile and, for WhatsApp, your phone number, together with your messages. We place a visitor identifier in your browser so that a chat continues when you return (see the Cookie Notice).
3.8 Sign-in history and device sessions. Each time you sign in, and for each device that stays signed in, we record the date and time, your IP address and your browser's description of itself (user agent). You can see your recent sign-ins and active sessions in the Client Area and end a session there.
3.9 Abuse reports. If you report abuse to us, the name and email address you give, the IP address or resource you report, and what you tell us. We pass the substance of your report to the Customer responsible for the Service. We share your name and contact details with that Customer only where that is needed to resolve the complaint (for example, for a copyright notice or counter-notice), or where the report is knowingly false; if you ask us not to share them, we will not, but we may then be unable to act on some kinds of complaint. Our Abuse & Takedown Policy explains this. If someone reports a Service of yours, the report and our handling of it are kept for the period in section 8.
3.10 Contact form. The name, email address, subject and message you send through the contact form on our website.
3.11 Newsletter. If you subscribe, your email address and the record of your confirmation. We use double opt-in: you are only subscribed after you click the link in our confirmation email.
3.12 Domain registrant data. When you register, renew or transfer a domain through us, the registrant contact you give us for that domain: name, organisation, postal address, email and phone. Section 6.4 explains where this goes.
3.13 Bot checks. Some of our forms (for example signup, sign-in, contact and abuse report) use Cloudflare Turnstile to tell people from automated abuse. Turnstile receives a check token and your IP address.
3.14 Network traffic metadata. For network operations and security, when our network collects them, we keep flow (NetFlow) records of the traffic to and from the Services: source and destination addresses, ports, volumes and times. We do not record the content of customer traffic.
3.15 What we do not collect. Apart from the page counts in 3.15a, which we make ourselves from our own server logs, we use no analytics, advertising, tracking pixels, session recording or third-party error-tracking tools on our website, Client Area or emails. This is enforced in our code: an automated check stops the platform from being built if such a service is added. We do not profile you, and we make no decisions about you by purely automated means that have legal or similarly significant effects.
3.15a Website visit logs. When you visit our website, our web server records the request: the date and time, the page, the address of the page that linked to it (without any query string), the response, your IP address and your browser's description of itself (user agent). We keep these logs for 1 year to keep the service secure and to investigate abuse. From them we count how many times each page is viewed, which websites and search engines visitors come from, and whether they use a computer, phone or tablet. Only those counts are kept, for 13 months. They contain no IP address, browser description or other detail that identifies a visitor. We use no cookie, script or third-party service for this.
4. Where the data comes from
4.1 Almost all of it comes from you, or from the person who manages your Account (for example a team owner who adds you as a contact).
4.2 Some comes from third parties: payment gateways and banks tell us whether a payment succeeded; domain registrars tell us the status of your domains; Meta tells us your Messenger or WhatsApp profile name when you write to us there; and someone who reports abuse tells us about a Service and what they saw.
5. Why we use your data, and on what basis
5.1 The PDPO lets us use personal data only on a basis it recognises. We do not rely on "legitimate interests": the PDPO has no such basis. The table shows the basis for each purpose.
| Purpose | What data | Basis under the PDPO |
|---|---|---|
| Creating and running your Account; signing you in | Signup and account data, sign-in history and sessions | Contract (and the steps you ask for before it) |
| Delivering, renewing and supporting the Services you buy | Account, contacts, orders, tickets, chats | Contract |
| Billing, collecting payment, refunds and Wallet Credit | Billing and payment data | Contract |
| Issuing VAT invoices and keeping accounting and tax records | Name, address, BIN/TIN, invoices, payments | Legal obligation |
| Confirming contact email addresses and phone numbers | Contact data, phone codes, the IP that asked | Contract |
| Registering and managing domains, and publishing registration data as the registry requires | Registrant contact data | Contract, and the registrar's and registry's legal and contractual obligations |
| Checking identity or business documents (KYC) | Identity documents | Explicit consent, and legal obligation or the prevention of fraud where the law requires it |
| Keeping the platform secure; preventing fraud and abuse; bot checks | Sign-in history, sessions, IP addresses, network traffic metadata, Turnstile token, abuse reports | Contract (security is part of the Service), legal obligation, and establishing or defending legal claims |
| Handling abuse reports | Reporter's name, email and report | Your consent (you choose to send the report), and legal obligation where the report concerns unlawful content |
| Answering contact-form messages and chats from people who are not yet customers | Contact form, chat data | Steps you ask us to take before a contract, or your consent |
| Service and account messages (invoices, receipts, payment reminders, password resets, maintenance and lifecycle notices) | Email, phone | Contract |
| Newsletter and product news | Email address | Consent, given separately from signup |
| Answering lawful Orders and requests from authorities | Whatever the order lawfully covers | Legal obligation |
5.2 Consent is always separate. We ask for each consent on its own: KYC documents, the newsletter and product news are never bundled into signup or into the Terms. Accepting our Terms and this policy at signup or checkout is recorded with the version of each document and the time, but that acceptance is not your consent to the newsletter.
5.3 Withdrawing consent. You can withdraw any consent at any time: unsubscribe from the newsletter by the link in every issue or in your notice settings; ask us to delete KYC documents by writing to help@zeeroow.com. Withdrawing consent does not affect what we did before. If you withdraw consent to KYC and we need it for a Service, we may be unable to deliver that Service.
5.4 Some messages cannot be switched off while you are a Customer, because they are part of the contract: invoices, receipts, payment reminders, suspension and termination notices, planned-maintenance notices, security messages and password resets.
6. Who receives your data
6.1 We do not sell personal data. We do not share it with partners for their own marketing. We give it only to the recipients below, each for the role shown, and each receives only what that role needs.
| Recipient | Role | What they receive |
|---|---|---|
| bKash, SSLCommerz | Payment gateways | The amount and our payment reference. They collect your payment details directly from you. |
| Banks | Bank transfers and refunds | What is needed to receive or return your payment |
| LogicBoxes (ResellerClub) | Domain registrars | The domain, nameservers, term and the registrant contact data for that domain |
| SMSQ | SMS delivery | Your phone number and the message (for example a confirmation code) |
| Meta (WhatsApp and Messenger) | Messaging channels | Your number or Messenger identity, your profile name, and the messages exchanged, when you contact us there or ask for a WhatsApp code |
| Cloudflare | DNS and Turnstile bot checks | DNS zone records for domains whose DNS it serves; for Turnstile, the check token and your IP address |
| Our off-site backup providers: SFTP to our own backup server in Bangladesh, and outside Bangladesh an S3-compatible store (AWS S3, Cloudflare R2 or Backblaze B2) or Google Drive | Storage of encrypted backup copies of our systems: one in Bangladesh, one outside it | Encrypted backup files. Encryption is turned on for every destination, so the provider cannot read them. |
| Public authorities | VAT and tax, and lawful Orders | What the law or the order requires (see section 6.5) |
6.2 Email. We send and receive email on our own mail server. No third-party email service processes your messages.
6.3 Our hosting systems. The control panels and systems that run your Services are operated by us on our own equipment. When we set up a cPanel hosting account, the panel holds your Account's contact email so that it can send you service messages.
6.4 Domain registration data and WHOIS/RDDS. A domain registry and the sponsoring registrar must hold registrant data, and may publish some of it in the public WHOIS/RDDS directory, as the registry's and ICANN's rules require. For most generic domains the public record shows the registry's redacted data. Where the ending allows it, you can buy privacy protection as a paid add-on, which replaces your details in the public record with the registrar's privacy service (see the Domain Registration Agreement). The registrar and registry use registrant data under their own policies, and the registrar keeps it for the period its ICANN obligations require. Our Domain Registration Agreement gives the details.
6.5 Law enforcement and authorities. We disclose personal data to a court, the police, BTRC, the National Cyber Security Agency or another public authority only when the law requires it and the request is lawful. Our Law-Enforcement Request Policy explains how we handle these requests and when we tell you about them.
6.6 Business transfer. If our business, or part of it, is sold or merged, personal data may pass to the new owner, who must keep to this policy or tell you of any change first.
6.7 Our staff see personal data only as their role needs. For support, staff may open your Client Area in a supervised "login-as" session, for at most 30 minutes and with a recorded reason. Every change made in such a session is recorded and shown in your account activity. In such a session staff cannot change your password, two-factor authentication, passkeys, API tokens or SSH keys, and cannot move your domain.
7. Where your data is held, and transfers abroad
7.1 Our servers are in our own data centre in Dhaka, at H-12, 11th Floor, Razzak Plaza Moghbazar, Ramna Dhaka-1217, Bangladesh. The platform, its database and the files you give us (tickets, attachments, chats, KYC documents) are held there. Backups of hosting and VPS, where your plan includes them, are kept there too.
7.2 Some data leaves Bangladesh:
- Encrypted backup copies of our systems are kept at two sites: one on our own backup server in Bangladesh, and one outside Bangladesh with an off-site backup provider in section 6.1. Both are encrypted before they leave our data centre.
- Domain registrars (LogicBoxes) and the registries they work with process registrant data outside Bangladesh, for example in India and the United States.
- Meta (WhatsApp and Messenger) and Cloudflare (DNS and Turnstile) process data outside Bangladesh.
- Payment gateways and SMS delivery may use systems outside Bangladesh under their own arrangements.
7.3 We transfer personal data abroad only where it is necessary to perform our contract with you (for example, to register the domain you ordered or to answer you on the channel you chose), or with your consent, and in every case with protection proportionate to the data: encryption for backups, and only the data the recipient needs. When the Authority publishes a list of jurisdictions with adequate protection, or rules for transfers, we will follow them.
7.4 We do not send KYC documents to any third party, except inside our encrypted backups.
8. How long we keep it
8.1 We keep personal data only as long as we need it for the purpose we collected it for, or as long as the law requires. Keeping account data for 1 year after closure is our policy: it lets us answer questions, disputes and claims about a closed Account, and deal with fraud and abuse.
| Data | How long we keep it |
|---|---|
| Account data (profile, contacts, team members, tickets and attachments) | The life of the Account, plus 1 year after the Account is closed. Then it is erased or anonymised. |
| Invoices, receipts, credit notes and payment records | For the period VAT and tax law requires, even after the Account data is erased |
| KYC identity documents | Erased with the Account data, 1 year after closure. You can ask us to delete them sooner (section 5.3), subject to any legal duty to keep them. |
| Live chats (website, Messenger, WhatsApp) | 1 year after the chat closes |
| Sign-in history, device sessions, abuse reports and system logs | 1 year |
| Web server access logs (IP address, browser, page, time) | 1 year |
| Website visit counts (no personal data) | 13 months |
| Network traffic metadata, when collected (flow records: source, destination, ports, volumes and times; never the content) | 1 year |
| Contact-form messages | 1 year |
| Newsletter subscription | Until you unsubscribe. After that we keep only a suppression record of your address, so that we do not mail you again |
| Backups of hosting accounts | As stated on your plan, stored on our equipment in our Dhaka data centre |
| Backups of VPS | As stated on your plan, stored on our equipment in our Dhaka data centre |
| Our own system backups | 14 days in our data centre; encrypted off-site copies are kept by the destination's own retention rules |
| Domain registrant data held by the registrar | As the registrar's ICANN obligations require |
8.2 Erasure from live systems is followed by erasure from backups as those backups age out on the schedule above.
8.3 Messages you exchange with us on WhatsApp or Messenger are also held by Meta under its own terms. Deleting them from our systems does not delete Meta's copy.
8.4 Erasure does not reach records the law requires us to keep, or records we need to establish, exercise or defend a legal claim. Where we must keep such a record we keep only what is needed and restrict access to it.
9. How we protect your data
9.1 We use measures proportionate to the risk, including:
- Encryption at rest (AES-256) of KYC documents and ticket attachments;
- KYC access limited to administrators, with every view of a document recorded in a log that cannot be altered;
- two-factor authentication for staff accounts, and available for your Account;
- staff roles that give each person only the access their work needs, and a log of administrative actions;
- malware scanning of every uploaded file, with quarantine of anything that fails;
- encrypted off-site backups, so a backup provider cannot read the data;
- passwords stored only as one-way hashes, and encrypted connections (HTTPS) to our websites and Client Area;
- physical access to our data centre by appointment, with identification, escorted.
9.2 No system is perfectly secure. You help by using a strong, unique password, turning on two-factor authentication, and keeping your contact details current.
10. Breaches
10.1 If a breach of security affects your personal data and is likely to harm you, we will tell you without undue delay, targeting 72 hours from when we become aware of it. We will tell you what happened, what data is involved, what we are doing about it, and what you can do.
10.2 We will notify the National Data Governance Authority in the manner and within the time the law prescribes.
11. Your rights
11.1 You have the rights below. We give them to everyone, wherever you live.
- Access and portability. You can ask for a copy of the personal data we hold about you. The Client Area has a "Download my data" option that gives you a machine-readable (JSON) copy of your profile, contacts, services, credit, credit notes, invoices, tickets, sign-ins and notices. For other data (for example chats or KYC documents), write to help@zeeroow.com.
- Rectification. You can correct most of your data yourself in the Client Area. Ask us to correct anything else.
- Withdrawal of consent. As section 5.3 describes.
- Erasure. You can ask us to erase your personal data. You can close your Account in the Client Area once every Service and domain has ended and every invoice is paid; any unused Wallet Credit you paid for is refunded as part of closing. We erase or anonymise account data 1 year after closure (section 8), and we keep invoices and payment records as law requires. If there is no reason to keep particular data for that year, ask us and we will consider erasing it sooner.
- Objection to direct marketing. You can stop newsletters and product news at any time.
- Complaint. You can complain to our Data Protection Officer at help@zeeroow.com, and to the National Data Governance Authority.
11.2 To protect you, we may need to confirm your identity before acting on a request. We answer within 30 days. Using your rights is free, unless a request is clearly unfounded or excessive.
11.3 If you are a member of a Customer's team, or a contact on someone else's account, some requests (for example to delete the Account) must come from the Account Owner. We will still tell you what we hold about you.
12. Children
Our Services are for people aged 18 or over, or acting for a business. We do not knowingly collect personal data from anyone under 18. If you believe a child has given us personal data, write to help@zeeroow.com and we will erase it.
13. Cookies
We use only strictly necessary cookies and functional browser storage, plus Cloudflare Turnstile on some forms. Our Cookie Notice lists them.
14. Changes to this policy
14.1 We may update this policy when our Services or the law change. The effective date at the top shows when it last changed.
14.2 For a material change we will tell you by email and in the Client Area at least 30 days before it takes effect. If a change needs your consent, we will ask for it.
15. Language
This policy is published in English and Bangla. The Terms of Service say which version prevails.
16. Contact
Data Protection Officer, Zeeroow Limited, H-12, 11th Floor, Razzak Plaza Moghbazar, Ramna Dhaka-1217, Bangladesh. Email: help@zeeroow.com.