Security, Explained for Board Members
If you're on a board or leading a chapter, you don't need to understand how OrgAlyne is built — but you probably do want a straight answer to one question: if we put our organization's real information in here, is it actually safe? Here's that answer, without the jargon.
Your organization's data is genuinely walled off from every other organization
Every piece of data in OrgAlyne — every priority, every committee, every document — is tagged as belonging to one specific organization. Every single time OrgAlyne looks anything up, it checks that tag first. This isn't just something shown to you on screen; it's checked at the deepest level, every time, automatically.
And we don't just assume that works — we've actually tried to break it on purpose, repeatedly, as part of building this, specifically attempting to reach one organization's data using another organization's access. Those attempts fail, and we keep testing that they keep failing.
Passwords aren't something even we can see
When someone sets a password, it's transformed into something irreversible before it's ever stored. Nobody — not even us — can look up what someone's actual password is.
Who can do what is actually enforced
A Committee Member and an Org Admin genuinely don't have the same abilities in OrgAlyne. That's not just a difference in what buttons they see — someone without the right role literally cannot perform an action they're not allowed to, even if they try to do it directly.
Real, established infrastructure, not a hobby server
OrgAlyne doesn't run on a server sitting under someone's desk. It's built on established, widely-used infrastructure providers — the same category of services many real companies rely on — for hosting, the database, and payments specifically.
Have a specific concern?
If something here doesn't fully answer your question, or your board has a specific requirement, just ask — hello@orgalyne.com. For the fuller technical detail behind this page, see our Security Overview.