Where your data lives
You're trusting us with your whole company's books. Here's exactly how that trust is engineered — in plain language, no jargon-flexing.
The architecture is the security
Most construction platforms put every customer into one giant shared database, separated by software rules. SelfConstruct provisions a complete, separate system per company. A problem in one instance is physically contained to that instance — the "one breach, every customer" failure mode of big multi-tenant SaaS doesn't exist here.
🔒 Backups sealed so even our servers can't read them
Offsite backups are encrypted with public-key cryptography (X25519 + AES-256-GCM). Your instance can create a sealed backup but can never open one — the key that decrypts lives offline with the operator, never on any server. A stolen backup file is noise.
📱 Two-factor authentication
Office logins support authenticator-app codes on top of the password — for the company admin credential and for individual team logins. One phished password is no longer enough to open your books.
🔐 Encrypted in transit, hardened at the door
HTTPS on every connection — our .app domains are HSTS-preloaded, so browsers refuse plaintext outright. Passwords are stored as salted PBKDF2 hashes (390,000 rounds). Login and portal-code guessing hits automatic lockouts. Uploaded files serve under unguessable names with signed, expiring links.
👀 Portals see only what you share
Clients, crews, and subs each enter through their own scoped door. A client sees their job's shared progress — never your costs, margins, or other clients. Internal notes and cost data never render on client-facing pages.
💳 We never store card numbers
Payment methods live in your settings as labels like "Visa •4421" — the actual numbers never touch our database.
🚪 Leave with everything
Your data is a company asset, not a hostage. Cancel and you receive your complete database and every uploaded file; we then delete your instance and its storage. Backups age out of retention automatically.
Operations behind the scenes
- Automated health monitoring across every instance with operator alerting
- Backups verified by automated restore tests — we don't just take backups, we prove they open
- Scheduled credential rotation and a written breach-response plan: if we ever confirm unauthorized access to your data, our commitment is notice to you promptly — target within 72 hours
- Additive-only database migrations and staged rollouts — updates can't destroy data by design
Honest limits
No vendor should tell you they're unhackable — anyone who does is selling something else. What we can tell you: the architecture contains failures instead of amplifying them, the backups are useless to a thief, and there's a written plan for the bad day. Questions we haven't answered here: hello@selfconstruct.app — you'll get an engineer's answer, not a brochure's.