Security
Handle every note as if it were said in confidence. Because it was.
Tidemend is built with HIPAA requirements in mind. Here's exactly what it does to protect clinical documentation, and what still needs to be in place before real client data goes anywhere near it.
This is a demo build: use sample data only
Do not enter real client information. Using Tidemend with protected health information requires a production hosting setup that meets your obligations (including TLS and encryption at rest), Business Associate Agreements with Tidemend and with any hosting, transcription, AI, email, text-message and clearinghouse providers involved, and your own practice policies. About the BAA.
Safeguards
What's built in today.
Plain descriptions of the protections in this build. No badges, no borrowed certifications.
Audit log of every access
Viewing, creating, changing, signing, deleting and exporting clinical records, AI generations and sign-ins are each recorded with who, what and when, including actions clients take in the portal. You can review the trail in the app.
Recordings deleted by default
Session audio exists to produce a transcript and a note. Once the note is generated, the recording is deleted unless you deliberately turn on keeping audio.
Encryption in transit
Production deployments serve Tidemend over HTTPS, so data travelling between your browser and the server is encrypted. The local demo runs without TLS.
Access controls
Passwords are stored as salted bcrypt hashes. Every client, session, note and plan is scoped to the clinician who owns it, and every request is checked against that owner.
Signed notes are locked
Once you sign a note it's locked against edits, and the signature is recorded in the audit log.
Data export
Export your clients, sessions, notes and treatment plans at any time. Your records belong to your practice.
Practice features
The portal, video, payments and reminders.
Practice management brings clients, card payments and outside messages into the picture. Here's how each is handled.
A separate login for clients
Clients sign in to the portal with their own account, set up from an invite link, on a separate session from clinician accounts. Every portal page only shows that client's own appointments, forms, messages and invoices.
Peer-to-peer video
Call setup goes through Tidemend's server, but audio and video travel directly between the two browsers, encrypted. If a relay server is needed on a strict network, it passes along media that stays encrypted.
Join links that expire
Each telehealth appointment gets its own secret link. It works from 2 hours before to 3 hours after the start time, and stops working if the appointment is cancelled or marked a no-show.
Card data stays with Stripe
Clients pay on Stripe's hosted checkout page. Card numbers never reach Tidemend; it keeps only the amount, the method and a reference.
No clinical content in email or texts
Reminders, invites and notifications are kept minimal: no diagnoses, no note content, and message alerts never include the message. Until email and text sending are connected, they wait in an in-app outbox.
A calendar feed with initials only
The subscribable calendar feed is behind a private link, is one-way, and shows client initials rather than names.
Messages inside Tidemend
Client messages stay in the app and portal behind sign-in. They're protected by access controls, not end-to-end encryption.
How data moves
From the room to a signed note, and what's left behind.
Session content only goes where it needs to in order to produce your note.
Step 1: Capture
With your client's consent, audio is recorded in the browser or uploaded. Dictation and typed bullets need no session recording.Step 2: Transcribe
Audio is converted to a transcript with speaker labels. If a hosted transcription service is configured, audio is sent to it for this step.Step 3: Draft
The transcript or your notes are used to draft the note. If a hosted AI model is configured, that content is sent to the model provider.Step 4: Sign, then let go
You review and sign. The recording is deleted by default; the note and transcript stay in your account until you delete or export them.
Shared responsibility
Security is a team effort.
Some protections live in the software, some in how it's hosted, and some in everyday practice. All three matter.
Built into Tidemend
- Audit logging of clinical-record access
- Deleting recordings after the note by default
- Scoping every record to its owner
- Hashing passwords
- Locking signed notes
- Full data export
The hosting setup
- HTTPS/TLS for every connection
- Encryption at rest for the database and stored files
- Backups, monitoring and restricted server access
- BAAs with hosting, transcription, AI, email, text and clearinghouse providers
- A relay (TURN) server for video on strict networks
- Secure management of keys and secrets
You and your practice
- Getting client consent before recording
- Telling clients messaging isn't for emergencies
- Using a strong, unique password
- Reviewing every note before you sign it
- Signing out on shared devices
- Following your record-retention policy
- Using real data only once a BAA is signed
Straight talk
What we don't claim.
Tidemend is built with HIPAA requirements in mind. Whether a particular deployment meets HIPAA depends on how it’s hosted, the agreements in place and how it’s used, so we don’t describe Tidemend as “HIPAA compliant” on its own.
This build hasn’t been through an independent security audit or certification. If and when it is, this page will say so, with details.
Insurance features run on a mock clearinghouse until a clearinghouse account is connected, so nothing is sent to a payer before then. Email and text reminders are only delivered once those providers are connected; until then they wait in an in-app outbox.
Reviewing Tidemend for your practice? Read the privacy policy, the BAA overview and the privacy features.
Try Tidemend with sample data.
Explore every feature with demo clients and fictional sessions. Bring real records only once your hosting and BAA are in place.
