Privacy Policy

What stays in your browser

The floor-plan editor runs entirely on your device. Unless you sign in, your plan is never uploaded anywhere. Specifically, the following are kept in your browser's local storage and are not sent to us:

• the plan you are working on, saved automatically as it changes so a refresh does not lose it;
• your display preferences — feet or metres, currency, region;
• a random identifier for this browser, which our server uses to keep this browser's credit balance (see Credits below) and to apply fair-use limits;
• a per-day counter of how many AI plans you have generated, used to apply usage limits where they apply;
• a flag recording that you have an account, so we know whether to load the sign-in code at all;
• the ad click you arrived from, if any — the campaign, the keyword and the match type, so the analytics events can say which ad brought you here.

Clearing your browser's site data for this domain erases all of it. If you have not signed in, that erases everything we could possibly know about your plan.

Share links work the same way. When you copy a share link, the whole plan is compressed into the part of the URL after the # — the fragment, which browsers never send to a server. Whoever opens the link decodes the plan on their own device. We never receive, store or see a shared plan, and we cannot recover one for you if the link is lost.

What you send us when you use the AI

The AI copilot is the one feature that sends your words off your device. When you describe the house you want, that text is sent to our server, which forwards it to OpenRouter, which routes it to Anthropic's Claude model. The reply comes back the same way.

We keep a copy of each message you type into the chat, so we can see what people ask for and improve the product. Before it is stored, email addresses and phone numbers in it are replaced with a placeholder. It is kept with a coarse record of what happened (for example, whether the change could be made) and a one-way scrambled identifier for your browser or account, never your plan's contents, your IP address or the model's full reply. OpenRouter and Anthropic process the request under their own terms and privacy policies; we do not control their retention.

Our server does briefly keep your IP address in memory to apply rate limits and daily message caps, and — if you are signed in — your account identifier for the same purpose. Both live only in the running server's memory and are not written to a database.

Please do not type anything into the copilot that you would not want processed by a third-party AI provider. It needs to know about rooms and plot sizes, not about you.

If you leave your phone number

The offer to have a plan finished with an expert is answered on WhatsApp. On a computer, where a WhatsApp link cannot open a chat directly, we offer a code to scan with your phone and, beside it, a field for your number. If you type one in, we store it — with the country code, the share link of the plan you were looking at if there is one, and the time — for the single purpose of messaging you about that plan on WhatsApp. It is not used for anything else, it is never sold or passed to an advertiser, and it never reaches our analytics. Write to us at the address below and we will delete it.

Numbers left with us before 29 September 2026 to have the exact dimensions of a plan sent on WhatsApp are kept the same way: with the plan's share link, its reference code and the time, and used only to send that plan and to follow up about it.

When you tap the button to have a plan finished

Each time you press the button that opens WhatsApp to have a plan finished, we store a record of that press: a reference code (which is also put into the WhatsApp message), a short summary of the plan — plot size, facing, number of floors, bedrooms, parking and whether you chose vastu — the ad or campaign your visit came from, our analytics identifiers for your browser, and the type of device. It holds no phone number. Its only purpose is to match a WhatsApp enquiry to the plan and the ad it came from.

If you then order the service over WhatsApp, we keep a record of the order — its reference, the payment identifiers, the dates, the amounts, and your phone number if you give it — so that we can deliver the work and keep our accounts. It is not used for marketing and is never sold. Write to us at the address below and we will delete what the law does not require us to keep.

Credits

Generating AI plans is free. Copilot work — edits and redraws — is paid for in credits, and the balance is kept on our server rather than in your browser. Until you sign in it is filed under the random browser identifier described above; when you sign in, what is left of it moves to your account.

For each credit entry we keep how many credits, what for (a free grant, a purchase, a generation, an edit, an export, a refund) and when. We do not keep the contents of your plan or the text you typed with it.

If you create an account

Accounts are optional and the product works fully without one. Their only purpose is to save your plans so you can open them on another device.

Sign-in is handled by Google Firebase Authentication, using either a Google account or a link sent to your email address. When you sign in we hold:

• your email address, and the account identifier Firebase gives us;
• the plans you choose to save, stored in Google Cloud Firestore under your account;
• your credit balance and its history, and a per-day count of AI generations, exports and copilot messages, stored under your account so they follow you across devices. These record how many, never what.

We do not have or want your password: Firebase handles authentication and we never see one.

Analytics

We use two measurement tools. PostHog counts how many people reach each step of the product — opened the app, generated a plan, made a purchase. Google Analytics (GA4) does the same for the marketing pages and, if you arrived here from one of our Google ads, tells Google Ads that the click led to a purchase, so we can see which ads bring people who actually use the product.

If you arrive from an ad, the click's campaign, keyword and match type are kept in your browser's local storage and attached to those analytics events. That is how we tell one ad from another; it does not identify you.

Analytics events deliberately carry no personal data, no plan contents, no money amounts and no text you typed. They record that something happened and, at most, a coarse category such as which unit you chose. We use them to see how the product is used and to measure our own advertising — never to sell your data, and never to follow you around other websites.

The Google tag runs on every page. PostHog is only active on builds configured with a PostHog key.

Who else is involved

HousePlanAI is a small product and relies on a handful of established providers rather than running its own infrastructure. They may process your data as described above:

• Vercel — hosting and content delivery. Sees the requests your browser makes, including your IP address, as any web host does.
• Google Firebase (Authentication and Firestore) — sign-in and saved plans, only if you make an account.
• OpenRouter and Anthropic — process the descriptions you send to the AI copilot.
• PostHog — product analytics, as described above.
• Google Analytics and Google Ads — usage measurement and ad conversion tracking, as described above. Google sets its own cookies for this.
• Razorpay — our payment processor. If you buy a credit pack or a plan's dimensioned sheet, Razorpay takes the payment: it sees your name, contact details and card or UPI details, and we never see your card. Razorpay tells us only that a payment succeeded, what it was for, which customer it belongs to, and later whether it was refunded or disputed.
• Google Fonts — the site's typefaces are loaded from Google's font servers, which means Google sees the IP address of anyone who loads a page here.

We do not sell your data, and we do not share it with advertisers. There is no third-party advertising on this site; the Google tag measures our own ads and nothing else.

Cookies

HousePlanAI sets no cookies of its own. Google's analytics and ads tags set their usual cookies (such as _ga) to tell one visit from the next; we use them for measurement, including of our own ads, and for nothing else. Everything else lives in your browser's local storage, for the things listed at the top of this page — your current plan, your preferences, your browser identifier, your daily counters, the ad click you arrived from, and an analytics identifier when analytics is enabled. If you sign in, Firebase sets its own storage entries to keep you signed in.

Keeping and deleting your data

Anything in your browser is deleted when you clear this site's data, and you do not need us for that.

Saved plans and usage counters stay in your account until you delete them. You can delete individual plans from the app. To delete your whole account and everything in it, write to us and we will do it.

Depending on where you live, you may have rights to access, correct, export, delete or object to the processing of your personal data — for example under the GDPR in the EU and UK, or India's Digital Personal Data Protection Act. Ask us at privacy@mercai.in and we will act on the request; we will not make you prove a legal basis for it.

Children

HousePlanAI is not designed for children and we do not knowingly collect data from anyone under 16. If you believe a child has created an account here, tell us and we will remove it.

Changes to this policy

If we change how the product handles data, we change this page in the same release. The date above is when it last changed. There is no archive of previous versions yet.

Contact

Questions, requests or corrections: privacy@mercai.in. A real person reads it.