Política de privacidad

Última actualización: October 1, 2026 · Versión 2.0

Este documento legal está disponible solo en inglés. La versión en inglés que aparece a continuación es la versión oficial. Si tiene preguntas, escríbanos.

Halo AI Ventures Corp (“Halo,” “we,” “us,” or “our”) runs the website haloaigroup.com and the Halo AI phone receptionist (the “Service”). This Privacy Policy explains what information we collect, why, who we share it with, how long we keep it, and the choices you have. It applies to people who visit our website, people who use the Service for a business (our “customers” and their team members), and people who call or text a business that uses Halo.

1. Who we are and our two roles

Halo AI Ventures Corp, 12287 Hillman Dr, Palm Beach Gardens, FL 33410. Privacy questions and requests: customerservice@haloaigroup.com.

We play two roles. For information about our customers, their team members and our website visitors, we decide how the information is used. For information about the people who call or text a customer’s business (“callers”), we act as that business’s service provider (processor): we handle caller information only to provide the Service to that business, under its instructions and our Customer Agreement. If you are a caller, the business you contacted is responsible for its own use of your information, and you can also contact it directly.

2. Information we collect

2.1 From customers and team members

  • Account information: name, email address, password (stored only as a one-way hash), business name, business address, phone numbers, industry, and team roles.
  • Business configuration: hours, services, prices, FAQs, the knowledge your receptionist uses, voice and greeting choices, call-handling and escalation rules.
  • Billing information: payment cards are entered into Stripe’s form and processed by Stripe. We never receive full card numbers; we keep the card brand, last four digits, subscription status and transaction history.
  • Acceptance records: when you sign up we store which versions of our legal documents you accepted, when, and the IP address and browser that sent the acceptance, so we can show what was agreed.
  • Integration credentials: if you connect Google Calendar, the access tokens Google issues to us for your account; if you connect Zapier, a token for your Zapier connection.
  • Ask Halo: the questions you ask Halo’s in-app assistant about your business, and its answers.

2.2 From calls the Service answers

  • The caller’s phone number, as the telephone network provides it, and the call’s date, time, duration and status.
  • A written transcript of the call. Speech is converted to text as the call happens. Halo does not record or keep call audio. Transcripts are generated automatically and may contain errors; they are a working record, not a verbatim one.
  • What the caller tells the assistant, such as a name, callback number, address, reason for calling, or an appointment request.
  • Information the Service generates from the call: a summary, the caller’s request, the outcome, topics, and a caller profile that lets the assistant recognise a returning caller.

What callers are told. Every call begins with the assistant saying that it is an AI assistant and that the call is transcribed, and the assistant says it is an AI whenever a caller asks.

2.3 From text messages

When the Service sends or receives a text message for a business, we keep the message content, the phone numbers involved, timestamps and delivery status. We also keep each person’s text-message consent (what they were told, when, and how they agreed) and any opt-out, because carriers and the law require proof of consent.

2.4 From our website

  • Talk to Halo live: if you start a demo call on our website, your microphone audio is handled like a phone call: it is transcribed by our providers and the transcript is kept under Halo’s own demo account.
  • Contact form: your name, email, company and message, which are emailed to our support inbox.
  • Technical information: our servers and providers receive your IP address and browser details when you load a page. We read your browser’s description to show the right version of the app on a phone or a computer; we do not store it for that purpose.

2.5 Cookies and similar technologies

We use only the cookies the site needs to work, and no advertising, analytics, session-replay or cross-site tracking technology. Signed-out visitors to our public pages get no cookies from us until they choose a language, pick a plan or sign in. The cookies we set are:

  • Sign-in session (names beginning sb-): completes your sign-in and keeps you signed in. Set when you sign in.
  • halo_locale: remembers the language you chose (one year).
  • halo_active_business: remembers which of your businesses you are working in (one year).
  • halo_pending_invite: finishes joining a team after you confirm your email (14 days).
  • halo_intended_plan: carries the plan you picked on our pricing page into signup (30 days).
  • google_oauth_nonce and google_oauth_return: protect the Google Calendar connection step (10 minutes).
  • halo_preview: lets an invited reviewer see the site while it is closed to the public (one year). It is not set while the site is open.

On the payment step, Stripe’s payment form sets its own cookies to prevent fraud, under Stripe’s privacy policy. Our sign-in and signup pages use Cloudflare Turnstile to block automated sign-ups. Our error monitoring (Sentry) receives technical details about errors and page sessions, such as your browser, without setting cookies. The app also stores, in your browser, whether you dismissed the “install app” banner.

3. How we use information

  • To provide the Service: answer calls, hold conversations, take messages, book appointments, send the texts and emails you set up, and show your calls and contacts in the app.
  • To run accounts: sign-in, security, billing, and service and account notices.
  • To support you: when you ask for help, staff may look at your account through the audited support console described in Section 4.3.
  • To keep the Service safe and lawful: detect and stop fraud, abuse and security incidents, and meet legal obligations.
  • To fix and maintain the Service: investigate errors and keep it working.

AI training. Halo does not use call transcripts, messages or other customer content to train artificial-intelligence models, our own or anyone else’s, and does not use caller information for any purpose of its own. Our providers handle that content as described in Section 4.2.

We do not sell personal information, we do not share it for cross-context behavioural advertising, and we do not use it for targeted advertising.

4. Who we share information with

4.1 Service providers

We use these providers to run the Service. Each receives only what its job needs:

  • Twilio Inc.: phone calls, text messages, and carrier (10DLC) registration.
  • Deepgram, Inc.: speech-to-text transcription of calls.
  • Anthropic, PBC: the language model (Claude) that holds conversations and writes summaries.
  • ElevenLabs Inc.: text-to-speech voices (the default voice).
  • Cartesia AI, Inc. and Rime Labs, Inc.: text-to-speech voices, only for businesses that choose one of their voices.
  • Supabase, Inc.: database, sign-in and storage.
  • Vercel Inc. and Render Services, Inc.: hosting for the app and the voice service.
  • Stripe, Inc.: payments and payment fraud prevention.
  • Resend, Inc.: account and notification emails.
  • Functional Software, Inc. (Sentry): error monitoring.
  • Cloudflare, Inc.: automated-signup protection (Turnstile).
  • Google LLC: calendar, only for businesses that connect Google Calendar.

If a business connects its own Zapier account, Halo sends that business’s chosen call details (who called, why, the summary and any appointment, never the transcript) to its Zapier account, at its direction. Some providers, such as Twilio and Stripe, also use limited information as independent companies under their own privacy policies, for example to route calls, deliver messages, prevent fraud and meet telecommunications law. We will update this list before we start using a new provider for customer data.

4.2 How our AI providers treat call content

  • Deepgram transcribes call audio. Halo sends every request with Deepgram’s model-improvement opt-out set, so Deepgram does not use Halo’s audio to train its models.
  • Anthropic’s commercial terms do not allow it to train models on content Halo sends through its API.
  • The voice providers (ElevenLabs, and Cartesia or Rime when a business selects them) receive the text of the assistant’s replies, which can include details a caller gave, such as a name or an appointment time, in order to speak them. Their standard terms allow, or do not rule out, using content they process to improve their services, and Halo has not obtained a separate opt-out from any of them. They do not receive call audio.

4.3 Halo staff

A small number of Halo staff can look at a customer’s account to provide support, only through a support console that logs every access: who, when, which account, and why. The console shows account health and settings; it does not display call transcripts or message content. Repairs and privacy deletions are run from a fixed list of actions, each logged with its result.

4.4 Legal reasons, business transfers and your direction

We may disclose information when we believe in good faith that the law or legal process requires it, to enforce our terms, or to protect the rights, property or safety of Halo, our customers or others. If Halo is involved in a merger, acquisition, financing or sale of assets, information may transfer as part of it, and the recipient will be bound by this policy for the information it receives. We also share information when you ask us to.

4.5 Text-message information

Mobile phone numbers, text-message consent and opt-out records are never sold, rented or shared with anyone for marketing or promotional purposes. They are shared only with the provider that delivers the messages, to deliver them.

5. How long we keep information

Halo keeps information for these periods and then deletes it:

  • Call transcripts and call summaries: deleted 12 months after the call.
  • Caller profiles: deleted 12 months after the caller’s most recent call.
  • Call log entries (date, time, duration, status and the caller’s number) and text messages: kept while the account is open, as the business’s call and message history.
  • Account, configuration and Ask Halo history: kept while the account is open.

When an account closes. When a subscription ends, we keep the account for 30 days so the customer can reactivate it. After that the account is closed, and within 30 days of closure we delete its call transcripts and summaries, caller profiles, the caller details in its call log, its text messages and its Ask Halo history.

Deleting from the app. Removing a call or a message thread in the app hides it from the account straight away; its content is then deleted on the schedule above, or sooner on request (Section 6).

What we keep longer, and why:

  • Billing and transaction records: at least seven years, for tax and accounting.
  • Legal-acceptance records and text-message consent and opt-out records: for as long as the account exists and at least five years after, to show what was agreed and to answer complaints.
  • Support and security audit records: kept permanently, in a tamper-evident log. They record staff actions, reasons and counts, not call or message content.
  • Information we must keep for a legal claim, investigation or legal obligation, until it is resolved.

Deleted information can remain in our database provider’s encrypted backups for up to 7 days, until those backups expire. Our providers keep the information they process under their own retention terms (for example, Anthropic deletes API content within 30 days by default).

6. Your choices and rights

Whoever you are and wherever you live, you can ask us to:

  • tell you what personal information we hold about you and give you a copy;
  • correct information that is wrong;
  • delete your information; or
  • export your account information in a portable form.

Email customerservice@haloaigroup.com. We will confirm we received your request within 10 business days and answer within 45 days. We verify identity before acting: an account request must come from the account’s email address, and a caller must give the phone number and a detail of the call. We keep records that the law requires us to keep (Section 5), and we will tell you if that applies. We will not treat you differently for making a request.

Callers. Because the business you called controls your call information, we will pass a caller’s request to that business within 5 business days and help it respond. A business can also ask us to delete a caller’s information, and we delete it within that business’s account using an audited tool.

  • Customers can correct most account information in the app, export their leads and contacts as a spreadsheet, and disconnect integrations such as Google Calendar at any time, which revokes our access.
  • Callers can stop text messages by replying STOP.
  • We do not track people across websites and do not sell or share personal information for advertising, so we offer no “Do Not Sell or Share” choice, and browser Do Not Track or Global Privacy Control signals do not change how our site behaves. Nevada residents can still send a request that we not sell their information to customerservice@haloaigroup.com.

7. Security

Information travels between your browser, our servers and our providers over encrypted (TLS) connections, and our database provider encrypts stored data. Telephony credentials are additionally encrypted by Halo before they are stored. Other integration credentials, such as Google Calendar tokens, are kept in database tables that no customer or browser session can read. Payment card details go directly to Stripe. Staff access is limited and logged. No system is perfectly secure and we cannot guarantee absolute security. If a breach affects your personal information, we will notify you as the law requires; for caller information, we will notify the business so it can notify its callers.

8. Children

The Service is a business tool and is not directed to children. We do not knowingly collect personal information from children under 13. If we learn that we hold a child’s information, including from a call, we will delete it, or work with the business to delete it. To report this, email customerservice@haloaigroup.com.

9. Where information is processed

The Service is offered to businesses in the United States. We and our providers process information in the United States.

10. Changes to this policy

When we change this policy we update the date and version above and keep earlier versions on request. For a material change, we will tell customers by email and in the app at least 30 days before it takes effect, and we will not apply a change that gives us broader rights to information collected before the change without asking for consent.

11. Contact us

Halo AI Ventures Corp
Attn: Privacy
12287 Hillman Dr
Palm Beach Gardens, FL 33410
customerservice@haloaigroup.com

Política de privacidad · Halo