Security
Security, in plain English
Every line is checked against the code it describes.
Who can see what
- Owners see published records and their own requests.
- Board members see their whole association; filing, publishing, restricted records and the log can be withheld per seat.
- Our setup staff, admitted by a board, can only file, in one association, for up to fourteen days.
- The operator console shows only titles, counts, dates and status.
- The company’s owner holds administrator access to the database itself, through Supabase, to apply reviewed changes to it and to check that they landed.
Nothing reaches owners or the public until a board member confirms it on a separate screen. Records the law lets you withhold carry a warning and need a written, logged acknowledgement.
Associations are kept apart
Every table carries its association’s id; access needs membership. Real-user tests try to read and write across that line, both ways, on every table and file, and a release ships only if they fail.
Signing in
- You sign in with your email and a password of at least 10 characters, or with a one-time link we email you.
- The sign-in and reset forms answer every address the same way, so they never show who is a member.
- After five wrong passwords for one address in an hour, the sign-in page makes you wait: 30 seconds at first, doubling, never more than fifteen minutes.
- No account is ever locked, and the emailed link still works.
- Whoever reads your email can use a link sent there.
Links expire after 60 minutes.
Our operators, who can see across associations, and our setup staff, whom a board lets in to set up its records, also enter a code from an authenticator app we confirm for each of them, so their password or their email alone opens nothing. Board members can turn on the same code.
The emailed-link and password-reset forms share one limit: no address is sent more than five links an hour, and no connection may ask for more than twenty.
Changing your password needs a sign-in from the last ten minutes, and signs you out everywhere else. Under Password and sign-in, Sign out everywhere ends every session at once.
The event log
Every change writes a log entry. No one who signs in can edit or delete one: there is no permission to, and a trigger refuses both. Board members with log access read and export it; owners cannot.
Where records are kept
Records are kept with Supabase in US East (Northern Virginia), in a private bucket under the same membership rules, over TLS and encrypted at rest. Supabase’s daily backups of the database are kept seven days.
The file you upload is kept exactly as it arrived. It is never changed or replaced.
Money
- Card numbers
- Only the last four digits and the brand are kept; no table can hold a full number.
- Stripe’s pages
- Card and bank details, and debit authorizations, are entered on Stripe’s own pages; no Stripe script runs here.
- Stripe’s reports
- Stripe reports through a database role with no table access, allowed only eighteen named functions.
- The books
- Posted entries in the books cannot be edited or deleted; corrections are linked reversing entries.
- Who sees it
- By database rule, owners see only their own unit’s money. Bills, bank, budgets and vendors are the board’s alone.
- Sending money
- It never sends money or connects to a bank; owners pay the association’s own Stripe account.
- W-9 forms
- A vendor’s W-9 carries a taxpayer number, so no document that is or was one can be published.
Your records stay yours
A board member can export everything, any time: originals as uploaded, the rest as CSV. Cancel at any period’s end; then 30 days to export, deletion, and backups clear within 30 more.
Sources: terms of service, data processing addendum.
If something goes wrong
Think an account or record was exposed? Write to hello@keeperlane.com. A person answers, tells your board what was involved and what we have done, and helps you tell anyone you must.
Found a security problem yourself? How to report it.