Privacy

Summary

This public tool is intended to work as a simple, no-account, public-access tool.

The expected privacy model is:

no sign-up
no login
no user account
no intentional long-term storage of the answers entered into the tool

If the tool is deployed as a static public tool, users should be able to use it without creating an account or submitting personal profile data.

What the tool asks for

The tool asks for information about a product, service, market, and accessibility context.

This information is meant to describe the offering being reviewed, for example:

type of service
delivery channel
sector
whether the offer is consumer-facing
accessibility work already done

Users should avoid entering unnecessary personal data.

Do not enter:

personal identity numbers
payment card data
passwords
sensitive personal data
confidential internal legal advice
private customer records

No-account use

This tool is intended for public use without account creation.

That means:

you should not need to register
you should not need to log in
the tool should not require a saved profile to generate results

No-storage assumption

The public release assumes a privacy-minimising setup.

Under this assumption:

answers are processed only for generating the immediate result
answers are not intentionally stored after the session
results are not tied to a user identity
no private workspace is created for the user

If the deployment changes and storage is later introduced, this privacy page should be updated before release.

Cookies and analytics

For a minimal public static release, the preferred approach is:

no tracking cookies
no behavioural profiling
no ad-tech
only strictly necessary technical delivery, if any

If basic analytics are added later, they should be limited, privacy-conscious, and clearly disclosed.

Local processing and browser behaviour

Depending on deployment, some processing may happen directly in the browser.

In a privacy-minimising setup:

the information you enter stays in the current browser session unless you choose to copy or save it yourself
generated text can be copied by you, but is not stored for later retrieval by the service

Your browser or device may still keep temporary data such as page cache, autofill, or local history under your own browser settings.

Generated outputs

The tool may generate:

an indicative applicability classification
a starter checklist
a starter accessibility statement draft

These outputs are intended for immediate use by the person using the tool.

If you copy or export the output, you are responsible for how you store and share it.

Third-party services

A privacy-minimising public release should avoid unnecessary third-party services.

If hosting, analytics, or monitoring providers are used, the live deployment should disclose them where required.

Limitations

This privacy page describes the intended privacy posture for a public static tool release.

It does not override the real behaviour of the live deployment.

If the live deployment later adds:

accounts
saved sessions
server-side logging of user inputs
analytics tied to user behaviour
export by email
CRM or support integrations

then this page must be updated to reflect those changes.

Practical privacy note for users

For best privacy:

enter only the information needed to get the result
avoid personal or confidential information
review generated text before sharing it internally or externally

Plain-language notice

This tool is intended to be usable without an account and without intentional long-term storage of what you enter. It is designed as a public first-pass tool, not a private case-management system.