Backend-only connections
Cliniko API keys and Calendly OAuth credentials are handled as backend secrets. They are not kept in browser storage, and database rows store the references and connection state needed to use them.
Security approach
Built for teams that need practical, privacy-aware automation.
MyHealthFollowup keeps bookings in Cliniko or Calendly, limits copied contact data, handles provider credentials on the backend, and shows useful activity without exposing more information than staff need.
Minimal booking data
Booking details are fetched close to send time where practical. Campaign audience details are stored only when an account syncs and uses that feature.
Preference checks before send
Cliniko sends use the relevant provider preferences. Campaigns check recorded permission, unsubscribe, bounce, complaint, and suppression status before delivery.
Redacted operations
Delivery events and dashboard previews are designed to show useful operational status without exposing recipient email addresses unnecessarily.
Data handling
Store configuration, not a second booking system.
The product stores the account configuration needed to send messages: templates, rules, delivery state, audit entries, and billing state. Campaign audience details are synced when the account uses Campaigns; other booking information stays in the connected platform unless it is needed for an email decision.
Provider credentialsCliniko keys and Calendly OAuth credentials are handled as backend secrets.
Templates and rulesStored per account with role-based access controls.
Booking detailsFetched from Cliniko or Calendly as late as practical for rendering and delivery decisions.
Campaign audienceSynced only when Campaigns are used, with permission and suppression status kept for safer future sends.
Logs and eventsRedacted by default, with delivery outcomes visible for support and troubleshooting.
BillingHandled through Stripe Billing; payment card details are not stored by MyHealthFollowup.
Operational safeguards
Controls that matter in day-to-day booking workflows.
Account-scoped users and roles
Audit history for sensitive configuration changes
Idempotent scheduling to avoid duplicate sends
Cancelable and retryable scheduled messages
Clear skipped-message reasons for preference and eligibility checks
Australian AWS region target for production infrastructure
Experience-informed engineering
Built with experience from critical digital health infrastructure.
The backend approach is informed by hands-on engineering experience in regulated digital health environments. That does not replace formal certification or a clinic privacy review, but it shapes the product decisions: explicit tenancy, conservative logging, backend secret handling, auditable changes, and patient-data minimisation.