Skip to content

Help · Security and privacy

How one association is kept apart from another

By the database, not by the screens — and it is tested both ways before every release.

This is the thing that would end the product if it were wrong, so it has the most proof behind it.

Can another association see our records?

No. The database ties every row to one association. Each release ships only if every attempt to cross that line fails.

Can your staff read our documents?

Not from the product. A board member may admit a setup helper for up to fourteen days, and every step is logged.

What can owners see?

Published records, and only their own unit, requests and payments. The board also sees unpublished records, every request, the checklist, the log and settings.

Each test suite also switches the protection off once and checks that it notices, so a test that would pass anyway cannot hide a gap.

Stripe reports payments through a database role with no table access. It may call eighteen named functions, which take Stripe’s ids and return a status; a test fails if one is added or removed.

An owner sees their own unit’s charges, payments, ledger lines, receipts and autopay, and nothing of any other unit’s.

More on security and privacy