Skip to content
Security

Every click is checked. Before any patient detail loads.

Syncroly checks practice, role and consent on the server for every read, message and download. The same protection runs on every plan, Free included.

General notes
  1. Encrypted in transit and at rest
  2. Database and files hosted in the US
  3. No patient details to a receiving practice before consent
  4. A BAA at setup for practices covered by HIPAA
Zero-trust, consent-gated architecture

One referral, start to finish.

Steps
  1. The referring practice sends a referral. Its files are scanned for malware, its notes are encrypted a second time, and the send is logged.
  2. The patient or pet owner gets an email with a secure link, never the referral itself. Notes and files stay in Syncroly.
  3. They give consent on their link, or the referring practice confirms it already has consent. Either way, it's on file before the receiving practice sees anything.
  4. The receiving practice signs in. Syncroly checks practice, role and consent before the referral opens, and again for every message and download.
How it works

Technical safeguards.

  1. Only the practices on a referral can open it.

    On every request, Syncroly checks that your practice sent or received the referral and that you're still on its team. A receiving practice also needs consent on file.

  2. Two layers of encryption.

    Connections use TLS 1.2 or higher, and the database and files are encrypted at rest with AES-256. Notes, messages and drafts get a second layer in the app, AES-256-GCM, before they're stored.

  3. Every file is malware-scanned.

    Files are stored under an ID, never their name, and encrypted with AES-256. A flagged file is blocked twice: by the app, and by the file vault itself.

  4. We store a bcrypt hash, never your password.

    You confirm your email before your first sign-in. Idle sessions sign out on their own, and changing your password signs you out everywhere.

  5. Who did what, and when. Kept 7+ years.

    It records sends, first opens, consent, status changes, messages sent, file uploads and downloads, sign-ins, and team and settings changes.

The database has managed backups with point-in-time recovery.

Where data lives

Hosted in the US. Four vendors, each under a BAA.

No marketing analytics in the app, or in any email or link we send to patients, pet owners and providers. Our payment processor sees billing details, never patient details.

Inside the BAA line
  • VercelHostingRuns Syncroly
  • NeonDatabaseStores referrals
  • AWSFile storageStores and scans files
  • MicrosoftEmailSends the links
Kept away from patient data
  • PaymentsBilling only
  • Error reportsFiltered first
  • Marketing analyticsPublic website only

Every vendor we use, and what it receives, is in our Privacy policy.

Your practice's controls
  • Everyone sees by role.Admins and coordinators see the practice's referrals. Your practitioners see their own, or all, if you choose.
  • One front desk login. A name on every send.On Teams, each front desk person has their own PIN, so every send, message and upload carries their name.
  • An Activity Log for admins.Who did what and when, recorded on every plan. Admins view and export it on Solo, Teams and during your trial.
  • A BAA at setup, on every plan.Practices covered by HIPAA accept it at setup, before sending any patient details. It sets out how we use and protect patient data, the subcontractors we use, and breach notice.

Vet practices get every protection on this page. HIPAA doesn't cover vets, so there's no BAA to sign.

Security question? Found a vulnerability?

Email security@syncroly.co. For a vulnerability, include the feature, what happened and the steps to reproduce it.

Revised October 2026