Privacy Policy
Last updated July 21, 2026
1. Scope and roles
This Policy explains how RevenueCallout(“RevenueCallout,” “we,” or “us”) handles personal information through the RevenueCallout website, application, and related support services (the “Service”). The Service is intended for business use by adults, not children.
For meeting, CRM, and sales content submitted by a business customer, that customer normally decides why and how the data is used and RevenueCallout processes it on the customer's instructions. For account administration, billing, security, support, and our own business operations, RevenueCallout determines the purposes of processing. Individuals appearing in a customer's content should contact that customer first; we will assist the customer as required.
2. Information we collect
Account and workspace data. Name, business email, organization, role, authentication identifiers, settings, and team membership.
Customer content. Meeting recordings or transcripts, speaker names, sales-process material, CRM records, uploaded files, notes, and feedback provided by a customer.
AI outputs and inferences. Call summaries, risk scores, predicted outcomes, coaching observations, tasks, briefs, and email drafts generated from customer content.
Commercial data. Plan, subscription status, invoices, transaction identifiers, and limited payment metadata. Payment-card details are handled by the payment provider, not stored by RevenueCallout.
Integration data. Tokens, account identifiers, webhook data, and records exchanged with meeting, CRM, email, and calendar services enabled by a customer.
Device and usage data. IP address, browser and device information, login and security events, feature usage, errors, request identifiers, and diagnostic logs.
Support and communications. Messages, support requests, survey responses, and records of legal or privacy requests.
Sales conversations may incidentally contain sensitive information. Customers must avoid submitting health information, payment-card data, government identifiers, account credentials, information about children, or other regulated data unless RevenueCallout has agreed in writing.
3. Sources
We receive information directly from users and meeting participants; from the customer that provides or records a conversation; automatically from browsers and systems; and from customer- directed services such as Zoom, Google Meet, Microsoft Teams, Meeting BaaS, Fathom, Fireflies, HubSpot, Keap, Stripe, and other integrations a customer enables.
4. How we use information
- provide, authenticate, maintain, and secure the Service;
- transcribe or ingest calls and generate requested analyses, tasks, briefs, and drafts;
- operate customer-directed CRM, meeting, billing, and email integrations;
- provide support, administer subscriptions, and communicate about the Service;
- detect abuse, investigate incidents, debug failures, and improve reliability;
- comply with law, enforce agreements, and protect rights and safety; and
- create aggregate or de-identified statistics that are not reasonably linkable to a person.
5. AI processing and automated output
Customer content may be sent to the AI provider identified on our Subprocessor List to generate the output requested by the customer. AI output is probabilistic and may be incomplete, inaccurate, or biased. RevenueCallout does not use the Service to make decisions about credit, housing, insurance, healthcare, education admission, legal eligibility, or employment, and customers may not use a score as the sole basis for such decisions.
RevenueCallout does not sell customer content. We do not intentionally use customer content to train a public foundation model. Provider handling may depend on the applicable account configuration and contract; current providers and functions are disclosed on the Subprocessor List.
6. Disclosures
We may disclose information:
- to vendors processing data for hosting, databases, AI, monitoring, meetings, communications, support, and billing;
- to integrations and recipients selected or authorized by the customer;
- to professional advisers under duties of confidentiality;
- in a merger, financing, acquisition, reorganization, or sale, subject to appropriate safeguards;
- when reasonably necessary to comply with law or protect the Service, customers, or others; and
- with a person's direction or consent.
We do not sell personal information for money. We do not currently share personal information for cross-context behavioral advertising and do not use third-party advertising cookies in the Service.
7. Recording notice and consent
Customers control when calls are recorded or submitted. They must provide all legally required notices, obtain consent from every participant where required, preserve evidence of consent, and offer a reasonable non-recorded alternative. See the Recording & AI Notice.
8. Retention and deletion
During the closed beta, the default is to retain account and Customer Content until the workspace owner deletes it or sends a verified deletion request. We do not currently promise automatic deletion after a fixed number of days. After verified account termination, we will delete active Customer Content within a commercially reasonable period unless an Order Form specifies a schedule or law requires retention. Transaction, consent, security, and dispute records may be retained for the applicable limitation, tax, or recordkeeping period. Deletion from provider backups occurs on their configured recovery cycles, during which the data is isolated from ordinary use and is not restored except for recovery. Customers that need fixed retention periods must agree them in an Order Form before submitting data.
9. Security
We use technical and organizational safeguards described in our Security Overview. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
10. U.S. state privacy rights
Depending on residency and applicable law, a person may have rights to know, access, correct, delete, or obtain a copy of personal information, and to opt out of certain sale, sharing, targeted advertising, or profiling. We do not discriminate for exercising applicable rights. An authorized agent may submit a request where permitted. We may verify identity and authority, and some information may be exempt.
Submit a request to hello@revenuecallout.com with “Privacy Request” in the subject. If the request concerns customer-controlled call or CRM content, identify the customer involved. Where applicable, you may appeal a denied request by replying with “Privacy Appeal.”
11. International access
RevenueCallout is operated for the United States. Information may be processed in the United States and other locations used by listed providers. Customers must not use the Service for data subject to international transfer restrictions unless the parties have executed the required addendum and safeguards.
12. Children
The Service is not directed to anyone under 18, and customers may not submit information about children. Contact us if you believe such information has been provided.
13. Changes
We may update this Policy. We will change the date above and provide additional notice when a material change requires it. Changes apply prospectively unless law permits otherwise.
14. Contact
Contact RevenueCallout at hello@revenuecallout.com.