Security and data handling
You are about to send us somebody else's confidential agreement
Your attachment agreement is not only yours. It carries the pole owner's rates, terms and methodology, and it almost certainly carries a confidentiality clause with your name on it. Your invoices carry your build. Sending both to an outside auditor is the part of this that keeps a network engineer awake, and the first question is always the same one.
No, your documents are not training anybody's model
Your documents are read by document reading service providers, including artificial intelligence services, which return the figures to us and whose contracts bar them from training models on your documents. They may keep a document for a limited period for security and abuse monitoring, as their terms allow. That is the same statement our Privacy Policy makes in Section 6, and it is the kind of claim you can hold us to.
Every finding traces to a document, a clause, a tariff section or a federal formula, and the arithmetic is shown beside it. You can check any one of them yourself.
Where your documents go, and what can reach them
Your documents go to one place: a private storage bucket in a US East region, restricted by file type and size, readable only by the account that owns them. They are never made public and never given a shareable link.
Behind it, the database is locked by default rather than by exception:
- The unauthenticated role has no read access to any table. Not one.
- The signed in role can read three tables and write to none.
- Our own application holds no delete permission on any table in the database. Deleting is done by a guarded database routine, never by application code that could be made to do it by accident.
Row level security is on for every table.
What we delete, and when it actually happens
We publish the periods and we run the deletion. A job runs every day, removes the files themselves before removing the records that point at them, and refuses to touch anything that is not genuinely past its own expiry date. Filed evidence, a document from your pole owner that one of your findings rests on, is kept as part of your audit trail and independently of your findings' own retention period; when we do remove the file, we keep the record.
| Your documents | We keep them for |
|---|---|
| If you never become a client | 90 days |
| If you do | 12 months after your engagement closes |
| Findings and the audit trail behind them | 7 years |
Those are ceilings, not targets. Ask us to delete sooner and we will, and a verified deletion request completes within 30 days, subject to the exceptions in Section 8 of our Privacy Policy.
Why seven years on findings: if you are building with federal money, your findings are part of your support for that award record, and you will need them long after the invoice is settled.
The site
Every page is served with a content security policy that allows no third party script, no framing by another site and no plugin content, along with the standard set of browser protections. Production builds ship no source maps.
What we do not claim
We are a new company and we would rather you heard this from us than found it out.
We do not hold a SOC 2 report, and we are not asking you to treat us as though we do. What we can give you instead is specificity: exactly what is built, exactly what can reach your documents, and exactly when they are deleted. All of it is above, and none of it is a slogan.
If your procurement process needs something we have not listed, ask. We will tell you plainly whether we have it.
Ask before you send anything
Write to hello@getpoleproof.com and a person will answer. You do not need to upload a document to ask a question about how we handle them.