Privacy Policy
Last updated November 10, 2026
Hoame is an individually operated community software project. “We” and “us” in this policy refer to its operator. This policy explains how Hoame handles information when you visit the site, use a community portal, or install the app. Your Association decides which community features to enable and what records to maintain. Its own privacy practices and legal responsibilities also apply to information it collects or shares through Hoame.
1. Information we handle
- Accounts and security: email address, display name, password hash, account status, preferences, sessions, verification and password-reset records. Email verification is the default second step for password login. If you set up an authenticator, we store its enrollment secret and recovery-code information.
- Community records: memberships, roles, directory preferences, invitations, units, ownership and occupancy details, and records provided by you, your Association, household members, or authorized managers.
- Financial activity: charges, assessments, ledger entries, payment amounts and statuses, transaction identifiers, refunds, budgets, expenses, reserves, and vendor records, depending on enabled features. Stripe-hosted checkout collects payment credentials; Hoame does not store full payment-card numbers or bank-account credentials.
- Content and participation: announcements, agendas, minutes, documents, discussion topics and replies, mentions, images, attachments and filenames, votes and eligibility records, reservations, maintenance and architectural requests, violations, and contact messages. Uploaded files may include metadata or personal information you place in them.
- Notifications and delivery: notification recipients, message excerpts, read status, email preferences, queued email content, delivery status, attempts, and errors.
- Technical data: IP addresses and request/browser information used by our infrastructure and security services, operational logs, abuse-prevention counters, and site-usage statistics.
2. How we use information
We use information to operate accounts and community features, apply access controls, maintain records, facilitate configured payments, deliver messages, respond to support requests, prevent abuse, diagnose errors, and understand and improve use of the Service. We do not sell personal information or use it for cross-site targeted advertising.
3. Who can see information
- Association managers: authorized administrators, board members, committee members, and management representatives can access records according to their roles. Assigned vendors can access the work made available to them.
- Community members: shared announcements, meeting records, discussions and attachments are available to authorized community users. Opting into the directory shares your display name, email address, role, and board title with members. Directory opt-out does not hide your name on content you author or from the community’s mention picker.
- Public and link-based access: community names, configured logos and icons, and public landing-page content are public. Some features, such as resale certificates and invitation links, grant access through a link; recipients should protect those links and any downloaded copies.
- Platform operations: authorized platform administrators can access information needed to administer, support, and secure the Service.
- Legal and safety: information may be disclosed where required by law or to protect rights, safety, or the integrity of the Service.
4. Service providers and external sites
- Cloudflare: hosts the application, database, files, caches, and security infrastructure. Turnstile processes browser/device and network signals to distinguish legitimate visitors from automated abuse. See Cloudflare’s Privacy Policy and its Turnstile Privacy Addendum.
- Resend: receives email recipients and message content to deliver account and community emails. See Resend’s Privacy Policy.
- Stripe: when online payments are configured, receives checkout information such as your email, amount, unit label, and Association/unit references, and handles payment details and connected-account onboarding. Its own processing responsibilities and Privacy Policy also apply.
- Plausible Analytics: provides aggregate site-usage measurement, including page addresses, referring sources, browser/device information, and approximate location derived from request information. Plausible describes its analytics as cookieless and says it does not retain raw IP addresses. See its Data Policy.
Community links, social links, and third-party payment sites lead to services with their own privacy practices. Our providers may process information in the United States and other countries where they operate; Hoame does not promise that all information stays in a single country.
5. Cookies, device storage, and the installed app
We use session cookies for sign-in and a theme cookie for appearance. Security services may use cookies or other browser signals for abuse protection. Browser-alert preferences and recently displayed notification IDs are stored locally on your device. The installed app’s service worker caches application assets such as scripts, styles, and bundled icons; it does not deliberately cache authenticated pages or API responses for offline use. Browsers may separately cache public logos and installation metadata. We do not use third-party advertising cookies.
6. Communications and notification choices
Account-security messages, including login codes and password-reset messages, are part of operating your account. You can control optional community email categories in Account; some are enabled by default. Mention emails require explicit opt-in. In-app mention notifications are available when Discussions is enabled. Optional browser/device alerts require your permission and work while Hoame is open, rather than as background push when it is closed. Alerts and emails may show the sender, topic, and message excerpt, including on a lock screen depending on device settings. You can turn off device alerts in Hoame or your browser/OS settings.
7. Retention, leaving, and deletion
Retention depends on the record’s purpose and the Association’s recordkeeping needs. Leaving an Association removes that membership; it does not delete your account or the Association’s historical records. Account deletion removes your account, sessions, memberships, and other linked account records, but does not erase all content or records you contributed to an Association. For example, financial records, discussion messages and attachments, meeting records, and delivery records may remain. An author reference may be removed while names or other personal information in the content itself remain.
Expired security records are cleaned up periodically. Other retained records do not all have an automatic deletion deadline. Backups, provider records, and copies previously emailed or downloaded can have separate retention periods. Contact your Association about its records and contact us about account or platform data. Administrators must transfer or close their associations before self-service account deletion; platform administrators must contact support. Uninstalling the app does not delete your account or server-side records.
8. Your choices and requests
You can update your profile, directory participation, and email preferences in Account, manage device alerts, leave a community, or use the account-deletion controls where available. Contact us at support@hoame.io for requests to access, correct, obtain a copy of, or delete personal information. Depending on where you live and the laws that apply, you may have additional rights to object to or restrict processing, appeal a response, or contact a privacy regulator. We may need to verify your identity and coordinate with your Association, and applicable recordkeeping or third-party rights may limit a request.
9. Security and age
We use password hashing, required second-step verification for password login, role-based access controls, and sign-in abuse protection. No system is perfectly secure. Keep your email account, password, authenticator, and recovery codes secure, and avoid uploading information unnecessary for your community activity. The Service is intended for adults aged 18 or older and is not directed to children. Contact us if you believe a child has supplied personal information through an account.
10. Changes and contact
We will update the date above when this policy changes. Where applicable law requires additional notice or consent, posting an updated policy does not replace those requirements. Questions about this policy or your privacy can be sent to support@hoame.io.
See also our Terms of Service.