Support and data storage information
These answers explain how this packaged version of the reporting tool stores report/project information.
Where is my data stored?
Your report/project data is stored locally in your own web browser using browser storage, specifically the tool’s local project state key. In practical terms, the answers, sample pages, WCAG results, evidence text, ADO links, branding settings and imported project data are kept on the device and browser profile you are using.
The tool reads that local browser data when you return, so your report can appear to be retained after you log back in. Exported HTML reports, page-level outputs, PowerPoint summaries and JSON files are generated from that local browser state and are only stored wherever you choose to save, upload or share those exported files.
Because browser storage is tied to the device, browser and profile, clearing site data, using a different browser, using private browsing, or changing device may remove or hide the locally saved project information. Use the “Save project JSON” option if you need a portable backup.
Is any of my data stored on Librumis servers?
The report content you enter into the tool is not intentionally stored on Librumis servers by this packaged version of the application. The server provides the application files and handles the login session, but the project/report content is processed in your browser and retained locally in browser storage.
Uploaded logos and imported JSON project files are read by the browser for use in the current project state. They are not uploaded to Librumis as part of the normal report-building workflow.
As with most hosted websites, the hosting platform or web server may still create ordinary technical logs, such as request time, IP address, browser/user-agent information, requested page path and error information. Those logs are separate from the accessibility report content and are not the report database.
Who is this tool intended for?
This tool is intended for accessibility testers, quality engineering teams, product teams, business analysts, governance/risk teams and organisations that need a structured way to record WCAG evidence and produce consistent accessibility reporting outputs.
It is a reporting and evidence-assembly tool. It does not automatically prove WCAG conformance and it does not replace expert manual testing, assistive technology testing, legal review or organisational sign-off. Its purpose is to help teams capture evidence consistently, explain user impact clearly and produce repeatable outputs for review, remediation and assurance.