HOAAdminly

Privacy Policy

How ONYXora LLC handles your data, documents, and communication when you use HOAAdminly.

Overview and operator

This Draft Privacy Notice describes how ONYXora LLC (we, us, or our), based in Omaha, Nebraska, USA, collects, uses, and protects information when you visit the public site, submit an inquiry, or use an HOAAdminly workspace. Draft privacy notice for review; not yet effective.

This policy was last updated on 2026-09-11. It is a product description for review, not legal advice or a representation that the service satisfies any particular legal requirement.

Information we collect

For a live workspace, we process the information needed to provide access and association features: account and authentication information handled through Clerk, association and lot details, member and homeowner contact records, financial ledgers, payment and autopay status, uploaded documents, invitations, and association activity. The information an association enters can include personal information about homeowners and other members.

The public contact form asks for your name, email address, role, inquiry category, optional community name, optional phone number, and message. The hidden website field is a bot-control field. Contact submissions are forwarded to our configured support inbox through SendGrid; the app does not promise a separate public support email address.

When you interact with the service, we may also receive technical data such as IP addresses, browser types, request metadata, and standard web request logs for security, abuse prevention, and debugging.

How we use your information

We use the collected data to provide, maintain, secure, and improve the HOAAdminly service. This includes authenticating users, displaying association records to authorized members, supporting eligible online ACH transactions through Stripe, sending configured association or support communications, and storing documents in private storage systems.

We do not sell your personal data to third parties. We do not use your community data for external marketing.

  • To authenticate and secure your account access.
  • To facilitate community operations like dues tracking and document sharing.
  • To debug technical issues and ensure platform stability.

Third-party providers

HOAAdminly relies on third-party providers. Clerk handles authentication; PostgreSQL stores application records; Replit-hosted storage stores private document objects; Stripe handles eligible online ACH payment and recurring ACH authorization flows; and SendGrid is used for configured contact, invitation, or association communications. These providers process information under their own terms and privacy policies.

The app does not expose Stripe bank-account details in the workspace. Availability of payments, invitations, and communications depends on the live configuration and provider response; the UI should be treated as the source of current feature status.

Cookies and tracking

The live workspace may use authentication cookies and browser storage needed for sign-in, session state, security, and the demo workspace. Demo records and the selected demo association are stored locally under the HOAAdminly demo keys until the visitor clears or resets them.

Optional analytics is off until you choose Allow; this uses basic consent gating, so no denied-consent analytics pings are sent. On allowed public routes, the hosted Replit-injected tracker (Umami) and the Google Analytics 4 tag are enabled only after consent. Public page views, sanitized public paths (without query strings or fragments), same-site public referrers, and the app’s limited public product or Web Vitals events may be sent to those configured analytics hosts. Analytics is suppressed on private routes and custom events are designed not to include names, email addresses, message text, association records, or sensitive-route activity.

After consent, Google Analytics may set `_ga` and `_ga_<measurement-id>` cookies. The footer preferences let you deny, revoke, or delete the local analytics keys controlled by this app (`hoaadminly-analytics-consent`, `umami.disabled`, and matching Umami keys); revoke and local deletion also request removal of the Google Analytics cookies on this site. Local deletion cannot erase information already sent to either analytics provider, and cookie removal cannot control cookies set on another domain. We do not state provider retention periods here; consult the providers’ current policies for retention and deletion practices. We do not use analytics for targeted advertising.

Security and retention

We implement standard security measures, including HTTPS encryption in transit and database safeguards. However, no internet transmission is entirely secure, and we cannot guarantee absolute data security.

Live association records are retained according to the association account and operational configuration. Demo records remain in the browser’s local storage until reset or cleared. Provider systems may retain copies under their own policies. We have not published a fixed deletion schedule in this draft; ask through the contact form about a specific data request rather than assuming that local deletion removes server or provider records.

Contact for privacy questions

If you have questions about this draft notice or how we handle your data, use the HOAAdminly contact form and select the Data and privacy category. The form sends your inquiry to the HOAAdminly support workflow operated by ONYXora LLC; it is not an automated data-deletion endpoint.