Draft. These pages are being reviewed by an attorney and may change before launch. Bracketed words are details still to be filled in.
Security
How an association's records are kept safe in Boardkeeping, what we do when something goes wrong, and how to tell us about a problem.
Not yet in effect.
How records are kept
- Encrypted in transit and at rest.
- Isolated per association inside the database. The database enforces the boundary itself (row-level security), so a mistake in the application cannot show one association another's records.
- Every change is written to an audit log the board can read: who, what, when.
- People sign in with an emailed link; there are no passwords to steal. Board members can add a second sign-in factor, and we will require one for the treasurer before an association collects payments online. A role ends on the day after the term the board recorded, and access ends with it.
- Files are reached through links that expire within minutes and carry no names, only identifiers.
- We do not write names, addresses or payment details into our logs or into web addresses.
Backups and getting records back
The database keeps a continuous history so it can be restored to any moment within its retention window, and we rehearse that restore with a scripted drill against a copy, never against live records. The drill checks that the copy is the moment asked for, that every association's isolation is intact, and that every document's file is present and unchanged.
Every association can download everything it owns at any time: a spreadsheet for every table and every version of every document (a library larger than 128 MB does not fit in one archive: its README lists any files left out, and each can still be downloaded on its own from the documents page). We encourage boards to take an export at the end of each fiscal year and keep it with their own records.
When something goes wrong
We keep a written incident response plan. If we confirm a security incident that affects an association's records:
- we contain it first, then work out what was affected;
- we tell the association's board within seventy-two hours of confirming it, in plain words: what happened, what records were involved, what we did, and what the board should do;
- we help the board tell its owners, and we tell owners ourselves if the board cannot;
- afterwards we write up what we learned and what we changed.
Reporting a problem
If you believe you have found a security problem in Boardkeeping, write to support@boardkeeping.com with what you found and how to see it. We will answer within two business days, keep you informed, and credit you if you wish once it is fixed.
We ask that you do not read, change or download records that are not yours while showing us the problem, and that you give us reasonable time to fix it before telling others.