TechnSols
Advertisement

Consent Log Viewer

View consent logs online for free. Paste or upload a CSV or JSON log and filter every consent record, with no install and no sign-up.

Be the first to rate this tool
Drop a CSV or JSON consent log here, or choose a file

Paste or upload a CSV or JSON consent log and press Load Log.

What Is Consent Log Viewer?

Consent Log Viewer is a free online tool by TechnSols that opens a consent log and lets you search, filter, and read every record in it. You paste or upload a CSV or JSON log, and the tool builds a filterable table with one row per consent decision, plus a summary of how many visitors accepted, rejected, or chose categories.

Advertisement

A consent log is the record of what each visitor agreed to: the consent id, the time, the choice, the categories, and the banner version shown. Under the GDPR, the site must be able to demonstrate that consent was given, and the log is that demonstration. The GDPR Article 7 says the controller must be able to prove consent, and a log you can search is how that proof is used in practice.

One honest limit matters most. The viewer reads the log you give it, and it cannot verify that the records are genuine or complete: a log file is only as honest as the system that wrote it. It checks that the required proof fields are present and flags the records that are missing one, but it does not verify signatures and it cannot prove that a record was not changed. If the banner that writes these records is missing, the Cookie Consent Banner builds it from a form.

People use it to answer a visitor who asks what they agreed to, to prepare evidence for an audit, to check that a new banner writes records correctly, or to find how many visitors rejected everything last month. It suits a data protection officer, a site owner answering a rights request, or a developer testing a banner. The export it writes is a CSV file, so you can keep it with the evidence.

How To Use Consent Log Viewer?

Here is how to view a consent log online in three quick steps. Using Consent Log Viewer is simple. There is no software to install and no account to make. Open the log, filter the records, and export the slice you need. If the log must be checked against the GDPR duties, the GDPR Compliance Checklist walks through them one by one.

Step 1: Open The Log File

Press Choose File and pick a CSV or JSON consent log, or paste the log text into the box. The file guard checks the extension and the magic bytes, and files over 100 MB are refused, because the whole log is read in your browser. The viewer reads the header row of a CSV, or the array of objects in a JSON file, and reports how many records it found and how many rows it could not parse.

Step 2: Filter And Search The Records

Use the status filter to show only accepted, rejected, or custom records, the date range to show one week or one month, and the search box to find one consent id. Each row shows the consent id, the timestamp, the status, the categories, and the banner version. Click a row to see the full record, including the exact categories the visitor chose and the text version they saw.

Step 3: Export The Slice You Need

Press Export Filtered CSV to download only the records the filters show, with the same columns as the log. Export the smallest slice that answers the question: one consent id for a rights request, or one month for an audit. If the cookies behind the records need a list, the Cookie Inventory Manager lists them next.

The whole job takes a few minutes. A file built from a form is ready to use, and the steps above are the same every time.

Why Consent Log Viewer?

A consent log nobody can read is not proof, it is a file. A regulator asks for one visitor record, and the team that must open a spreadsheet, search by hand, and guess at the columns will take hours and still miss the row. A viewer fixes that: it parses the log, filters it, and shows the record in seconds. The proof is only useful when it can be found. If the policy behind the records needs writing, the Privacy Policy Template writes it from a form.

The fields it checks come from the law. The ICO consent guide explains that consent must be recorded with who, when, what, and how, so the record can be shown later. This viewer checks for those fields on every record and flags the ones that miss them, so the gaps are visible before an auditor finds them.

One Record In Seconds

A rights request names one visitor, and the answer is one record. The search box finds it by consent id, and the detail view shows the time, the choice, the categories, and the banner version, so the reply is complete in one step. The Data Retention Policy sets how long those records are kept.

Missing Fields Are Flagged

A record without a timestamp or without a banner version is a record that cannot prove consent. The viewer flags every record that misses a required field, with the field name, so the team can fix the banner that writes the log instead of fixing the log after the fact.

Export Only What You Need

Sharing a whole log shares every visitor decision, which is more data than the question asked for. The export writes only the filtered records, so a rights request gets one record and an audit gets one month. Less data shared means less risk, and the export is the proof of that restraint.

What Can You Do With Consent Log Viewer?

A consent log viewer fits any site that keeps consent records. These are the jobs this viewer handles best.

Answer A Visitor Rights Request

A visitor writes and asks what they agreed to. Search the log by their consent id, open the record, and reply with the time, the choice, and the categories. If the risk of the request needs a score, the Privacy Risk Assessment scores the privacy risk the records help lower.

Prepare Evidence For An Audit

An auditor asks for the consent records of one month. Filter the log by that date range, check the flagged records, and export the slice. The export is the evidence, and the flagged rows are the gaps to fix before the auditor arrives.

Test A New Banner

A new banner must write records that a viewer can read. Upload a small log from the new banner, check that every record has its fields, and look for the banner version on each row. A banner that writes bad records is worse than no banner, because it promises proof it cannot give.

Advertisement

Quality And Settings

The tool parses CSV logs with a small parser that handles quoted fields and commas inside quotes, and JSON logs as an array of record objects. Each record is normalised to the same fields: consent id, timestamp, status, categories, banner version, and country where present. The table filters by status, by date range, and by search text, and the detail view shows the full record. The export writes the filtered records as CSV. If a CSV file will not parse, the CSV Structure Validator checks its structure first.

  • Reads CSV and JSON consent logs, pasted or uploaded, in the browser.
  • Normalises records to one set of fields: id, time, status, categories, version.
  • Filters by status, date range, and consent id search.
  • Flags records missing a required proof field, with the field name.
  • Exports only the filtered records, as CSV, with the same columns.

There are no other settings to learn, because the viewer is a table with filters and an export. Open the log, filter the records, and export the slice. If a row will not parse, the viewer reports the row number instead of hiding it, so the bad rows are visible too.

How Consent Log Viewer Works

The viewer reads the log file into memory, detects CSV or JSON from the content, and parses it into records. Each record is checked for the required proof fields, and the ones that miss a field are flagged with the field name. The table renders the records newest first, and the filters apply to the parsed records in memory, so searching is instant even on a large log. When the log is JSON, the JSON Validator checks the JSON form on its own.

Two limits are worth knowing. The viewer reads only the log you give it, and it cannot verify that the records are genuine, complete, or unaltered: a log file is only as honest as the system that wrote it. It also reads the whole log in your browser, so a very large log needs a machine with enough memory, and files over 100 MB are refused. For proof that stands up in court, the records need the system behind them, not only the file.

Privacy

Everything you open stays in your browser. The log is read on your own computer, and nothing you paste or upload is sent to a server, stored, or shared with anyone. Closing the tab clears the log, so the visitor records never leave your device.

Because no account is needed, there is no name, email, or history tied to what you view. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.

Tips

A few habits make Consent Log Viewer work smoother, whether this is your first file or your fiftieth.

  • Search by consent id first, because it answers a rights request in one step.
  • Check the flagged records before an audit, and fix the banner that wrote them.
  • Export only the filtered slice, never the whole log, when you share evidence.
  • Keep the banner version on every record, so a change in wording is traceable.
  • Re-check the log after any banner change, to catch new missing fields early.

When the log is clean, keep the export with the audit file and note the date. If the log file must be proven unchanged, the File Hash Generator hashes it in seconds.

More Tools For The Same Job

These tools handle the same kinds of jobs: consent records, cookies, and privacy evidence.

FAQ

Common questions about viewing a consent log, answered plainly.

Is Consent Log Viewer by TechnSols Free?

Yes, Consent Log Viewer by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can view as many logs as you like, and everything you paste or upload stays in your browser, so nothing is uploaded or stored anywhere.

Which Log Formats Can It Read?

It reads CSV files and JSON files, and pasted text in either format. A CSV log needs a header row with columns such as consent id, timestamp, status, and categories. A JSON log needs an array of record objects with the same fields. The viewer reports which rows it could not parse, instead of hiding them.

Does It Verify The Signatures?

No, it does not verify cryptographic signatures or prove that a record is genuine. It reads the records, checks that the required proof fields are present, and flags the records that are missing a field or hold an invalid value. Proof of consent is a record plus the system that wrote it, not a file alone.

Can I Find One Visitor Record?

Yes, paste the consent id into the search box, and the viewer filters the table to the records with that id. Each record shows its timestamp, its status, its categories, and the banner version it was given under, so one id answers the whole question of what that visitor agreed to.

Can I Export The Filtered Records?

Yes, the export downloads the filtered records as a CSV file, with the same columns as the log. Export only the slice you need, such as one consent id or one date range, so the file you share holds no more data than the question asked for. The export never includes the raw file itself.

Open the log, find the record, and export the slice. A consent record you can find is proof you can use, and that is the whole point of viewing the log.

Follow TechnSols on Google
Add TechnSols as a preferred source to see more of our tools in Google Search.
Add to Preferred Sources
Advertisement