Havara: Deleting Your Account
Effective August 28, 2026
You can permanently delete your Havara account yourself, inside the app or on the web console, in about a minute. Deletion is immediate and cannot be undone. Your profile and personal records are erased; things you posted into shared community spaces (chat messages, notices, comments) stay visible to your neighbors but become anonymous. The author simply shows as "Member." Download a copy of your data first if you want one.
This page is the account-deletion instructions resource required by Apple App Review Guideline 5.1.1(v) and Google Play's account-deletion policy (both platforms require a full, in-app deletion path for any app that supports account creation; Google Play additionally requires a web-accessible resource, which is this page). Requirements per the platform-rules brief, verified 2026-07-12 against developer.apple.com/support/offering-account-deletion-in-your-app/ and support.google.com/googleplay/android-developer/answer/13327111.
1. Before you delete: download your data
The export button lives right next to the delete button. Use it first if you want a copy.
Deletion is permanent and there is no recovery window, so take your copy first:
- In the app: Profile ▸ Privacy & data ▸ Download my data.
- The export is a single JSON bundle (format
havara.personal-data-export.v1) assembled server-side from only your own rows, scoped to your authenticated account and nothing else. It includes: your profile, community memberships, event RSVPs, announcement acknowledgements and comments, chat messages, emergency-alert responses, join requests, amenity bookings, AI Ask threads and answers, consent records, violation cases where you are the named subject (plus your case comments and any notices delivered to you), ARC requests and their events, general requests and their comment threads, your poll votes, and your unit record(s).
2. How to delete your account
Two taps to find it, two confirmations to run it.
In the iOS or Android app (either path reaches the same flow; confirmAndDeleteAccount):
- Open Profile.
- Tap Privacy & data ▸ Delete my account, or scroll to the delete-account section at the bottom of Profile.
- Confirm twice. The confirmations state plainly that deletion is permanent, removes you from every community, and cannot be undone.
- On success you see an explicit "Account deleted" confirmation, are signed out, and returned to the sign-up screen. If deletion fails, you see an error and your account is unchanged. The app never pretends a failed deletion succeeded (
deleteAccountthrows on RPC error; surfaces it).
On the web console: Account ▸ Delete my account, with the same two-step confirmation.
If you wrote moderation case notes as a board member or moderator, those notes stay as part of the community's governance record, with your authorship cleared, the same way the rest of your content is anonymized. (An earlier version of this page said in-app deletion failed outright for case-note authors. That was true and is fixed: verified against production, the deletion routine clears the author reference rather than refusing.)
If you can no longer sign in: email [email protected] from the address on your account and ask us to delete it. We verify the request against the account email and fulfil it manually; we aim to complete manual deletions within 30 days, inside the 45-day response windows common to US state privacy laws (per the us-state-privacy regulatory brief, 2026-07-12).
3. What is deleted, what is anonymized, what remains
Almost everything keyed to you personally is erased, and Section 5 names the one exception honestly; content you contributed to shared spaces is kept for your neighbors but stripped of your identity; board records about your unit (not about your account) stay with the community.
Deletion runs server-side as a single self-only operation: the deletion runs strictly against your own authenticated account and takes no target as input, so no one can target anyone else.
Deleted immediately
| What |
|---|
| Authentication record (email, sign-in credentials) |
| Profile (name, email, phone, avatar initials, bio, timezone) |
| Avatar image file(s) |
| Push token and notification preferences |
| Community + org memberships, join requests |
| Announcement acknowledgements, event RSVPs, chat reactions, channel participation, sub-group memberships, amenity bookings, chat read receipts |
| Poll votes you cast |
| Violation cases in which you are the named subject, and notices delivered to you |
| ARC (architectural review) requests you submitted |
| Resident requests/cases you opened |
| Emergency-alert responses ("I'm safe" acknowledgements) |
| Consent records (terms/privacy acceptance ledger) |
Each row above is enforced in the database or the app itself, not by policy alone. The exact enforcement point for every row is recorded in Havara's source repository and is available to platform reviewers and to counsel on request at [email protected].
Retained but anonymized (author becomes "Member")
Content you contributed to shared community spaces stays in place so conversations and records remain coherent for the members who stay, but the link to you is cleared:
| What |
|---|
| Chat and direct-message bodies you wrote, including attachments you shared into them |
| Announcements and announcement comments you authored |
| Sub-groups you created |
| AI Ask answers linked to you as the asker |
| Invitations you sent |
| Audit-log entries for actions you took |
| Safety alerts you raised |
| Comments you left on other residents' requests; polls you authored; roles as case opener/decider |
| Quote requests you sent to a vendor, and the vendor's answer. The request stays with your community's vendor records, because it is the board's record of a job and the vendor may already have answered it. The link to you is cleared and it shows as "Member". The phone number and email you put on the request are erased with it, so your own contact does not outlive the reference to you. A request already passed to a vendor cannot be recalled from that vendor's own inbox |
Each row above is enforced in the database or the app itself, not by policy alone. The exact enforcement point for every row is recorded in Havara's source repository and is available to platform reviewers and to counsel on request at [email protected].
Remains with the community (records about the unit, not about your account)
- Per-unit dues standing, budget and reserve data, and unit records are board-entered community records keyed to the unit/community, not to your account, and are unaffected by account deletion.
- Governing documents and community media uploaded by the board remain community property.
4. Timing, grace windows, and backups
It happens now, and there is no undo.
- Immediate, no grace window. There is deliberately no "deactivate first" or cooling-off period. Apple's guidance is explicit that temporary deactivation is insufficient, and Havara performs a true delete in the live database the moment you confirm.
- This is a one-way door. The two confirmation dialogs say so before you commit. If you want your data, export it first (Section 1).
- Backups. Copies of the live database in our infrastructure provider's routine encrypted backups expire on that provider's backup-rotation schedule rather than instantly.
- Already-delivered notifications and emails (e.g., push previews on neighbors' devices, invitation emails you sent) cannot be recalled.
5. What deletion does not do
Honest limits.
- It does not remove content other members posted about shared community matters (report concerns to your community's administrators or via in-app content reporting).
- It does not dissolve community records about your unit (Section 3). Those belong to the HOA's own governance record.
- It does not reach crash reports already sent to Sentry. When the app hits an error it sends the error, the stack trace and your account's user id to Sentry so we can fix it (see the Privacy Policy, Section 7). Those events sit in Sentry's systems, not ours, and the deletion above is a database operation that cannot reach them; they expire on Sentry's own schedule, within 30 days on our current plan and 90 days at the outside, backups included. If you want them erased sooner, write to [email protected] and we will do it by hand. Nothing in a crash report identifies you beyond that user id: no message content, no email, no phone number, no push token.
- It does not prevent you from creating a new account later, but Havara communities are invitation-gated, so rejoining a community requires a fresh invite or approved join request.
6. Platform-compliance mapping (for reviewers and counsel)
| Requirement | Where Havara meets it |
|---|---|
| Apple 5.1.1(v): in-app, easy-to-find, full deletion | Profile ▸ Privacy & data ▸ Delete my account; true delete of account record + associated personal data (Sections 2 to 3). Fully self-service, including for board members and moderators who have written case notes: those notes stay as governance history with the authorship cleared |
| Apple: no forced phone/email path | Fully self-service in-app; email is a fallback for locked-out users only |
| Apple: Sign in with Apple token revocation | Not applicable: Apple/Google sign-in is not live |
| Play: in-app deletion path | Same in-app flow (Android build is the same Expo app) |
| Play: web link resource usable without the app | This page, published at havara.app/account-deletion, plus the web console Account page |
| Play: retention exceptions disclosed | Anonymized community content and the ≥12-month audit log, disclosed in Section 3 |