Subprocessor List
Walkie Pro
Last updated: 30 September 2026 Version: 2.6
What this is
A subprocessor is a company we use to help operate Walkie Pro that may access or process your personal information in the course of doing so.
We publish this list so you know exactly who touches your data. It supplements our Privacy Policy.
Every provider below is bound by a written agreement limiting them to processing your information only to provide services to us, and requiring appropriate security.
1. Providers that receive your communications content
Read this section first. These providers receive the substance of what you say, write, and share — not just metadata.
| Provider | What they receive | Purpose | Location | Training excluded |
|---|---|---|---|---|
| Supabase Inc. | Everything. Account data, messages, photos, videos, documents, voice memos, call recordings, transcripts, summaries, lists, notes, map pins | Database, file storage, authentication, backend infrastructure | United States | N/A — infrastructure, no model training |
| LiveKit Inc. | Live call audio, and call recordings written into our storage. Also connects calls to ordinary phone numbers via a SIP trunk. Calls to our support line: the call audio and the recording; through LiveKit Inference, what the caller says goes to Deepgram (speech recognition), the conversation to Google Gemini (the language model), and the assistant’s replies to Cartesia (its voice), each with zero data retention. LiveKit keeps its own diagnostic copy of each support call for 30 days, with personal data redacted except the calling number (it is part of the call’s internal name). | Real-time voice call transport, recording, and telephone connectivity; the AI voice assistant that answers our support line | United States (us-east) | Excluded from training |
| Twilio Inc. (as LiveKit’s telephone carrier) | Call audio for calls to ordinary phone numbers. Twilio carries the telephone leg of every outside call | Telephone network connectivity | United States | N/A |
| Deepgram Inc. | Call recordings, including voicemails; voice memo and walkthrough audio; and the audio of videos where video transcription is on, sometimes as the video file itself. For calls, also the job names, the street part of job-site addresses, and the names of the people on the call, to improve word recognition. Through LiveKit Inference, what callers say on calls to our support line, with zero data retention | Speech-to-text transcription | United States | Excluded from training |
| Anthropic PBC | Full verbatim call transcripts, unredacted. Also your content when you use Ask. Transcripts of calls to our support line, and the questions callers asked that no Help Center article answered | Call summaries, per-job summaries, action items, question answering; support-call summaries and draft Help Center fixes | United States | Excluded from training |
| Google LLC (Gemini) | The text of your content, to make it searchable — messages, notes, list items, file names and change notes, photo and video captions and descriptions, voice memo, walkthrough, and call transcripts, summaries and action items, follow-up notes, and calendar events, with the job, conversation, person, and date each belongs to — and every question asked in Ask. Transcripts and summaries submitted for translation. Photos, with their captions and job details, if they are described automatically. Messages and voice memo, walkthrough, and video transcripts, with their job and conversation details, if we switch summary writing to Gemini. Through LiveKit Inference, the conversation on calls to our support line, with zero data retention | Machine translation; search indexing and Ask; automatic photo descriptions and summaries, where used; the language model behind the support-line assistant | Global (no regional guarantee) | Excluded from training |
| Google LLC (Firebase Cloud Messaging) | Push notification content — including message text, sender name, and conversation name | Push notification delivery | United States | N/A |
| SparrowDesk (customer support) | The messages you send us — through the contact form, the notes you add when you tell us a help article did not help, and live chat on walkiepro.com — with your name and the email address or phone number you asked us to reply to — a phone number only if you ticked the box to be called or texted back. Also your name, email address, and phone number, if you gave one, when you create a Walkie Pro account. For calls to our support line that need our team: the AI summary of the call, the next step, and your email address or phone number — never the full transcript | Customer-support inbox and live chat; follow-ups from support calls | ||
| Attio (sales CRM — support calls) | If you call our support line about starting with Walkie Pro and give us an email address: that address, the number you called from, and a note about the call | Following up with people who called about getting started | Not yet confirmed | Not yet confirmed |
On Firebase. It is natural to assume a push notification service receives only a delivery token. Ours carries the message itself, which means Google receives communications content. We would rather say so than let you assume otherwise.
On unredacted transcripts. There is no redaction or masking step between a call transcript and the AI provider that summarizes it. Everything said on the call — names, prices, addresses, phone numbers — is sent as spoken.
On search indexing. Content is sent to Google Gemini to be indexed as it is saved, whether or not anyone uses Ask, and that includes call transcripts. It is not redacted either.
2. Providers that receive account, device, or transaction information
| Provider | What they receive | Purpose | Location |
|---|---|---|---|
| Apple Inc. | Account identifiers | Sign in with Apple, app distribution | United States |
| Google LLC | Account identifiers | Google Sign-In, app distribution | United States |
| Google LLC (Google Play — Android only) | For each subscription charge and refund made from the Android app: the amount, the tax, the time, your country, and a transaction token Google issued. Google does not process the payment | Reporting Android subscription transactions to Google, as its external content links programme requires | United States |
| Stripe, Inc. | Your email address and a Walkie account identifier; what you enter on Stripe’s checkout page, such as your name, billing address, and payment details; subscription and invoice records. Stripe holds your payment details — we never see them | Payment processing, subscription billing, invoices, and sales-tax calculation | United States |
| Functional Software, Inc. (Sentry) | Device model, OS and app version, error diagnostics, and limited context around a crash | Crash and error reporting | United States |
| Google LLC (Maps Platform) | Address queries and approximate location for map display | Address lookup, map rendering | United States |
| Twilio Inc. (via Supabase) | Phone number, verification code | SMS verification for sign-in | United States |
| Twilio Inc. (website download link) | A mobile number, for one message. Nothing else, and no recurring send | Delivering the download-link text you asked for from walkiepro.com — Privacy Policy §6.7 | United States |
| Twilio Inc. (support line) | The number you are calling from, to send a one-time verification code through Twilio Verify. We do not store the code. And, only if you said yes on the call, one text with the app link or a recap of the call | Verifying callers to our support line; the texts they said yes to — Privacy Policy §2.7 and Text Messaging Terms §2.6 | United States |
| Plus Five Five, Inc. (Resend) | An email address. No content beyond the email we send you | Delivering the download-link email you asked for; the verification and access emails for a jobsite access request, if you chose email; the email confirming a message you sent through the contact form; the recap of a call to our support line; and, if you asked for them, product updates — Privacy Policy §2.7, §6.9, §6.10, §6.11 and §6.12 | United States |
| Attio (sales CRM) | Account information only. Your name, email address, phone number if you gave one, and your Walkie Pro plan, when you create an account. No messages, calls, or content from the app. What it receives about a call to our support line is listed in Section 1 | Keeping a customer record of who has signed up | Not yet confirmed |
| CookieYes Limited | Website visitor data, cookie consent choices | Cookie consent management on walkiepro.com | United Kingdom |
3. Where your data is processed
All processing takes place in the United States, except where the table above indicates otherwise.
If you use the Services from outside the United States, your information is transferred to and processed in the United States. See Terms of Use §23.
4. Model training
We require providers who receive your content to exclude it from training their models.
This applies to Deepgram, Anthropic, Google, and LiveKit. Supabase does not train models on customer data.
Note on Google. Google’s data-use terms differ substantially depending on which product tier is used — consumer-grade AI Studio and enterprise Vertex AI are not the same on training, retention, or residency.
5. Changes to this list
We will update this page when we add or replace a subprocessor.
Where a new subprocessor will receive the contents of your communications, we will update this list at least 30 days before they begin processing, and note the change below.
If you object to a new subprocessor, write to support@walkiepro.com. Because our providers are integral to how the Services work, we may not be able to offer the Services without them — but we would rather hear your objection than not.
6. Change history
| Date | Change |
|---|---|
| 26 August 2026 | Initial publication |
| 13 September 2026 | Added Twilio as the provider for the walkiepro.com download-link text. Added Resend for the download-link email and product updates. Replaced Termly with CookieYes as our consent platform |
| 24 September 2026 | Added SparrowDesk, our customer-support platform, which receives the messages you send us through the contact form, help-article feedback, and live chat. Added Attio, our sales CRM, which receives account information when you create an account |
| 25 September 2026 | Resend now also sends the email confirming a message you sent through the contact form. SparrowDesk receives a phone number instead of an email address when you ask to be called or texted back |
| 28 September 2026 | The Google LLC (Gemini) entry now lists everything Gemini receives: besides text for translation, the text of your content and every Ask question, to make your records searchable, photos where they are described automatically, and the content of summaries if we switch summary writing to Gemini. Google is not a new subprocessor. The Deepgram Inc. entry now also lists walkthrough and video audio, voicemails, and the names sent to improve recognition on calls. Deepgram is not a new subprocessor |
| 29 September 2026 | Our support line will be answered by an AI assistant. The LiveKit Inc. entry now covers it: through LiveKit Inference, Deepgram, Google Gemini and Cartesia process support calls with zero data retention; LiveKit keeps a 30-day diagnostic copy with personal data redacted except the calling number. Cartesia is new, and Attio will receive a note about some support calls. Both changes take effect when the support line opens, without the 30-day advance notice described above. Anthropic, SparrowDesk, Resend and Twilio also handle support calls; none of them is a new subprocessor |
7. Contact
Questions about this list, or a request for a copy of our agreement with any provider:
Walkie Corporation (dba Walkie Pro) 23945 Calabasas Rd, Suite 101, Calabasas, CA 91302, United States support@walkiepro.com · +1 (323) 504-7400