Privacy Policy

This policy explains what information Homeowner Alliance may collect, how it may be used, and how Phase 1 preview behavior differs from future backend processing.

Last updated: May 12, 2025

1. Information users provide

Homeowner Alliance may collect information you choose to provide while using public pages, address lookup, account flows, document workflows, assistant previews, and support forms.

  • Name, email address, property role, association or resort details, and contact preferences
  • Facts you type into forms, messages, questions, uploads, notes, or support requests
  • Information needed to provide educational support, member access, and account communication

2. Property addresses

Property addresses may be used to normalize owner searches, identify likely condo, HOA, co-op, townhome, or timeshare communities, and prepare document-readiness checklists.

  • Address, unit, parcel, community, resort, interval, or association details where provided
  • Search terms and selected suggestions used to route the address-check experience
  • Mock or preview results that may differ from future production source discovery

3. Address autocomplete and Mapbox-related data

Where configured, address autocomplete may use Mapbox to return location suggestions. Homeowner Alliance should not expose private provider configuration values in source code or public pages.

  • Typed address queries may be sent to the autocomplete provider to retrieve suggestions
  • If Mapbox is not configured, the public site may use demo-mode behavior
  • Provider processing is governed by the provider's terms and privacy practices

4. Uploaded documents

Uploaded documents are owner-provided content and may include declarations, bylaws, rules, amendments, budgets, notices, minutes, correspondence, insurance records, inspection materials, and timeshare documents.

  • Do not upload unnecessary sensitive information, unrelated personal data, or documents you are not authorized to provide
  • Some Phase 1 upload flows may be mocked or preview-only
  • Future backend services may ingest, OCR, index, classify, summarize, and retrieve document content

5. Account information

Future authentication may use Clerk for sign-in, account creation, and session management. Account features may collect identifiers needed to maintain secure member access.

  • Name, email address, authentication identifiers, session state, and account settings
  • Clerk-ready behavior may remain mocked during Phase 1
  • Account information may be used to provide access, security, support, and service notices

6. Membership and billing information

Homeowner Alliance describes a $10/year membership. Stripe may be used for future billing, but Phase 1 payment behavior may be preview-only or mocked.

  • Billing provider pages may collect payment details when future paid checkout is configured
  • Homeowner Alliance should avoid storing raw card details directly
  • Membership status, renewal state, invoices, and support records may be retained as needed

7. Questions asked to the assistant

Questions submitted to assistant-like experiences may be processed to provide document-based educational support, show sources, and help prepare better questions.

  • Prompts, context, selected property, document references, and answer feedback may be used
  • Future FastAPI/Agno backend services may support AI-assisted workflows
  • Assistant outputs are educational support only and not legal advice

8. Generated communications

Generated letters, emails, and templates may be saved or processed to help owners communicate clearly with boards, managers, resorts, or professionals.

  • Drafts should be reviewed, edited, and verified before sending
  • Future services may use Resend for email where configured
  • Generated communications should not include facts the user has not verified

9. Email preferences

Email preferences may be used to manage transactional notices, product updates, membership messages, and unsubscribe choices.

  • Resend may be used for future transactional or preference-managed email
  • Users should be able to opt out of non-essential marketing emails
  • Some account or service notices may still be sent as needed to provide the service

10. Device, log, and analytics information

The service may collect device, browser, log, and analytics information to operate, secure, improve, and monitor the website and future backend services.

  • IP address, browser type, device type, pages viewed, timestamps, referral URLs, and error logs
  • Cloudflare may process hosting, security, performance, and infrastructure information
  • Analytics should be configured carefully and should not expose private provider values

11. How information may be used

Information may be used as needed to provide the service, improve product quality, maintain safety, communicate with users, and prepare future document and assistant workflows.

  • Operate address lookup, account access, document organization, assistant previews, and communications
  • Provide support, diagnose errors, maintain security, and prevent misuse
  • Develop future backend document ingestion, indexing, monitoring, and AI-assisted workflows

12. How documents may be processed

Future backend services may add document ingestion, storage, OCR, classification, indexing, source retrieval, monitoring, and assistant workflows.

  • Document processing may be performed by a future FastAPI/Agno backend and related infrastructure
  • Processing may create derived text, metadata, summaries, source links, and readiness labels
  • Mock backend behavior may not store or process documents the same way as future production services

13. Third-party providers

Homeowner Alliance may use third-party providers to operate the service. Provider use may change as the product moves from Phase 1 preview behavior to production services.

  • Clerk for authentication; Mapbox for address autocomplete; Resend for email
  • Stripe for future billing; Cloudflare for hosting, security, and infrastructure
  • Future FastAPI/Agno backend services for document and assistant workflows

14. Data retention

Information may be retained for as long as needed to provide the service, comply with obligations, maintain security, resolve disputes, and improve reliable operations.

  • Retention periods may vary by account, billing, document, support, security, and log category
  • Deletion requests may require verification and may be subject to legal, security, or operational limits
  • Phase 1 mock data may not reflect final production retention behavior

15. User choices

Users may have choices about account information, email preferences, uploaded documents, and whether to use optional workflows.

  • Review information before submitting it and avoid unnecessary sensitive information
  • Use unsubscribe or preference controls where available
  • Contact Homeowner Alliance to ask about account, document, or privacy choices

16. Security

Homeowner Alliance aims to use reasonable administrative, technical, and organizational safeguards appropriate for the service stage and information involved.

  • No website, provider, or backend service can guarantee absolute security
  • Future production systems should use access controls and appropriate monitoring
  • Users should protect account credentials and upload only documents they intend to use with the service

17. Children's privacy

The service is intended for adult homeowners and is not directed to children under 13. Homeowner Alliance does not knowingly seek information from children.

  • If child information is submitted unintentionally, contact Homeowner Alliance for review
  • Do not submit children's personal information unless it is necessary and appropriate for the service context

18. International users

Homeowner Alliance is designed for United States homeowner association, condo, co-op, townhome, and timeshare contexts. Users outside the United States may have information processed in the United States.

  • Privacy rights and provider practices may vary by location
  • International users should consider whether the service fits their jurisdiction and documents

19. Changes to this policy

Homeowner Alliance may update this policy as Phase 1 preview behavior changes, provider integrations are configured, and future backend services are added.

  • The Last updated line reflects the current draft date
  • Material changes may be communicated through the website, account notices, or email where appropriate

20. Contact placeholder

For privacy questions, use the contact placeholder until production support details are finalized.

  • Privacy contact placeholder: privacy@homeowneralliance.example
  • Do not send unnecessary sensitive documents by email unless specifically requested through a secure workflow

Educational support only. Homeowner Alliance is not a law firm and does not provide legal advice. Information provided is for educational purposes only and does not create an attorney-client relationship.

Legal Disclaimer

Review related owner resources

Read the service terms, legal boundary, or start with an address check.