Havara: Eligibility and Children Policy

Effective October 6, 2026

Havara accounts are for adults, 18 and older, full stop. We ask you to confirm your age when you sign up, but we do not run identity or age verification. This page says exactly what we check and what we honestly don't. Children may appear in community life (a household record, a photo in chat), but they may not hold accounts, and here is what we do when that line is crossed.

This page is the single, detailed statement of who may use Havara and how the age rule is enforced during our pilot. Terms of Service Section 3 refers to this policy, and Privacy Policy Section 15 summarizes the same rule.

1. The rule: adults only (18+)

You must be at least 18 to create or use a Havara account, resident, homeowner, board member, admin, or vendor alike.

Havara is community software for homeowners' associations and residents' communities. Every account holder, in every role (resident, homeowner, board, admin, vendor, platform-level owner, and declarant), must be at least 18 years old.

This is a deliberate decision: adults only, no knowing collection from anyone under 18, deletion on discovery. A community that wants under-18 participation is a separate product and legal question we have not taken on. If your HOA is asking for it, contact us and we will say no.

2. Where you agree to it: every acceptance surface, read against the app on September 28, 2026

The mobile app and the web console both ask you to confirm "18 or older" in so many words; every acceptance is recorded with the document version you accepted.

Every acceptance is written to an append-only consent ledger with the exact document version accepted. When the legal version changes, both the app and the console re-prompt before you can continue.

(Honest note: until 2026-09-28 the web surfaces relied on Terms acceptance rather than an express "I am 18 or older" line; the console now asks in the same words as the app. The confirmation is still recorded as acceptance of the Terms and Privacy Policy versions, not as a separate age record, and nothing on the server refuses an account that skipped it. An account can be created through the sign-in API without either screen; the app and the console then block it until it accepts, but the server does not require acceptance, so an account used only through the API directly (for example to create a community or redeem an invite) is not stopped.)

3. How we enforce the rule, and how we honestly don't

Self-attestation plus an invitation-gated community structure, not age verification. We don't collect birthdates and we don't check IDs.

What we DO:

• Require an affirmative 18+ / Terms acceptance before any use of the app or the console (Section 2), recorded per user per document version. This is enforced by the two clients, not by the server (Section 2's honest note).
• Gate community access behind the community itself: creating a bare account gives access to no existing community. (It can set up a new, empty community of its own from the console's "Create a new community" door, as a board member would.) Joining an existing community requires an invite code from the board or, for a tenant, from the unit's homeowner (a code joins instantly or, at the board's option, only after board approval) or a board-approved join request. In practice, a community's board knows who its residents are (a second, human layer on top of the attestation).
• Delete accounts we learn belong to someone under 18 (Section 6).

What we DON'T do (and don't claim to):

• No date-of-birth collection. We do not ask for or store birthdates anywhere (on 2026-07-12 we searched the app, the console and the database schema for any birthdate field and found none).
• No age verification. We do not verify age against documents, databases, or estimation technology, and we do not use any third-party age-assurance service.
• No identity verification. We do not check government ID at sign-up.
• No age-screening of invitees. Boards choose whom they invite; Havara does not independently screen invite recipients for age.

The practical effect: our age rule is enforced by attestation, contract, and the board-controlled invitation structure, not by verification technology. We state this plainly rather than implying checks we do not run.

Havara's decision. Havara relies on the age confirmation at sign-up and on invitation-gated communities (an invite code or a board-approved join request), and does not verify age. The app and the console do not read the app stores' age signals. Havara sells no personal data and shares none for advertising. The only advertising it sells is labeled vendor placement (Terms of Service, Section 13), and accounts are for adults only (Section 1).

4. Children under 13 (COPPA posture)

The Service is not directed to children, and we do not knowingly collect any child's personal information (from children of any age, not just under-13s).

Havara is not directed to children under 13, is not marketed to children, and contains no child-directed content or features. We do not knowingly collect personal information from any child under 13, or from any minor under 18. If we learn that we have collected personal information from a child through an account, we will delete the account and that information (Section 6).

A board-entered record that mentions a child belongs to the community: ask your board to correct or remove it, or write to privacy@havara.app and we will help.

5. Minors in community life: what may still touch the platform

Households include kids. Kids may not hold accounts, but an adult's photo, a board's household record, or an event listing may still reference them. Here's how that data is handled and how to get it removed.

Three ways information about a minor can lawfully appear on Havara, none of which involves a child using the Service:

1. Board-entered household records. Boards and unit owners may keep unit and household records (units, household roles such as owner / co-owner / tenant / occupant) as part of ordinary community administration. A record referencing a household member who is a minor is board-entered administrative data controlled by your HOA. It is not a child's account, and the occupant roles that carry accounts are themselves subject to the 18+ rule. Requests to correct or remove such records go to your board first, per the controller/processor split in the Privacy Policy.
2. Content posted by adults. Photos and videos in chat, event posts, or announcements may incidentally include children (a community barbecue, a pool photo). The adult who posts is responsible for having the right to post it (Terms, Sections 6 and 8). Any member can report content, boards can hide it, and you can ask us to remove content depicting your child at privacy@havara.app.
3. Event RSVPs and bookings. An adult may RSVP or book an amenity for their household, including children attending. The account, the RSVP, and the booking belong to the adult.

What we never do with any of this: no advertising, no data sales, no profiling, and no AI training on member content. These are the same commitments that apply to all community content (Terms, Section 8; Privacy Policy).

6. If we learn someone under 18 has an account

If you believe an account holder is under 18, email privacy@havara.app with the community and account details. If we confirm it (or the account holder cannot attest to being 18+), we will:

1. Delete the account using the same deletion machinery members use themselves: personal records erased; content authored into shared spaces anonymized to "Member" rather than left attributed (full semantics in Deleting Your Account);
2. Notify the community's board that the membership was removed; and
3. Delete any associated invite so the account cannot simply be recreated through the same invitation.

We aim to complete this within 30 days of confirmation. (Honest disclosure: this is a manual, staff-performed process today; there is no automated underage-account detection, consistent with Section 3.)

7. What boards agree to

Boards are the gatekeepers. Don't invite minors, and keep children's details out of governance records unless genuinely necessary.

Boards and administrators, as the people who control invitations, join approvals, and governance records, agree to:

• Issue invitations and approve join requests only for adults (18+);
• Not enter children's personal details into violation cases, requests, chat, or other free-text surfaces (see the prohibited-sensitive-data list, Terms Section 6) beyond what household administration genuinely requires;
• Route any resident request about a child's data in board-controlled records through the HOA's own processes, with Havara assisting as processor per the DPA.

8. Contact

Questions about eligibility, or a report about an underage account or a child's data: privacy@havara.app.

Havara LLC, a Georgia limited liability company 525 Tribble Gap Rd, P.O. Box 724, Cumming, GA 30040