Security and your data.
Arbor Lane holds the money you collect and the roster of the people who live in your community — rent and dues, tenants and owners, leases and governing documents. We treat all of it the way you'd want your own treated: locked down, backed up, and yours. This page lays out exactly how, in plain terms, with no fine print between you and the facts.
How we handle your data.
Here's what's true today — stated plainly, not dressed up.
Arbor Lane runs on Cloudflare's global network. Your community's data lives on infrastructure built and operated by one of the most established names on the internet, not on a server in a closet somewhere.
Every connection to Arbor Lane uses TLS 1.3, the current standard, with HSTS turned on — so traffic between you and Arbor Lane is encrypted, and browsers are told to use a secure connection every time. The padlock in your browser isn't decoration; it's the whole path.
Your community's data is isolated from every other community on Arbor Lane. Tenants, owners, the money, the documents — one community's records don't bleed into another's. The walls between communities are part of how the product is built, not a setting you have to find.
The money moves through Stripe — the same payments infrastructure trusted by a large share of the businesses you already buy from. Card and bank details are handled by Stripe, not stored by us, so the most sensitive part of the transaction sits with a specialist whose entire job is handling it safely.
Sensitive actions are written to an audit log — a record of what happened and who did it. When a question comes up later about who changed what, there's an answer on file instead of a guess.
Your data is backed up, so a bad day doesn't become a lost roster or a missing ledger. The record of your community's money and its people is kept, not held in one fragile place.
Where we are on compliance.
We'll be straight about this, because it's the kind of thing that's easy to overstate and we won't. Arbor Lane is working toward SOC 2 Type II — the audit is underway. SOC 2 is the standard that checks, independently, that a company actually does the security things it says it does, over time. We're in that process now, not finished with it, and we'd rather tell you that plainly than imply a stamp we don't yet hold.
In the meantime, the practices on this page are real and in place today: Cloudflare hosting, encryption in transit, isolation between communities, payments through Stripe, audit logging, and backups. The full security policy — subprocessors, how we handle access, and how to report a vulnerability — lives on our policy page.
What that means for the people you answer to.
When an owner asks whether their dues are safe, or a tenant wonders where their lease went, or a board member asks who can see the directory, you have a real answer. The money runs through Stripe. The records are isolated to your community, backed up, and logged. And you can point anyone who asks at this page and the full policy behind it, instead of saying "I think so."
That's the point of doing this plainly. You're trusted with other people's money and other people's information, and the software underneath you should make that trust easy to keep.
Your community's data, treated like your own.
Locked down, backed up, isolated to your community, with the money through Stripe and the practices laid out in plain sight — that's how Arbor Lane holds what you put into it. You can start the trial yourself, today, and see exactly how your community's data is handled, no sales call to get there.
Questions about security first? There's a human on the other end
Month-to-month by default. No sales call to get started.
Less time on the busywork. More on the people.