Home / Fix a Problem / Security, Access & Backups / Consent record storage configuration

Showing a consent banner is only half the requirement in most frameworks — you also need to be able to demonstrate, later, what a specific visitor actually consented to and when, which means the choice itself has to be recorded somewhere reliable, not just acted on in the moment and forgotten.

PRV-008

Consent record storage configuration

Consent choices recorded reliably, so you can show what a visitor agreed to, and when.

$109.32 delivered in 48 hours
Needs WP admin login and Database access. Create a limited sub-account — we never ask for your own password.
  • Full backup taken before we start
  • If we can’t fix it, you get your money back
  • We never ask for your own password

What we need from you

  • Access to your existing consent banner or plugin
  • Confirmation of how long consent records need to be retained
  • Any specific reporting or export format you’d want for these records

This or something else?

You want visitor consent choices recorded and stored reliably, not just acted on in the moment This fix covers it
You don’t have a consent banner set up yet to record choices from Cookie consent banner implementation, the prerequisite step
You want the consent record specifically tied to checkout terms acceptance Terms acceptance logging at checkout, a related but distinct fix
You want to know what’s being consented to in the first place Cookie audit & categorisation report, worth doing beforehand

What we do

  1. Confirm what consent data needs to be recorded (choice, timestamp, and what was consented to)
  2. Configure reliable storage for consent records, whether in the database or via the consent tool’s own logging
  3. Set an appropriate retention period for consent records
  4. Test that a real consent choice is correctly and reliably recorded
  5. Provide a way to look up or export consent records if ever needed
  6. Document how the records are stored and how to access them

What is included

  • Reliable consent record storage configured and tested
  • An appropriate, documented retention period
  • A method to look up or export records if needed
  • A written note on the configuration

Not included

  • Implementing the consent banner itself, if not already in place
  • Legal advice on how long records specifically need to be retained
  • Terms acceptance logging at checkout, a separate, related fix
  • Ongoing management of records as a ongoing service

Questions about this fix

Why isn't just having the banner enough, without recording anything?

Most frameworks expect you to be able to demonstrate what a specific visitor consented to if ever questioned, which a banner that doesn't keep a record can't provide after the fact.

How long do consent records typically need to be kept?

This varies by which regulations apply to you, which is worth confirming specifically, though we can recommend a sensible default retention period based on common practice.

Will this slow down my site by adding a database write to every visit?

The additional write for recording a consent choice is lightweight and shouldn't cause any noticeable performance impact for visitors.

Can I export these records if I'm ever asked to prove compliance?

Yes, we set up a method for looking up or exporting records specifically so this is possible rather than records existing but being inaccessible when actually needed.

Does this work with the specific consent banner I'm already using?

In most cases, yes — we configure this to work with your existing banner or plugin rather than requiring you to switch to a different tool.

Consent record storage configuration
$109.32 · delivered in 48 hours · needs WP admin login, Database access

Related fixes

If this is the second time this year

A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.

See care plans

Your access, your rules

Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.

We back up first, always

Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.

If it is not what you bought

If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.

If we cannot fix it

You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.

If it comes back

Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.

What we are responsible for

If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.