keepcalculator

06 Numbers and Powers

Users Data Requests: How to Handle Them

Card No. 06·76416 · Updated · Standard formula, shown below

Users data requests are formal inquiries from individuals asking an organization to access, correct, or delete the personal information it holds about them. This article explains what these requests are, the legal framework behind them, and how to respond effectively and lawfully.

What Are Users Data Requests?

Users data requests, also known as data subject access requests (DSARs), are rights granted under privacy laws like the GDPR (General Data Protection Regulation) in the EU and the CCPA (California Consumer Privacy Act) in the US. They allow individuals to ask a company: what data do you have on me, why do you have it, and what are you doing with it? Other common requests include asking for a copy of the data, requesting corrections, or demanding deletion.

These requests can come from customers, employees, or website visitors. They are not limited to digital data—paper files and CCTV footage count too. The key is that the data must be “personal,” meaning it identifies a living individual.

Why They Matter for Your Business

Ignoring or mishandling a data request can lead to fines, legal action, and reputational damage. For example, GDPR fines can reach up to €20 million or 4% of global annual turnover, whichever is higher. Even if you are not in the EU, if you serve EU citizens, the GDPR applies. Similarly, the CCPA applies to businesses that meet certain thresholds, regardless of where they are located.

Beyond legal compliance, handling requests well builds trust. Customers are more likely to share data with companies that respect their privacy. A transparent process can also uncover internal data silos, helping you improve data governance.

How to Handle a Data Request (Step-by-Step)

Here is a practical workflow for responding to a data request:

  1. Verify identity: Confirm the requester is who they claim to be. This is especially important for sensitive data. Ask for a copy of an ID or a matching signature.
  2. Log the request: Record the date, the requester’s details, and what they asked for. This helps you track deadlines and show compliance.
  3. Search all systems: Look across databases, email archives, cloud storage, and even paper files. If you use third-party processors, you may need to ask them for data too.
  4. Review for exemptions: Some data may be exempt, such as data held for legal claims or confidential references. Redact information about other people if disclosing it would infringe their rights.
  5. Provide the response: Send the data in a clear, commonly used format (e.g., CSV or PDF). Include a description of how you use the data and any third parties you share it with.
  6. Meet the deadline: Most laws require a response within one month. The clock starts when you receive the request, not when you verify identity.

Common Mistakes and Pitfalls

Even well-meaning companies make errors. Here are the most frequent ones:

  • Charging a fee: Under GDPR, requests are free. Under CCPA, you can charge a fee only for excessive or repetitive requests.
  • Ignoring the request: Some requests are sent to generic contact emails and get lost. Designate a responsible person or team.
  • Over-redacting: Be careful not to delete too much. The requester has a right to see their own data, even if it is mixed with others’ data.
  • Missing the deadline: If you need an extension (e.g., for complex requests), inform the requester within the first month.
  • Not documenting your process: If you are audited, you must show you handled requests properly.

How to Choose a Tool or Service

Many organizations use software to automate data request management. When evaluating a tool, consider:

  • Integration: Does it connect to your CRM, helpdesk, and databases?
  • Automation: Can it automatically search for data based on an email address or user ID?
  • Compliance features: Does it track deadlines, generate audit logs, and support redaction?
  • Ease of use: Can non-technical staff operate it?
  • Pricing: Some tools charge per request, others per user. Estimate your volume first.

If you have a small volume (e.g., fewer than 50 requests a year), a spreadsheet and manual process may be enough. For larger volumes, a dedicated tool can save hours and reduce errors.

Costs and Resources

The cost of handling data requests varies widely. A simple request might take 30 minutes of staff time. A complex one—involving multiple systems, third parties, and legal review—can take days. Hidden costs include:

  • Staff time for searching, redacting, and responding.
  • Software subscriptions for automation.
  • Legal counsel for reviewing exemptions or handling disputes.
  • Potential fines if you fail to comply.

To control costs, maintain a data map—a record of what data you hold, where it is, and why. This makes searches faster and more accurate.

Legal Framework and Your Obligations

Here is a quick comparison of major privacy laws:

  • GDPR (EU/UK): Applies to any organization processing EU/UK residents’ data. Requests must be fulfilled within one month, extendable by two more for complex cases. You must provide the data in a machine-readable format.
  • CCPA/CPRA (California): Applies to for-profit businesses that meet revenue or data volume thresholds. Consumers can request disclosure, deletion, and opt-out of sale. You must respond within 45 days.
  • LGPD (Brazil): Similar to GDPR, with a 15-day response period for some requests.
  • PIPEDA (Canada): Requires response within 30 days, extendable if you notify the requester.

Always check the specific laws that apply to your jurisdiction and industry. When in doubt, consult a privacy professional.

Frequently Asked Questions

Can I charge a fee for a data request?

Under GDPR, no. Under CCPA, you can charge a fee only if the request is excessive, repetitive, or manifestly unfounded. If you do charge, you must explain the fee and provide a cost estimate.

What if I don’t have any data on the requester?

You must still respond, stating that you hold no personal data about them. Do not simply ignore the request. Confirm their identity first, then respond within the legal deadline.

Can I refuse a request?

Yes, in limited cases. For example, if the request is manifestly unfounded or excessive, or if the data is exempt (e.g., legal privilege). You must inform the requester of the refusal and their right to complain to a supervisory authority.

Do I need to provide data in a specific format?

GDPR requires a “commonly used, machine-readable format” like CSV or JSON. CCPA requires a format that is “readily usable” and allows the consumer to transmit it to another entity. PDF is generally acceptable for small amounts, but structured data is better.

How long do I have to respond?

Under GDPR and UK GDPR, one month. Under CCPA, 45 days. Some laws allow extensions for complex requests, but you must notify the requester within the initial period.

What if the request includes data about other people?

You must redact any data that identifies third parties, unless they consent to disclosure. For example, if an email chain includes a colleague’s name, you can remove that name or replace it with “[redacted]”.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →