Information & your rights
Cookie Policy
How BREACH REDRESS uses cookies and similar technologies, what is stored on your device, and how to choose or withdraw optional permissions.
Last updated: 17 November 2026
Cookies and similar technologies
Cookies are small files saved by a website in your browser. Local storage and session storage are similar technologies used to keep information on your device. The relevant UK rules can apply to these technologies as well as to cookies.
This policy covers BREACH REDRESS, operated by Accident Claims Specialists Ltd. Read it alongside our Privacy Policy. Essential technologies and optional measurement have different purposes. You do not have to accept optional categories to read the website or register an enquiry.
Essential storage
Essential storage supports requested services, sign-in, security and remembering your cookie choices. It is not used as permission for advertising.
- Cookie preference: local storage under breachredress_cookie_choices records Analytics and Advertising choices, a consent version and the time you saved them. The choice is valid for 180 days. After expiry or a consent-version change, a new choice is requested. The stored entry remains until replaced or removed through browser settings;
- Authentication: if you sign in, our cloud solutions providers and sub contractors may store authentication tokens locally to maintain your session. Sign-in redirect and verification steps can use tab-session storage. These support access and security rather than advertising. Their lifetime depends on the account session, expiry, sign-out and browser settings;
- Submission confirmation: session storage under breachredress_thank_you_receipt holds a random private submission receipt, journey type and confirmation time for up to one hour within the current tab, so the requested thank-you page can survive a refresh. It holds no name, email, form answers, documents or signature. Display details remain in the current page’s memory and may be unavailable after a reload. With Advertising permission, this receipt can be checked against our server for conversion eligibility. The private receipt itself is never supplied to Meta;
- Hosting and security: the hosting infrastructure may use essential technologies to deliver and protect the website.
Removing essential storage may sign you out or interrupt a requested account function. It does not delete information already submitted to us.
Analytics preferences
Analytics is optional and starts unticked in the banner for a new visitor. The category concerns measurement of visits and website use, including online identifiers where a measurement service uses them.
The banner communicates your selection through the analytics_storage consent signal. The website operator must configure hosting-level visitor tracking to wait for consent; the banner itself does not change the operator’s hosting settings. Turning off Analytics sends a denied signal so consent-aware systems can stop optional measurement.
Optional website measurement is distinct from the enquiry records themselves. This enquiry service has no separate Google Analytics, article reader or reading-depth integration. Enquiry answers, signatures and uploaded documents are not analytics event data.
Necessary security and delivery logs are different from optional visitor measurement and may still be processed to operate the website.
Advertising and campaign measurement
Advertising is optional and starts unticked. It controls ad_storage, ad_user_data and ad_personalization permissions together: advertising storage, advertising user-data uses and personalised advertising, where such systems are configured.
If an affiliate code is present in the landing address, it stays in the address while you decide. Before Advertising permission we do not store it in browser storage or send it for tracking. After permission, the approved referral is saved in local storage under breachredress_affiliate_referral. It holds a random receipt, affiliate code, click time, expiry and a random request key. Tab-session storage under breachredress_affiliate_click uses the code, page path, request key and click time to avoid counting a refresh as a new referral. Both are used for up to 30 days from the referral; outdated entries can remain until replaced, cleared or checked. New approved referrals replace the previous one for future attribution, including across tabs on the same site. Returning without a new affiliate link retains the latest valid receipt. If resolution is unavailable, we save the enquiry using the last valid receipt we have, or without affiliate attribution. This does not change an earlier submission’s recorded affiliate.
With Advertising permission, our own records can count a page view, your first form interaction, completed steps (step number only), and a validated submission. We record the event type, time and random identifiers needed to link it to a referral and avoid duplicates. The event record does not contain the page address, form answers, contact details, documents or signatures. An inactive form is a started referral with no submission and no recorded form activity for 24 hours or more. Repeat validated leads from one visit count as a single converted referral. Signed-in affiliates see only totals for their own referrals. Blocking or clearing storage can reduce accuracy. Withdrawal clears the stored referral and stops future optional measurement, but does not remove previously recorded attribution.
After Advertising permission, an affiliate with an approved Pixel ID and a recorded public-page review may use Meta’s official Pixel script on the public homepage and the Legal Aid Agency campaign landing page. The script sends PageView on these public pages and ViewContent on the campaign landing page, using Meta’s standard browser event format and a random event identifier to avoid duplicate dispatches for the same navigation. Only the credited affiliate’s pixel is addressed. For a visit credited to Panaco, an enabled Pixel addresses Panaco’s Meta data source. Our integration does not load the Meta script before valid Advertising permission and an approved configuration, and does not provide a consent-free fallback Pixel. Reading these policies, accepting our terms or submitting an enquiry is not advertising consent.
Validated conversion measurement: If the credited affiliate’s Meta dataset has separate Lead approval and your Advertising permission is active, we can send one standard Lead event after our server validates your submission. Meta receives the submission’s record identifier to deduplicate the event and may collect browser metadata. A tab-session flag under breachredress_meta_lead_sent (keyed by the submission identifier) prevents a refresh from sending the event again. The confirmation lookup is available for one hour; the flag remains until the tab session ends or browser storage is cleared.
What Meta does not receive: We do not send form starts, step events or thank-you page views. Lead has no custom fields: no contact details, claim category, form answers, uploaded documents, signatures or private receipts.
Meta may receive the true page address, an approved referrer, IP address, browser/device information and advertising identifiers. The advertising cookies set on this website through Meta’s Pixel are:
- _fbp: a first-party browser identifier used by Meta for advertising delivery and measurement, normally lasting up to 90 days;
- _fbc: a first-party Meta ad-click identifier, set where a relevant fbclid click identifier is available, normally lasting up to 90 days.
Browser limits can shorten these periods, and permitted later use can renew a cookie. The 90-day cookie periods are separate from our 30-day affiliate-attribution window and 180-day cookie preference. These identifiers are personal data, not anonymous statistics. Meta may link event information with information it already holds, including Facebook or Instagram account information, to measure and personalise advertising, and may process it internationally. See Meta’s Cookie Policy and Meta’s Privacy Policy.
Meta measurement is limited to reviewed public pages and separately approved validated conversions on our production sites. On public pages, we remove recognised campaign parameters and skip addresses with unknown parameters, a fragment or an unapproved referrer. For a validated Lead we remove all parameters and fragments from the confirmation address before the Pixel starts. The Lead Pixel runs in a separate frame, with a clean address and no access to the confirmation page or app storage. It does not set first-party Meta cookies.
The integration uses Meta’s manual-only mode, disables automatic page-change reporting and supplies no advanced-matching contact information. We require automatic events, automatic advanced matching and Event Setup Tool rules to be disabled for the relevant Meta dataset. On claim forms, the thank-you page and other excluded pages, the public-page Pixel stops and this integration removes its _fbp and _fbc cookies. Only the isolated, separately approved Lead event may run on verified confirmation. Changing Advertising to off stops future Meta events, removes these cookies and clears the stored affiliate referral. The submission-confirmation receipt is separate and expires after one hour. Withdrawal does not erase events already received by Meta.
Optional advertising storage, affiliate attribution and the collection and transmission of permitted advertising events rely on your consent, including Article 6(1)(a) UK GDPR where personal data is processed and prior storage/access permission under PECR. They are not necessary to receive the enquiry service.
We review whether a Meta dataset may be used on this website before enabling public-page or Lead events, including the advertising partner’s authority to use it, data-source restrictions and any required international-transfer safeguards. Consent does not override Meta’s restrictions on sensitive information.
Choosing Advertising does not authorise a solicitor referral. Material new purposes require a fresh choice, not silent reuse of an old preference.
Enquiry forms and electronic signing
The current claim-enquiry form and unfinished signing actions are held in the page as you work through them. They are not saved by the cookie preference entry.
Selecting a proof file uploads it separately before the final enquiry is submitted. The legal aid signing journey saves your signature and completed Milberg client pack when you submit your instruction. Final submission stores the enquiry and its associated records. If you sign in and save an address, that address can be retained with your account.
The cookie preference does not contain your name, contact details, breach answers, documents or signature. Rejecting optional categories does not stop you using the enquiry form. Clearing cookies or leaving the page does not delete previously uploaded files or submitted records. See the Privacy Policy for rights and deletion requests.
Choosing, changing or withdrawing consent
On your first visit, optional categories are off. You may choose Reject optional, Accept optional, or Manage preferences to select categories separately and Save preferences. There is no pre-ticked optional category, and continuing to browse is not treated as consent.
Use Cookie settings in the footer or the control on this page to change a saved choice. Reject optional switches both optional categories off. The banner sends all four consent signals on a new choice, a later change and a page load that restores a saved choice.
A saved choice is valid for 180 days. If your browser blocks preference storage, the choice can be applied for that visit but may not be remembered next time. Clearing it means you will be asked again.
Withdrawal stops future optional collection and transmission governed by the relevant consent signal. For this affiliate integration it also clears the stored referral and removes its _fbp and _fbc cookies. It does not automatically erase historic measurements or enquiries already lawfully recorded, or information already received by Meta. Meta-held information and advertising preferences can also be managed through the rights and controls described in Meta’s Privacy Policy. It also does not withdraw permission to respond to an enquiry; contact us separately if you want that contact to stop.
Browser controls and external websites
You can remove cookies, local storage and session storage through your browser settings. Blocking storage may affect sign-in or other requested functions. Private browsing does not guarantee that a visit is hidden from someone with access to your device, browser history or network.
External links lead to websites with their own technologies and policies. Choices made here do not control cookies on those sites. Essential hosting processing is distinct from optional advertising or analytics.
The operator should keep an inventory of technologies on the published website and review it whenever providers or measurement features change. This policy does not claim a complete independently audited inventory of the hosting infrastructure.
Contact and policy changes
BREACH REDRESS is operated by Accident Claims Specialists Ltd, company number 09146224, with its registered office at 9 Lower Park Road, Hastings, TN34 2LB. Our ICO registration is ZA067220.
For questions about cookies or personal information, contact enquiries@breachredress.co.uk or use our Contact page. This policy will be updated if the website’s technologies or their purposes change.