Privacy Policy
What Bridgeside AI collects on its website and in its platform, why, who receives it, how long it is kept, and the rights you have under GDPR, UK GDPR and US state privacy laws.
Effective date: 10 November 2026. Last updated: 22 November 2026.
This Privacy Policy is provided by PILOTLAB LLC, a Wyoming limited liability company, doing business as Bridgeside AI ("Bridgeside AI", "we", "us"), 1309 Coffeen Ave Ste 1200, Sheridan, WY 82801, United States.
It explains what personal data we collect, why, who receives it, how long we keep it and how you can exercise your rights. It covers the public website at bridgeside.ai and the customer portal and call platform at app.bridgeside.ai (together, the "Service"). Privacy questions and requests go to hello@bridgeside.ai. Support questions go to support@bridgeside.ai.
Related pages: Cookie Policy, GDPR, Data Processing Agreement, Data Deletion, Terms of Service and Acceptable Use Policy.
Summary
- Bridgeside AI provides AI voice agents that answer and place phone calls for businesses (our customers) through the customer's own dialer or phone numbers. The people those agents speak to are callers.
- We have two roles. We are the controller of account, billing, website and security data. We are a processor of the call data customers put into the Service, which we handle under our Data Processing Agreement.
- We do not sell personal data, and we do not use customer scripts, call transcripts or Google data to train AI models.
- We do not store call audio. During a call, live audio is streamed to third-party speech-recognition and voice providers in the United States for speech-to-text and voice, and we do not keep it.
- Customers choose how long call transcripts are kept, from 1 to 90 days, after which they are redacted or deleted automatically.
- Analytics cookies are only set if you click Accept, and there are no advertising cookies or pixels.
1. What we collect
Account and organization data (portal). Name, email address, password (stored only as a bcrypt hash), role and permissions, organization name, plan, billing status, prepaid credit balance and credit history, the date and time you agreed to the Terms of Service and this Privacy Policy at sign-up, sign-in times, and the IP address and browser used to sign up and sign in. If you sign in with Google we also receive your Google account id, name, email address and profile picture.
Configuration data (portal). Campaign scripts, greetings, questions, FAQs, uploaded product documents, dispositions, voice settings, transfer targets, webhook addresses, dialer connection details (host, credentials for the dialer's management interface, API user) and any speech or voice provider API keys an organization chooses to store. Credentials, API keys and tokens are encrypted with AES-256-GCM.
Call data (portal). For each call an agent handles: the phone number and lead id passed by the dialer or carrier, the campaign, start and end time, duration, a text transcript of what the caller and the agent said, a short summary, answers collected during the call (for example yes or no, a number or a choice), the outcome (transfer, hang-up, appointment) and the disposition written back to the dialer. Do-not-call requests are written to the customer's own dialer; we do not keep a separate do-not-call list.
Call audio. Not stored by us. While a call is live, its audio is streamed to our speech-recognition provider to be transcribed, and the agent's replies are sent as text to our voice providers to be spoken. Recordings, if any, are made and kept by the customer's own dialer or carrier.
Appointment data (portal). When an agent books an appointment: the caller's name, phone number, chosen time and time zone, and the id and link of the calendar event created.
Billing data. Plan, invoices, payments, credit top-ups and automatic recharge settings. Card details are entered on Stripe's pages and never reach us.
Website data. Contact-form submissions (name, email, phone, company, dialer type, message, your consent choice and its wording, IP address and browser); cookie-consent decisions (choice, date, IP address, browser, operating system, device, language, referring page, page and policy version); and, only if you accept analytics cookies, Google Analytics data. Website administrators' accounts (name, email, password hash, last sign-in).
Security data. On the portal's sign-in, sign-up and forgot-password forms, the website's contact form and the website's admin sign-in, our bot-protection provider receives your IP address and technical details of your browser and connection (such as the user agent) so it can check that the request comes from a person. It sets no cookies. We keep only whether the check passed in our server log.
Technical logs. Server logs with IP addresses, request paths, timestamps, call ids, word counts and error details. Logs never contain what callers or agents said.
2. Why we use it, and our legal basis
This table covers the data we control. For call data, the customer decides why it is collected and on what legal basis; we process call data only on the customer's instructions under the Data Processing Agreement.
| Purpose | Data | Legal basis (GDPR and UK GDPR, Art. 6) |
|---|---|---|
| Creating and running portal accounts, delivering the Service to the customer, support | Account and configuration data | Contract (Art. 6(1)(b)) |
| Billing: subscriptions, prepaid credit, automatic recharge, invoices | Account and billing data | Contract (Art. 6(1)(b)) |
| Keeping tax and accounting records | Billing data, per-call billing records | Legal obligation (Art. 6(1)(c)) |
| Security and abuse prevention: bot protection on our forms, rate limits, spotting scripted sign-ups, investigating incidents | Security data, technical logs, sign-up details | Legitimate interests in protecting the Service and its users (Art. 6(1)(f)) |
| Improving the Service with aggregate, de-identified statistics | De-identified usage data | Legitimate interests (Art. 6(1)(f)) |
| Answering contact-form messages | Contact-form data | Legitimate interests in replying to enquiries (Art. 6(1)(f)) |
| Website analytics | Google Analytics data | Consent (Art. 6(1)(a)), given on the cookie bar |
| Recording cookie choices | Cookie-consent records | Legal obligation to show consent (Art. 6(1)(c)) |
| Product updates and marketing | Contact details | Consent (Art. 6(1)(a)), see section 9 |
| Transactional email: verification, password reset, invites, billing, low-credit notices | Account data | Contract (Art. 6(1)(b)) |
Automated decisions. We do not make decisions about you that have legal or similarly significant effects based solely on automated processing. The AI agent records an outcome and a disposition for the customer, who decides what to do with it.
AI providers and training. We do not use customer data to train AI models. Under the standard terms we use with our speech-recognition and voice providers, those providers may keep call audio or text for a limited period and may use it to improve their own services. Our language-model hosting provider receives the campaign script, the conversation so far and the transcript for the summary; under its terms it does not store this data on disk and does not use it to train models.
3. Google user data
The portal offers two optional Google integrations. Both are off until an organization administrator turns them on, and both can be turned off at any time.
Sign in with Google. Requests the openid, email and profile scopes. We use your Google account id, email, name and picture only to create or match your portal account and to show who is signed in.
Google Calendar (appointment booking). Requests the calendar.readonly and calendar.events scopes for the Google account the administrator connects, for one purpose: so an agent can offer appointment times that are actually free and then book them.
- We read the connected account's list of calendars and its busy periods to work out free slots. We do not read the titles, descriptions, attendees or contents of existing events.
- We create the appointment events the agent books (caller's name, phone number, time, campaign) and may update or cancel those same events. We do not modify events we did not create.
- The refresh token Google issues is stored encrypted (AES-256-GCM) and used only to obtain short-lived access tokens for the calls above.
- Calendar data is not used to train models, not used for advertising, and not shared except as needed to place the booking.
- Disconnect at any time in the portal under Settings, Google Calendar. Disconnecting revokes the token at Google and deletes it from our database. You can also remove access at myaccount.google.com/permissions.
Bridgeside AI'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.
4. Who receives personal data
We share personal data only with service providers we need to run the Service, under written contracts that limit them to that purpose:
| Recipient | What they receive | Why | Country |
|---|---|---|---|
| Cloud hosting provider (dedicated server) | All Service data | Running our servers and databases | United States |
| Speech-recognition provider | Live call audio | Turning the caller's speech into text | United States |
| Voice providers | The agent's reply text | Speaking the agent's replies with Basic and Premium voices | United States |
| Language-model hosting provider | The campaign script, the conversation so far, the transcript for the post-call summary | Writing the agent's replies, dispositions and summaries | United States |
| Weather data provider | A place name a caller mentions, with no phone number or name | Answering "how is the weather there" | Switzerland |
| Email delivery provider | Email address and message content | Sending account, billing and contact-form email | United States |
| Bot-protection provider | IP address and technical browser details on our sign-in, sign-up, password and contact forms | Telling people from automated scripts | United States |
| Stripe (payment processor) | Organization name, email, plan, payments and the card you enter on Stripe's pages | Subscriptions, prepaid credit, invoices | United States |
| Sign-in identity; calendar availability and appointment events (only if connected); website analytics (only with consent) | Sign in with Google, Calendar booking, analytics | United States and other countries | |
| PILOTLAB LLC personnel | Any Service data, as needed for their role | Support and engineering | United States and Pakistan |
Customers can request the list of our sub-processors by emailing hello@bridgeside.ai.
When an organization uses its own speech or voice provider keys, call audio and agent text go to that provider under the organization's own agreement with it.
Systems the customer controls. The customer's dialer or carrier receives dispositions, do-not-call requests and transfers from us, and any webhook address the customer configures receives call events. These are the customer's systems, not our providers.
We may also disclose data when the law requires it, to protect the rights and safety of our customers, callers or the public, or as part of a merger or acquisition, in which case this Privacy Policy continues to apply.
5. International transfers
PILOTLAB LLC is based in the United States. Bridgeside AI is hosted in the United States. Some of the service providers we use are located in the United States and other countries. Our support and engineering staff, including team members in Pakistan, may access personal data remotely to run and support the service. When personal data from the EEA, the UK or Switzerland is transferred to a country without an adequacy decision, we use the European Commission's Standard Contractual Clauses, with the UK Addendum and Swiss amendments where they apply. Where a US provider is certified under the EU-U.S. Data Privacy Framework, we may rely on that certification for transfers to that provider.
6. How long we keep data
| Data | How long |
|---|---|
| Call transcripts, summaries, phone numbers, lead ids and collected answers | The period the organization sets in the portal, from 1 to 90 days (default 90). An hourly job then redacts them (removes transcript, summary, phone number, lead id and collected answers) or deletes them (also removes the outcome and dialer references), as the organization chooses. |
| Per-call billing record (call id, date, duration, campaign, status, disposition, billable minutes) | For the life of the account, then 7 years. |
| Past appointments | Their caller name and number are cleared, or the appointment is deleted, by the same hourly job and on the same schedule as call content. Upcoming appointments are kept until they have passed. |
| Call audio | Not stored. |
| Account and organization data, including sign-up and sign-in records | For the life of the account. Deleted within 30 days of a verified deletion request. |
| Email verification links, password reset links, invitations | Verification links work for 3 days, password reset links for 1 hour and invitations for 7 days. The records are removed with the account. |
| Portal sign-in session | 30 days. |
| Google Calendar refresh token | Until the organization disconnects Google Calendar, then deleted immediately. |
| Credit and payment history | For the life of the account. Stripe keeps payment records under its own terms. |
| Contact-form messages | Until a website administrator deletes them. |
| Cookie-consent records | Until deleted. |
| Server logs | 30 days. |
| Database backups | Nightly backups kept for 14 days. |
| Website analytics | 14 months (the data-retention setting in Google Analytics). |
Organization administrators can also delete calls, campaigns and appointments in the portal at any time. The full process, including how callers can ask for removal, is on the Data Deletion page.
7. Security
All traffic to the website, the portal and our providers is encrypted with TLS. Stored credentials, API keys and Google tokens are encrypted with AES-256-GCM, and passwords are hashed with bcrypt. The databases are not reachable from the internet, a firewall admits call audio only on the ports the Service uses, and portal users see only the sections their administrator grants them. No system is perfectly secure. If a personal data breach affects you, we will tell the affected customers within 48 hours of becoming aware of it and, where the law requires, the competent supervisory authority. Our security measures are listed in Annex II of the Data Processing Agreement.
8. Callers
If an AI agent called you, or answered your call, on behalf of one of our customers, that customer decides why you were called and is responsible for having the right to call you. The agent says it is an automated assistant when asked. If you ask not to be called again, the request is written to the customer's do-not-call list.
To see, correct or delete a transcript of your call, contact the company that called you. If you do not know who that was, email hello@bridgeside.ai with the number that was called and the approximate date and time; we will identify the customer, pass your request on and help them answer it.
9. Marketing communications
To send us a message through the contact form you tick one box that reads:
I have read and agree to the Privacy Policy, and I consent to receive product updates, offers and marketing messages from Bridgeside AI by email, phone and SMS. I can unsubscribe at any time.
Consent is not a condition of purchase. Message and data rates may apply to SMS; reply STOP to any text to opt out, or use the unsubscribe link in any email. Phone and SMS contact only applies if you gave us a phone number. We record the wording you agreed to, its version, the date and time, your IP address and browser, and which channels apply. You can withdraw consent at any time by those methods or by writing to us; we will still answer your original enquiry.
10. Your rights
You can ask us to:
- access the personal data we hold about you;
- correct data that is wrong or incomplete;
- delete your data, subject to records we must keep by law;
- restrict how we use it;
- receive it in a portable, machine-readable format (portability);
- object to processing based on our legitimate interests, including direct marketing;
- withdraw consent at any time, for analytics cookies or marketing, without affecting earlier processing.
We do not make solely automated decisions with legal or similarly significant effects (see section 2).
To make a request, email hello@bridgeside.ai from the address on your account, or call 1 888 370 6801. We answer within one month, may ask you to verify your identity, and do not charge for reasonable requests. For call data we hold on a customer's behalf, we pass your request to that customer and help them respond.
Complaints. If you are in the European Economic Area, you can complain to the data protection supervisory authority in the country where you live, work or think your rights were infringed. In the United Kingdom, you can complain to the Information Commissioner's Office (ICO).
US state privacy rights. If you live in California or another US state with a consumer privacy law, you have the right to know what personal data we collect and how we use it, to delete it, to correct it, and to opt out of its sale or sharing. We do not sell personal data, and we do not share it for cross-context behavioral advertising; the website runs no advertising pixels. You may use an authorized agent, and we will not discriminate against you for exercising these rights. Send requests to the address above.
11. Children
The Service is for businesses and is not directed to children under 16. We do not knowingly collect their data, and we delete it if we learn that we have.
12. Changes
We post changes on this page and update the dates at the top. For material changes we email the account owners of every organization before they take effect.
13. Contact
PILOTLAB LLC, doing business as Bridgeside AI, 1309 Coffeen Ave Ste 1200, Sheridan, WY 82801, United States. Email hello@bridgeside.ai. Phone 1 888 370 6801.