Legal
Privacy Policy
What DropPerch collects, what it sends to a registry on your behalf, and how to get any of it back or removed.
- Effective
- 10 September 2026
- Last updated
- 22 October 2026
01Who we are
DropPerch monitors the lifecycle of domain names you choose and tells you when their registry status changes. This policy explains what personal data the service handles, why, and what you can do about it.
The service is operated by the individual trading as WebVogue Technologies, a sole proprietorship based in India. For the purposes of the Digital Personal Data Protection Act, 2023 and the UK and EU GDPR, the operator of WebVogue Technologies is the data fiduciary and controller of the data described below.
A question about your data is answered directly by the people who build the code that handles it, not passed to a third-party support desk. The operator is an individual rather than a registered company, and their name is given on request to the address below — ask and you will be told who you are dealing with.
Questions about this policy go to support@dropperch.com.
02What this policy covers
It covers the DropPerch website, the signed-in application, the monitoring engine that performs the registry checks, and the emails we send you.
It does not cover the domain registries, registrars, or marketplaces we link out to. Following a link to a registrar to buy a domain puts you on their site under their terms, and we have no part in that transaction.
03What we collect and why
We collect what the service needs to work and nothing speculative. There is no advertising pixel and no session recorder on this site, and Google Analytics runs only if you allow it in the cookie banner.
Account identity
- What it holds
- Email address, password (stored only as a hash by Firebase Authentication), optional display name, and a Google account identifier if you sign in with Google
- Why we have it
- To create your account, sign you in, and prove a watchlist is yours
- Lawful basis
- Performance of our contract with you
- Retention
- Until you delete the account
Watchlist
- What it holds
- The domain names you add, your own notes against them, and the lifecycle state, registry status codes, expiry and last-checked timestamps we record for each
- Why we have it
- This is the service. Without it there is nothing to monitor
- Lawful basis
- Performance of our contract with you
- Retention
- Until you remove the domain or delete the account
Lifecycle history
- What it holds
- One record per observed state change: the previous state, the new state, the raw registry status codes, and which RDAP server answered
- Why we have it
- So the timeline on a domain can be shown, and so an alert can be explained after the fact
- Lawful basis
- Performance of our contract with you
- Retention
- Until you remove the domain or delete the account
Alert preferences
- What it holds
- Alert email address if different from your sign-in email, and which state changes you want to hear about
- Why we have it
- To send you the alerts you asked for and none of the ones you did not
- Lawful basis
- Performance of our contract with you
- Retention
- Until you change them or delete the account
Plan and usage counters
- What it holds
- Your plan, how many domains you are watching, the goal you selected during setup, and where you told us you heard about DropPerch
- Why we have it
- To apply the plan limits, to set sensible alert defaults, and to know which channels bring people to us
- Lawful basis
- Performance of our contract with you
- Retention
- Until you delete the account
Upgrade interest
- What it holds
- Your account identifier, email address, watchlist size, and which part of the product you were looking at when you asked to upgrade
- Why we have it
- Recorded when someone asked to upgrade before checkout existed, so we could tell them it had opened
- Lawful basis
- Our legitimate interest in operating and financing the service
- Retention
- Until we have contacted you, or you ask us to remove it
Subscription and licence
- What it holds
- The Gumroad licence key you paste in, the verification result, the subscription identifier, the billing period, and the email address the purchase was made with
- Why we have it
- To apply your paid plan and to stop applying it when the subscription ends
- Lawful basis
- Performance of our contract with you
- Retention
- Until you delete the account
Messages you send us
- What it holds
- The name, email address, subject and message you submit through the contact form, or send us by email
- Why we have it
- To answer you
- Lawful basis
- Our legitimate interest in responding to enquiries
- Retention
- Up to 24 months after the conversation ends
Site analytics (only if you allow it)
- What it holds
- Pages viewed, the site that referred you, approximate location derived from your IP address (Google Analytics does not store the address itself), device and browser type, a random identifier kept in a cookie, and whether the visit ended in creating an account (only the sign-in method, email or Google, is sent with it)
- Why we have it
- To see which pages are useful and which channels bring visitors who sign up
- Lawful basis
- Your consent, given or refused in the cookie banner and changeable from “Cookie settings” on every page
- Retention
- No more than 14 months in Google Analytics (its longest setting); the cookie expires after 2 years, or is deleted when you decline
Bot protection
- What it holds
- Signals about your browser and device, and your interaction with the page, read by Google reCAPTCHA Enterprise when the app talks to our database
- Why we have it
- To stop automated abuse of the sign-up and database endpoints
- Lawful basis
- Necessary to provide a secure service (a legitimate use: keeping the service you asked for working and safe)
- Retention
- Held by Google under its reCAPTCHA terms; we receive only a pass/fail token
Operational logs
- What it holds
- Server-side records of monitoring runs and email delivery attempts, including the domain checked and the outcome
- Why we have it
- To find out why a check or an alert failed
- Lawful basis
- Our legitimate interest in keeping the service working
- Retention
- Up to 90 days
We never see or store your password. Firebase Authentication holds it as a hash, and it is not readable by us.
We do not collect special category data, we do not profile you, and we make no automated decisions about you that have a legal effect.
04What watching a domain causes us to send out
This is inherent to how the service works, so it is stated plainly rather than buried. When you add a domain to your watchlist, that domain name leaves our systems as part of every subsequent check:
- Domain registries and registrars (RDAP) — We query the authoritative registry for each domain you watch, over RDAP (RFC 9083). The query contains the domain name and nothing about you.
- IANA bootstrap registry — We fetch IANA’s public list of which RDAP server is authoritative for which top-level domain. This request contains no domain name and nothing about you.
- Open PageRank (DomCop) — On the Portfolio plan only, we send the domain name to DomCop to retrieve the authority figures shown in your watchlist. On the free plan this request is never made.
None of these requests identify you. They contain the domain name, not your account. A registry cannot tell from our query who asked, or that anyone is watching.
05Our legal grounds for using it
Where the GDPR applies, we rely on the following:
- Performance of a contract — Running your account, storing your watchlist, performing the checks, and sending the alerts you configured. Without this we cannot provide the service you signed up for.
- Legitimate interests — Keeping the service secure and working, responding to your messages, and contacting people who asked to be told when paid plans open. We have weighed these against your interests and consider the impact minimal.
- Legal obligation — Retaining records where the law requires it, and responding to lawful requests from authorities.
Under the Digital Personal Data Protection Act, 2023 we rely on your consent (section 6) for your account and watchlist, given when you create an account after seeing the notice on the sign-up form, and separately for analytics cookies, given or refused in the cookie banner. Where you send us something yourself, such as a contact-form message, we use it for the purpose you sent it for, which that Act treats as a legitimate use (section 7). You can withdraw consent at any time, as easily as you gave it — see your rights. Withdrawing does not affect processing that happened before.
07International transfers
Our infrastructure runs on Google Cloud, and our email provider is in the European Union or the United States depending on which is active. Your data will therefore be processed outside India.
For transfers out of the UK and EEA we rely on the European Commission’s Standard Contractual Clauses, which are part of our agreements with these providers. Google Cloud is additionally certified under the EU–US Data Privacy Framework.
Under section 16 of the Digital Personal Data Protection Act, 2023, personal data may be transferred outside India except to countries the Central Government restricts. None of the countries our providers operate in is restricted, and we will move away from any provider whose location becomes restricted.
09Your rights, and how to use them
You can exercise the following at any time:
- Access and portability — The Account page has an export button that downloads everything your account holds as a JSON file, immediately and without asking anyone.
- Correction — Edit your display name and alert preferences in the app. For anything else, email us and we will correct it.
- Deletion — Delete your account from the Account page. This removes your profile, your watchlist, and the lifecycle history recorded against it. Sign-in credentials are removed from Firebase Authentication at the same time.
- Objection and restriction — You can object to processing based on our legitimate interests, including the upgrade-interest list. Email us and we will stop.
- Withdrawing consent — You can turn off any category of alert on the Alerts page, withdraw analytics consent from “Cookie settings” on any page, or withdraw consent entirely by deleting your account — each as easy as the step that gave it.
- A summary of what we hold and who else has it — Ask, and we will send a summary of the personal data we process about you, what we do with it, and the name of every service provider listed below that has received it. The export above covers the data itself.
- Nominating someone — Under the Digital Personal Data Protection Act, 2023 you can nominate another person to exercise these rights for you if you die or become unable to. Email us from your account address with the nominee’s name and email address.
- Grievances — If something we did with your data is wrong, tell us. See contact and complaints.
Deleting your account also cancels the checks on every domain you were watching. We keep no shadow copy of a deleted watchlist. Backups taken before deletion are overwritten on their normal cycle, within 30 days.
To make a request by email, write to support@dropperch.com from the email address on your DropPerch account — that address is how we confirm the request is yours, and we will not ask for identity documents. We answer within 30 days, and do not charge for this.
10How it is protected
The database enforces access at the document level: rules on the server, not checks in the browser, decide that a watchlist can only be read by the account that owns it. The paid-only authority figures are held in a separate collection that a free account is not permitted to read at all, rather than being sent to the browser and hidden there.
Lifecycle history is append-only — no client can write or alter it, including you. Traffic is encrypted in transit, and data is encrypted at rest by our infrastructure provider.
No system is perfect. If we discover a breach affecting your personal data, we will email you without delay at your account address, saying what happened and when, what it means for you, what we have done about it, what you can do to protect yourself, and who to contact. We will report it to the Data Protection Board of India straight away and in full within 72 hours, as the Digital Personal Data Protection Rules, 2025 require, and to any other authority the law requires.
11Children
The service is for business use and is not directed at children. You must be 18 or over to create an account, and the sign-up form asks you to confirm that. We do not knowingly collect personal data from anyone under 18, and we do not track or target advertising at anyone. If you believe a child has created an account, tell us and we will delete it.
12Changes to this policy
If we change how we handle your data, we will update this page and move the “last updated” date. For a change that materially affects your rights, we will email account holders before it takes effect rather than relying on you to notice.
13Contact and complaints
Privacy questions and rights requests: support@dropperch.com. Anything else: the contact form.
Grievance Officer. Under the Digital Personal Data Protection Act, 2023, questions about how your personal data is processed, and grievances, are answered by the operator of DropPerch, who reads this inbox personally: support@dropperch.com. We respond within 30 days. Every reply to a rights request will repeat this contact.
You must raise a grievance with us first. If we do not resolve it, you can complain to the Data Protection Board of India.
If you are in the UK or EEA, you also have the right to complain to your local data protection authority. We would rather you came to us first, but that is your right and not conditional on doing so.