---
title: "What is the right to be forgotten?"
description: "The right to be forgotten allows individuals to request the deletion of personal data in certain circumstances, or the removal of particular links from..."
published: "2026-10-16T12:00:00.000Z"
updated: "2026-10-16T12:00:00.000Z"
url: "https://getdosya.com/what-is-the-right-to-be-forgotten"
canonical: "https://getdosya.com/what-is-the-right-to-be-forgotten"
site: "Get dosya"
---

# What is the right to be forgotten?

The right to be forgotten allows individuals to request the deletion of personal data in certain circumstances, or the removal of particular links from...

## Key takeaways

- Erasure, removal at the source, search delisting, and rectification are different routes, so define the result you want before choosing whom to contact.
- The right to erasure is not absolute, and exceptions include freedom of expression, legal obligations, public-health purposes, archiving or research, and legal claims.
- Under the EU GDPR organisations generally must respond within one month, extendable by two further months for complexity, and requests are generally free.
- Backups may keep data temporarily until overwritten, but it should be put beyond use, and organisations should test that a restore cannot reintroduce deleted information.

The right to be forgotten allows individuals to request the deletion of personal data in certain circumstances, or the removal of particular links from name-based search results. It is not a universal right to erase your history: organisations must consider the legal grounds for deletion alongside duties to retain information and protect freedom of expression. This guide explains when the right applies, how to make a request, and what individuals and businesses should expect. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en))

## What does the right to be forgotten mean?

The right to be forgotten generally refers to the right to erasure under data protection law. Article 17 of the EU General Data Protection Regulation, or GDPR, allows people to have personal data deleted when specified conditions apply. The UK GDPR also provides a right to erasure, although UK rules and guidance should be checked separately from EU requirements. ([eur-lex.europa.eu](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng))

The protection concerns personal data, not simply information you dislike. Personal data is information relating to an identified or identifiable living individual. Names, photographs, contact details and combinations of information that identify someone can fall within that definition; information about a company is not automatically personal data, although details identifying its staff or owners may be. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/data-protection-explained_en))

The phrase also has a more specific meaning in search engine cases. Someone may ask a search engine to stop displaying links to particular pages when users search for their name. This is usually called **delisting** or **dereferencing**, and it does not necessarily require the publisher to delete the page. ([aepd.es](https://www.aepd.es/en/activities/internet-and-social-media/right-erasure-right-be-forgotten-internet-search-engines))

That distinction should shape your request. If the problem is an organisation holding unnecessary records, focus on erasure. If the problem is an old article appearing whenever someone searches your name, consider whether delisting addresses the harm, alongside any separate request to the publisher.

## Erasure, delisting and reputation management are different

Personal data removal can mean several things. Before contacting anyone, define the result you want: deleting a record, changing a webpage, or reducing its visibility in name-based searches. A request aimed at the wrong organisation may not achieve your intended outcome. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en))

| Approach | What it seeks to change | Important limitation |
| --- | --- | --- |
| Data erasure | Personal information held by an organisation | Some records may need to remain for lawful purposes |
| Removal at source | The information published on the original website | Separate copies may require separate consideration |
| Search delisting | Particular links displayed for searches involving your name | The underlying page can remain available |
| Rectification | Inaccurate or incomplete personal data | Correction is different from deletion |

These routes address different processing activities. A publisher may have grounds to retain an article while a search engine must separately assess whether linking it prominently to an individual's name remains justified. Likewise, correcting a factual error does not automatically resolve whether the information should remain searchable. ([edpb.europa.eu](https://www.edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_201905_rtbfsearchengines_afterpublicconsultation_en.pdf))

Treat online reputation management as an objective, not as a legal entitlement. Ask any adviser or service provider to explain the specific action they propose and how success will be measured. “Remove an identified URL from qualifying name searches” is a clearer objective than “clean up the internet”.

## When can you ask for personal data to be removed?

You can seek erasure when a recognised legal ground applies, such as information no longer being necessary, unlawful processing, or withdrawal of consent where no other legal basis remains. An organisation must assess the circumstances rather than automatically grant every deletion request. Explain which ground fits your situation and supply the facts needed to evaluate it. ([ico.org.uk](https://ico.org.uk/for-the-public/your-right-to-get-your-data-deleted/?seg=UFZDRTB38))

### The original purpose has ended

An organisation may no longer need information for the reason it collected or used it. For example, a completed activity may leave behind personal details that have no continuing purpose. However, ending a customer relationship does not automatically eliminate every reason to retain records. ([ico.org.uk](https://ico.org.uk/for-organisations/advice-for-small-organisations/getting-started-with-gdpr/data-protection-principles-definitions-and-key-terms))

For your request, identify the information and explain why its original purpose has ended. Distinguish optional profile details from records the organisation might need for another purpose. This makes it easier to assess deletion category by category rather than treating the entire account as one indivisible record.

### Consent has been withdrawn

Where processing relies on consent, withdrawing that consent can support erasure if there is no other legal basis for the processing. The important point is the basis actually used for the activity. Withdrawal does not mean every record held by that organisation must disappear regardless of its purpose. ([edpb.europa.eu](https://www.edpb.europa.eu/system/files/2024-04/recommendations-on-imi-transparency-obligations_en.pdf))

Be specific about the activity you agreed to and what you now want stopped. If the organisation says it must retain some information, ask it to identify the categories and explain its justification. Avoid assuming that a consent setting controls every use of your data.

### An objection applies, or processing is unlawful

An objection may lead to erasure where there are no overriding legitimate grounds for continued processing. Objections to direct marketing receive stronger protection: individuals can require organisations to stop using their information for that purpose. Unlawful processing is another potential ground for deletion. ([europa.eu](https://europa.eu/youreurope/business/governance-and-sustainability/digital-and-data-compliance/data-protection-gdpr/index_en.htm))

State whether you are challenging the collection, disclosure, retention or particular use of the data. “You are breaking privacy law” gives the recipient little to investigate. A precise explanation, supported by correspondence or screenshots, creates a more useful basis for a decision.

### Legal deletion requirements and children's information

Erasure may also be required to comply with a legal obligation. Special protection applies to personal data collected from children in connection with online services; reaching adulthood does not necessarily remove the ability to seek deletion of that childhood information. These requests still require attention to the relevant circumstances and applicable exceptions. ([ico.org.uk](https://ico.org.uk/for-the-public/your-right-to-get-your-data-deleted/?seg=UFZDRTB38))

## Limits that protect other rights and obligations

The right to erasure is not absolute. Data protection law must accommodate competing rights, legal duties and defined public interests. A refusal should therefore turn on the processing and the applicable exception, rather than a general preference to keep information. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/dealing-requests-individuals_en?prefLang=bg))

The main exceptions include processing necessary for:

- **Freedom of expression and information**, including qualifying publication activities.
- **Compliance with a legal obligation**, or certain public-interest tasks and official functions.
- **Specified public-health purposes.**
- **Public-interest archiving, scientific or historical research, or statistical purposes**, where the legal conditions are met.
- **Establishing, exercising or defending legal claims.** ([eur-lex.europa.eu](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng))

### Lawful reporting and public interest

Embarrassment alone does not establish a right to remove a news article. Reporting about public responsibilities, professional conduct or matters affecting others may engage a legitimate public interest. At the same time, lawful publication does not automatically settle a separate request concerning name-based search results. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/dealing-requests-individuals_en?prefLang=bg))

For a practical assessment, separate three issues: whether the content is accurate, whether publication remains justified, and whether search visibility remains justified. Addressing each issue prevents a request from relying entirely on the emotional or professional impact of the material.

### Necessary records and partial deletion

An organisation may need to retain some information even after you leave a service or job. Payroll, financial or other regulated records can have continuing legal purposes. That does not necessarily justify keeping unrelated personal information or using retained records for unrelated activities. ([ico.org.uk](https://ico.org.uk/for-organisations/advice-for-small-organisations/getting-started-with-gdpr/data-protection-principles-definitions-and-key-terms))

Ask for a category-level explanation if the answer is simply “we must keep your records”. Useful follow-up points include what remains, why it remains, who can access it and when retention will be reviewed. A partial outcome may be more appropriate than either complete deletion or blanket refusal.

## Search engines and the public-interest balance

Search engine delisting concerns the connection between your name and particular results. The European search-law framework developed through the Google Spain judgment of 13 May 2014, which recognised that search engines process personal data and can have independent obligations concerning links. It did not establish an unrestricted power to remove any unwanted reference. ([eur-lex.europa.eu](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=legissum%3A310401_1))

Search engines consider whether information is inaccurate, inadequate, irrelevant or excessive, alongside the public interest in access. Google's published explanation identifies factors such as a person's public role, the nature and age of the information, and the context of publication. Age matters, but there is no simple rule that every article becomes removable after a set period. ([support.google.com](https://support.google.com/legal/answer/10769224?hl=en-GB))

Build a request around concrete points:

- Identify each exact page address rather than only the website's homepage.
- Specify the name or name variation producing the result.
- Explain what has changed since publication.
- Distinguish factual inaccuracies from information that is accurate but allegedly outdated.
- Address any continuing public-interest reason for access.
- Describe the impact without presenting distress as the only reason for removal.

Where inaccuracy is central, supply relevant evidence. In a judgment delivered on 8 December 2022, the Court of Justice of the European Union explained that sufficient evidence of manifest inaccuracy can require dereferencing; a person does not necessarily need an earlier judgment against the publisher. The evidence still needs to substantiate the challenge. ([curia.europa.eu](https://curia.europa.eu/site/upload/docs/application/pdf/2022-12/cp220197en.pdf))

Geography also matters. The Court's judgment of 24 September 2019 established that EU law does not generally require worldwide dereferencing across every version of a search engine. Do not assume an approved European request makes the page inaccessible everywhere. ([europarl.europa.eu](https://www.europarl.europa.eu/RegData/etudes/ATAG/2019/642273/EPRS_ATA%282019%29642273_EN.pdf))

## Making a clear, evidence-based request

You do not need to begin with a lengthy legal argument. In the UK, an erasure request can be verbal or written and does not require special wording. A written record is nevertheless useful for showing what you requested and tracking the response. ([ico.org.uk](https://ico.org.uk/for-the-public/your-right-to-get-your-data-deleted/?seg=UFZDRTB38))

### Step 1: Define the information and desired outcome

Write down exactly what concerns you before sending anything. For an account, list the relevant identifiers and data categories. For online content, record the page address, publication details and the searches displaying it.

Then state the requested action separately. You might want a profile deleted, an inaccurate statement corrected, or a particular result delisted. Avoid combining these into a broad demand to “delete everything” unless that genuinely reflects your intended scope.

### Step 2: Identify the responsible organisation

The data controller decides why and how personal data is processed. A processor acts on the controller's behalf. For search results, the search engine's role is separate from the website publisher's role, so consider whether you need distinct requests. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en?prefLang=nl))

Check the privacy notice and relevant privacy-request process. Keep a copy of the form submission or email, including attachments. If contacting both a publisher and a search engine, maintain separate records so their decisions do not become confused.

### Step 3: Provide focused supporting material

Useful evidence might include a closure confirmation, an earlier consent withdrawal, or documents demonstrating a factual error. Explain what each item proves instead of attaching a large, unexplained collection. Redact unrelated information where possible.

An organisation may need proportionate information to verify your identity. It should not request more than necessary for that purpose. Before sending sensitive documents, check the recipient and ask whether a less intrusive verification method is available. ([ico.org.uk](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/individual-rights/right-to-erasure/?q=sensitive+data))

### Step 4: Request an intelligible decision

Ask the organisation to confirm what it has deleted and explain anything it retains. For delisting, ask which URLs and name searches its decision covers. Keep your request focused on information you can use to understand the outcome, rather than demanding an unqualified promise that no copy exists anywhere.

A practical tracking sheet should record the recipient, submission date, reference number, requested action, follow-up date and outcome. Add separate rows for separate URLs or organisations. This gives you a manageable record if further correspondence becomes necessary.

## A practical erasure-request template

Adapt the following wording to your facts and jurisdiction. It is designed to clarify the information, legal ground and outcome rather than guarantee acceptance. For search engine delisting, use the relevant search engine process and provide the requested URL-specific details.

**Subject: Request to erase personal data**

I am requesting erasure of the following personal data: [identify the information, account or records].

My details for locating the information are: [name and relevant account reference].

I believe erasure applies because: [explain the relevant ground and supporting facts]. I have attached [identify relevant evidence].

Please confirm what action you take. If you retain any information, please identify the categories, explain the applicable reason and describe the intended retention period or review criteria.

Please also explain any action concerning recipients of the information, where relevant. If you need additional information to verify my identity, please specify what is necessary and how I can provide it securely.

If you refuse any part of this request, please explain your reasons and the available complaint routes.

Before sending, replace every bracketed instruction and remove irrelevant sentences. Check that your evidence supports the ground you have selected. Save the final version, not just an earlier draft, so you know exactly what the organisation received.

## Response times, fees and refusals

Under the EU GDPR, organisations generally must respond without undue delay and within one month. A further two months may be available where necessary because of complexity or the number of requests, with notice and reasons provided within the initial month. Requests are generally free, although specific rules allow fees or refusal for manifestly unfounded or excessive requests. ([eur-lex.europa.eu](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng))

UK ICO guidance likewise describes a usual one-calendar-month response period and possible extensions. Timing can depend on necessary identity information and other applicable rules. The ICO flags relevant guidance as under review following the Data (Use and Access) Act 2025, so check the current UK position rather than treating one calendar month as an inflexible deadline in every case. ([ico.org.uk](https://ico.org.uk/for-the-public/time-limits-for-responding-to-data-protection-rights-requests/?hit_count=1))

A response is not necessarily an approval. Review whether it addresses each part of your request, distinguishes deleted information from retained information, and explains any refusal. If the organisation has misunderstood the scope, clarify that before escalating.

If you disagree, start by setting out the unresolved issue in writing. In the UK, the ICO advises raising the matter with the organisation before complaining to the regulator. Judicial remedies may also be available, but obtaining independent legal advice is sensible before starting proceedings. ([ico.org.uk](https://ico.org.uk/for-the-public/your-right-to-get-your-data-deleted/?seg=UFZDRTB38))

For a complaint, organise your material chronologically. Include the original request, proof of submission, identity-verification correspondence, the response and a short explanation of what remains unresolved. Avoid resubmitting the same unsupported demand; address the organisation's stated reasoning directly.

## EU, UK and United States differences

Do not assume that the law follows nationality alone. The EU GDPR can apply to processing connected with an EU establishment and, in defined circumstances, to organisations outside the EU offering goods or services to people there or monitoring their behaviour. Application depends on the processing context. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en?prefLang=nl))

The UK has its own data protection framework, including the UK GDPR, and subsequent legislation can affect its operation. For a UK matter, check UK legislation and ICO guidance rather than assuming every EU development produces an identical UK result. This is particularly important when calculating procedures and deadlines. ([legislation.gov.uk](https://www.legislation.gov.uk/ukpga/2025/18/part/5/chapter/1/2025-06-19?timeline=false))

For United States readers, California's Consumer Privacy Act provides qualifying consumers with a right to request deletion from covered businesses, subject to exceptions. That consumer deletion right should not be confused with a general entitlement to delist news coverage. California guidance describes a 45-calendar-day response period, with a possible further 45 days when the required notice is given. ([oag.ca.gov](https://www.oag.ca.gov/privacy/ccpa))

Before choosing a request route, establish:

1. Which organisation is processing the information.
2. Which activity you want changed.
3. Which jurisdiction's law may apply.
4. Whether the information and organisation fall within that law.
5. Which exceptions and response rules govern the request.

For cross-border cases, ask an adviser to explain these points explicitly. An international brand name, foreign website address or overseas server does not by itself provide the full answer. Keep the territorial question separate from whether deletion is justified on the merits. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en?prefLang=nl))

## GDPR compliance: building a workable erasure process

For organisations, effective GDPR compliance requires more than a deletion button. A useful operational approach connects request handling, information ownership, retention decisions and technical execution. The controller must be able to demonstrate compliance, so a documented decision matters alongside the action taken. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en?prefLang=nl))

### Create a consistent assessment workflow

Use the following checklist as an operational starting point, adapting it to your legal obligations and systems:

- **Capture the request:** record its scope, receipt date and responsible team.
- **Verify proportionately:** resolve genuine identity concerns without collecting unnecessary documents.
- **Locate the information:** check relevant systems, exports and service-provider relationships.
- **Assess each purpose:** distinguish information suitable for deletion from information requiring retention.
- **Coordinate action:** assign deletion or restriction tasks and confirm completion.
- **Explain the outcome:** describe partial decisions clearly and retain an appropriate decision record.

Do not let a request become stuck between customer support, legal and technical teams. Assign one person or function to coordinate the response. Where different systems have different owners, use a shared case record rather than relying on informal assurances.

A refusal deserves the same discipline as an approval. Record the relevant facts, the applicable justification and the categories affected. This helps prevent a valid exception for one record from becoming an unsupported reason to keep every record.

### Address recipients, public copies and backups

Erasure can involve more than the primary database. GDPR rules address communicating erasure to recipients, subject to specified limits, while organisations that have made information public may need to take reasonable steps to inform other controllers about requested removal of links or copies. These are qualified obligations, not a guarantee of universal recall. ([europa.eu](https://europa.eu/youreurope/business/governance-and-sustainability/digital-and-data-compliance/data-protection-gdpr/index_en.htm))

Backups need an explicit plan. ICO guidance recognises that data may remain temporarily in backups until overwritten, but stresses putting it beyond use and clearly explaining what happens. Retaining a backup should not become a way to continue using information that should have been erased. ([ico.org.uk](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/individual-rights/right-to-erasure/?q=sensitive+data))

As a practical safeguard, document backup rotation and restoration procedures. Test whether a restore could reintroduce information marked for deletion, and establish how the team would address that situation. Include these checks when reviewing retention and disaster-recovery arrangements. ([ico.org.uk](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/security/encryption/encryption-scenarios/))

### Keep privacy law updates actionable

Track privacy law updates through relevant regulators and official legislation, then translate changes into specific operational tasks. Review request templates, escalation rules and technical procedures rather than updating a policy document alone. Where guidance is under review, identify which decisions require additional checking. ([ico.org.uk](https://ico.org.uk/for-the-public/time-limits-for-responding-to-data-protection-rights-requests/?hit_count=1))

For each review, record the source, review date, affected process and owner of the change. Avoid mixing EU, UK and US requirements into one unexplained deadline or exception list. A jurisdiction-specific decision path is easier for staff to apply and audit.

## Choosing legal help for a difficult case

Consider specialist advice where publication rights, disputed accuracy, criminal-history reporting or cross-border processing complicate the assessment. You can also seek help when an organisation's retention explanation is difficult to evaluate. Begin with a concise evidence pack so the adviser can assess the actual dispute rather than reconstructing it from scattered messages.

If you are searching for “right to be forgotten lawyers london”, prioritise relevant expertise over location alone. Ask who will assess the matter, which legal route they recommend and what outcome they consider realistic. For solicitors in England and Wales, check the individual and firm through the Solicitors Regulation Authority's register. ([sra.org.uk](https://www.sra.org.uk/consumers/register/))

Before instructing anyone, ask for clarity on:

- The distinction between publisher removal and search delisting.
- The evidence needed and weaknesses in the proposed case.
- Fees, scope of work and possible additional costs.
- Whether complaints or proceedings are included.
- How sensitive documents will be handled.
- What a partial or unsuccessful outcome would mean.

Do not treat a promise of complete disappearance as a substitute for a reasoned assessment. The most useful advice should identify both opportunities and limits. Ask for the proposed next step in writing before committing to wider work.

## A realistic path to greater control

The right to be forgotten is a targeted protection, not a reset button. Its practical value depends on matching the information, responsible organisation and legal ground to the outcome you need. Deletion, correction and search delisting can each help, but they solve different problems. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en))

Start with one clear request supported by relevant evidence. Keep a record, examine the response and challenge specific unresolved points where necessary. For businesses, the corresponding priority is a process that produces timely, explainable decisions—not automatic deletion and not automatic refusal.

*This guide provides general information, not legal advice on an individual case.*

## Related guides

- [Biometric data definition under privacy laws](/biometric-data-definition-under-privacy-laws)
- HIPAA Privacy Rule vs Security Rule explained

## Sources

1. [Information for individuals - European Commission](https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en)
2. [Regulation - 2016/679 - EN - gdpr - EUR-Lex](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng)
3. [Data protection explained - European Commission](https://commission.europa.eu/law/law-topic/data-protection/data-protection-explained_en)
4. [Right to erasure ("right to be forgotten"): internet search engines | AEPD](https://www.aepd.es/en/activities/internet-and-social-media/right-erasure-right-be-forgotten-internet-search-engines)
5. [edpb.europa.eu: Edpb guidelines 201905 rtbfsearchengines afterpublicconsultation en](https://www.edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_201905_rtbfsearchengines_afterpublicconsultation_en.pdf)
6. [ico.org.uk: Your right to get your data deleted](https://ico.org.uk/for-the-public/your-right-to-get-your-data-deleted/?seg=UFZDRTB38)
7. [ico.org.uk: Data protection principles definitions and key terms](https://ico.org.uk/for-organisations/advice-for-small-organisations/getting-started-with-gdpr/data-protection-principles-definitions-and-key-terms)
8. [edpb.europa.eu: Recommendations on imi transparency obligations en](https://www.edpb.europa.eu/system/files/2024-04/recommendations-on-imi-transparency-obligations_en.pdf)
9. [Data protection under GDPR - Your Europe](https://europa.eu/youreurope/business/governance-and-sustainability/digital-and-data-compliance/data-protection-gdpr/index_en.htm)
10. [Dealing with requests from individuals - European Commission](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/dealing-requests-individuals_en?prefLang=bg)
11. [Right to be forgotten on the Internet | EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=legissum%3A310401_1)
12. [Right to be forgotten overview - Legal Help](https://support.google.com/legal/answer/10769224?hl=en-GB)
13. [curia.europa.eu: Cp220197en](https://curia.europa.eu/site/upload/docs/application/pdf/2022-12/cp220197en.pdf)
14. [europarl.europa.eu: EPRS ATA%282019%29642273 EN](https://www.europarl.europa.eu/RegData/etudes/ATAG/2019/642273/EPRS_ATA%282019%29642273_EN.pdf)
15. [Application of the GDPR - European Commission](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en?prefLang=nl)
16. [ico.org.uk: Right to erasure](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/individual-rights/right-to-erasure/?q=sensitive+data)
17. [ico.org.uk: Time limits for responding to data protection rights requests](https://ico.org.uk/for-the-public/time-limits-for-responding-to-data-protection-rights-requests/?hit_count=1)
18. [Data (Use and Access) Act 2025](https://www.legislation.gov.uk/ukpga/2025/18/part/5/chapter/1/2025-06-19?timeline=false)
19. [California Consumer Privacy Act (CCPA) | State of California - Department of Justice - Office of the Attorney General](https://www.oag.ca.gov/privacy/ccpa)
20. [ico.org.uk: Encryption scenarios](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/security/encryption/encryption-scenarios/)
21. [SRA | Solicitors Register | Solicitors Regulation Authority](https://www.sra.org.uk/consumers/register/)
