Wednesday, 7:10 AM, coffee still going, and a breach headline scrolls past: a company you have never heard of, a database you will never see, another industry entirely. You run the half-second inventory anyway, the one every operator runs now: what of ours lives in clouds we do not control? Then the day starts, and the question dissolves the way it always does.
Here is what the question would have found. Your ledger, the real one, the one with every owner's numbers and every deposit you are liable for, lives inside someone else's software. You know this; you chose it, for good reasons, and the alternative was a filing cabinet and a spreadsheet named FINAL-v3. But somewhere in the move, a question that used to have an obvious answer quietly stopped being asked at all: who can read the books?
When the books lived in the office, you answered it by naming names. The bookkeeper. Your partner. Whoever held a key to the cabinet, and you knew exactly who held a key to the cabinet, because there were two of them and one was yours. It was not a security policy. It was custody, and you could recite it. When the bookkeeper retired, you changed where the key hung, and the list stayed short.
Ask the same question about the cloud ledger and the answer goes soft. The vendor's site says encrypted, and it is true: encrypted in transit, encrypted at rest, the phrases sound complete. But encryption at rest, in almost every platform, means the vendor encrypts your data with keys the vendor holds. Their support staff can read your books under their access policy. Their engineers can, under their controls. None of that is a scandal; it is how cloud software works, and reputable vendors govern it carefully. It is just not custody. It is trust, professionally managed, and nobody ever actually asked you whether you wanted to extend it.
Encrypted at rest tells you there is a lock. It does not tell you who holds the key.
What changes when the key moves is the shape of the answer. Who can read the books goes back to being a list you can recite: the people in this office who hold the secret, and no one else. Not a support queue, not a curious engineer, not whoever ends up with a copied backup, because the fields worth protecting are ciphertext without a secret that has never left your browser. The due-diligence question from an owner's accountant gets a one-line reply instead of a forwarded brochure. When someone leaves the firm, they come off the list the day you rotate the secret, the way a returned key used to work. And the half-second inventory on a breach morning comes back different too: what they would have of yours is a lock without a key.
That is what Scaalr's ledger encryption is: optional, field-level protection for the sensitive fields in your books, where you choose a secret in your own browser, the browser strengthens it with Argon2id and derives the keys there, only the public key is ever stored, and there is no recovery through the vendor, by design, a condition you acknowledge on the record when you turn it on. What it covers, what deliberately stays readable so your reports still total, and how the enable flow works: Is Your Financial Data Safe in Cloud Property Software? Accounting Data Only You Can Unlock.
For the field-by-field coverage map, the enable procedure, and the honest boundaries, see: Is Your Financial Data Safe in Cloud Property Software? Accounting Data Only You Can Unlock.
Put one building on it first. $99 covers your first 50 units, Alex included. Cancel anytime.