PsyEntry security
PsyEntry 1.0 is local-first and has no PsyEntry account, sync service, telemetry, advertising, analytics, or crash-report upload. Local-first software still depends on the security of the device, OS account, backups, exports, and operator practices.
Design summary
- Direct identifiers and clinical free text use AES-256-GCM application-layer encryption.
- A random vault key is wrapped by password- and recovery-derived keys using PBKDF2-HMAC-SHA256 with a per-vault salt and 600,000 iterations.
- The recovery phrase itself is not stored; only its confirmation state is retained.
- Finalized notes, addenda, clinical-plan revisions, and audit history have application and database integrity controls.
- Encrypted backups are validated before a transactional replace restore.
- The app locks after inactivity and clears active key material on lock.
- User-directed external writes are audited without recording the destination path or clinical content.
- Support failures use fixed references and an optional deliberately redacted support report.
- Public macOS releases must be signed; the direct build must also be notarized and stapled, while the App Store build uses Apple’s sandbox.
- Public Windows releases must pass the platform package and certification gates. Microsoft signs an accepted Store package; a direct MSI requires timestamped publisher signatures on both launcher and installer.
Important limits
The database is not wholly encrypted. Some operational metadata can remain visible at the SQLite layer. Plain-text reports are not encrypted after export. A recovery phrase cannot recreate a missing database, and an encrypted backup cannot be recovered without its separate passphrase.
PsyEntry does not replace FileVault or BitLocker, a protected OS account, patching, physical security, a verified backup program, privacy procedures, or incident response.
Supported versions and updates
Security maintenance targets the current public major release and its latest available update. Obtain updates only from the Apple App Store, Microsoft Store, or signed PsyEntry download page once the relevant channel is public. Do not install from an unverified mirror or bypass operating-system security or publisher warnings.
Report a vulnerability
Email support@psyentry.com with “Security report” in the subject. Include the affected version, distribution channel, reproduction steps, observed impact, and only the minimum non-sensitive evidence needed. No encrypted-email key is currently published, so do not include client data, credentials, recovery phrases, passwords, backup passphrases, or clinical exports.
Reports are reviewed and handled through coordinated, case-specific communication. Triage, remediation, disclosure timing, credit, and any testing authorization are determined for the report. Do not access another person’s records, degrade a production practice, or assume testing authorization, safe harbour, a reward, or a disclosure deadline unless an authorized representative provides it in writing.
Privacy incidents
For a suspected privacy incident rather than a product vulnerability, contact support@psyentry.com and follow the affected practice’s incident procedure.