Contact and Privacy Requests
- Legal entity
- Human Advisor AI LLC
- Effective date
- Privacy requests
- privacy@humanadvisor.ai
- Compliance, incidents and accessibility
- compliance@humanadvisor.ai
Scope. This page explains how Human Advisor AI LLC collects, uses, discloses, and retains personal information through its website contact, advisor-connection, accessibility, compliance, incident-reporting, and privacy-request channels and related website interactions.
1. General contact
Visitors may use the corporate contact path for general questions about Human Advisor AI, its services, educational materials, or a possible business conversation.
A general enquiry does not create a client, advisory, fiduciary, agency, employment, partnership, franchise, or vendor relationship. Advisory services, when offered, require a separate agreement with the applicable independently owned and operated Human Advisor AI franchise.
2. Contact categories
| Need | Approved contact path | Important limitation |
|---|---|---|
| General corporate enquiry | HAA-owned corporate enquiry form, with support@humanadvisor.ai as the approved fallback when the form is unavailable | Submission must fail closed if delivery is unavailable or unconfirmed. The fallback address is an ordinary mailbox: it does not create a record, and no delivery, receipt or response time is promised. |
| Request a connection with a Human Advisor | Advisor-specific enquiry form or Ava connection flow after the destination is disclosed | The server determines advisor, destination, ownership, tenant, and franchise scope from trusted configuration |
| Privacy request | privacy@humanadvisor.ai | Browser deletion alone does not delete server-side consent, lead, delivery, security, or privacy-request records |
| Compliance concern or incident report | compliance@humanadvisor.ai | Do not include credentials, payment data, government identifiers, health information, or unnecessary confidential material |
| Accessibility feedback | Accessibility contact identified in the Accessibility Statement. | See the Accessibility Statement for available contact methods and accommodations. |
| Legal notice | Method specified in the applicable agreement or otherwise authorized by law | Human Advisor AI does not designate an email address as formal service of legal process |
3. Information we collect
We collect only the information a visitor chooses to provide and that is reasonably needed for the requested contact. Depending on the selected purpose, that may include:
- name;
- business email address;
- business phone number, if the visitor chooses to provide it;
- company or organization;
- job title or role;
- location or service area where relevant;
- the subject and details of the enquiry;
- preferred Human Advisor or advisor page context, when applicable;
- information needed to locate or administer a privacy request;
- consent and destination confirmation required for a connection request.
The fields displayed in the applicable form determine the information requested. This list does not require visitors to provide every category of information.
3.1 How we use and disclose information
We may collect technical information such as IP address, browser or device information, timestamps, and security or delivery logs when these channels are used. We use personal information to respond to enquiries, route advisor requests to the disclosed destination, verify and administer privacy requests, maintain security, prevent misuse, keep required records, and comply with law. We may disclose information to the intended Human Advisor or independently owned franchise, service providers acting for us, and authorities or other parties where required by law or necessary to protect rights or security. Where applicable, we rely on consent, steps requested before entering a contract, legitimate interests, or legal obligations.
4. Information not to submit
Visitors should not submit passwords, security credentials, payment-card information, government identifiers, health information, sensitive personal information, confidential third-party information, or information the visitor is not authorized to disclose.
If additional sensitive information is genuinely required for a later service, Human Advisor AI or the applicable Human Advisor should provide a separately governed collection method rather than asking the visitor to place it in a public enquiry form or ordinary Ava chat.
5. Advisor connection requests
An advisor connection request must identify the intended destination before submission and obtain separate affirmative lead-delivery consent. The browser cannot select or override the advisor, owner, tenant, franchise, destination, or record scope.
When advisor routing is missing, retired, unavailable, or ambiguous, the request must fail closed and offer the approved corporate contact route. A calendar link or enquiry control must not imply availability, delivery, or a response time that the relevant system has not confirmed.
Only the structured contact and business information submitted through the connection flow is delivered. No Ava conversation transcript or conversation summary is delivered with the lead.
6. Privacy requests
Privacy requests may be sent to privacy@humanadvisor.ai. A visitor may ask about applicable access, correction, deletion, restriction, objection, portability, consent withdrawal, or other privacy rights. The rights available and the verification required depend on the applicable law and the information involved.
Human Advisor AI may request information reasonably necessary to verify the requester and locate the relevant records. Verification information must be limited to what is reasonably needed for that purpose.
If information has already been delivered to a disclosed destination, the public-assistant process must reconcile the request with that destination. Human Advisor AI must not claim that a destination completed deletion until confirmation exists.
7. Retention and deletion context
We retain the following records for the periods shown, unless a longer or shorter period is required by applicable law:
| Record | Governing requirement |
|---|---|
| Unsubmitted form values | Browser memory only; unsubmitted form values are not stored durably server-side. |
| Submitted website lead | 2 years in the public-assistant intake layer, subject to stronger law and Portal or client-record policy |
| Consent evidence | 7 years |
| Delivery attempts and receipts | 2 years |
| Security and abuse logs | 395 days; no free-text form body |
| Public-assistant backups | Controlled rotation with a target maximum of 35 days |
| Portal CRM record | Portal or client-record schedule; privacy requests must reconcile both intake and destination |
8. Submission and delivery states
The public experience must distinguish clearly among validation error, unavailable, rate-limited, pending, accepted, delivered, and failed states. A success or thank-you page may appear only after the server confirms an accepted or delivered outcome under the approved contract.
A browser-generated state, URL parameter, local flag, or unconfirmed response cannot establish delivery. If the service is unavailable, the visitor must receive an honest message and an approved alternative path where one exists.
9. Confirmation email and follow-up
If a confirmation email is available, it is sent only after the system accepts the submission. A confirmation email does not promise a response time.
Marketing enrollment remains separate from an enquiry or connection request. Submitting a required enquiry-delivery consent must not be treated as consent to receive marketing.
10. Security and misuse prevention
We use reasonable technical and organizational safeguards, including field validation, rate limits, controlled routing, access restrictions, and delivery logging, to protect submitted information against unauthorized access, use, alteration, or disclosure.
11. Accessibility
We aim to make our contact forms, instructions, consent controls, validation messages, status messages, and confirmation paths accessible. Accessibility feedback may be submitted through the contact method identified in the Accessibility Statement.
12. Changes to this Contact and Privacy Requests page
We may update this page to reflect changes in our contact channels, practices, technology, or legal obligations. We will post the revised policy on this website and update the effective date above.
Contact form
Tell us about your business and what you are looking to achieve.