Privacy

Who publishes this

Hoam is independent: not published by any association, board or management company, and no association funds pay for it.

Hoam is operated by Tessera Systems, LLC.

What is collected, and why

Signing in

You sign in with Google, or with a link mailed to you. Google tells us your email address, whether it is verified, and your first name — your full name, if it gives no first name. The account holds that address, an identifier, a date, and a display name: the one Google gave, or the one you type if you sign in by email. Neighbours see it only if you choose it as a byline; otherwise a posting is signed “A verified owner” or “A verified resident”. Your browser holds a signed token that names your account, and three cookies that carry only an expiry and a signature.

Verifying a home

A card goes to the property, at the address on its parcel record — never to anything you type. An owner’s card goes instead to the mailing address the association itself supplies for that lot; where it has supplied none, no home can be claimed as owner. The code is stored as a salted one-way hash. A verified home is one row: your account, the association, the lot by its parcel number, and the tier.

Taking part

A posting stores which household wrote it and, separately, the byline your neighbours see; the link between them is never sent to anybody. A sign-up sheet resolves to a list of bylines, an RSVP to a count. A report stores the reason and who filed it, and neither is returned to anybody. Statutory votes are not run here; advisory polls take one choice per home and publish totals, never rows.

Ask

Ask sends your question, and the ten passages of the association’s own documents that match it, to a model running on Amazon Bedrock inside Hoam’s own AWS account. Your thread is kept against your account, and an opening question and its answer are cached for the association under a hash of the question, with no account on the row. Your network address is counted against a daily cap.

Documents

A document proposed with the form goes from your browser straight to a private bucket. Your filename and your note go to you and the stewards and nobody else: a filename routinely names a home. One mailed in is matched to a member by the sending address, which is then not kept, and neither is the subject line; a photograph’s metadata is stripped before storage, whichever way it arrives.

A confirmed document is read by Amazon Textract inside Hoam’s own AWS account, and — if it is a budget, an audit, a reserve study, or a governing document, which includes a recorded declaration and a set of Architectural Standards — its pages then go to a model that pulls out its figures; the published record carries the kind, the date and the byline.

The directory

If your city is not covered you can send the city, the state and your association’s name; no email address is collected.

Counting

Hoam counts how much its pages are used, from its own server logs and from nothing running in your browser. A signed-in request adds one line saying which part of the site was called, with no account on it. A second line counts how many verified members were active in a week, under a code made from your account and from the week itself — so the same account is a different code the following week, and the two cannot be joined.

What is never done

• No advertising, no tracking pixels, no third-party scripts, and nothing that reports back from your browser. What Hoam counts, it counts from its own server logs.
• Nothing sold, rented or shared for anybody else’s purposes.
• Nothing to the Association, the Board or the management company.
• What a home owes, or has been cited for, is neither collected nor shown to a neighbour.
• No record against your account of what you read, and none at all of what you searched.

Who can see what

Other verified households see your byline, what you post, when you posted it, and your name on a sign-up sheet if you put it there — not your account, your email address, your lot, or which home anything came from.

Stewards, the neighbours who keep the records straight, see what has been proposed, filenames and notes included. Nobody else sees any of it.

Who else is involved

Google — sign-in, if you choose it, the two typefaces its font service serves to the public pages, and the mailbox our support address is served from.

Amazon Web Services — where Hoam runs, in the United States: the pages, the database, the mail, the reading of documents, and the model, which does not keep questions or train on them.

How long things are kept

• Your account and your verified home: until you ask for them to be removed.
• Your session: thirty days; the cookies that open your association’s files, seven.
• A mailed sign-in link: thirty minutes, one use.
• An Ask thread: seven days. A cached answer: thirty.
• Logs: thirty days for the services; three days for the web access log — the address that asked, the link it asked for and anything the link carried after the question mark, the site it came from, and the browser. Then it is reduced to counts: the address becomes a one-way code that changes every day, everything after the question mark is thrown away, the site it came from is reduced to a website’s name, and on members’ pages the association’s name is removed. What is left says which section was opened, and never which association, which record, or who. Those counts are kept four hundred days. The daily count against your network address: three days.
• A request to cover a city: four hundred days.
• What you posted has no expiry; removing it hides it from everyone, and the row is kept, marked removed.

Your choices

Stop the email. The only unsolicited mail is a deadline notice, at most two per deadline; the unsubscribe link in each works without signing in.

Remove a posting yourself. Every posting and every reply carries a Remove control for whoever wrote it. Removing one takes it out of everyone’s reach, including your own; what stays is marked removed, so the replies under it and anything reported about it still mean something to whoever looks.

Have your account removed. Write to support@go-hoam.com and ask. There is no setting for it today; your request is all we need. It ends every home you have verified and takes your sign-in with it, and the postings and replies you wrote are removed the same way the control removes one. Four things stay, and it is worth knowing which before you ask. Letters already delivered stay with the neighbour who received them, under the name you wrote them under, because a conversation somebody else was part of is theirs as well as yours. Anything you reported stays: it may be one of the reports holding a posting, and it goes on its own a few months after you filed it. If you said yes to a neighbour’s sign-up and somebody else at your address is verified too, that answer stays, because one home takes one place and the place is theirs as much as yours; they can change it from their own screen. And where you have looked after an association’s records, the line saying what was done stays under the name it was done under, because that is the association’s record of its own documents — as is any document you sent in that has been published.

Change the display name your neighbours see. Write to the same address and ask. There is no setting for that either. Changing it changes the name on what you write next, and never the name on what you have already written: a posting, a reply, a sign-up or a letter keeps the name it was written under, so a neighbour reading one still knows who they were talking to.

Age

Hoam is for adults. You must be 18 or older to hold an account.

Changes to this policy

The date at the top is when this version took effect.

Revised 13 September 2026: names the company that operates Hoam.

Revised 12 September 2026: the age section states the age and nothing else.

Revised 9 September 2026: what having an account removed keeps, how the name neighbours see is changed, and what is counted from the server logs.

Revised 4 September 2026: shortened, and corrected to match how Hoam works.

Contact