For therapy practices
The days between sessions, in the room with you.
Clients already keep a daily journal in TherapiSync — free text, a mood, the activities of the day. This is where a therapy practice can see that history — with the client’s consent, one entry at a time, without asking anyone to recite a week from memory.
One account per practice
The office is the account. Each clinician works their own panel inside it, and a colleague covering a shift can still open the chart in front of them.
Clients join with a code
Share a join code at the first session or by email. The client types it into the app once; no separate sign-up flow for the practice to manage.
The daily journal, not a summary
Free text, a mood tag, an activity tag — one entry a day, on one calendar, by day, week or month, so a session starts from what actually happened.
Clients push, the clinic reads
Sync is one-directional by design, and it is enforced as a database privilege rather than a convention. Nothing the practice does can write to a client’s journal.
Every access, accounted for
Logins, issued join codes, and every client-link change are written to an append-only audit log — a record a practice can answer for, not just a feature it trusts.
Consent that can be withdrawn
A client unlinks from their own device, on their own schedule, and can ask that everything they sent be deleted along with it.
How a client joins
- 01
Share a join code
A clinician shares their practice’s join code with a new client.
- 02
The client enters it
Once, in the TherapiSync app, after creating their own account.
- 03
The journal appears
Their entry history syncs to the practice until they unlink.
Straightforward pricing
See full pricing →Free to start. After that, a flat rate per Provider seat — the clinician role with full read/write access — while account owners and read-only staff stay free and unlimited on every plan. Computed the same way for every practice, with no custom billing.
Built to be trusted with a client's journal
Read about our security practices →- A practice's data is isolated at the database level, not just by application code.
- Clinician accounts require email verification before the office is usable.
- Passwords are hashed, never stored in plain text, and never leave the server.
- Traffic to the portal and the sync API is encrypted in transit.