Recovery does not end
after treatment.
Neither does our
responsibility.
Sobriety Journey exists because the most critical period of recovery — the weeks and months after discharge — is also the least supported. We built a platform to change that. This page explains why, and how.
The most dangerous time in
recovery is after treatment.
Research consistently shows that the 90 days following discharge from residential treatment are when relapse risk is highest. Patients leave structured environments — where meals, routines, and peer support are built in — and return to the same conditions that contributed to their substance use in the first place.
The gap is not a failure of treatment. It is a failure of aftercare. Most treatment centres discharge patients with a follow-up appointment date and a phone number. That is not enough.
The First 90 Days
The period immediately following discharge is consistently identified in clinical literature as the highest relapse risk window. Daily structure and connection during this period significantly improves long-term outcomes.
Re-Admission Rates
Many patients who relapse re-enter treatment — sometimes multiple times. Structured aftercare that maintains therapeutic connection between discharge and the next crisis is the most effective intervention point.
Connection Matters
Isolation is one of the strongest predictors of relapse. Platforms that maintain structured connection — between patient and therapist, and between patients in recovery — show measurable impact on engagement and stability.
Built from the inside out —
not from assumption.
Sobriety Journey was not built by technologists who read about addiction recovery. It was built by someone who has spent 40 years walking alongside people in need — as a pastor, as a counsellor, and as a board member, pastoral caretaker, and CEO of Stabilis Treatment Centre in Pretoria.
Every design decision in Sobriety Journey was tested against one question: what does this mean for the person at 2am who is in crisis? That question is not a marketing line. It is in the development documentation. It is the standard we hold every feature to.
A system failure for a patient at 2am has real clinical consequences. Reliability and data integrity are not optional — they are clinical requirements.
What we will never compromise.
These principles are not marketing commitments. They are enforced at the architecture level — in the code, in the database, and in every feature decision.
AI Never Replaces the Therapist
AI features in Sobriety Journey assist with reflection prompts, pattern awareness, and pre-session summaries. AI never provides therapy, assesses risk autonomously, or makes referral decisions. These boundaries are non-negotiable and enforced at the architecture level.
Patient Data Belongs to the Centre
Patient records belong to the admitting treatment centre — not to Sobriety Journey, not to SANCA National, not to any umbrella organisation. Data isolation is enforced at the database level. Cross-centre access is impossible.
No PII in AI Queries
Every AI feature runs on anonymised database views. The AI never has access to patient names, contact details, or clinical notes. This is not a configuration — it is architectural.
POPIA by Design
POPIA compliance is not an add-on. Explicit consent at onboarding, purpose limitation enforced at every data access point, complete audit trail, and data exportable on request. Built in from day one.
Children's Act Compliance
Minor patients receive specific handling: SA Children's Act s.129 compliant consent recording, guardian fields, safeguarding panel with mandatory reporting audit trail, and elevated risk alerts on the therapist dashboard.
Complete Audit Trail
Every action by every user — across every role — is logged with a timestamp and role attribution. The audit log is permanent, exportable, and required for clinical governance and POPIA accountability.
The compliance layer is not
a feature. It is the foundation.
Every piece of compliance infrastructure in Sobriety Journey was built before the feature it protects — not added after.
Row-Level Security
Supabase Row-Level Security enforces data isolation at the database level. No application-layer configuration can override it. Each query returns only the data the authenticated user is permitted to see.
DSD SP4.4 Aligned
The reporting tools were built alongside the DSD SP4.4 service specification. Quarterly KPI reports, SACENDU exports, aftercare follow-up tracking, and provincial coverage data are all built in — not bolted on.
Encrypted in Transit and at Rest
All data is encrypted in transit (TLS) and at rest (Supabase encryption). Session tokens are hashed. Demo access keys are bcrypt-hashed. No plaintext credentials are stored anywhere in the system.
Clinical Safety by Design
The platform is designed for people in one of the most vulnerable periods of their lives. Every design decision is evaluated against clinical safety — not just functionality.
If this resonates — let's talk.
Whether you are evaluating Sobriety Journey for your treatment centre, your member organisation, or a national deployment — we would like to hear from you.