Security and your data

You are putting your customers' addresses, your certification number and your gauge calibration dates into this. Here is exactly what happens to them.

Where it lives

Canada. The database and every stored document sit in the Canada (Central) region. That matters for a BC firm in a way it does not for an American vendor, and every established competitor in this market hosts in the United States.

The qualification, because you would find it out anyway: the web application itself and the document renderer run on servers in the United States, so your data passes through the United States in transit. What is stored — records and PDFs — stays in Canada.

Who can see it

Your firm's data is isolated at the database level, not only in the application. Every table enforces row-level access, so another firm asking the database directly for your customer list gets nothing back. There is a test that creates two firms and tries, as one, to read and modify the other's rows; it has to come back empty. We check it by attacking it rather than by assuming it.

On our side: one person has production access. Filed is a sole proprietorship run by Ethan Kerr in Victoria, BC; nobody else browses your records, and no analytics vendor receives them.

There are no passwords to steal, because we do not have any — you sign in through a one-time email link or through Google.

Getting your data out

Every report you produce is a PDF you can download from the test it belongs to, at any time, for as long as your account exists. That is the part that matters most: the documents you may have to produce years from now are files, not entries in our database.

For the rest — customers, sites, devices, test history, every document and who it went to — there is a button in Settings that hands you the lot as CSV in one zip. No fee, no support queue, no ticket, and it works whatever your subscription is doing. If you would rather we sent it to you, ask and we will.

If you stop paying

You keep everything. Cancelling does not lock you out of your own records or your own documents. We are not going to hold a tester's compliance history hostage when keeping that history is a legal obligation you carry personally.

If you close your account for good, we delete your data within 90 days — see the Privacy Policy. Ask for the export first.

In transit and at rest

Encrypted both ways. The site is served over HTTPS only, with HSTS, and the usual browser hardening headers are set:

• Strict-Transport-Security — HTTPS only, for two years
• X-Frame-Options: DENY — the app cannot be framed by another site
• X-Content-Type-Options: nosniff
• Referrer-Policy: strict-origin-when-cross-origin
• Permissions-Policy — camera and location only for the app itself, microphone off entirely

Verification pages

Every document carries a verification code so a building owner or an inspector can confirm it is genuine. Those pages show only what is already printed on the document, they carry a noindex header, and the codes are not guessable. A customer's address does not end up in a search engine because you used us.

What we don't have

No SOC 2 audit. No ISO certification. We are not going to imply otherwise by listing frameworks we have not been audited against.

If you need that level of assurance — most municipalities do — we are not the right vendor yet, and we would rather say so here than in a procurement questionnaire six weeks in.

Questions

Email help@backflowfiled.com. A person answers, usually the same day. If you find something here that is wrong, that is the message we most want to get.

See also our Privacy Policy and Terms of Service.