Privacy Policy

HavnOS, 12311 Ridge Top Ct, Conroe, Texas 77304, United States. Questions about your data go to privacy@havnos.com.

Your email address and the documents and details you give us about your home — inspection reports, contracts, policies, warranties, receipts, and anything you type in yourself. We also keep a record of actions you take in the product, like completing a task or filing a document, because that history is the product.

Inside your account we also count, for each day, which screens were opened — the screen's name, like Vendors or Files, never what is on it — and two actions: pressing a plan button, and reading an appliance label from a photo. It shows us where people get stuck. It is tied to your account, never shared with anyone, and deleted with your account. Global Privacy Control and the switch under Ad measurement don't change it, because it is part of running the product, not advertising.

To build your record: the systems and appliances in your home, the maintenance they need, and the dates and obligations your paperwork contains. Reading happens when you ask for it, on the document you chose.

Documents are read using Anthropic's Claude models through their API. Anthropic does not train on data sent through the API. We do not train any model on your documents and we do not build a shared model from customer data.

The chats. What you type into the chat — Customer service, or the AI House Manager on Max — is sent to Anthropic's Claude to write the answer, and both are labelled as AI. For the House Manager, your home's record goes with it: its address, systems and appliances, tasks, findings, vendors, jobs, mortgage and money questions, and the names of your files. When it looks up a manual or a how-to video, it searches the web with the appliance's make and model and the job — never your name or address. Conversations are saved to your account so you can come back to them, and they are deleted with it.

AI tools that help us run HavnOS. We also use Anthropic's Claude to help us run and support the service — for example, to look into a problem with an account, answer a support ticket or check that something works. When we do, it can see the account details involved, such as your name, email address and the records in question.

• We do not sell your data. Not to anyone, at any price.
• We do not show advertising and do not let anyone pay to influence what the product tells you.
• We do not share your documents with other users, including any inspector or realtor who referred you. An affiliate sees that you signed up. They do not see your house.

You. Access is enforced in the database itself, per row, against your account — not only in the interface. A small number of staff can access production systems where it is necessary to operate or debug the service.

Our infrastructure providers necessarily hold the data to serve it: Supabase (database, sign-in, file storage), Vercel (hosting, cookieless page-view counts on our public pages, and the first place an uploaded document is stored), Anthropic (reading documents, answering the chats, and the AI tools that help us run the service), Postmark (email), Stripe (payments — card details go directly to Stripe and never reach our servers; and affiliate payouts — an affiliate's identity and bank details go directly to Stripe, and we keep only the id of their Stripe account), and Google Sheets, which receives the email address and report link of anyone who asks us to email them their report.

Real estate paperwork often contains social security numbers, bank details and signatures. Treat everything you upload as something worth protecting, because it is. Turning on two-factor authentication is the single most effective thing you can do, and we will keep asking you to once you are on a paid plan.

Redaction now runs on every document we read. Before anything is stored or shown, we scan what the reader extracted for social security numbers, bank and card numbers and similar identifiers, mask them, and flag the document so you can see what was found. If you would rather the file itself were gone, you can shred it from the document view and keep the record without the original.

Being exact about the limit, because the difference matters: we redact what the reader returns. The original file is still uploaded and still passes through the reading service intact. So redaction protects what we keep and display — it does not mean a social security number was never transmitted. If a document contains something you do not want leaving your machine at all, black it out before uploading.

We keep your data while your account exists. Cancelling a paid plan does not delete anything — you move to the free plan and your record stays.

You can delete your account yourself, from Account & security → Deleting your account. Every property, document, photo, task and vendor goes, and the files themselves are removed from storage — not just the records pointing at them. There is no bin and we cannot get it back. If you would rather a person did it, write from the address on the account to privacy@havnos.com. You can also ask for a copy of what we hold.

If you never made an account. Upload a report without signing up and we keep it for 30 days so your link works, then delete the file and the reading. Ask us to email you the link and we keep it the same 30 days. A forwarding code (see Ad measurement) is deleted after the same 30 days. If an upload fails and you leave your email in the box under it, that address is kept with our support records and used only to help you with that report.

What we cannot pull back. A document read by our AI provider is sent to them to be read. We ask them to delete it, but we cannot promise what a third party has already logged. If a document is sensitive enough that this matters, do not upload it.

Session cookies to keep you signed in; a cookie remembering which of your homes you are looking at; a referral cookie for ninety days if you arrived through an affiliate link; a cookie for ninety days noting which site, post or ad first brought you here (see Ad measurement); a cookie for a year if you turn ad measurement off; and, if you read a report or a contract before signing up, a cookie for twenty-four hours that lets the account you create pick it up. Unless you opt out, Meta's pixel also sets its own cookies, named _fbp and _fbc — see Ad measurement.

Do Not Track. Browsers' older “Do Not Track” setting never became an agreed standard, so we don't act on it. We honour Global Privacy Control, the signal that replaced it — see Ad measurement below.

We count where visitors come from — an ad, a post, a search, another site — so we know which of them are worth paying for. A cookie on your browser remembers for ninety days where you first came from (for example “instagram”, or the name of one of our ads), and we keep daily totals of how many people each source sends, how far they get on the way to uploading (whether the upload button came into view, was pressed, and so on — a note in your browser makes each step count once a day), and how many of them upload a report or create an account. The totals carry no name, email, address or IP. If you create an account, where you first came from is saved with it, so we can see which sources lead to paying customers. None of this is shared with anyone.

On a phone, the address we show for forwarding your inspection report can carry a short code — for example report+k3fq7a@in.havnos.com — so a report forwarded to it is counted for where you came from, the same as an upload. We keep the code for 30 days with that source and, if Meta's pixel had set them, Meta's two cookies (below) — never your email address, and nothing from the report.

Our public pages and the billing page also load Meta's pixel, so Meta can tell us whether our Facebook and Instagram ads work. It receives that one of those pages was viewed, and three moments: that an inspection report was uploaded, that an account was created, and that a plan or read pack was bought — the currency, not the amount. It never receives anything from your reports or your account: no address, name, email, document or number. It is never loaded by your report links or by the pages that hold your home's records, and nothing is ever sent to Meta from them. Meta can connect these events to a Facebook or Instagram account signed in on the same browser — that is how it measures an ad — under Meta's own privacy policy.

Our server also tells Meta when an inspection report is uploaded on our site or arrives at a forwarding address with a code, so the moment is counted even when a browser blocks Meta's script, and counted once when it does not. It is the same moment and nothing more: for an upload, the page's address, your browser's type and internet address, and Meta's two cookies — all things the pixel itself sends; for a forwarded report, only the two cookies kept with its code. We do not store your internet address for this, and your email address is never sent.

We also count page views on our public pages — the home page, the guides, the FAQ and pages like them, and the sign-up, sign-in and billing pages — with Vercel Web Analytics, to see which pages people read and where they came from. For each view it receives the page's address with anything that could identify you taken out, the site that sent you, your approximate location (country, region and city) and your kind of device, operating system and browser. It sets no cookies: Vercel tells one visit from another with a code made from the request and discards it after 24 hours, and keeps no name, email or internet address. It never counts your report links, your account or the pages that hold your home's records. (Inside your account we keep a simpler count of our own — see What we collect.)

We honour Global Privacy Control: if your browser sends it, the pixel never loads, our server tells Meta nothing about your visit, and the forwarding address carries no code — and Vercel counts none of your page views. You can also turn ad measurement off for this browser here; it stays off for a year, or until you clear your cookies, and it stops the page-view counting as well. The switch is for Meta and those counts — our own totals above say nothing about who you are, and the source saved with an account is never shared.

Checking this browser…

Material changes will be announced by email to account holders rather than by quietly editing this page. See also our terms.