Security

• The signing key of every wallet created in Orbook is sealed with AES-256-GCM before it is stored. Keys are never stored in plain text.
• Keys are decrypted only on the server, only to sign a transaction a member with the right role asked for.
• The Owner decides which roles may export keys, and can switch export off for the whole organization.
• Watch-only wallets have no key in Orbook at all.

• Passwords are stored as hashes. Email addresses are verified with a one-time code.
• Sessions last up to 12 hours. You can see your active sessions and revoke them in Settings → Security; changing your password signs out the others.
• Five roles (Owner, Admin, Trading Manager, Trader, Analyst) limit what each member can see and do.
• Two-factor authentication is supported by the sign-in flow, but its setup screen isn't available yet.

Every action in an organization is written to an append-only audit log. Each entry carries a SHA-256 hash that covers the entry before it, so editing or deleting any entry breaks every hash after it. Owners and Admins can run Verify chain at any time: it reports “Chain intact” or the first entry where the chain breaks.

Launches are reviewed before they are signed, and risky actions ask for a risk notice to be acknowledged first. Every live launch keeps its quote, signed transactions and receipts in Launch Logs.

Email [security@ email] with what you found, how to reproduce it and its impact. Please:

• test only against your own accounts and organizations;
• don't access other users' data, move their funds, or degrade the service;
• give us reasonable time to fix the issue before you disclose it.

We'll acknowledge your report within [response time]and keep you updated. We won't take legal action against research done in good faith under these rules. Our machine-readable contact is at /.well-known/security.txt.