The Everborn Platform handles licensing and onboarding records — people’s names, progress, and documents. We treat that as a design constraint, not a policy afterthought: the strongest guarantees on this page are structural, checked automatically on every change to the platform.
Every customer is an isolated tenant. Every database query is scoped to that tenant at the data-access layer — and automated build checks reject any code change that tries to reach the database outside that layer. Cross-tenant access isn’t a rule we follow; it’s a path that doesn’t exist.
All traffic is encrypted in transit with TLS, and data is encrypted at rest on Cloudflare’s infrastructure. Unknown hostnames fail closed — a request for a tenant that doesn’t exist never reaches application code.
Passwords are stored only as salted PBKDF2 hashes. Secrets and API tokens are compared in constant time — a class of timing attack eliminated by a build rule, not by review. Secrets live in the platform’s secret store, never in code or configuration files.
Role-based access control is deny-by-default: every route declares who may call it, and the mapping is locked by an automated test. Coordinators see their own tenant; administrative access is explicit, granted, and logged.
Administrative and coordination actions are logged with actor, action, and time. When something needs explaining — who changed what, when — the record already exists.
The platform runs on Cloudflare’s global edge with redundant storage layers, durable write queues, and serve-stale fallbacks — designed so a single infrastructure component failing degrades gracefully instead of taking the service down.
A short, deliberate list. Each provider processes data only as needed to run the platform, under contract.
Compute, database, document storage, caching, and CDN/TLS — the platform’s core infrastructure, running in Cloudflare’s global network with US-region processing posture.
Connected email and calendar, only when a customer links a Google account — plus document-storage fallback during an outage. Access is per-tenant OAuth the customer grants and can revoke.
Transactional email delivery — the reminders and notifications the platform sends on a customer’s behalf.
SMS and voice — off by default, active only when a customer enables texting or calling features.
We don’t currently hold a SOC 2 or ISO 27001 certification, and we’d rather say so than imply otherwise. What we offer instead is transparency: a written security overview, a data processing agreement, and direct answers to security questionnaires during evaluation.
Found a vulnerability? We want to hear about it before anyone else does: admin@everbornops.com. Please don’t test against production tenants without written coordination.
Send your security questionnaire — we answer it directly, in writing, without a sales filter.
Contact us