Privacy Policy

Effective date: October 9, 2026 · Version v2026-10-09

Cache CRM (“Cache”, “we”, “us”) is a customer relationship management platform for home-service businesses. Cache CRM is a product of SoCal Cleaner, LLC. This policy explains what personal information we collect, where it comes from, why we collect it, who we share it with, how long we keep it, and what choices you have.

This policy covers two different groups of people, and the difference matters:

1. Information we collect

Account information

When someone creates a Cache account or is invited to a Workspace, we collect their name, email address, phone number, password credential (or Google sign-in identifier), role, company name, legal entity name, business address, business phone, timezone and any logo they upload. If a user signs in with Google, we receive their name, email address and profile image from Google — never their Google password. When you accept our Terms of Service or Privacy Policy, we record the version accepted, the date and time, a hashed form of your IP address, and your user agent.

Workspace (CRM) data

Workspaces enter and generate business records in Cache: contacts (names, phone numbers, email addresses, service addresses, tags, notes), leads, jobs and schedules, estimates, invoices and payment records, call logs, and message threads. This content belongs to the Workspace. We store and process it to provide the service, and we do not use it to build advertising profiles or sell it to anyone.

Messages and calls

Cache sends and receives SMS through Twilio and email through Resend on behalf of Workspaces. We store message and email content, sender and recipient addresses or numbers, timestamps and delivery status. For calls placed or received through Twilio we store call metadata (direction, duration, outcome) and, where a Workspace has enabled call recording with the consent that its state requires, the recording link and any transcript Twilio returns. Voicemails a caller chooses to leave are recorded, stored and may be transcribed the same way.

Call recording is off by default. A Workspace administrator must turn it on. When it is on, the other party hears a recording announcement (for example, “This call may be recorded”) before recording begins — on inbound calls before the call is connected, on outbound calls as soon as the customer answers — so that calls with people in all-party-consent states such as California (Cal. Penal Code § 632) are lawful. Recordings and transcripts belong to the Workspace, are kept as described in Section 7, and can be deleted by the Workspace. The Workspace is responsible for any additional notice or consent its industry or its own customers’ laws require.

We store SMS opt-in and opt-out status for each contact, together with a Workspace-wide opt-out registry: the keyword or carrier signal that caused the opt-out, the number involved, and when it happened. This includes STOP, START and HELP keyword handling and opt-out signals reported to us by carriers. For email, we store unsubscribe status for non-transactional mail.

Payment information

Card details never touch Cache servers. Card payments are collected and processed by Stripe. Cache stores only Stripe identifiers (customer ID, payment method ID), the last four digits and card brand as returned by Stripe, the amount, the currency and the payment status. We never store full card numbers, CVV codes or magnetic-stripe data. In the iPhone app, a team member saving a customer’s card types it into Stripe’s own secure card field, and the number goes from that field directly to Stripe. Payments in Cache are a Workspace’s customers paying that business for its services; Cache does not sell anything to you inside the iPhone app. Non-card payments a Workspace records manually — cash, check, Zelle, other — are stored as an amount, a method label and an optional confirmation number.

Usage and device information

We collect standard technical information when the app or website is used: IP address, browser or app version, operating system, device type, pages or screens viewed, timestamps, and server-side request and error logs. If you use the mobile app and turn on notifications, we store the push notification token your device issues. We use this to keep the service running, to investigate abuse, and to fix defects.

The Cache iPhone app

The iPhone app asks for device permissions only when you use the feature that needs them, and you can change each one at any time in iOS Settings → Cache:

The app does not access your device contacts or your location, does not use the advertising identifier, does not track you across other companies’ apps or websites, and contains no advertising or analytics SDK. If the app crashes, a crash report (error details, app version, device model and a pseudonymous account identifier — never message content, email addresses or phone numbers) is sent to Sentry so we can fix the defect.

Location and addresses

Cache uses the Google Maps Platform, including Places, to autocomplete and validate service addresses that a Workspace enters. Address lookups you type are sent to Google to return suggestions. Cache does not track device location in the background.

Cookies and similar technologies

We keep this minimal. The marketing site at cachecrm.com uses no advertising cookies, no analytics SDK, no session replay and no cross-site tracking pixels. The application uses cookies and local browser storage that are strictly necessary to keep you signed in, remember your active Workspace, and hold your interface preferences. We do not sell or share information for cross-context behavioral advertising.

Where the information comes from

We collect personal information from: you directly, when you create an account, fill in a form on our website, or contact support; the Workspace you belong to or are a customer of, when it enters or imports records about you; your device and browser automatically, when you use the app or website; our sub-processors, which report delivery status, opt-out signals, payment results and similar operational data back to us; and the third-party integrations a Workspace chooses to connect.

2. Mobile Information and SMS Consent

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All other categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

Phone numbers and SMS opt-in consent collected through the form at cachecrm.com/#contact, inside the Cache application, or by a Workspace from its own customers are used only to deliver the messages the user requested — and for nothing else.

Specifically:

See our SMS Terms & Conditions for the full messaging program disclosure.

3. How we use information

Cache does not use Workspace CRM content or message content to train machine-learning models, and we do not sell personal information. Separately, and only when a Workspace switches on an AI integration and supplies its own API key, that Workspace's automations and AI assistants can send message text and contact fields to a third-party AI provider — see Section 5.

4. Legal bases

Where a legal basis is required, we rely on: performance of a contract (providing the service you signed up for), legitimate interests (securing the platform, preventing abuse, improving the product), consent (SMS messaging and optional communications), and compliance with legal obligations.

5. Sub-processors and service providers

Cache runs on third-party infrastructure. Each provider below receives only the data needed for its function, under a contract that restricts its use and requires it to protect that data to the same or an equal standard as this policy. The same list, with locations, is published at cachecrm.com/subprocessors. We will give at least 30 days' notice before adding a new sub-processor; email support@cachecrm.com to be added to that notice list.

Core sub-processors — used for every Workspace

Core Cache CRM sub-processors and what each one handles
ProviderPurposeData involved
Google Firebase / Google CloudAuthentication, database, file storage, serverless functions, and push notification delivery to web browsersAccount data and all Workspace CRM content
TwilioSMS delivery, inbound SMS, voice calls and call logsPhone numbers, message content, call metadata, recordings and transcripts where enabled, opt-out status
ResendTransactional and Workspace-sent email deliveryEmail addresses, subject and body, delivery and unsubscribe status
Amazon Web Services (Amazon SES, via Resend)Underlying email transport used by ResendEmail addresses, subject and body, delivery status
StripeCard payment processing, Stripe Connect payouts and stored payment methodsCard data (held by Stripe), amounts, customer and payment method identifiers
Expo (Expo Application Services)Mobile push notification deliveryDevice push tokens and notification payloads, which can include a contact name and a message preview
Typesense CloudSearch index behind in-app searchIndexed text from contacts, jobs, invoices, estimates and leads
Google Maps PlatformAddress autocomplete and validationAddress text entered into address fields
SentryCrash and error reports and performance traces from the iPhone app, the web app and our serversError details, app version, device type and a pseudonymous account identifier; no message content, email addresses or phone numbers
Apple (Apple Push Notification service)Delivering push notifications and incoming-call alerts to iPhonesDevice push tokens and notification payloads, which can include a contact or caller name, number and a message preview
VercelHosting and delivery of the cachecrm.com websiteRequest logs, IP address, user agent
Google FontsWeb font delivery on the cachecrm.com websiteIP address and user agent of site visitors

Optional sub-processors — only if a Workspace turns them on

Optional, Workspace-enabled sub-processors
ProviderPurposeData involved
Anthropic (Claude)AI automation actions, AI-generated message drafts and AI assistant replies; conversation content is sent only when a Workspace enables an AI assistantMessage text and the contact, job, invoice and estimate fields the Workspace puts in its prompt template
Google (Gemini)AI automation actions, AI-generated message drafts and AI assistant replies, when selected; conversation content is sent only when a Workspace enables an AI assistantMessage text and the contact, job, invoice and estimate fields the Workspace puts in its prompt template
OpenAIAI automation actions, when the Workspace enables the integration with its own API keyMessage text and the contact, job, invoice and estimate fields the Workspace puts in its prompt template
xAIAI automation actions, when the Workspace enables the integration with its own API keyMessage text and the contact, job, invoice and estimate fields the Workspace puts in its prompt template
ElevenLabsAI voice assistant for phone calls, when enabledCall audio and the conversation content handled by the voice assistant
SlackAutomation notifications to a Slack channelWhatever the Workspace puts in the notification
DiscordAutomation notifications to a Discord channelWhatever the Workspace puts in the notification
Google Workspace (Calendar and Sheets)Writing jobs to a calendar and rows to a spreadsheetJob, contact and schedule fields the Workspace maps
QuickBooks (Intuit)Accounting syncCustomer, invoice and payment records
ConnectTeamCrew scheduling and dispatchJob and assignment fields
JotFormReceiving lead-intake form submissions into the WorkspaceThe fields the Workspace’s form collects (typically name, phone, email, address and service details)
WorkizImporting the Workspace’s own records from its Workiz accountClients, leads, jobs and invoices the Workspace chooses to import
Zapier and other webhook destinationsSending event data to any https endpoint the Workspace configuresThe event payload the Workspace selects; the destination is chosen by the Workspace, not by Cache

AI assistance

AI features are off by default. A Workspace administrator must connect a provider and paste that Workspace's own API key before anything is sent. When an AI automation runs, the prompt the Workspace wrote is filled in server-side and sent to the provider it chose. The fields that can be substituted into a prompt are: workspace name; the body of the last inbound message (up to 2,000 characters); contact first name, last name, full name, phone, email and company; job date, time, revenue and status; invoice number, amount and due date; estimate total; and lead name, phone, email, pipeline, stage and assigned user. Service addresses, contact notes and payment data are not sent.

A Workspace can also switch on an AI assistant that replies to inbound texts, emails or phone calls on the Workspace's behalf (for example, after business hours). When it is on, the conversation with that customer — the messages exchanged, the contact's name, phone number, email and service address, and the Workspace's pricing and booking instructions — is sent to the AI provider the Workspace selected (Anthropic, Google or ElevenLabs for voice) to generate each reply. The assistant identifies itself as an AI at the start of the conversation, a person can take over at any time, and the Workspace administrator must give explicit consent before the first assistant is enabled. The provider processes this content to produce the reply and does not use it to train models under our agreements; we keep the conversation only as part of the Workspace's normal message history.

Because the Workspace supplies its own key, the Workspace is contracting with that provider directly and the provider's own terms — including whatever retention or human-review practices they permit — govern what happens to the content. Cache does not hold a shared AI key, does not train models on Customer Data, and does not send anything to an AI provider for a Workspace that has not enabled one. AI output can be written to a contact note or sent to a customer as SMS or email by the Workspace's automation; the Workspace remains the sender and is responsible for that content.

6. When we share information

We share personal information only in these situations:

We never sell personal information, and we never share mobile numbers or SMS consent with third parties for marketing or promotional purposes.

7. Data retention

We keep information only as long as we need it for the purpose it was collected for, plus any period the law requires. By category:

How long Cache keeps each category of information
CategoryHow long we keep it
Account information (name, email, role, acceptance records)For the life of the account, then 90 days after it is closed.
Workspace CRM data (contacts, leads, jobs, estimates, invoices)Until the Workspace deletes the record or terminates, then 60 days.
Messages, email and call logs (including recordings and transcripts where enabled)Until the Workspace terminates, then 60 days.
Payment records and financial ledgers7 years, for tax and accounting obligations.
SMS opt-out and email unsubscribe recordsIndefinitely. We must be able to prove that a number or address asked not to be contacted.
Website enquiries submitted at cachecrm.com24 months.
Server request and security logsUp to 12 months.
Encrypted backupsCycled out on a rolling schedule; residual copies of deleted data are purged within 90 days of deletion.

We may keep information longer where we must to comply with legal, tax or telecommunications obligations, to resolve a dispute, or to enforce our agreements.

8. Security

We take the security of this data seriously and design for it rather than bolt it on:

We do not hold a SOC 2 report or other third-party security certification today. If we obtain one we will say so here.

No system is perfectly secure. If we become aware of a breach affecting personal information, we will notify affected customers and any required regulator without undue delay, and in any event within 72 hours of confirming the breach for customers covered by our Data Processing Addendum.

9. Your rights and choices

Depending on where you live, you may have the right to:

How to exercise them

Workspace administrators can export their Workspace data from the application at any time and can edit or delete most records directly. You can delete your own Cache account and the personal data associated with it at any time from My Settings → Danger zone → Delete my account inside the app. That deletes your reminders and push subscriptions, removes you from every Workspace you belong to, anonymizes your user profile, and deletes your login credential immediately. If you still own a Workspace, you will need to transfer it or schedule its deletion first, from Settings → General. A minimal record of your acceptance of these terms, and related audit-log entries, is retained for three years as compliance evidence even after your account is deleted. For anything the in-app path does not cover — a complete copy of everything we hold, correction of an account record, erasure of a Workspace and its contents, or if you are unable to sign in — email support@cachecrm.com and we will complete the request within 30 days.

We will verify your identity before acting, normally by confirming that the request comes from the email address on the account and, where the request is sensitive, by asking you to confirm details we already hold. We will not use the information you give us for verification for anything else.

Authorized agents. You may designate an authorized agent to make a request for you. We will ask the agent for written permission signed by you, and we may ask you to verify your own identity with us directly.

Response times. We acknowledge requests promptly and respond within 45 days, extendable once by a further 45 days if a request is complex, and we complete account closure, deletion and erasure requests within 30 days. We do not charge for these requests and we will not treat you differently for making one.

If you are an end customer of a Cache Workspace, we will forward your request to that business, since they control the record.

California residents (CCPA / CPRA)

If you are a California resident, you have the rights to know, access, delete, correct, and to opt out of sale or sharing of personal information, and to limit use of sensitive personal information.

Cache does not sell personal information and does not share personal information as those terms are defined by the CPRA, including for cross-context behavioral advertising. We have not done so in the preceding twelve months, and we do not knowingly sell or share the personal information of anyone under 16.

In the preceding twelve months we have collected the following categories of personal information, from the sources described in Section 1, for the business purposes listed in Section 3, and disclosed each to the service providers listed in Section 5:

Categories of personal information collected, their sources and purposes
CategoryExamplesSourcesPurpose
IdentifiersName, email, phone number, account ID, IP address, device push tokenYou; the Workspace; your deviceAccount creation, authentication, messaging, support
Customer recordsBusiness name, legal entity name, billing and service addressYou; the WorkspaceProviding the service, invoicing, scheduling
Commercial informationJobs, estimates, invoices, payments, payment method tokensThe Workspace; StripeProviding the service, payment processing, reporting
Internet or network activityPages and screens viewed, app version, request and error logsYour device and browserOperating the service, security, defect diagnosis
Geolocation (limited)Service addresses entered by a WorkspaceThe Workspace; Google MapsScheduling and dispatch
Contents of electronic messagesSMS and email bodies, call recordings and transcripts where enabledYou; the Workspace; Twilio and ResendDelivering and displaying the Workspace's own communications
Account log-in credentialsPassword credential or Google sign-in identifierYou; GoogleAuthentication only
InferencesNone. We do not create profiles or infer characteristics.——

Sensitive personal information. We collect two categories of sensitive personal information: account log-in credentials, and the contents of the messages and emails that pass through a Workspace's inbox. We use both only to perform the service you asked for — authenticating you, and sending, receiving and displaying your messages — and for the security, fraud-prevention and service-quality purposes permitted by Cal. Civ. Code section 1798.121(d). We do not use or disclose sensitive personal information to infer characteristics about anyone. Because our use falls within those permitted purposes, we do not offer a separate “Limit the Use of My Sensitive Personal Information” option; there is nothing to limit.

You may exercise your rights, or designate an authorized agent to do so, by emailing support@cachecrm.com.

10. International users

Cache is operated from the United States, is intended for customers in the United States, and its infrastructure providers store and process data in the United States. If you use Cache from outside the United States, you understand that your information will be transferred to, stored in, and processed in the United States, where data-protection law may differ from that of your country.

11. Children

Cache is a business tool. It is not directed to children, and it is not intended for anyone under 18. We do not knowingly collect personal information from anyone under 18. If we learn that we have, we will delete it. If you believe a minor has given us information, email support@cachecrm.com.

12. Changes to this policy

We may update this policy as the product or the law changes. When we do, we will revise the effective date and version at the top of this page. If a change is material — for example, a new category of data, a new purpose, or a new sub-processor — we will give account holders at least 30 days' notice by email and in the application before it takes effect.

13. Contact us

Questions, requests, or anything in this policy that is not clear:

Cache CRM (a product of SoCal Cleaner, LLC) support@cachecrm.com 562-280-2925 20208 State Rd, Cerritos, CA 90703

Related: Terms of Service · SMS Terms · Data Processing Addendum · Sub-processors