← All posts
SOC 2 without storing customer datado I need SOC 2 if I don't store customer dataSOC 2 for SaaS startups

Do You Need SOC 2 If You Don't Store Customer Data?

No customer-content storage does not settle a SOC 2 request. Map transient processing, logs, providers, and buyer requirements before deciding whether to pursue a report.

A data path and a buyer request determine whether a no-storage claim changes the SOC 2 decision.
A data path and a buyer request determine whether a no-storage claim changes the SOC 2 decision.

You may still need a SOC 2 report even if your SaaS product never saves customer content. A request can pass through your service, reach a provider, appear in a log, or leave an account record behind. The business decision also depends on what a buyer asks you to prove. Map the real data paths and confirm the buyer’s requirement before starting or ruling out a SOC 2 examination.

Does no customer-data storage remove the need for SOC 2?

No-storage is one fact about a service, not a SOC 2 exemption. The AICPA Trust Services Criteria describe Security in terms of information during collection, use, processing, transmission, and storage. Their system-boundary definition includes the infrastructure, software, people, procedures, and data needed to provide a service. A service that handles data briefly can still have access, transmission, change, and incident risks.

The AICPA SOC 2 Description Criteria say management’s system description should explain how information flows through and from the system. The data component includes customer data transmitted through the system as well as data that resides there. A report is about the described service and its controls, not a claim that the company holds a particular amount of customer content.

There are two separate questions to answer:

  1. What does your service actually handle, and which controls and providers support it?
  2. Does a customer or partner require a report for that service, with a specific type, scope, category, and date or period?

If no buyer has requested a report, the startup SOC 2 decision guide helps you weigh the work against your sales plan and current risks. If a buyer has asked, get the exact wording before promising a report or telling them one is unnecessary.

Check what “we do not store customer data” means

Take one customer request from entry to deletion. For each stop, record the information, operator, retention behavior, and source you checked. A team often means “we do not persist the customer’s uploaded content” while it still stores account emails, request metadata, support tickets, or error traces.

Place to check Question to answer Useful source to inspect
Application path Does the API receive or transform content, even briefly? Request handling and deployed config
Queue and cache Can a retry, failed job, or cache retain the input or output? Queue settings and safe job samples
Logs and errors Can payloads, identifiers, or URLs appear in logs or crash reports? Collector settings and safe samples
Provider call Does another service receive the request, and what does it retain? Contract, settings, and provider docs
Accounts and help Which names, email addresses, tickets, and support copies remain? Account schema and support settings
Backups and export Are any of these copies backed up, exported, or sent to another region? Backup and export configuration

Keep the answer narrow enough to verify. “We do not store uploaded documents in our production database” may be true while “we do not store customer data” is false. Record exceptions and the date of the check. A diagram or policy is only a starting claim until someone compares it with deployed systems. Use the data flow diagram template to label each route and source.

A short-lived request still has a service boundary

Suppose a SaaS API receives a customer’s document, sends it to a processing provider, returns a result, and discards its working copy. That statement leaves several facts open: the API’s access to the document, the provider’s retention, retry queues, logs, account data, and support access. The team should check those paths before describing the product to a buyer or CPA firm. No-storage can reduce some risks and evidence work; it cannot prove that the rest of the service is outside the examination.

The same care applies to customer-hosted software. If the customer runs the entire product, your company may have a narrower operated-service boundary. But a vendor-operated update service, license server, support channel, or telemetry endpoint may still be relevant. Draw who operates each component. Then ask the buyer whether it wants assurance over your service, its own deployment, or both. A report’s stated scope determines what it covers.

Use the SOC 2 scope guide to record the candidate boundary and challenge each exclusion. Management can prepare that map, but the exact engagement scope belongs in discussion with the CPA firm.

Decide what to do with the buyer’s request

Before you allocate a team to SOC 2, send the requester a precise follow-up:

Our product does not persist customer-uploaded content in its production database. It does process that content during a request, and we are checking logs, providers, and retention paths. Which product and deployment do you need covered, which SOC 2 report type and Trust Services Categories will you accept, and what date or period and delivery date do you require?

Use your verified facts in place of the example sentence. If you have not checked the claim, say it is under review. The customer-request guide has a fuller reply workflow.

Once you have the answer, make one of these decisions:

Buyer response Next step
No report required for this purchase Complete the requested security review using current, sourced answers.
Report requested, but scope or type is unclear Clarify the service, deployment, categories, report type, and date or period.
Report required for a service you operate Map the service boundary, current controls, evidence, cost, and CPA availability.
Report requested for software the customer operates Explain your operated boundary and ask which assurance would satisfy the customer’s need.

Do not describe a provider’s SOC 2 report as covering your own controls. A provider report can inform your review of that provider, while your application, people, and procedures have their own boundary and evidence.

Keep the decision tied to source records

FileGRC is a Git-native GRC workspace for SOC 2 work. JSON holds structured records, Markdown holds long-form work, and Git supplies the change history. A team can record its System boundary, Information Types, Components, Vendors, controls, and evidence references, then have an agent check whether the no-storage statement matches those records. Starter records are proposals, not compliance claims. Source systems still prove how data moves and how controls operate. Management reviews the answer, and an independent CPA firm performs any SOC 2 examination and judges the evidence.

Open source · MIT

Run your SOC 2 program as files in Git.

Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.

Frequently asked questions

Do we need SOC 2 if we do not store customer data?

Not storing customer data does not settle the decision. A service may still receive, process, transmit, log, or give a provider access to information. Map those paths and ask the buyer whether it requires a SOC 2 report for the service, report type, and date or period. Management and a CPA firm set the examination scope if you proceed.

Does transient processing count for SOC 2?

Yes, transient processing can be relevant to the scoped service. The AICPA Trust Services Criteria address information during collection, use, processing, transmission, and storage. Check the actual request path, access, provider handling, and any copies before describing the service as no-storage.

Does a customer-hosted product need its own SOC 2 report?

A customer-operated deployment may create a different assurance question from a vendor-operated service. Identify who runs the product, who can access it, which hosted services or update paths the vendor still operates, and what the buyer wants covered. Do not say a vendor report covers the customer's environment unless its stated scope does.

Can we tell a buyer that we do not store customer data?

Only after checking production paths, logs, queues, backups, support tools, error reports, and provider retention. Say which data type and environment the statement covers, whether the service still processes or transmits it, and when the facts were checked. Do not claim zero retention from an architecture diagram alone.

Can FileGRC decide whether we need SOC 2?

No. FileGRC can keep the service boundary, information types, providers, controls, and evidence references reviewable in a Git-native GRC workspace. Your team verifies live data paths and the buyer's request. Management and the CPA firm decide the engagement scope, and the CPA firm performs the examination.