Privacy
Bountee reads public conversations to find people asking for what our customers sell, and drafts helpful replies that a person approves. This page says what we collect, why, who helps us process it, how long we keep it, and what you can ask us to do.
- Nothing is posted, sent or booked without a person approving it, unless a customer turns on autonomy for a kind of reply that has earned it.
- We do not sell personal information. We do not use your content, or the conversations we read, to train AI models.
- Connected accounts are used for one job each: your calendar shows us when you are busy, not what your events are; Gmail and Outlook send the replies you approve and are never read.
- Raw public posts are deleted after 90 days. Connection tokens are encrypted.
- You can ask for a copy of your data, a correction, or deletion at hello@bountee.ai.
What we collect
Your account
Your name, email address, time zone, role and workspace settings. When you sign in with Google or Microsoft we receive your name, your email address and whether it is verified.
What you give us
Your website and the description of your business, examples of your writing, the drafts you edit and approve, and notes. If you use voice: what you dictate, voice notes you record, and, only after you record your consent, a voice sample to create a cloned voice for your own voice notes.
Public conversations
Posts and comments that are publicly visible in the places a workspace watches, such as Reddit, X, Hacker News, Bluesky, Mastodon, Stack Exchange, GitHub, blogs and forums, public city records, and Google and Yelp reviews of the business; messages in Telegram groups and Discord servers where a customer added our bot; and, for LinkedIn, what the customer's own connected account can see. We keep the text, the public name or handle, the link, and our analysis of it. We work at the level of companies: when a public profile or post names an employer, we may link the post to that company.
From your integrations, only what each feature needs
- Calendars (Google, Outlook): the times you are busy, to offer meeting times, and the events we create when a meeting is booked.
- Email sending (Gmail, Outlook): permission to send the replies you approve from your own address. We do not read your inbox.
- Slack and Microsoft Teams: the messages Bountee sends you and the buttons you press.
- CRMs (HubSpot, Salesforce, Pipedrive, Attio, Zoho, Close): the records we create or update because you asked us to.
- Reviews: reviews of your business on Google Business Profile and the replies you approve; Yelp inquiries through Zapier or Yelp's partner program.
- Zapier, webhooks and our API: whatever your Zaps and tools send us, and the events you subscribe to.
- Contact enrichment: if you connect an enrichment provider, a verified work email for a person at a company Bountee resolved.
Voice Line
When a business uses Voice Line, calls to its number are answered by an AI assistant that says it is an AI and that the call is transcribed. We process the call audio to respond, and keep the transcript, a summary and any voicemail so the business can follow up. Texts to the number are kept so the business can answer them. Reply STOP to any text from a Voice Line number and we stop texting you.
Payments
Stripe processes card payments. We receive your plan, its status and your invoices, never your full card number.
On bountee.ai
The website address you type into the box on our home page, the host name of the site that sent you there and any campaign tags in the link, with a random visitor id in a cookie, so we can connect the address to your account if you sign in. We do not keep your IP address with it.
Usage and security records
Sign-ins, what is done in the app, an audit log of approvals and changes, and technical logs that keep the service working and safe.
How we use it
- To run Bountee: find and score conversations, draft replies, route leads to the right person, send what you approve, book meetings and update your CRM.
- To keep it safe: check each community's rules before anything is posted, respect opt-outs, limit how often anyone is contacted, and prevent abuse.
- To support you and to bill you.
- To improve Bountee with aggregated counts of what works, such as which kinds of communities lead to meetings. These counts do not identify you, your company, or the people in the conversations.
We do not use your content, or the conversations we read, to train AI models.
AI processing
We use AI models from Anthropic to understand posts and draft replies, and speech models from Deepgram (with OpenAI as a fallback) for dictation, read-aloud and Voice Line. ElevenLabs creates a cloned voice only after the speaker records their consent. These providers process content to return a result to us. We use the settings and agreements each offers to keep customer content out of their model training, and we list them below so you can read their terms.
Google user data
Bountee's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google sign-in for your name and email; Google Calendar for your free and busy times and the meetings you book; Gmail only to send the replies you approve; and Google Business Profile for your reviews and the replies you approve. We do not use Google user data for advertising, we do not sell it, and people at Bountee do not read it except with your permission, to keep the service secure, or when the law requires it.
Who we share it with
We share information only with the service providers that run Bountee for us, with the tools you connect (to do what you asked), when the law requires it, or as part of a merger or sale of the business, after telling you. We never sell personal information. We never share mobile numbers or text-message consent with third parties for their marketing.
| Provider | What they do for us |
|---|---|
| Anthropic | AI models that read posts and draft replies |
| Deepgram, OpenAI | Speech to text and text to speech |
| ElevenLabs | Cloned voices, only with the speaker's recorded consent |
| Twilio | Voice Line calls and texts |
| Stripe | Payments and invoices |
| Resend | Sign-in links, invitations and summaries by email |
| Apify | Collecting public Reddit, X and review content |
| Unipile | The LinkedIn connection a customer makes |
| Fly.io, Supabase | Hosting and the database |
How long we keep it
- Raw public posts: 90 days.
- Our analysis of them (scores and reasons): 24 months.
- A public handle we saw but never worked with: deleted after 90 days unseen.
- Leads, replies, conversations and meetings: while the workspace exists.
- The audit log: at least 24 months.
- Website addresses typed on our home page: 24 months.
- Your account: until you close it. Deletion is completed within 30 days, except records the law requires us to keep.
If you wrote a public post
Anyone can ask us to stop. Reply to a Bountee customer with "stop", or write to hello@bountee.ai with the link to your post or your handle. We delete what we hold about you, and we keep a minimal record of the request so that no Bountee customer's draft addresses you again.
Security
Data travels encrypted. Connection tokens and keys are encrypted at rest with AES-256-GCM. Each workspace sees only its own data, the audit log is hash-chained so changes to it can be detected, and we ask each integration for the narrowest permission that does the job.
Your rights
Depending on where you live, you may ask for a copy of your personal information, ask us to correct or delete it, object to how we use it, or ask us to limit it. Write to hello@bountee.ai. We answer within 30 days and never treat you differently for asking.
Children
Bountee is for businesses and is not meant for anyone under 18.
Where we process data
We process data in the United States. Where the law requires it, we use appropriate safeguards for transfers.
Changes
When this page changes we update the date at the top. For a material change we tell account owners by email before it takes effect.