Privacy Policy
Last updated 20 November 2026 ยท Effective 20 November 2026
The short version
- We never see your conversations. The extension redraws them on your own screen. It does not store them and it does not send them anywhere.
- The free Notion disguise needs no account. An extension that is not linked to an account sends us nothing.
- The 15-day trial needs a Google sign-in on this website. We then store your Google account id, your email address, your name and the profession you pick.
- A linked browser sends us one thing: a random id that the extension made for itself.
- If you buy, Razorpay takes the payment. We store the order or subscription id, the amount, the status and the date you have paid up to.
- This website has no analytics and no trackers. It sets two cookies, both for sign-in.
- You can delete your account from the extension's popup at any time. Two things outlive it: a hash that records that your trial was used, and purchase records with your account removed from them. Both are explained below.
Who we are
This service is operated by Mrinal Singh, an individual based in India. For anything in this policy, contact mriinaaal@gmail.com.
What the extension never collects
Masque does not store any of the following, and does not send any of it to us or to anyone else. This is true on every tier, paid or free:
- The content of your conversations: your prompts and the model's replies
- Files or images you attach
- The pages you visit, your URLs, or your browsing history
- Keystrokes, clipboard contents, or screenshots
- Usage analytics, telemetry, crash reports, or behavioural data of any kind
Your chat still goes to ChatGPT, Claude or Gemini exactly as it would without Masque. Those sites keep running underneath the disguise, and their own privacy policies cover what you type there.
This comes from how the extension is built. The scripts that run on the chat page are the only part that can see a conversation, and they contain no code that can make a network request. An automated test fails the build if anyone adds one. The only part that can use the network is the background worker. The rest of the extension can ask it three things: what tier this install is on, to cancel a subscription, and to delete the account. None of those carries page content. Chrome extensions ship as readable files, so you can check this in the copy you have installed.
What stays in your browser
Your settings are kept in Chrome's own extension storage. They are never sent to our server.
- Chrome's synced storage: the disguise you chose, including a choice per site; the titles you type into a disguise; the names and email addresses you tell the disguises to show; the decoy you picked and any decoy text you wrote; your hotkeys; and the shake and auto-panic switches. If Chrome sync is on, Chrome copies these to your other browsers through your Google account. That copy is made by Chrome and Google, not by us.
- Chrome's local storage, on that device only: whether the disguise and the decoy are on; the install id and the signed token described under "Linking a browser"; your profession; the time of the last check with our server; and the latest clock time the extension has seen, so that turning the computer's clock back does not extend a token.
The free tier
The free tier is the Notion disguise on ChatGPT, Claude and Gemini. It needs no account, no sign-in and no card. Our database holds nothing about a person who uses only the free tier without signing in.
When you install the extension it opens this website's start page in a new tab, once. That is an ordinary page visit. You can close it without signing in.
Signing up with Google
Sign-up happens on this website, with Sign in with Google and nothing else. You do not create a password with us.
When you press Sign in with Google, your browser goes to Google. We ask Google for three standard scopes: openid, email and profile. Google asks you which account to use and then sends our server an ID token, a short statement about that account. From it we store:
- Your Google account id. This is the identifier Google assigns to the account. It is how we recognise you when you sign in again.
- Your email address, unless Google tells us the address is unverified. In that case we store no address.
- Your name, as it appears on the Google account.
- The time the account was created with us.
The profile scope can also include a profile picture. We do not store it. We do not keep the access token Google issues, and we do not call any other Google service for your account. We cannot see your Google password, mail, contacts or files.
Each time you sign in, we replace the stored email address and name with the ones Google sends that time.
What we use them for:
- The account id: to recognise you, and to make the trial record described below.
- The email address and name: to show you which account you are signed in with, to prefill Razorpay's checkout if you buy, and to find your account when you write to us.
- Our server sends no email. If we write to you, it is by hand, about your account, a purchase, or a material change to this policy or the terms.
Google knows that you signed in to Masque, as it does for any site that uses Sign in with Google. Google's privacy policy covers what Google does with that.
Your profession
After your first sign-in we ask for your profession: student, teacher, developer, office or other. We store the answer on your account. It does one thing: it picks which invented sample content the disguises show around your chat, such as page names, channel names and inbox rows. The sample content is made up and is not about you.
The profession is set once. It cannot be changed from the site or from the extension. To change it, write to mriinaaal@gmail.com. The server includes it in the token it gives a linked browser, and the extension keeps a copy in its local storage.
The trial
The first sign-in with a Google account starts a 15-day trial of everything. There is one trial per Google account. It needs no card.
To keep it at one, we hold a separate trial record with two fields: a hash, and the time the trial started. The hash is the SHA-256 of the fixed text masque-trial: followed by your Google account id. It holds no email address and no name.
A hash cannot be run backwards to get the account id out. But it is not random. Anyone who already has a Google account id can compute the same hash and check whether it is in the table. That is exactly how we use it: when a Google account signs in, we compute its hash and look for the record.
This record is kept when an account is deleted. If you delete your account and sign up again with the same Google account, you get the original start date back, not a new trial. After the trial ends, the Notion disguise stays free.
Linking a browser
The trial and paid plans reach a browser by linking it to your account. Only the extension's background worker talks to our server, and only at getmasque.app.
The install id. The first time the extension runs, it generates a random id and keeps it in its local storage. The id is not derived from your device, your Chrome profile or your Google account. It is sent only to our server.
Before linking, nothing is sent. The worker's scheduled checks are skipped for an install that is not linked. The address of the start page that opens on install includes the extension's own id, so the page can reach the extension. Nothing in our database records it.
Linking. When you are signed in on this website and have chosen a profession, the site hands the extension a one-time code. The code is random, works once and expires after five minutes. The extension sends our server that code and its install id. We store the install id against your account, with the time it was linked and the time it last checked in.
An account can have two browsers linked. Linking a third unlinks the one that was linked earliest, and we delete that browser's install id from the account.
After linking. The worker sends our server the install id, and nothing else, at these times:
- when Chrome starts, and when the extension is installed or updated
- every six hours while Chrome is running
- when this website asks it to check, for example after a purchase
- when you press Cancel subscription or Delete my account in the popup
- on the free tier after a trial or plan has ended: when you open the popup or one of the three supported sites, at most once an hour, so that a new purchase is noticed. The request is the same and does not say which site.
These requests carry no cookies. Like any web request, they reach us from an IP address and with your browser's standard headers. See "Server, logs and backups" for what is and is not written down. Each check updates the "last checked in" time we hold for that browser.
The token. The server answers with a signed token that is valid for at most seven days. It states the tier, whether it comes from the trial, Pro or Lifetime, the install id, your profession, and the relevant dates. The extension keeps it in local storage. This is why paid features keep working for up to seven days without a connection.
Payment
Paid plans are sold only in India for now, in Indian rupees. We are the seller. Payments are taken by Razorpay, a payment gateway.
Until you press Buy, this website loads nothing from Razorpay or from any other third party. When you press Buy:
- Our server asks Razorpay to create an order (Lifetime) or a subscription (Pro). It sends the amount or the plan, and our internal id for your account as a reference.
- Your browser loads Razorpay's checkout from Razorpay. We pass it your name and email address so the form starts filled in.
- You enter your card or UPI details in Razorpay's form. They go to Razorpay, not to us. We never receive your card number, CVV, UPI PIN or bank login.
- Razorpay then tells our server what happened, in signed notifications. A notification can include details we do not need, such as the last four digits of a card, a UPI ID, or the email address and phone number you gave Razorpay. Our server reads the order or subscription id and, for Pro, the date the paid period ends. It does not store or log the rest.
What we store about a purchase: the plan (Pro or Lifetime), the Razorpay order id or subscription id, the amount, the status (for example created, paid, active or cancelled), the paid-until date for Pro, and the time the record was made. The record is made when checkout opens, so it exists even if you close checkout without paying. There are no licence keys. A purchase is attached to your account.
Razorpay keeps its own records of the payment and may contact you about a subscription. Its checkout may set its own cookies. Razorpay's privacy policy covers all of that.
What our database holds
This is the complete list.
| Account | Our id for the account, your Google account id, email address (if verified), name, profession, time created. Kept until you delete the account. |
| Trial record | The hash described under "The trial" and the time the trial started. Kept with no end date, including after the account is deleted. |
| Linked browsers | Install id, the account it belongs to, time linked, time of last check. At most two per account. Deleted when the browser is unlinked or the account is deleted. |
| Link codes | The code, the account it is for, its expiry time. A used code is deleted at once. An expired one is deleted the next time any code is issued. |
| Purchases | Plan, Razorpay order or subscription id, amount, status, paid-until date, time created, and the account. Kept with no end date. When the account is deleted the record stays but no longer points to an account. |
Cookies
This website sets two cookies. Both are our own, and both exist only for sign-in.
| gst | Set when you press Sign in with Google. It holds a random value, so we can check that Google's reply belongs to the sign-in your browser started, and the page to return you to. It lasts ten minutes at most and is cleared as soon as sign-in finishes or fails. |
| sid | Set when sign-in succeeds. It holds our id for your account, an expiry time and a signature that stops it being forged. It lasts 30 days, after which you sign in again. Signing out clears it. It stops working the moment the account is deleted. |
Scripts on the page cannot read either cookie. There are no advertising or analytics cookies. Every script, font and image on this site is served from this site. The one exception is Razorpay's checkout, which loads only when you press Buy.
Server, logs and backups
The website and the database run on one server that we operate ourselves. It is a virtual machine on Oracle Cloud Infrastructure, in Oracle's Mumbai region in India. The database is a single file on that machine's disk. The site is served over HTTPS only.
Logs.
- We keep no access log. Ordinary page visits and ordinary requests from the extension are not written down: no IP address, no page, no browser details.
- The application writes a line when it starts, a line naming the type of each Razorpay notification it receives (for example "payment.captured", with no ids or amounts), and a line when something fails. A failure line about a Razorpay call can include a subscription id.
- The web server in front of the application logs its own errors. If a request fails because the application did not answer, that entry includes the request: its IP address, the address requested and the browser's headers.
- These logs stay on the server. Each of the two is capped at 15 MB. When one is full, its oldest lines are overwritten, so there is no fixed number of days: on a quiet server a line can last months, and it is gone once the log has filled.
Backups. A job on the same server copies the database every night at 02:30 UTC. The same job deletes copies that are more than 14 days old, so a copy lasts 15 or 16 days. The copies stay on that server. They exist to undo a fault, such as a bad update. An account you delete is removed from the live database at once, but it is still inside the copies made before then until they are deleted.
Who else processes your data
- Google: sign-in, as described above.
- Razorpay: payments, only if you press Buy.
- Oracle: the virtual machine and disk the server runs on, in Mumbai.
We use no analytics, advertising or tracking service. If you email us, we have your message and address, as with any email. We do not sell your data, and we do not share it for advertising.
How long we keep it
- Account and linked browsers: until you delete the account
- Trial record: no end date, so that one Google account gets one trial
- Purchase records: no end date. They are our record of what was sold, and the server counts Lifetime purchases from them
- Backup copies of the database: 15 or 16 days
- Server logs: until overwritten. Each log is capped at 15 MB
Deleting your account and data
Open the extension's popup in a linked browser and press Delete my account, then press it again to confirm. You do not have to ask us first. It cannot be undone.
What happens, in this order:
- If a Pro subscription can still charge, we cancel it at Razorpay first. If Razorpay does not confirm the cancel, the account is not deleted and the popup asks you to try again.
- The account is erased: our id for it, your Google account id, email address, name, profession and the time it was created.
- Every linked browser is unlinked, and any unused link code is erased.
- The browser you pressed the button in discards its token and drops to the free tier. Any other linked browser does the same the next time it checks in.
- The sign-in cookie stops working, because it points to an account that no longer exists.
What is kept:
- The trial record: the hash and the trial's start time.
- Purchase records, with the account removed: plan, Razorpay order or subscription id, amount, status, paid-until date and time created. In our database they no longer point to anyone. Razorpay's own records can still connect those ids to the person who paid.
- Backup copies made before the deletion, for up to 16 days.
- Whatever Razorpay and Google hold in their own systems.
- Your extension settings, which are in Chrome's storage on your devices and were never on our server.
Deleting the account ends paid access at once. The rest of a paid Pro month and a Lifetime purchase both go with it, because they were attached to the account. Signing up again does not bring them back. If you want a refund, ask for it before you delete.
Uninstalling the extension deletes nothing on our side and does not cancel Pro. Cancel or delete from the popup first.
If you cannot use the popup, for example because you no longer have a linked browser, write to mriinaaal@gmail.com from the email address of the Google account. We will delete the account for you within 30 days.
Your rights
We use your data only for the purposes described in this policy.
Under India's Digital Personal Data Protection Act, 2023
The Act calls you a Data Principal and us a Data Fiduciary. It gives you the rights below. This is how to use each one with us.
- Access. Ask, and we will send you a summary of the personal data we hold about you and what we do with it. The table above is everything our database can hold.
- Correction and updating. Your name and email address come from Google. Change them in your Google account and sign in here again, and ours are replaced. To change your profession, write to us.
- Erasure. Use Delete my account in the popup, or write to us. What is kept afterwards, and why, is listed above.
- Withdrawing consent. You can withdraw at any time by deleting your account. That ends the trial or a paid plan, because neither can run without an account. The free tier needs no account.
- Nomination. You may name another person to use these rights for you if you die or become unable to act. Write to the Grievance Officer with their name and contact details.
- Grievance redressal. Write to the Grievance Officer below. If you are not satisfied with the answer, you may complain to the Data Protection Board of India.
If you are outside India
This one policy applies in every country. We do not publish a separate one for each. The free tier and the trial work from anywhere. Paid plans are sold only in India for now. Wherever you are, your account data is sent to and stored in India, on the server described above.
European Economic Area, United Kingdom and Switzerland. If the GDPR or the UK GDPR applies to you:
- The controller of your data is the operator named under "Who we are".
- Why we may use it: to provide the account, the trial and any plan you asked for (performing our contract with you); and to keep the record that a trial was used, keep our record of what was sold, and keep the service secure (our legitimate interests).
- Your rights: to see your data, correct it, have it deleted, restrict or object to its use, receive a copy you can take elsewhere, and withdraw consent. Use the delete button, or write to mriinaaal@gmail.com. We answer within 30 days.
- Your data is stored in India. The European Commission has not recognised India as giving the same level of protection as the EU. Signing up sends your data there, because that is where the service runs.
- You can complain to the data protection authority where you live.
- We have not appointed a representative in the EU or the UK.
California and other US states. We do not sell personal data, we do not share it for advertising, and we use no advertising or tracking cookies. You can ask to see or delete your data in the same way as anyone else.
Everywhere else. If the law where you live gives you rights over your personal data, you can use them in the same way: the delete button, or an email to mriinaaal@gmail.com.
If something goes wrong
If a breach affects your personal data, we will tell you and the Data Protection Board of India without undue delay. We will say what happened, what it affects and what we are doing about it. If the law of another country requires us to notify an authority there, we will do that too.
A breach of our server could expose what is listed in this policy: Google account ids, email addresses, names, professions, install ids and purchase records. It could not expose your conversations, your card or UPI details, or your extension settings, because none of them is stored there.
Grievance Officer
This is the person who answers questions and complaints about your personal data.
Name: Mrinal Singh
Designation: Owner
Email: mriinaaal@gmail.com
We acknowledge every grievance within 48 hours and resolve it within 30 days. If we cannot resolve it in that time we will tell you why and give you a date.
Children
Masque is not meant for anyone under 15, and you must be 15 or older to create an account. If you are 15, 16 or 17, sign up only with the permission of a parent or guardian. We do not ask for your age, and we do not knowingly collect data from anyone under 15. If you believe someone under 15 has signed up, or you are a parent who wants a child's account deleted, write to us and we will delete it.
Changes
If we change this policy we will update the date above. For a material change we will also email account holders at the address from their Google sign-in, where we have one. We will not retroactively reduce your protections.