Security that fits sensitive records
GenesisOS holds contact, lending, investor, and accounting information. Here is how we protect it, in plain terms.
Effective October 8, 2026
Separated by organization
Every account’s data is kept apart from every other account’s.
Encrypted secrets
Tax IDs and integration credentials are encrypted with AES-256-GCM.
Controlled access
Roles, protected sign-in, and a throttle against password guessing.
Data separation
GenesisOS is multi-tenant, and every record belongs to one organization. The application’s data layer adds the organization filter to queries automatically, so one customer’s staff cannot see another customer’s records through the normal paths of the application. Uploaded documents are stored outside the public web folder and are served only through the application after an access check, in a folder per organization.
Authentication and sessions
- Passwords are stored only as salted, one-way hashes, never in readable form.
- Sign-in throttling. Repeated failed sign-ins temporarily lock further attempts (five failures triggers a 15-minute lockout), which slows automated guessing.
- Session cookies are HTTP-only (not readable by page scripts), sent over HTTPS only, and use SameSite=Lax. Sessions expire after a fixed period.
- Forms are protected against cross-site request forgery with per-session tokens.
Access control
Staff accounts have roles, so administrators decide who can manage settings and who works with records. Client-portal users (tenants, owners, borrowers, investors) sign in separately and see only the statements, documents, and records their organization shares with them.
Encryption
- In transit. The application is designed to be served over HTTPS.
- Sensitive fields at rest. Tax identification numbers and integration credentials (such as SMTP and SMS provider secrets) are encrypted with AES-256-GCM before being stored, and are shown masked in the interface.
Backups
The platform includes built-in backup tooling, with the option to send backups to a remote destination, so data can be restored after a failure.
Accountability
- Audit trail. Accounting entries are posted to a double-entry ledger, and unusual activity is flagged for review.
- Approval workflows. Organizations can require approval before sensitive actions, such as paying bills.
- Deletion safeguards. The application blocks deleting records that other records depend on, such as properties with investor money.
Your part
Security is shared. Use a strong, unique password; give users only the role they need; remove people when they leave; and review who has portal access.
Reporting a vulnerability
If you believe you have found a security issue, please tell us through legal@getgenesisos.com before disclosing it publicly. Include enough detail to reproduce it. We will acknowledge your report, investigate, and work with you in good faith. Please do not access other customers’ data, degrade the service, or use social engineering while testing.