Security overview
Effective date: November 20, 2026. ProtocolGurus ("ProtocolGurus," "we," "us," or "our").
This page describes ProtocolGurus's security posture for the public website and partner portal. It is informational and does not expand warranties beyond the Terms of Service. For privacy practices, see the Privacy Policy. Clinics that need a Business Associate Agreement (BAA) should request one in writing before sending PHI.
1. Our role
ProtocolGurus is a B2B protocol design provider. Partner clinics may submit maps and related materials through the authenticated portal. We apply safeguards appropriate to that context. We do not claim to replace your clinic's own HIPAA policies, workforce training, or endpoint security.
2. Controls we use
- TLS encryption in transit for the website and portal
- Managed hosting and Postgres with provider-side encryption at rest (Vercel / Prisma Postgres stack)
- Object storage for uploads through our configured blob provider
- Password hashing for email/password accounts; OAuth via Google when enabled (Apple planned)
- Optional MFA (TOTP) and passkeys; MFA enrollment may be required for admin roles
- Role-based access control inside the portal
- Account approval gates for new signups and new clinic foundations
- Session cookies with secure settings in production
- Security-related HTTP headers (CSP report-only on portal surfaces, referrer policy, and related controls)
- Application and platform logging for operations and incident response
3. Payments
Card payments are processed by Stripe. We do not store full payment card numbers on our servers. Stripe's security documentation applies to card data in their environment.
4. Integrations
Calendar OAuth tokens, telephony credentials, and similar secrets are stored for the features you enable and used only to provide those features. Disconnect integrations you no longer need. Third-party security is governed by those vendors' terms.
5. Your responsibilities
- Use strong unique passwords or passkeys; enable MFA when available
- Limit portal seats to authorized workforce members; revoke access when staff leave
- Keep clinic devices patched and avoid shared unsupervised logins
- Submit PHI only through approved portal channels, never public marketing forms
- Report suspected account compromise immediately
6. Incidents
If we become aware of a security incident affecting your personal information or PHI we process, we will investigate and notify affected clinic contacts as required by law and any applicable BAA. Notification timing and content follow those obligations.
7. Vulnerability reports
If you believe you found a security issue, contact us through the contact form with enough detail to reproduce the issue. Please do not access data that is not yours or disrupt the service. We will acknowledge good-faith reports.
8. Related documents
Last updated: November 20, 2026.
Contact
Privacy, legal, and security questions: call (317) 753-4547, or use the contact form. Portal account holders may also message us from inside the partner portal.
