Privacy notice
This is version 1 of this notice, published on 18 September 2026. Version 2 replaced it on 10 October 2026. It is kept here as it read on 10 October 2026, so the earlier text stays on record. Read the current notice
What we collect, why, who sees it, how long we keep it, and how to ask us to delete it.
The public reporting form this notice describes is not open yet. No barrier report has been filed and none is held, so every section below describes what will happen rather than what has. The notice is published first on purpose: nobody should have to hand over a name before the page explaining what happens to it exists.
Version 1 · 18 September 2026Español
The short version
- You can file a barrier report without giving your name. The form works, and the public entity still has to answer it.
- If you do give your name, email or phone number, the public entity you reported to sees it.
- We keep the report for as long as that entity’s records rules require, then we remove your contact details and keep the rest.
- We do not sell anything, we do not advertise, and we do not use what you write to train anything.
- To have your details removed, open the tracking link you were given and ask. We will tell you the outcome either way.
- To ask us anything about this: privacy@barrierops.com.
If you filed a barrier report
| Field | Required? | Why it is asked | Who sees it |
|---|---|---|---|
| What happened | Yes | It is the report. Without it there is nothing to act on. | Staff at the public entity you reported to. Our support staff only if that entity asks us for help with your report. |
| Page address | No | So the entity can find the page you were on | The same people as the row above |
| Assistive technology you were using | No | So the entity can reproduce the problem. Free text, never a list of products, because the list is always wrong. | The same people as the row above |
| Your browser and device | No | Filled in from what your browser sends, if you leave it | The same people as the row above |
| Your name | No | So the entity can address you if they reply. Leave it blank and the report still works. | The same people as the row above |
| Your email address | No | So you can be told the outcome | The same people as the row above, plus our email provider, to deliver it |
| Your phone number | No | Only if you would rather be called | The same people as the row above |
| Whether you want a reply | A checkbox, off by default | So nobody contacts you who you did not ask to | Staff at the public entity you reported to |
| Your tracking link | Generated | It is how you check the status without an account | Only you, and staff at the public entity you reported to |
You can file this report without giving your name. Every contact field is optional, the form submits without them, and the public entity’s obligation to respond does not depend on knowing who you are. If you leave them blank we have no way to contact you, which is the trade — you will still be able to see the status through your tracking link.
Telling us what you use is optional. We ask because “the menu does not work” and “the menu does not work with NVDA in Firefox” are different reports and only one of them can be fixed. It is stored with the report, seen by the same people, and kept for the same time. It is never used to categorise you, it is never shared outside the report, and leaving it blank does not weaken your report.
Your tracking link is how you check the status without an account. Treat it like a password.
Who is responsible for your report
The public entity decides what happens to your report. We do what they ask.
When you report a barrier on a city’s website, that city — not us — decides how the report is handled, how long it is kept and whether it can be deleted. We run the system it arrives in.
In the words a lawyer would use: the public entity is the controller of the report, and BarrierOps is the processor. We process it on their instruction and for no other purpose. We do not decide what to collect, we do not use it for anything of our own, and we do not pass it to anyone the entity has not instructed us to pass it to.
- A deletion request goes to the entity. We carry it out when they tell us to, and we tell you what they decided.
- A records request about your report goes to the entity, under that state’s public records law, not to us.
- If you disagree with how the entity handled your report, the entity’s own grievance procedure is the route. We do not host it and we do not decide it.
How long it is kept
We do not delete these on a timer, because in many US states a complaint made to a public entity is a public record. Its retention is set by that state’s schedule, sometimes for years. Deleting your report on a fixed twelve-month clock could destroy the entity’s own record, which is not ours to destroy.
| What | How long | Then what |
|---|---|---|
| A barrier report | No public-records retention rule is recorded for this jurisdiction. The report is retained and flagged for the entity to decide. It is not deleted. | Your name, email and phone number are removed. The report, its dates, its resolution and its ledger link are kept. |
| Evidence events | Never automatically deleted. They are excluded from every automated retention job and the exclusion is asserted by a test. | Deleted only on explicit written instruction from an organisation owner |
| Scan artifacts, screenshots, DOM snapshots | Not deleted yet. The retention job that would delete them is not built. The default period and what each edition can change about it are published here before it runs. | Deleted, once that job exists |
| Prospect data | 12 months | Deleted. It is not evidence and it is not ours. |
After the retention period your name, email and phone number are removed. The report, its dates, its resolution and its ledger link are kept — the entity keeps its record, and you stop being in the system.
Which rule applied to your report is recorded with it, so the entity can answer a records request about it without guessing.
How to ask for deletion
- Open the tracking link you were given when you filed the report.
- Choose “ask for my details to be removed”. You do not need an account, and you do not need to prove who you are beyond holding the link.
- The request goes to the public entity. It is not carried out automatically.
- They decide, and we tell you the outcome.
- Where deletion goes ahead, your name, email and phone number are removed and an event is written recording that a deletion happened — without recording what was deleted.
The request goes to the public entity, because the record may be theirs to keep by law. It is not carried out automatically. They decide, and we tell you the outcome either way, including when the answer is no and why.
If you have lost your tracking link, write to privacy@barrierops.com with enough detail to identify the report. We will find it or tell you we could not.
If you work for a customer
| What we hold | Why |
|---|---|
| Your name, work email address and role: owner, admin, editor or viewer | To let you in and to say who did what |
| Sign-in events, once sign-in auditing is built | Security, and the audit log your own organisation can read. The audit trail exists and records changes to your data; sign-in events are not written to it yet. |
| Every action you take that changes something — status changes, assignments, exports, verification | It is the evidence ledger. It is the product. |
| Your notification preferences, once they can be set | To send the right email and no others. Email is the only channel. |
- A user is never deleted; an account is deactivated. The ledger records who did what, and removing the actor would break the chain that makes the ledger worth having. Deactivation removes access immediately.
- Staff access to your organisation is impersonation: read-only, requires a written reason, is announced in a banner you can see while it is happening, and is written to the audit log.
If you only visited this website
- No cookie is set. Nothing is written to your browser’s storage. There is no tracking pixel, no session recording, no heatmap and no advertising of any kind.
- Nothing counts your visit today. When page-view counting is turned on it will be a first-party, cookieless tool running on our own hardware, recording the page, the referring site’s hostname, a rough viewport size and a country. Your IP address is shortened before it is stored and the full address is never kept.
- The public barrier-report form loads nothing at all from anyone else — no analytics, no fonts from a content network, no embedded map.
That is why there is no cookie banner. There is nothing to consent to.
Who else sees it
| Who | What they can reach |
|---|---|
| Staff at the public entity you reported to | The whole report |
| Our support staff | Only when that entity asks us for help, read-only, with the reason recorded |
| Our subprocessors | Only what each needs: the email provider sees the address your acknowledgement is sent to; the hosting and storage providers hold the data at rest; the error tracker may hold a page address in a stack trace |
| Anyone else | Nobody. We do not sell, rent, share or license anything in this system to anyone. |
Where it is
All data at rest is in the United States — every store in the subprocessor register, not three named ones.
BarrierOps is not incorporated yet. This notice will name the company, and the privacy laws that apply to it, once it is. What this page describes holds until then: we collect as little as possible, we publish this notice, we honour deletion requests, and we act as the processor for the entity that is the controller.
All data is hosted in US regions.
How to contact us
| About | Where |
|---|---|
| Privacy questions | privacy@barrierops.com |
| Response target | We reply within 1 business day and answer within 5 business days |
| Postal | The address is not published yet |
| About your own report | The public entity’s ADA coordinator, whose name, title, email, phone and postal address are on that entity’s own accessibility statement, under 28 CFR 35.107(a) |
| Security issues | Security issues go to security@barrierops.com, not here |
What we do not do
- We do not sell, rent or share personal information. There is no exception, no affiliate carve-out and no “business partner” clause.
- We do not advertise, and there is no advertising technology anywhere in this product or on this website.
- We do not use anything a resident writes to train a model.
- We do not build a profile of you across sites. There is no cross-site identifier to build one from.
- We do not store customer credentials, and we scan public pages only.
- We do not ask for anything the workflow does not need, which is why every contact field on the report form is optional.
Changes to this notice
- This notice is versioned and dated. The version and its date are at the top of the page.
- Previous versions stay retrievable. A privacy notice whose earlier text has vanished is not a record.
- Where a change reduces what you can ask for, or widens what we collect, we say so at the top of this page for 90 days rather than only in the version list.
- Customers are notified before a new subprocessor reaches customer data.
This is the first version, so there are no previous ones to read. Every later version will be listed here with its date.