Sub-processors

DigitalOcean, LLC

Application hosting, the production database, and object storage (DigitalOcean Spaces) for call-recording audio, uploaded documents and support attachments. Our storage region is New York (nyc3), in the United States.

Data processed: All platform data, since this is where the application and its database run.

Twilio Inc.

Phone number provisioning, outbound and inbound call routing, answering-machine detection, media streams, call recording, and SMS delivery.

Data processed: Called and calling phone numbers, call metadata and timing, call audio in transit, and SMS message content.

OpenAI, L.P.

GPT Live / Realtime — the conversational model, speech-to-text, and text-to-speech on live sales calls. ClinchRev calls the OpenAI API directly.

Data processed: The agent script and the live conversation as it happens.

Google LLC — Gemini API

Text-model inference for AI script drafting, call and reply classification, lead-enrichment summaries and suggested reply drafts.

Data processed: Whatever is in the prompt for the task at hand — typically call transcripts, email reply text, lead records and the script being worked on.

Resend

Delivery of ClinchRev's own transactional email: password-reset codes, billing receipts, booking confirmations and system alerts. Not used for your outreach campaigns, which go through your own connected mailbox.

Data processed: Recipient email address and the content of the transactional message.

Stripe, Inc.

Payment processing for ClinchRev subscriptions, and for billing your own customers if you enable that feature.

Data processed: Billing name and email, subscription and invoice records, and payment-method details. Full card numbers are handled by Stripe and are not stored by ClinchRev.

Braintree (PayPal, Inc.)

An alternative payment processor for ClinchRev subscriptions, used where Braintree is the configured billing provider for an account.

Data processed: Billing contact details and vaulted payment-method tokens. As with Stripe, ClinchRev does not store full card numbers.

Google LLC — Workspace APIs

Sending outreach email from your Gmail account, detecting replies to email ClinchRev sent, and creating Google Calendar events. Scopes requested are gmail.send, gmail.readonly, calendar, and basic profile. See Section 3b of the Privacy Policy for the Google Limited Use disclosure.

Data processed: Outbound message content, messages threaded with email ClinchRev sent, and calendar events ClinchRev creates.

Microsoft Corporation — Graph API

Sending outreach email from your Outlook account, detecting replies, and creating Microsoft Calendar events. Scopes requested are Mail.Send, Mail.Read, Calendars.ReadWrite, User.Read and offline_access, and nothing else.

Data processed: Outbound message content, messages threaded with email ClinchRev sent, and calendar events ClinchRev creates.

Zoho Corporation — Zoho Mail

Sending and receiving outreach email through a connected Zoho mailbox, over the Zoho Mail API or SMTP/IMAP.

Data processed: Outbound message content and replies to it, plus the mailbox credentials or OAuth tokens you supply.

HubSpot, Inc.

Two-way sync with your own HubSpot CRM, invoked only for the records you authorise.

Data processed: Contact, company and deal records you choose to sync.

Apollo.io

Lead search and contact enrichment, run against your own Apollo account using the API key you provide.

Data processed: The search parameters you specify and the lead records returned. Your existing lead data is not sent to Apollo beyond what a lookup requires.