Privacy policy

Effective October 31, 2026

Who this covers

Hollerback is a service of Pendium LLC. Businesses use Hollerback to have an AI voice agent place phone calls for them. This policy covers two groups of people:

  • Customers. These are the businesses and developers who sign in and use Hollerback.
  • Call recipients. These are the people our voice agent calls for a customer, and people who call a Hollerback number.

If you got a call from our voice agent, a business that uses Hollerback asked us to call you. That business decides who to call and why. Its own privacy policy also applies to you.

What we collect from customers

  • Your GitHub username and display name, when you sign in.
  • Your legal business name and tax ID. Phone carriers require them.
  • Your settings, such as your webhook URL and the company name the voice agent says.
  • Your API keys. We store only a one-way hash of each key and its first few characters, so we cannot read a key after we show it to you.
  • Your payments. Stripe collects your card or bank details. We receive only the amount, the status, and Stripe's reference IDs.
  • Your usage, such as the tasks you create, the calls we place, and what we charge for them.

What we collect about call recipients

  • What the customer sends in a task: your name and phone number, and optionally your time zone, language, and how to say your name. The task also holds the goal of the call and the facts the voice agent may state.
  • Background knowledge the customer sends with a task, such as account or order details. The voice agent uses it only to answer your questions.
  • The customer's record of how it got your consent to be called.
  • An audio recording of each call. The voice agent tells you at the start of each conversation that the call is recorded and may be monitored.
  • A written transcript of each call, and the result we write from it.
  • Call times, call lengths, and whether each call was answered.
  • Your request to stop calls. If you ask the voice agent to stop calling, we keep your number on a block list for that customer.
  • If you call a Hollerback number, your phone number and the recording and transcript of that call.

How we use it

  • To place calls, hold the conversation, and return results to the customer who asked for them.
  • To charge customers and keep billing records.
  • To honor requests to stop calls.
  • To find and stop abuse, such as calls without consent.
  • To fix problems and improve how the voice agent handles calls.
  • To meet legal duties and answer lawful requests from authorities.

We do not sell personal information. We do not use it for advertising.

We do not use call audio or transcripts to train AI models.

Who we share it with

The customer who created a task gets the recording, the transcript, and the result of each call in that task. We also use these providers to run Hollerback. Each one gets only the data it needs for its job.

  • Twilio. Carries calls over the phone network, provides phone numbers, and stores call recordings.
  • LiveKit. Carries live call audio between the phone network, our voice agent, and people who listen to or take over a call.
  • Deepgram. Turns call audio into text while the call happens. It also finds sensitive details in recordings that customers share redacted.
  • Cartesia. Turns the voice agent's replies into speech.
  • Anthropic. Runs the conversation and writes the result from the transcript.
  • Neon. Hosts our database, which stores accounts, tasks, transcripts, and results.
  • Vercel. Hosts this website, the dashboard, and the API. It also stores redacted copies of recordings.
  • Fly.io. Runs the voice agent and the call scheduler.
  • Stripe. Processes payments when customers add funds.
  • GitHub. Handles sign-in for customers.

We may also share information when the law requires it, to protect people from harm, or as part of a sale or merger of our business. A buyer would have to follow this policy.

Share links, live listening, and takeovers

A customer can share a call recording outside Hollerback. A customer can also let people from its organization listen to a call or take it over while the call happens.

  • Share links. A customer can create a link to one call's recording and transcript. Anyone who has the link can play the recording until the link expires or the customer revokes it. A link lasts 30 days at most. We count how often each link is opened and keep the time of the last view.
  • Redaction. By default, a share link plays a redacted copy of the recording. Deepgram transcribes the recording and marks personal, payment, and health details. We replace each marked word with a tone in the copy and remove it from the copy's transcript. On calls that are not in English, we replace only spoken numbers. Redaction is best effort. Speech recognition can miss a word, and a missed word stays in the copy.
  • Live listening. A customer can create a link that lets people from its organization hear a call and read its transcript while the call happens. A listener cannot speak on the call. The voice agent tells you at the start of each conversation that the call may be monitored.
  • Takeovers. A person from the customer's organization can take over a call by browser or by phone. Before they speak, the voice agent tells you their name and the company they work for. We record what they say and add it to the transcript under their role. When they hand the call back, the voice agent tells you.
  • A live listening or takeover link stops working when the task ends, or after 24 hours.

How long we keep it

  • We keep call recordings and transcripts until the customer deletes them or closes its account. A customer can delete a task's recordings and transcripts at any time with DELETE /v1/tasks/{id}/data. That also deletes any redacted copies, and the task's share links stop working.
  • We delete a task's background knowledge 30 days after the task ends. A customer can delete it sooner with DELETE /v1/tasks/{id}/data.
  • We keep customer account data while the account is open.
  • We keep requests to stop calls for as long as we run the service, so that we keep honoring them.
  • We keep payment records for as long as tax law requires.

Cookies

We set only the cookies that sign-in needs. They keep you signed in to the dashboard. We use no advertising cookies and no third-party analytics.

Security

The website, the dashboard, and the API accept only encrypted connections. We store API keys only as hashes. Customers can see only their own tasks. No system is perfectly secure. If a breach affects your information, we will tell you as the law requires.

Your choices

  • To stop calls, tell the voice agent to stop calling you during any call. You can also contact the business that called you.
  • To see, correct, or delete your information, email us. If you are a call recipient, tell us your phone number and, if you know it, the business that called you. We may ask that business to act on your request, because it controls the task.
  • Customers can delete task data through the API, and can close their account by emailing us.

Some states give their residents more privacy rights. We will honor those rights where they apply. We will not treat you differently because you used them.

Children

Hollerback is for businesses. We do not knowingly collect information from children under 13. If you think we have, email us and we will delete it.

Where we operate

Hollerback is for US businesses calling US and Canadian phone numbers. Our providers may process data in other countries.

Changes to this policy

We will post any change on this page and update the effective date. For a material change, we will also tell customers by email or in the dashboard before it takes effect.

Contact

Email privacy@hollerback.dev with privacy questions or requests. Our terms of service cover the rest of how Hollerback works.