Torch CRMCRM for manufacturers' reps

TEC World Subprocessors

Last updated 2026-11-11

The third parties that may process customer data on our behalf to run the service: what each one does, what it receives and when. Some receive data only when a feature is switched on or when your workspace connects an integration, and each of those says whether it is on today.

Core subprocessors (always in use)

These run the service for every workspace.

Vercel

  • Purpose: Application hosting and delivery.
  • Data: Application traffic, request metadata and logs.
  • Region: Server functions in US West (Oregon).
  • Assurance: SOC 2 report: available from the vendor.
  • Vendor pages: Data processing terms · Security

Supabase

  • Purpose: Database, sign-in and file storage.
  • Data: All customer data in the service, sign-in data and uploaded files.
  • Region: AWS us-west-2 (Oregon, United States).
  • Assurance: SOC 2 report: available from the vendor.
  • Vendor pages: Data processing terms · Security

Stripe

  • Purpose: Billing and payment processing.
  • Data: Billing contact and subscription and payment details. We do not store full card numbers.
  • Status: On.
  • Vendor pages: Data processing terms · Security

Sentry

  • Purpose: Error monitoring.
  • Data: Error reports: error messages (including any text written into one), stack traces, page and API addresses without their query strings and with share-link tokens removed, and a trail of recent requests, page changes and clicks. Automatic collection of request and response bodies, headers, cookies, user details and IP addresses, database query data and on-screen labels is switched off.
  • Vendor pages: Data processing terms · Security

Hetzner Online

  • Purpose: Virus scanning of uploaded documents and attachments. We run the scanner ourselves on a Hetzner cloud server; Hetzner provides the machine.
  • Data: The contents of each file it scans, in transit only: held in memory for the scan, never written to disk and not stored. No file name, workspace or record identifier is sent.
  • Status: On.
  • Assurance: ISO/IEC 27001 certificate: available from the vendor.

Twilio (Verify)

  • Purpose: Text-message sign-in codes for two-step verification.
  • Data: The mobile numbers of users who choose text-message codes, and the one-time code messages sent to them. No CRM data.
  • Status: On.
  • Vendor pages: Data processing terms · Security

Google Workspace

  • Purpose: Our own business email, including our support mailbox, and our calendar for calls booked on our website. Not used to send CRM email.
  • Data: Support requests and other mail you send us: sender name and address, message contents and attachments. When you book a call on our website: your name, email address, phone number, company and notes, and the time you picked.
  • Vendor pages: Data processing terms · Security

Postmark (account email)

  • Purpose: Sending our own account email: workspace invitations, password-reset links, sign-in codes and security alerts. Not used to send CRM email.
  • Data: The recipient's email address and name, and the message itself, including any sign-in link or code in it. Postmark keeps delivery and bounce records. No CRM data.
  • Vendor pages: Security

Better Stack

  • Purpose: Uptime monitoring and status page.
  • Data: No customer data: it checks our public health endpoints. If status-page subscriptions are turned on, it also holds the email addresses of people who subscribe.
  • Vendor pages: Data processing terms · Security

Google Ads

  • Purpose: Measuring our own ads: whether a visitor who clicked one of our ads later signs up or registers interest.
  • Data: No customer data: only visitors to our public web pages (home, pricing, sign-up and similar, never the service itself). The visitor's browser loads Google's tag, which sets a Google Ads cookie and sends Google the page address (trimmed to the ad's campaign tags and click id), the referring site and the browser's IP address and signals, and a sign-up event without any form contents. Ad personalization is off. It loads only after the visitor chooses Accept on our cookie notice, and never when the browser sends Global Privacy Control.
  • When: Only on our public web pages.
  • Status: On.

PromoteKit

  • Purpose: Running our partner (affiliate) program: remembering which partner's link a visitor arrived from, and working out the partner's commission on that customer's payments.
  • Data: On our public web pages, the visitor's browser loads PromoteKit's script, which sets a referral cookie and sends PromoteKit the visit to a partner's link. When that visitor subscribes, the referral id is added to the Stripe checkout, and PromoteKit reads that customer's email address, subscription and payment amounts from Stripe to calculate the partner's commission. No CRM data. It loads only after the visitor chooses Accept on our cookie notice, and never when the browser sends Global Privacy Control.
  • When: Only on our public web pages and for customers who arrived through a partner's link.
  • Status: On.

LinkedIn (Insight Tag)

  • Purpose: Measuring our own ads: whether a visitor who clicked one of our LinkedIn ads later signs up or registers interest.
  • Data: No customer data: only visitors to our public web pages (never the service itself). The visitor's browser loads LinkedIn's tag, which sets LinkedIn cookies and sends LinkedIn the page address (only when it carries nothing but campaign tags and LinkedIn's click id), the referring page, the browser's IP address and signals, and a sign-up event without any form contents. It loads only after the visitor chooses Accept on our cookie notice, and never when the browser sends Global Privacy Control.
  • When: Only on our public web pages.
  • Status: On.

YouTube (product tour video)

  • Purpose: Playing our product tour video on our home page.
  • Data: No customer data: only visitors to our home page, and only after they press play. Until then the page shows our own picture and nothing is sent to YouTube. When the visitor presses play, their browser loads the video from YouTube's privacy-enhanced youtube-nocookie.com player, which receives the browser's IP address and signals and may store data in the browser. (Separately, a workspace's knowledge base can embed training videos the workspace itself links from YouTube, Vimeo or Loom.)
  • When: Only on our home page, after the visitor presses play.

Cloudflare (R2 file backup)

  • Purpose: Nightly backup copy of uploaded attachments and documents, images pasted into notes and knowledge-base uploads (not voice recordings), so a deleted or damaged file can be restored.
  • Data: The copied files, encrypted by us before they are sent, so Cloudflare cannot read their contents. Cloudflare can see each copy's file name and path (which include workspace and record identifiers and the original file name), size, file type and upload time.
  • Region: Eastern North America
  • Vendor pages: Security

AI subprocessors

These receive customer data only through the AI features listed under "What each AI feature sends" below.

Anthropic (Claude)

  • Purpose: AI statement reading, report summaries, the voice assistant's proposed actions and the assistant chat.
  • Data: Only what the AI features below send, when they run.
  • Vendor pages: Data processing terms · Security

OpenAI

  • Purpose: Business-card scanning and the voice assistant's audio transcription.
  • Data: Only what the AI features below send, when they run.
  • Vendor pages: Data processing terms · Security

What each AI feature sends

Business-card scanning

  • Sent to: OpenAI
  • What is sent: The card photo a user takes or uploads on New Contact, New Company or New Lead (name, title, company, email, phone and address on the card). We do not store the photo; the fields read from it fill in the form, which the user checks before saving.
  • When: Each time a user scans a card. On for every workspace; a workspace admin can turn it off in Settings > Workspace > AI processing.

AI statement reading

  • Sent to: Anthropic (Claude)
  • What is sent: The commission statement PDF a user uploads, or one a user chooses to read from the commission intake list (manufacturer, customer names, invoice numbers and amounts). A person reviews every row it reads before it is saved.
  • When: Only when a user with permission to manage commissions uploads or reads a statement. On for every workspace.
  • Status: On.

Report summaries

  • Sent to: Anthropic (Claude)
  • What is sent: The uploaded report file (a PDF as is, a spreadsheet, CSV or text file as text, cut at 60,000 characters and at most six sheets), its file name and the name of the manufacturer it is linked to.
  • When: After each report upload, and whenever a user asks for a new summary. On for every workspace; a workspace admin can turn it off in Settings > Workspace > AI processing. A user reviews the summary before it goes to anyone.
  • Status: On.

Voice assistant (Ginger)

  • Sent to: OpenAI and Anthropic (Claude)
  • What is sent: To OpenAI, the recording's audio for transcription. To Anthropic, the transcript or typed instruction with the assistant's fixed instructions and the current date, time and workspace time zone. No other CRM records, names or ids are sent to either. Every proposed change is checked against the user's own workspace before anything is written.
  • When: In workspaces whose plan includes the assistant, each time a user records, uploads or types an instruction for it, and for a recording only after the user confirms everyone recorded consented. The user reviews every proposed change before it is saved.
  • Status: On.

Assistant chat

  • Sent to: Anthropic (Claude)
  • What is sent: The conversation a user types and the CRM records the assistant looks up for that user: names, listed fields and links of records the user can already see, at most 20 per lookup. It is sent on the company's own Anthropic API key, which a workspace admin adds, never on ours. A drafted update goes to the assistant's review screen before anything is saved.
  • When: Each time a user sends a chat message, in workspaces that have the assistant and have added their own key.
  • Status: On.

Address lookup

These receive addresses only, each when the feature below is used.

Google Maps Platform (Places API)

  • Purpose: Street-address type-ahead on company and contact Street Address fields (United States addresses).
  • Data: Sent from our server only: the partial street address a signed-in user types, a random per-typing-session id that identifies no person or record, and the place id of a suggestion they pick. No workspace, user or record id, name, email or IP address is sent. Nothing is stored by the lookup; the form saves only what the user confirms.
  • When: Only while street-address type-ahead is switched on, which applies to every workspace at once.
  • Status: Off.

US Census Bureau (Geocoder)

  • Purpose: Map locations for companies: turns company street addresses into map coordinates.
  • Data: Sent from our server only: each company's record id, street address, city, state and ZIP code, in one batch. No names, contacts or other CRM data.
  • When: Only when a workspace admin runs geocoding from Settings.

Zippopotam.us

  • Purpose: Fills in ZIP codes from city and state on the New Company form and the Manufacturers list.
  • Data: Sent from our server only: a city and state. No person, record or workspace identifier.
  • When: When a user leaves City or State on the New Company form with the ZIP code blank, or uses the fill-missing-ZIP-codes action on the Manufacturers list.

Integration subprocessors (only when you connect them)

These receive data only if your workspace connects the integration, and only the data within the connection you authorize.

HubSpot

Salesforce

Microsoft Outlook

  • Purpose: Email and calendar integration: the workspace's connected Outlook mailbox, and capture of each connected rep's Inbox and Sent mail, which needs your Microsoft 365 admin's consent.
  • Data: Email and calendar data within the connection scope you authorize. Rep capture reads each new Inbox and Sent message's subject, sender, recipients, times and Outlook's preview (at most the first 255 characters of the text), never the full body or attachments, and keeps it as an activity only when an outside participant is already a contact in the workspace.
  • When: Only for the reps your workspace connects.
  • Status: On.
  • Vendor pages: Data processing terms · Security

Google (Gmail API, Google Calendar API, Cloud Pub/Sub)

  • Purpose: Gmail and Google Calendar integration for Google Workspace customers: the workspace's connected mailbox, and capture of each connected rep's Inbox and Sent mail through the domain-wide delegation your Workspace admin grants.
  • Data: Email and calendar data within the connection scope you authorize. Rep capture reads each new Inbox and Sent message's sender, recipients, subject, message id, date and Gmail's snippet (the first characters of the text), never the full body or attachments, and keeps it as an activity only when an outside participant is already a contact in the workspace. Change notifications carry the mailbox address and a change marker, not message content.
  • When: Only for the mailboxes your workspace connects.
  • Status: On.
  • Vendor pages: Data processing terms · Security

Dropbox

Quickbase

  • Purpose: Accounting integration: reads the Quickbase app you point it at.
  • Data: Financial and billing records within the connection scope you authorize.
  • Vendor pages: Security

Power BI (Microsoft)

  • Purpose: Reporting and business intelligence.
  • Data: Reporting data within the connection scope you authorize.
  • Vendor pages: Data processing terms · Security

Jira (Atlassian)

  • Purpose: Issue and project tracking integration.
  • Data: Issue and project data within the connection scope you authorize.
  • Vendor pages: Data processing terms · Security

Trainual

  • Purpose: Training platform connector.
  • Data: For a workspace whose admin connects it: we receive its Trainual people's names, email addresses and status, their training progress and the titles of training subjects; we send the name and email address of each person the workspace invites, archive and restore requests, and the training search text users enter.
  • When: Only for workspaces that connect their Trainual account.
  • Status: On.

Gusto

  • Purpose: Payroll connector: reads only. Nothing is written to Gusto.
  • Data: For a workspace whose admin connects its own Gusto account: we receive its employees' names, email addresses, departments and job status, and each processed payroll's dates and per-employee pay totals (gross and net pay, hours, taxes, deductions and reimbursements), which go into Accounting. We send only the requests that read them.
  • When: Only for workspaces that connect their Gusto account.
  • Status: On.

Constant Contact

  • Purpose: Email marketing connector: lead and contact sync (no campaigns or mail sending).
  • Data: For a workspace whose admin connects its own Constant Contact account and turns on updates: we send and receive the selected leads' and contacts' names, email addresses, company, job title, list membership and email permission status.
  • When: Only for workspaces that connect their Constant Contact account and turn on updates.
  • Status: On.

Meta Platforms

  • Purpose: Facebook and Instagram lead ads connector: lead form submissions become leads, and campaign spend is read.
  • Data: For a workspace whose admin connects its own Meta login: we receive the answers people give on the workspace's lead forms (name, email, phone, company, job title and any custom question) with the form, ad and campaign names, and each campaign's daily spend, impressions, clicks and lead count. We send only the requests that read them and the Page subscription.
  • When: Only for workspaces that connect their Meta login.
  • Status: Off.

Odoo

  • Purpose: ERP connector: stock and order sync.
  • Data: Product, order and inventory records within the connection you configure.
  • Status: On.

Postmark

  • Purpose: Commission statement forwarding address: mail sent or forwarded to a workspace's statements address is received by Postmark and passed to the service.
  • Data: The whole message as sent: sender and recipient addresses, subject, headers, body and attachments. The service keeps only statement files (PDF, Excel, CSV) from a sender the workspace listed or one of its own users, virus-scanned; everything else is discarded.
  • When: Only when someone sends mail to a workspace's statements address.
  • Status: Off.
  • Vendor pages: Security

Snowflake

  • Purpose: Data warehouse connector: sends CRM records to your company's own Snowflake account and reads back the views your Snowflake administrator shares.
  • Data: Sent: companies, contacts, activities (including their subjects and call, email and meeting notes), leads, opportunities (including notes and lost reasons), samples, line sheets, manufacturers, users' names, email addresses and status, products with their cost, sales, quotes and quote lines, multipliers, price sheets, inventory, and commissions only when commission export is on, including deleted-row markers. Read back: companies, contacts, products, sales and inventory from the views you share.
  • When: Only when your workspace connects its Snowflake account, and only while the connector is switched on.
  • Status: Off.
  • Region: Your Snowflake account's region, which your company chooses.

Not our subprocessors

AI apps you connect

A member of your workspace can connect an AI app of their own to the service through our Model Context Protocol (MCP) server, by signing in from an AI app we have approved, or with a personal API key. The app receives only the records that member can see, and it can change data only through a connection that holds a write permission. The app's provider is your own vendor, chosen by your organization, not our subprocessor. A workspace admin can switch off AI app sign-in for the workspace; that switch does not affect a personal API key a member has pasted into an app.

Your browser's speech recognition

When a user dictates into a text box, their own web browser turns the speech into text: Chrome sends the audio to Google, Edge to Microsoft, and Safari to Apple or processes it on the device. We send nothing to these services and receive only the resulting text. A workspace admin can turn dictation off for the whole workspace.

Signing in with Google

A user can choose "Continue with Google" on the sign-in page instead of a password. They sign in at Google, under Google's own terms and privacy policy, and Google tells our sign-in service (Supabase, above) who they are: their name, email address, profile photo address and Google account ID. Google receives no customer data from us. Signing in with Google gives no access by itself: a user has access only after being invited to a workspace or provisioned into one, and password sign-in stays available. This is separate from the Gmail integration listed above, which a workspace admin connects.

Services you connect through Custom API

Custom API is not yet available. Once it is, a workspace admin will be able to connect another service's API, such as Apollo.io, Pipedrive or Microsoft Dynamics 365 Business Central, with their own account and key. The service reads only: it fetches records from that account and keeps them in your workspace. The service you connect is your own vendor, chosen by your organization, not our subprocessor.

Training videos you link

A workspace admin, or a user whose role lets them manage the knowledge base, can add a training video to the knowledge base by linking it from YouTube, Vimeo or Loom. The video plays from that site in the viewer's own browser, which the site can see (its address and browser details). We send these sites no customer data. The site is the one your organization chose to host its video on, not our subprocessor.

Your own email server

Outbound CRM email is sent through each workspace's own configured outgoing mail server, so that mail passes through no email-sending service of ours; your mail provider is under your own vendor management.

Changes to this list

We update this list when we add or replace a subprocessor, and record each change here.

  • 2026-11-11: Switched on PromoteKit (our partner program): a referral cookie on our public web pages, loaded only after you accept our cookie notice.
  • 2026-11-09: Added PromoteKit (our partner program), not switched on yet.
  • 2026-11-09: Google Workspace now also holds our calendar for calls booked on our website (name, email, phone, company, notes and the time picked).
  • 2026-11-09: Added LinkedIn (Insight Tag): a conversion cookie on our public web pages (not the service itself) that counts sign-ups from our LinkedIn ads.
  • 2026-11-03: Added Google Ads: a conversion cookie on our public web pages (not the service itself) that counts sign-ups from our ads.
  • 2026-10-23: Added Meta Platforms (Facebook and Instagram lead ads) under Integrations, not switched on yet.
  • 2026-10-22: Added the US Census Bureau geocoder and Zippopotam.us under Address lookup, Trainual, Constant Contact and Gusto (reads only) under Integrations, and training videos you link under Not our subprocessors.
  • 2026-10-22: The voice assistant (Ginger) is available to every workspace whose plan includes it, no longer a pilot.
  • 2026-10-22: Added services you connect through Custom API under Not our subprocessors.
  • 2026-10-22: Added Cloudflare (R2 file backup): an encrypted nightly copy of uploaded files.
  • 2026-10-19: Business-card scanning: the New Company page scans cards too.
  • 2026-10-19: Added signing in with Google under Not our subprocessors.
  • 2026-10-14: First version of this list.