Security

Security and responsible disclosure

Found a vulnerability? We want to hear about it, and we will not take legal action against good-faith research.

Report a vulnerability

Email [email protected] with the steps to reproduce, the affected URL or endpoint, and what an attacker could do. Encrypting is optional; plain email is fine. Please do not include other people's personal data.

What happens next

Acknowledgementwithin 3 business days
First assessment and severitywithin 7 days
Fix target — critical7 days
Fix target — high30 days
Fix target — medium / low90 / 180 days
Public disclosurecoordinated with you, normally after the fix or 90 days

In scope

  • pryntid.com
  • app.pryntid.com (console)
  • api.pryntid.com (API)
  • The browser agent and the SDKs we publish

Out of scope

  • Denial-of-service and load tests
  • Social engineering, phishing, physical attacks
  • Third-party services we use (Cloudflare, Stripe, email providers): report to them
  • Reports from automated scanners without a demonstrated impact
  • Missing best-practice headers or SPF/DMARC settings without an exploit
  • Bot or fingerprint “bypasses” of the free tier’s detection — welcome as product feedback, not as vulnerabilities

Rules

  • Test only accounts you created (a free account is enough).
  • Never access, change or keep other customers’ data. If you reach any, stop and tell us.
  • Keep automated requests gentle (under 10 per second) and avoid anything that degrades the service.
  • Give us reasonable time to fix before telling anyone else.

Safe harbor

If you follow these rules in good faith, we consider your research authorized, we will not pursue or support legal action against you, and we will work with you to understand and fix the issue. We do not run a paid bug bounty yet; we credit researchers (with permission) on this page.

How we protect the service

  • Every customer’s data is isolated by account and environment; this is checked by automated tests on every console route.
  • Multi-factor authentication, SSO/SAML, roles, session revocation and an exportable audit log in the console. Platform operators must use MFA.
  • Secret API keys and signing secrets are hashed or encrypted at rest; results can be sealed (AES-256-GCM) so the browser cannot read them.
  • TLS 1.2+ everywhere; security headers on the site and console; no inbound ports open on our servers (Cloudflare tunnel).
  • Webhooks are signed (HMAC-SHA256 with timestamp) and can only be delivered to public addresses.
  • Dependencies, code and container images are scanned automatically every week and on every change.
  • Daily backups, restore tests, and data retention per plan.

Not done yet

Prynt has not yet completed a SOC 2 audit or an independent penetration test. Our internal assessment and the plan to get there are summarized on the Trust page.

Thanks

No reports yet — be the first.

security.txt