Skip to main content

Legal

Privacy Policy

Effective Date: January 1, 2026 · Last Updated: March 27, 2026

TABLE OF CONTENTS

01Introduction & Controller Identity
02Definitions
03Information We Collect
04How We Use Your Information
05Legal Basis for Processing (GDPR)
06Contact Data: Third-Party Subjects
07How We Share Your Information
08Google API Services & User Data
09Other Integration Disclosures
10Data Security
11Data Retention
12International Data Transfers
13Your Rights and Choices
14Cookies & Tracking Technologies
15Children's Privacy
16Call Recording Disclosure
17Data Breach Notification
18Changes to This Policy
19Contact Us

01Introduction and Controller Identity

Fuentes Digital Ventures LLC, a Wyoming limited liability company operating under the commercial brand Callengo ("Callengo," "we," "us," or "our"), is committed to protecting the privacy of individuals who interact with our platform, our website, and our services. This Privacy Policy explains who we are, what personal data we collect, why we collect it, how we use and share it, and what rights you have with respect to your personal data.

Legal EntityFuentes Digital Ventures LLC
Commercial BrandCallengo
Registered Address5830 E 2nd St, Ste 7000 #20312, Casper, WY 82609, United States
Privacy Contactprivacy@callengo.com
Legal Contactlegal@callengo.com
Websitehttps://callengo.com
Applicationhttps://app.callengo.com

This Privacy Policy applies to:

  • The Callengo Application available at app.callengo.com, the AI-powered outbound voice automation platform used by business customers and their authorized team members;
  • The Callengo marketing website available at callengo.com, including all pages, blog content, and web forms; and
  • All related services, integrations, APIs, and communications associated with the Callengo platform.

This Privacy Policy governs data about Callengo's business customers and their authorized team members (the people who create and use Callengo accounts). For information about how Callengo processes personal data of individuals contacted through customer campaigns (call recipients), please refer to Section 6.

02Definitions

For purposes of this Privacy Policy, the following definitions apply:

"Application" means the Callengo AI voice automation platform accessible at app.callengo.com.
"Call Data" means all data generated from an AI Voice Agent call, including call recordings, transcripts, AI-generated summaries, call outcome classifications, metadata, and structured analysis outputs.
"Contact" means an individual whose personal data has been uploaded to or imported into the Application by a Customer for use in outbound AI calling campaigns.
"Customer" means a business entity or individual that has registered for a Callengo account and uses the Application.
"Customer Data" means all data submitted, uploaded, imported, or generated by a Customer through the Application, including Contact Lists, Call Data, CRM data, and campaign configurations.
"Personal Data" means any information that relates to an identified or identifiable natural person, as defined under applicable privacy law including the GDPR and CCPA.
"Service" means the Application, the Website, and all associated Callengo services collectively.
"Sub-processor" means any third-party entity engaged by Callengo to process Personal Data on behalf of Callengo in connection with the Service.
"Website" means the Callengo marketing website accessible at callengo.com.

03Information We Collect

We collect personal data in the following categories, depending on how you interact with our Service:

3.1 Information You Provide to Us (Application)

Account Registration Data. When you create a Callengo account, we collect your full name, business email address, and password. Passwords are never stored in plaintext; they are hashed server-side by our authentication provider using bcrypt. We verify your email address before granting access to the Application.
Company and Profile Information. During onboarding or through your account settings, we may collect your company name, company website URL, industry, team size, and other business profile information you choose to provide.
Team Member Information. If you invite team members to your Callengo account, we collect the name and email address of each invited individual to facilitate account setup and access.
Payment and Billing Information. When you subscribe to a paid plan, your payment method details (card number, CVV, expiry date) are collected and processed exclusively by our third-party payment processor. We do not receive, store, or have access to your full payment card details. We do receive and store: your billing email address, subscription status, payment history, payment method type, and invoice records.
Communications. If you contact us by email or through a web form, we collect the content of your message and any information you voluntarily include.
AI Assistant Conversations. If you use the Cali AI in-app assistant, your typed messages and the AI's responses are stored to provide conversation history within your session. These conversations are stored within your account and are accessible to you.

3.2 Information We Collect Automatically (Application)

Usage and Behavioral Data. We collect data about how you interact with the Application, including pages visited, features used, buttons clicked, time spent on features, error events, and navigation patterns. This data is collected using product analytics tools.
Session and Authentication Data. We collect session information necessary to authenticate you and maintain your logged-in state, including session tokens, session duration, and login timestamps.
Geolocation and Device Data. When you first access the Application, we automatically detect and store your approximate location (country, region, city, timezone) and IP address for the purpose of selecting your default currency display, applying appropriate time zone settings, and security monitoring.
reCAPTCHA Data. On the registration form, we use Google reCAPTCHA v3, an invisible bot-detection service that processes your IP address, browser characteristics, and behavioral signals to generate a risk score. This risk score is used to determine whether a registration attempt is human or automated. The score is not stored by Callengo.

3.3 Information We Collect Through Integrations (Application)

When you connect a third-party service to your Callengo account, we receive and store data from that service as necessary to operate the integration. All OAuth access tokens and refresh tokens are encrypted at rest using AES-256-GCM before storage. Integration credentials are deleted from our database when you disconnect the integration.

IntegrationData We AccessData We Write Back
Google CalendarCalendar events (titles, dates, times, attendees), connected account emailConfirmed, rescheduled, or cancelled appointment events
Microsoft Outlook CalendarCalendar events, Microsoft account email and tenant IDAppointment events from campaign outcomes
Microsoft Dynamics 365CRM contact records (name, email, phone, company, address)Call outcome notes (future)
HubSpot CRMContacts, companies, deals, list memberships, owner assignmentsCall outcomes, activity logs, lifecycle stage updates
Salesforce CRMContact and lead records (name, email, phone, company, address)None currently (read-only)
Pipedrive CRMPerson records (name, email, phone, company, deal stage)Call outcomes and qualification updates
Zoho CRMContact and lead records, organizational settings for field mappingCall outcome notes
Clio (Legal)Client records, matter details, firm informationNone (read-only)
SimplyBook.meBooking client records (name, email, phone, booking details)None (read-only)
Google SheetsSpreadsheet row data mapped to contact fields (import only)None
ZoomAccount identity for meeting link generationNone
SlackWorkspace identity, channel identifiersCall completion notifications

3.4 Customer Contact Data (Information About Third Parties)

When you use the Application to run calling campaigns, you upload or import personal data about your contacts (the individuals to be called). This data may include names, phone numbers, email addresses, postal addresses, company names, job titles, and any custom fields you configure. This data belongs to you as the data controller; Callengo processes it on your behalf as a data processor. See Section 6 for important information about Contact data.

3.5 Information We Collect (Website: callengo.com)

The Callengo marketing website at callengo.com uses a consent-based tracking architecture. All tracking technologies on the Website are managed through Google Tag Manager (container GTM-MXFGV52S) and are subject to Google Consent Mode v2, which defaults all cookie storage to "denied" until you provide explicit consent through our cookie consent management platform. No non-essential tracking occurs until you affirmatively consent.

Consent Management. The Website uses Usercentrics (an EU-based Consent Management Platform) to present you with a cookie consent banner when you first visit callengo.com. Usercentrics manages your consent state for all non-essential tracking technologies in compliance with GDPR and ePrivacy Directive requirements. Google Consent Mode v2 is configured with a 500ms wait period to ensure your consent preferences are loaded before any tags fire. You may update your consent preferences at any time by clicking the cookie settings link in the Website footer.
Web Analytics Data (Google Analytics 4). When you consent to analytics cookies, the Website collects information about your visit using Google Analytics 4 (GA4), including: pages viewed, session duration, scroll depth, outbound link clicks, referring URL, geographic location (country/region level), browser type, operating system, and device type. GA4 also tracks the following custom events on the Website:
  • Audio demo interactions (play, pause, scenario change)
  • Call-to-action button clicks (free trial, talk to sales)
  • Pricing page interactions (plan selection, billing cycle toggle)
  • Contact form and HubSpot form submissions
  • Newsletter subscriptions
  • Feature and integration page interactions (learn more clicks, integration card clicks)

All GA4 data collection is consent-gated via Google Consent Mode v2 and will not activate unless you have granted consent through Usercentrics.

CRM and Marketing Attribution (HubSpot). The Website loads the HubSpot tracking code (portal 147914572, EU1 region) via Google Tag Manager. When active, HubSpot captures UTM parameters from your visit URL and stores a hubspotutk cookie to associate your browsing session with your identity if you later submit a form. When you convert (e.g., by submitting the contact form or subscribing to the newsletter), HubSpot attaches source attribution data to your CRM contact record, including: hs_analytics_source, utm_source, utm_medium, utm_campaign, utm_content, and utm_term.
Advertising and Audience Tracking (LinkedIn Insight Tag). The Website loads the LinkedIn Insight Tag via Google Tag Manager. This tag enables LinkedIn Campaign Manager to attribute website visits to LinkedIn advertising campaigns and to build retargeting audiences for advertising purposes. The LinkedIn Insight Tag is consent-gated and will not load until you grant consent for marketing cookies.
Form Submissions (HubSpot Forms). The contact page on the Website uses an embedded HubSpot form. When you submit this form, your data (including name, email address, company name, and message) is sent directly to HubSpot CRM. This data is used to create or update a contact record in our CRM for the purpose of responding to your inquiry and managing our sales pipeline.
Newsletter Subscriptions. When you subscribe to our newsletter via the Website, your email address is submitted to HubSpot Contacts API (v3), where a contact record is created or updated with lifecycle stage set to "subscriber" and marketable status set to true. You may unsubscribe at any time via the link in any newsletter email.
Ad Platform Connections. Callengo maintains connected ad accounts with Google Ads and LinkedIn for the purpose of measuring advertising campaign performance. These platforms may receive anonymized conversion data from the Website when you have consented to marketing cookies. Auto-tracking is enabled for attribution purposes.
Inbound Webhooks (Smartlead). The Website receives inbound webhook events from Smartlead, a cold email outreach platform, containing email engagement data (opens, clicks, replies). This data is synced to HubSpot CRM for contact creation, note logging, and deal management. This processing does not involve Website visitor data and does not set cookies on your browser.

04How We Use Your Information

4.1
Providing and Operating the Service. We use your account data, usage data, and integration data to: create and maintain your account; authenticate you and manage your sessions; operate the Application and all features you use; process and execute your calling campaigns; sync data between the Application and your connected Third-Party Services; deliver transactional communications (account verification, password reset, team invitations, billing notifications); and provide customer support.
4.2
AI Voice Agent Execution. When you launch a campaign, we use your Contact data (name, phone number, and other fields you have configured) to construct the AI agent's call instructions, which are transmitted to our voice infrastructure provider to execute the call. We use Call Data returned from each call (transcript, recording, outcome) to display results in your dashboard, trigger post-call AI analysis, write outcomes to your connected CRM or calendar, and store campaign performance records.
4.3
Post-Call AI Analysis. We use call transcripts and Contact data to perform automated AI analysis of call outcomes, including intent classification, lead qualification scoring, appointment confirmation status, contact data validation, sentiment analysis, and follow-up recommendations. This analysis is performed by an AI processing service operating under a data processing agreement.
4.4
Billing and Subscription Management. We use your account and payment information to process subscription payments, manage billing cycles, track metered usage (call minutes), generate invoices, handle subscription upgrades and cancellations, and respond to billing inquiries.
4.5
Internal Business Operations. We use data about how our customers use the Application (in aggregated or pseudonymized form where possible) to analyze product usage patterns, improve platform features and performance, develop new features, conduct internal research, and monitor platform security and integrity.
4.6
Communications. We use your contact information to send you: transactional emails required to operate your account; product update and feature announcement emails (from which you may opt out); and responses to inquiries you submit.
4.7
Legal and Compliance. We use personal data where necessary to comply with applicable legal obligations, respond to valid legal requests from law enforcement or courts, enforce our Terms of Service, protect our rights and safety, and prevent fraud or abuse.
4.8
Website Analytics and Marketing. We use data collected through the Website to understand how visitors discover and interact with callengo.com, measure marketing campaign effectiveness, improve Website content and user experience, and generate leads and manage our sales pipeline using our CRM platform. Specifically: Google Analytics 4 data is used to analyze traffic patterns, content engagement, and conversion funnels; HubSpot tracking data is used to attribute leads to marketing channels and manage the sales pipeline; LinkedIn Insight Tag data is used to measure LinkedIn advertising campaign performance and build targeted audiences; and Google Ads conversion data is used to optimize advertising spend and measure return on ad investment. All non-essential Website tracking is consent-gated via Google Consent Mode v2 and Usercentrics and does not activate until you provide explicit consent.

05Legal Basis for Processing (GDPR)

For users in the European Union, European Economic Area, or United Kingdom, we process personal data under the following legal bases as required by the General Data Protection Regulation (Regulation (EU) 2016/679) and the UK GDPR:

Processing ActivityLegal BasisGDPR Article
Account creation and managementPerformance of contractArt. 6(1)(b)
Delivering the Application and its featuresPerformance of contractArt. 6(1)(b)
Billing and payment processingPerformance of contractArt. 6(1)(b)
Transactional communicationsPerformance of contractArt. 6(1)(b)
Security monitoring and fraud preventionLegitimate interestsArt. 6(1)(f)
Product analytics and improvement (Application)Legitimate interestsArt. 6(1)(f)
AI assistant conversation storagePerformance of contractArt. 6(1)(b)
Website analytics via GA4 (non-essential cookies)ConsentArt. 6(1)(a)
Website CRM tracking via HubSpot (non-essential cookies)ConsentArt. 6(1)(a)
Website advertising attribution via LinkedIn Insight TagConsentArt. 6(1)(a)
Website advertising attribution via Google AdsConsentArt. 6(1)(a)
Contact form submission processingLegitimate interests / Performance of contractArt. 6(1)(f) / Art. 6(1)(b)
Newsletter subscription managementConsentArt. 6(1)(a)
Marketing communicationsConsentArt. 6(1)(a)
Legal compliance and regulatory obligationsLegal obligationArt. 6(1)(c)
Responding to legal requestsLegal obligation / Legitimate interestsArt. 6(1)(c) / Art. 6(1)(f)
Geolocation detection for currency and timezoneLegitimate interestsArt. 6(1)(f)
Processing Contact data on behalf of CustomersCustomer's instruction (data processor)Art. 28
Retention of financial recordsLegal obligationArt. 6(1)(c)

Where we rely on legitimate interests as our legal basis, we have conducted a balancing assessment and concluded that our legitimate interests are not overridden by your rights and interests, given the nature of the data processed and the safeguards we apply. You have the right to object to processing based on legitimate interests; see Section 13.

Where we rely on consent, you have the right to withdraw your consent at any time without affecting the lawfulness of processing prior to withdrawal; see Section 13.

06Contact Data: Third-Party Data Subject Information

6.1
Callengo's Role with Respect to Contact Data. When you use the Application to run outbound calling campaigns, you provide us with personal data about the individuals you intend to call ("Contacts"). With respect to Contact data:
  • You are the data controller. You determine the purpose for which Contacts are called, the data fields collected, and how call outcomes are used in your business.
  • Callengo is the data processor. We process Contact data exclusively as instructed by you, in accordance with your campaign configuration, and subject to our Data Processing Addendum (available at callengo.com/legal/dpa).

Callengo does not use Contact data for any purpose other than executing your campaigns and providing the Service to you. We do not sell, share, or commercially exploit Contact data.

6.2
Your Responsibilities as Data Controller for Contact Data. As the data controller for Contact data, you are solely responsible for: (a) ensuring you have a lawful basis to process Contact data for the purposes of automated AI calling; (b) providing all legally required notices and disclosures to Contacts before they are called; (c) obtaining any consents required by applicable law, including the TCPA's prior express written consent requirement for AI-generated voice calls to wireless numbers; (d) maintaining records of consents and being able to produce them upon demand; (e) honoring data subject rights requests from Contacts promptly; and (f) ensuring Contact data was lawfully obtained and is lawfully processed.
6.3
What Happens to Contact Data During Calls. At call dispatch time, Contact data (including the Contact's phone number, name, company name, appointment details, and other fields configured by you) is incorporated into the AI agent's instructions and transmitted to our voice infrastructure provider to execute the call. Call recordings and transcripts are generated during every call and may contain the spoken words, name, and any personal information voluntarily disclosed by the Contact during the conversation. Transcripts are returned to your Callengo account and may be processed by our AI analysis service to extract structured outcomes.
6.4
Data Subject Rights for Contacts. If a Contact submits a data subject rights request (such as a deletion request or access request) to you, you must handle that request as the data controller. Callengo will cooperate with your handling of data subject rights requests as required by our DPA. If Callengo receives a rights request directly from a Contact, we will promptly forward it to the relevant Customer.

07How We Share Your Information

We do not sell your personal data. We do not share personal data for cross-context behavioral advertising. We share personal data only in the circumstances described below.

7.1
Sub-processors. We engage trusted third-party service providers ("Sub-processors") to assist us in operating the Service. These Sub-processors process personal data on our behalf under written agreements that require them to protect personal data at least as strictly as we do. Our Sub-processors fall into the following categories:
Infrastructure and Hosting. We use cloud infrastructure and serverless hosting providers to host the Application and process all Application traffic. All data stored in the Application resides on databases managed by our infrastructure provider within the United States.
Authentication. We use a managed authentication service to handle user account authentication, password hashing, session management, and multi-factor authentication, including social login via Google and Microsoft.
Voice Call Infrastructure. All outbound AI voice calls are executed by a third-party voice infrastructure provider. When a call is dispatched, the Contact's phone number, AI agent task instructions (which include the Contact's name and other configured details), and call parameters are transmitted to this provider. The provider records all calls by default, generates transcripts, and returns call outcomes to our platform. This provider operates under a comprehensive Data Processing Agreement that prohibits use of Customer personal data outside the scope of providing the calling service, includes Standard Contractual Clauses for EU data transfers, and provides for deletion of Customer personal data within 14 days of service cessation upon written request.
AI Analysis. We use a third-party AI language model service to perform post-call analysis of call transcripts and Contact data, including intent classification, lead scoring, appointment confirmation detection, and sentiment analysis. This service also powers the Cali AI in-app assistant. When you use the Cali AI assistant, your message, the conversation history, and your company profile information (including team member names and email addresses) are included in the request sent to this service. Our AI processing provider does not use our API data to train its models; all model training data sharing is disabled at the organizational account level. Prompts and completions are retained by this provider for up to 30 days for logging purposes, after which they are deleted.
Payment Processing. We use a PCI DSS Level 1 certified payment processor to handle all subscription billing and payment processing. Your full payment card details are collected and processed exclusively by this provider; Callengo never receives or stores your card number, CVV, or expiry date.
Transactional Email. We use a transactional email service to deliver authentication emails (account verification, password reset, magic links) and team invitation emails from our noreply@callengo.com address.
Product Analytics. We use product analytics tools to understand how customers use the Application. These tools collect behavioral events and session data using a pseudonymized user identifier (your account UUID, not your email address). One of these tools also records sessions with password, email input, and phone number fields masked.

A current list of Callengo's Sub-processors, including entity names and processing locations, is available at callengo.com/legal/sub-processors. We will provide at least 30 days' advance notice of any addition of a new Sub-processor through our Sub-processor list page and by email notification.

7.2
Third-Party Integration Providers. When you enable an integration with a Third-Party Service (such as a CRM, calendar, or scheduling application), Customer Data (including Contact records, call outcomes, and related information) may be transmitted to and stored in that Third-Party Service. You authorize this transmission by enabling the integration. Each Third-Party Service processes data it receives under its own privacy policy and terms of service. Callengo is not responsible for the privacy practices of Third-Party Services.
7.3
Customer-Configured Webhooks. If you configure outbound webhook endpoints, Callengo will transmit event data (which may include Contact names, phone numbers, call outcomes, and AI analysis results) to the URLs you specify. You are responsible for ensuring that your webhook destinations handle received data in compliance with applicable data protection law.
7.4
Internal CRM Synchronization. Callengo uses a CRM platform internally to manage our business customer relationships. Information about Callengo account holders (including company name, subscription plan, and account email) may be synchronized to our internal CRM for account management and customer success purposes. This is not a sale or sharing of data for advertising purposes.
7.5
Website Third-Party Services. The following third-party services receive data from the Callengo Website (callengo.com) when you have provided consent through our cookie consent management platform:
ServiceProviderData SharedPurpose
Google Tag ManagerGoogle LLCTag configuration, consent stateCentral tag management and deployment
Google Analytics 4Google LLCPage views, sessions, custom events, device/browser infoWebsite analytics and conversion tracking
Google AdsGoogle LLCAnonymized conversion signalsAdvertising attribution and campaign optimization
HubSpot TrackingHubSpot Inc. (EU1 region)Page visits, UTM parameters, form submissions, emailCRM contact creation, lead attribution, sales pipeline
HubSpot FormsHubSpot Inc. (EU1 region)Name, email, company, messageContact form processing and CRM record creation
LinkedIn Insight TagLinkedIn CorporationPage visits, anonymized ad attribution signalsLinkedIn ad campaign measurement and audience building
Usercentrics CMPUsercentrics GmbH (EU)Consent state, consent historyCookie consent management for GDPR/ePrivacy compliance

Additionally, data flows exist between the following platforms in connection with our business operations: Stripe payment data is synced to HubSpot CRM for contact, invoice, and product lifecycle management; PostHog application analytics data is synced to HubSpot for product-led growth insights; and Smartlead cold email engagement data is synced to HubSpot for contact and deal management via webhook and native integration.

7.6
Legal Disclosures. We may disclose personal data to courts, law enforcement agencies, regulatory authorities, or other third parties if we believe in good faith that disclosure is necessary to comply with a valid legal obligation, protect the rights or safety of Callengo or our customers, detect or prevent fraud or security breaches, or enforce our Terms of Service.
7.7
Business Transfers. If Callengo is involved in a merger, acquisition, asset sale, financing, or other corporate transaction, personal data we hold may be transferred to the successor entity as part of that transaction. We will provide notice of any such transfer in accordance with applicable law.

08Google API Services and User Data

This section specifically addresses the requirements of the Google API Services User Data Policy, including the Limited Use requirements, and is structured to satisfy Google's OAuth app verification requirements. Callengo requests only the minimum scopes necessary for the features you activate, and uses the non-sensitive drive.file scope with the Google Picker for Google Sheets, rather than broader Drive scopes.

8.1
Data Accessed via Google APIs. When you connect your Google account to Callengo, we request the following OAuth scopes. The Google Calendar scopes are requested only when you connect the Calendar integration; the drive.file scope is requested only when you connect the Google Sheets integration. Each scope is requested independently and you may connect either integration without the other.
OAuth ScopeData AccessedPurpose
auth/calendarRead/write access to Google Calendars owned by or shared with the connected accountRead availability and create, update, or delete calendar events for appointment scheduling
auth/calendar.eventsRead/write access to individual calendar eventsManage event records (create, update, cancel) as appointments are confirmed, rescheduled, or marked as no-show
auth/drive.filePer-file access to ONLY the specific Google Sheets spreadsheets you select through the Google Picker, plus any files Callengo creates on your behalfRead contact rows (phone number, name, email, company, notes) from spreadsheets you explicitly pick, for one-time import or continuous inbound sync into your Callengo contact list
auth/userinfo.emailGoogle account email addressIdentify which Google account is connected and associate the OAuth credentials with your Callengo user
auth/userinfo.profileDisplay name and profile picture URLDisplay the connected account's name and avatar in your Callengo integration settings

Google Sheets file selection. Because Callengo uses the non-sensitive drive.file scope rather than broader Drive scopes, Callengo cannot list, search, or read any file in your Drive unless you explicitly share it with the application through the Google Picker. When you click “Pick a spreadsheet from Google Drive” inside Callengo, Google's own file picker opens and you select which spreadsheet(s) to grant access to. Callengo only ever sees the files you pick (or files Callengo itself creates). If you want Callengo to stop accessing a spreadsheet, you can unlink it from Callengo's integration settings or remove Callengo's permissions in your Google Account.

8.2
How We Use Google User Data. We use Google user data exclusively to provide the calendar synchronization and spreadsheet import features you have authorized by connecting your Google account. Specifically:

Google Calendar data is used to check availability for appointment scheduling, create new calendar events for confirmed appointments, update existing events when appointments are rescheduled or cancelled, and display synced calendar events within the Application interface.

Google Sheets data is used exclusively for one-way inbound contact import. When you pick a spreadsheet via the Google Picker, Callengo reads the spreadsheet's file name, sheet tab names, and the cell values in the tab you choose, mapping columns (such as phone number, name, email, company, and notes) into contact records in your Callengo account. Callengo does not write to, modify, or create Google Sheets files. The sync is strictly read-only and inbound-only.

Google account identity data (email, display name, profile picture) is used solely to identify which Google account is connected and associate the OAuth credentials with your Callengo user account.

We do not use Google user data for any of the following purposes: serving or personalizing advertising; building user profiles for purposes unrelated to the authorized integration feature; selling, renting, or transferring Google user data to any third party for their own purposes; training general-purpose AI or machine learning models; or any purpose not directly related to providing the calendar synchronization or spreadsheet import feature to you.

8.3
Sharing of Google User Data. Google user data is not shared with any third party except: (a) our database infrastructure provider (Supabase), which stores encrypted OAuth credentials, synced calendar event data, and imported contact records as our data processor; and (b) our hosting provider (Vercel), through whose infrastructure all API requests transit. Google user data is never transmitted to our voice infrastructure provider (Bland AI), our AI transcript-analysis provider (OpenAI), any advertising or analytics platform, or any other third party. Calendar event data and Google Sheets data never leave Callengo's data-processor boundary.
8.4
Storage and Protection of Google User Data. Google OAuth access tokens and refresh tokens are stored encrypted at rest using AES-256-GCM encryption with a unique initialization vector per record. The encryption key is stored as a protected server-side environment variable and is never committed to source code or exposed to client-side code. Calendar event data and imported Google Sheets contact data are stored in your Callengo account subject to row-level security policies that restrict access to authorized members of your company account. OAuth tokens are automatically refreshed before expiration and refresh failures immediately deactivate the integration and prompt you to reconnect. All API traffic between Callengo and Google services is transmitted over TLS.
8.5
Retention and Deletion of Google User Data. Google OAuth credentials and the associated Google email address are retained for as long as the integration remains connected. When you disconnect the Google Calendar or Google Sheets integration within Callengo, the access token, refresh token, and Google email stored by Callengo are immediately deleted and the OAuth token is revoked with Google. Calendar events and contact records previously synced into Callengo remain in your account until you delete them or delete your Callengo account, at which point all associated data is permanently deleted. You may also revoke Callengo's access to your Google account at any time through your Google Account settings at myaccount.google.com/permissions.
8.6
AI and Machine Learning. Callengo does not use Google user data to develop, improve, or train general-purpose AI or machine learning models. Google Calendar data, Google Sheets data, and Google account profile data are never sent to our AI providers (OpenAI) or voice provider (Bland AI). AI features within Callengo that process call transcripts operate only on data generated during the specific call session itself — never on data sourced from your Google account.

Google API Limited Use Disclosure: Callengo'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. Callengo does not use Google user data for advertising, does not transfer Google user data except as necessary to provide or improve user-facing features, does not allow humans to read Google user data unless we have your affirmative agreement, the access is required for security purposes, or we are legally compelled to do so, and does not use Google user data to train or improve general-purpose AI models.

09Other Integration-Specific Data Disclosures

The following disclosures apply to customers who connect specific integrations. These integrations are optional and only activated when you explicitly connect them. In each case, OAuth tokens are stored encrypted at rest, and integration data is used exclusively for the stated purpose.

9.1
Microsoft Integration. When you connect your Microsoft Outlook calendar or Microsoft Dynamics 365 account, we access calendar events and, for Dynamics 365, CRM contact records (name, email, phone, company, address) within the permissions of your connected Microsoft account. Microsoft data is used exclusively to provide the calendar synchronization and CRM contact management features. You may revoke Callengo's access to your Microsoft account at any time through your Microsoft account's Connected Apps settings.
9.2
HubSpot Integration. When you connect your HubSpot account, we access contact records, company records, deal records, owner assignments, and list memberships. We may write call outcomes, activity records, and lifecycle stage updates back to your HubSpot account. HubSpot data is used exclusively to populate your Callengo contact records and to sync call results back to your CRM.
9.3
Salesforce Integration. When you connect your Salesforce account, we access contact records, lead records, account records, and user information from your Salesforce organization using OAuth. Salesforce data is used exclusively to import contacts into your Callengo account. The Salesforce integration uses broad API permissions necessary for comprehensive CRM automation; actual API calls are strictly limited to reading Contact, Lead, Account, Event, and User objects.
9.4
Pipedrive Integration. When you connect your Pipedrive account, we access person records, deal records, and organization records. We may write call outcomes and qualification results back to your Pipedrive person records.
9.5
Zoho CRM Integration. When you connect your Zoho CRM account, we access contact records, lead records, account records, user records, and organization settings necessary for field mapping. We may write call outcomes back to Zoho contact and lead records.
9.6
Clio Integration (Legal Practice Management). When you connect your Clio account, we access client records and matter details from your Clio legal practice management system. This data may include legally sensitive information regarding your clients. Clio data is used exclusively to import client contact information for calling campaigns you configure. Law firm customers using this integration bear independent professional obligations under state bar rules regarding client communications.

10Data Security

We implement reasonable and appropriate technical and organizational security measures designed to protect personal data against unauthorized access, disclosure, alteration, loss, or destruction. These measures include:

Security MeasureDescription
Encryption in TransitAll data transmitted between your browser and the Application is encrypted using TLS 1.2 or higher. HTTP Strict Transport Security (HSTS) is enforced on all Callengo domains.
Encryption at RestOAuth access tokens and refresh tokens for all integration providers are encrypted at rest using AES-256-GCM encryption with a 256-bit key before storage.
Database Access ControlsRow-level security (RLS) is enforced on all database tables, ensuring authenticated users can only access records belonging to their own company account.
Authentication SecurityPasswords are hashed using bcrypt and never stored in plaintext. Session tokens are stored in HTTP-only, Secure, SameSite cookies not accessible to client-side scripts. TOTP-based MFA is available to all users.
Webhook SecurityAll inbound webhooks are verified using HMAC-SHA256 signatures. All outbound webhook deliveries include HMAC-SHA256 signatures. Webhook URLs are validated against SSRF protections.
Privilege ControlsDatabase-level triggers prevent privilege escalation and unauthorized modification of sensitive fields. Service-level credentials are stored as protected environment variables, never exposed to client-side code.
Security HeadersAll Application responses enforce: Content Security Policy, X-Frame-Options: DENY, X-Content-Type-Options: nosniff, Referrer-Policy, Permissions-Policy, and HSTS.
Administrative Audit LoggingAll administrative actions performed on the platform are logged to an audit log recording the action, the performing user, the timestamp, and the IP address and user agent of the request.

While we implement these measures, no method of transmission over the internet or electronic storage is 100% secure. We cannot guarantee absolute security of personal data. In the event of a data breach, we will respond in accordance with our breach notification obligations described in Section 17.

11Data Retention

We retain personal data for as long as necessary to fulfill the purposes for which it was collected, to comply with our legal obligations, and to resolve disputes and enforce agreements. The following retention periods apply as general guidelines:

Data CategoryRetention PeriodNotes
Account and profile informationDuration of account + 90 days90-day window allows data export after closure
Contact recordsUntil deleted by Customer or account closureCustomer controls deletion via Application
Call logs and transcriptsUntil deleted by Customer or account closureCustomer controls deletion via Application
Call recordings (basic)30 days from call dateDefault; deleted after 30 days
Call recordings (Recording Vault add-on)Up to 12 months (customer-configured)Extended retention requires paid add-on
AI analysis resultsRetained with call logDeleted when call log is deleted
Integration OAuth tokensDeleted on integration disconnectionImmediate deletion upon disconnect
Billing and transaction recordsMinimum 7 yearsRequired for tax and accounting compliance
Session and authentication logs30 daysRolling deletion
Security and audit logs12 monthsRolling deletion
AI assistant conversationsDuration of accountDeleted on account closure
OpenAI prompt/completion logsUp to 30 days on OpenAI's serversRetained by AI provider for operator review only; not used for training
Website analytics data (GA4)Per Google's data retention settingsControlled via GA4 data retention configuration
HubSpot CRM contact records (Website leads)Until manually deleted or contact requests erasureManaged within HubSpot CRM
HubSpot tracking cookiesPer HubSpot cookie lifecyclehubspotutk cookie expires after 13 months
Usercentrics consent recordsPer Usercentrics retention policyConsent proof retained for GDPR compliance
LinkedIn Insight Tag dataPer LinkedIn's data retention policyManaged by LinkedIn

When you close your Callengo account, operational data (contacts, call records, campaign data, integration credentials, AI conversations) is permanently deleted within 90 days of account closure, following a period during which you may export your data. Billing history, transaction records, and other financial data required by applicable law are retained regardless of account closure.

12International Data Transfers

Callengo is incorporated in the United States and our primary infrastructure is located in the United States. Personal data that we collect may be transferred to, stored, and processed in the United States or other countries where our Sub-processors operate.

If you are located in the European Union, European Economic Area, United Kingdom, or Switzerland, we ensure that transfers of your personal data to countries that do not provide an adequate level of protection are made using appropriate safeguards, including:

  • Standard Contractual Clauses (SCCs). For transfers to the United States and other third countries, we rely on the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) as an appropriate transfer mechanism. Our Data Processing Addendum (available at callengo.com/legal/dpa) incorporates the applicable SCCs.
  • EU-US Data Privacy Framework. Where applicable, we rely on the EU-US Data Privacy Framework and its UK and Swiss equivalents as an additional adequacy mechanism for transfers to Sub-processors certified under the Framework.

By using the Service from outside the United States, you acknowledge that your personal data will be transferred to and processed in the United States and other countries. We take steps to ensure that such transfers are made in compliance with applicable data protection law.

13Your Rights and Choices

13.1 All Users

  • Account Information. You may access, review, and update most of your account profile information at any time through your Account Settings within the Application.
  • Communication Preferences. You may opt out of marketing and promotional emails by clicking the "unsubscribe" link in any such email. You cannot opt out of transactional emails necessary to operate your account.
  • Data Export. You may export your contact data from the Application in CSV, JSON, or XLSX format at any time through the Contacts section of the Application.
  • Account Deletion. To request deletion of your Callengo account, please contact us at privacy@callengo.com. We will process your request in accordance with our data retention obligations.
  • Analytics Opt-Out. You may opt out of behavioral analytics tracking by enabling the "Do Not Track" setting in your browser. The Application respects the Do Not Track browser signal for product analytics. You may also manage cookie preferences through the Cookie Settings tool on the Website.

13.2 European Union and EEA Residents: GDPR Rights

If you are located in the EU or EEA, you have the following rights under the General Data Protection Regulation:

RightGDPR ArticleDescriptionHow to Exercise
Right of AccessArt. 15Request confirmation of whether we process personal data about you and receive a copy of that data.Email privacy@callengo.com
Right to RectificationArt. 16Request correction of any inaccurate personal data we hold about you.Account Settings or privacy@callengo.com
Right to ErasureArt. 17Request deletion of your personal data where certain conditions apply, subject to exceptions.Email privacy@callengo.com
Right to RestrictionArt. 18Request that we restrict the processing of your personal data in certain circumstances.Email privacy@callengo.com
Right to Data PortabilityArt. 20Receive your personal data in a structured, machine-readable format.Data export in Account Settings
Right to ObjectArt. 21Object at any time to processing of your personal data based on legitimate interests.Email privacy@callengo.com
Right to Withdraw ConsentArt. 7(3)Withdraw consent at any time where processing is based on consent.Cookie Settings or privacy@callengo.com
Right to Lodge a ComplaintArt. 77Lodge a complaint with the competent supervisory authority.Agencia Española de Protección de Datos (AEPD), aepd.es

We respond to data subject rights requests within 30 days of receipt. Where requests are complex or numerous, we may extend this period by an additional 60 days with prior notice.

13.3 California Residents: CCPA / CPRA Rights

If you are a California resident, you have the following rights under the California Consumer Privacy Act (Cal. Civ. Code §§ 1798.100–1798.199.100) and the California Privacy Rights Act:

  • Right to Know. Request disclosure of the categories and specific pieces of personal information we collect about you, the purposes for which we use it, and the categories of third parties with whom we share it.
  • Right to Delete. Request deletion of personal information we have collected about you, subject to certain exceptions.
  • Right to Correct. Request correction of inaccurate personal information.
  • Right to Opt-Out of Sale or Sharing. Callengo does not sell personal information. Callengo does not share personal information for cross-context behavioral advertising.
  • Right to Limit Use of Sensitive Personal Information. We limit our use of sensitive personal information (including IP addresses) to purposes necessary to provide the Service.
  • Right to Non-Discrimination. You will not be denied services, charged different prices, or treated differently for exercising your CCPA rights.

To submit a CCPA request, contact us at privacy@callengo.com. We will respond within 45 calendar days.

13.4 Service Provider Relationship for Contact Data

When Callengo processes the personal information of individuals on behalf of its business customers (Contact data), Callengo acts as a "service provider" under the CCPA. As a service provider, Callengo is prohibited from retaining, using, or disclosing Contact data for any purpose other than performing the services specified in the agreement with the customer, combining Contact data from different customers, or using Contact data for Callengo's own commercial purposes.

14Cookies and Tracking Technologies

For detailed information about the cookies and similar tracking technologies used on the Callengo Website and Application, including the specific cookies set, their purpose, duration, and how to manage your preferences, please refer to our Cookie Policy available at callengo.com/cookies.

14.1 Website (callengo.com): Consent-Based Tracking Architecture

The Website implements a privacy-by-default tracking architecture using the following components:

  • Google Consent Mode v2. All tracking tags on the Website are governed by Google Consent Mode v2, which is configured to default all storage types (analytics_storage, ad_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, security_storage) to "denied" until you provide explicit consent. A 500ms wait period is configured to ensure your consent preferences are loaded before any tags fire.
  • Usercentrics Consent Management Platform (CMP). The Website uses Usercentrics, an EU-based Consent Management Platform, to present you with a cookie consent banner upon your first visit. Usercentrics manages consent state for all non-essential tracking technologies, stores your consent preferences, and communicates your choices to Google Consent Mode v2 and all downstream tags. You can update your preferences at any time via the cookie settings link in the Website footer.
  • Google Tag Manager (GTM). All tracking tags are deployed and managed centrally through Google Tag Manager (container GTM-MXFGV52S). GTM itself does not set cookies but serves as the orchestration layer that loads tags only when the appropriate consent has been granted.

The following tracking technologies are loaded via GTM on the Website, subject to consent:

TechnologyProviderCookie(s) SetPurpose
Google Analytics 4Google LLC_ga, _ga_*Website analytics: page views, sessions, scroll depth, outbound clicks, and 14 custom events
HubSpot Tracking CodeHubSpot Inc. (EU1)hubspotutk, __hssc, __hssrc, __hstcCRM tracking: UTM capture, session association, lead attribution on form conversion
LinkedIn Insight TagLinkedIn Corp.li_sugr, bcookie, lidc, UserMatchHistory, AnalyticsSyncHistory, ln_orAd attribution: LinkedIn campaign measurement and retargeting audience building

No non-essential cookies are set until you grant consent. If you decline non-essential cookies or do not interact with the consent banner, only strictly necessary cookies (such as Usercentrics consent state storage) are set. Google Consent Mode v2 ensures that even Google's own tags respect your consent preferences by blocking cookie writes and data collection when consent has not been granted.

14.2 Application (app.callengo.com)

The Application uses product analytics tools (PostHog) to track how authenticated users interact with Application features. These tools use pseudonymized identifiers (your account UUID, not your email address) to track usage. Session recordings are captured with sensitive field masking. Strictly necessary cookies (authentication session cookies) are always active in the Application as they are required for the Application to function.

14.3 Managing Your Preferences

  • Website cookie consent. Click the cookie settings link in the Website footer to open the Usercentrics consent dialog and update your preferences at any time. You may grant or revoke consent for each category of cookies independently.
  • Browser controls. Most web browsers allow you to block or delete cookies through browser settings. Note that blocking all cookies may impair Website functionality.
  • Do Not Track. The Website and Application respect the Do Not Track (DNT) browser signal. When DNT is enabled, non-essential tracking is suppressed.
  • Google Ads opt-out. You may opt out of personalized advertising from Google at ads.google.com/settings.
  • LinkedIn opt-out. You may opt out of LinkedIn advertising at linkedin.com/psettings/advertising.

15Children's Privacy

The Service is not directed to individuals under the age of eighteen (18). We do not knowingly collect personal data from children under 18. If you believe that we have inadvertently collected personal data from a child under 18, please contact us immediately at privacy@callengo.com and we will take steps to delete such information as promptly as possible.

16Call Recording and Transcript Disclosure

All calls initiated through the Callengo platform are recorded by default. Call recordings and transcripts are stored in your Callengo account and are accessible to authorized members of your company account. You are solely responsible for ensuring that you have obtained all legally required consents to record calls in every jurisdiction where your campaign calls are placed or received.

In the following U.S. states, among others, all parties to a telephone call must consent to the call being recorded before recording may lawfully begin: California, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, New Hampshire, Oregon, Pennsylvania, and Washington. Please refer to our Compliance page for detailed information about call recording consent obligations by jurisdiction.

17Data Breach Notification

In the event of a personal data breach that is likely to result in risk to your rights and freedoms, we will:

  • Notify affected EU/EEA residents and the relevant supervisory authority (AEPD) within 72 hours of becoming aware of the breach where required by GDPR Articles 33 and 34;
  • Notify affected Wyoming residents and, where applicable, the Wyoming Attorney General in accordance with the Wyoming Data Security Act (Wyo. Stat. §§ 40-12-501 et seq.);
  • Notify affected customers where their Customer Data has been accessed or disclosed;
  • Take prompt steps to contain, remediate, and investigate the breach; and
  • Maintain records of all security incidents, including those that do not require formal notification.

To report a security concern or potential breach, please contact us immediately at legal@callengo.com.

18Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technologies, legal requirements, or for other operational, legal, or regulatory reasons. When we make material changes, we will:

  • Post the updated Privacy Policy on this page with a revised "Last Updated" date;
  • Send an email notification to the primary email address associated with your account; and
  • Display a notice in the Application.

Your continued use of the Service after the effective date of any change constitutes your acceptance of the updated Privacy Policy. If you do not agree to the updated Privacy Policy, you must cease using the Service.

19Contact Us

For questions, concerns, or requests regarding this Privacy Policy or our privacy practices, please contact us:

EntityFuentes Digital Ventures LLC
BrandCallengo
Address5830 E 2nd St, Ste 7000 #20312, Casper, WY 82609, United States
Privacyprivacy@callengo.com
Legallegal@callengo.com
Websitehttps://callengo.com

EU / EEA Supervisory Authority

Agencia Española de Protección de Datos (AEPD)
C/ Jorge Juan, 6 · 28001 Madrid, Spain
www.aepd.es

This Privacy Policy was last updated on March 27, 2026. By using the Callengo Service, you acknowledge that you have read and understood this Privacy Policy.