FAQ
Frequently Asked Questions
Quick answers about security model, product workflows, and deployment readiness.
How does Aegis protect my credentials?
Aegis encrypts credential material on the client side before sync operations and applies session and device checks before sensitive actions are allowed. The master key is derived locally and stays under user control. For architecture details, review the Security Overview.
Can Aegis staff read my vault contents?
No. Aegis services handle encrypted vault payloads and policy metadata, but cannot decrypt your credential plaintext without your locally derived master key.
Does Aegis support passkeys?
Yes. Passkey-first authentication is built into onboarding and ongoing account workflows, with support for modern platform authenticators.
Can teams share credentials securely?
Yes. Shared vault workflows support invite, role management, and rotation paths so teams can collaborate without exposing core secrets.
Where can I find security and compliance information?
See the Security and Compliance pages for architecture overviews, policy expectations, and governance alignment guidance.
How do I get started quickly?
Open Onboarding from the Dashboard button in the header, complete setup, then move into Vault and Security Console workflows.
How can I protect passwords better every day?
Use a unique password for every account, use a long master passphrase, and review weak or reused credentials monthly. The Password Protection Guide includes a practical checklist.
What should I do if one of my passwords is exposed in a breach?
Rotate the exposed credential immediately, enable stronger MFA or passkeys, review active sessions, and check for reused passwords across other accounts. You can also verify exposed emails with Have I Been Pwned.