Security at Pagyra.
People put confidential documents in Pagyra. Here is what protects them, in plain terms, including what we don’t offer yet.
Workspaces are kept apart
- Every database read and write is scoped to one workspace by the code that talks to the database, not by developers remembering to.
- An automated test suite tries to reach one workspace’s data from another through every route, search, export and share link. A failure blocks the release.
- Uploaded files are stored per workspace and never shared between workspaces.
Accounts and sign-in
- Passwords are hashed with argon2id and never stored in a form we can read.
- Sign-in cookies are HttpOnly, Secure and SameSite, and end when you sign out or change your password.
- Verification and reset links are single-use, stored hashed, and expire in 24 hours and 1 hour.
- Sign-in, sign-up and password reset are rate-limited, and never reveal whether an email has an account.
- Anyone can sign in or sign up with Google instead of a password.
- On Enterprise, single sign-on over OpenID Connect works with Okta, Microsoft Entra ID, Google Workspace and others, and can be required for your email domains.
Share links
- Each link carries a random token of at least 128 bits, so links cannot be guessed.
- Links allow reading, and on Pro and Enterprise commenting. They never allow editing.
- A link can be turned off instantly. On Pro and Enterprise it can have an expiry date or a password; link passwords are hashed with argon2id, and guesses are rate-limited.
- An admin can switch off every link in the workspace at once.
- Every visit through a link is recorded. On Enterprise, admins can view and export that log and set how long it is kept.
Encryption
- All connections to Pagyra are encrypted with TLS.
- Stored files are encrypted at rest.
Production access
- Access to the production database is limited to one account protected by multi-factor authentication, and its access logs are kept.
Backups and availability
- Continuous database backups with 7 days of point-in-time recovery and daily snapshots kept for 30 days.
- Uploaded files keep earlier versions for 30 days.
- We restore a backup into a separate environment before launch and every quarter, and record the result.
- We aim for 99.9% availability each month, on managed infrastructure with automatic failover.
No outside trackers, few services
- No advertising, third-party analytics or session-replay code, in the app or on this site. Fonts and icons are served by Pagyra.
- Error reports have document content, cookies and credentials removed before they are sent.
- Only a short list of services processes customer data, and it is public.
- Gyra, the AI assistant, sends content only when someone uses it, and an admin can turn it off for the workspace at any time. The service it uses is named in our list of subprocessors.
Not available yet.
We would rather tell you now than have you find out in a security review. If one of these matters to your firm, tell us.
- Two-factor authentication
- Single sign-on over SAML (OpenID Connect is supported)
- A SOC 2 or ISO 27001 report
- Data stored outside the United States
Reporting a vulnerability.
Email support@pagyra.com with what you found and how to reproduce it. Please give us a chance to fix it before telling anyone else, and don’t access or change data that isn’t yours while testing. We read every report and will tell you what we do about it.
security.txtSubprocessorsPrivacy policyData processing agreement