Practice rules determine what can be booked
Practice hours, work blocks, services, existing appointments and absences determine the times patients see.
Already have an account?
Log inTempo Booking supports the non-clinical process around consultations and treatments: online booking, availability, calendars and appointment communication. The current product is intended for practices with individual appointments at one location, including dermatology practices.

A consultation, review or treatment has its own duration, suitable care provider, available times and related communication. Tempo Booking brings those steps together so the patient and practice work from the same configured appointment rules.
Tempo focuses on the operational appointment process. It is not presented as an EHR, clinical triage, healthcare billing or a hospital software integration.
Not broad brand values, but concrete choices that determine how Tempo works in your practice.
Practice hours, work blocks, services, existing appointments and absences determine the times patients see.
Team members sign in to their practice workspace. Organisation management remains limited to administrators.
Tempo supports scheduling and appointment communication and does not claim clinical record or healthcare billing functionality.
Consultations, reviews and treatments can each have their own duration and linked dermatologists. Patients only see times that fit the configured availability; front-office staff retain a practice-wide overview while each dermatologist works with their own current appointments.

The trial is designed to evaluate the complete appointment flow with your own practice rules, without a mandatory sales call.
Activate the practice yourself and configure practice details, regional preferences, booking rules and opening hours. Then add services, team members and availability.
The trial starts after activation, requires no payment method and makes no automatic charge. It includes capacity for three active care providers.
You can contact Tempo with questions about setup and use. Data migration and setup performed by Tempo are not currently included.
We distinguish between what the current implementation demonstrably supports and the company, legal and production arrangements that still need to be documented publicly.
Health data is sensitive personal data. That is why we do not use a broad ‘GDPR-proof’ badge or present one technical measure as a substitute for a complete assessment by your practice.
These statements are deliberately limited to behaviour found in the code, database controls or operational documentation.
Data is linked to a practice. Ordinary back-office access uses a signed-in user session, per-practice database policies and permissions for administrators, front-office staff or care providers.
BulkGate provider credentials are stored server-side in encrypted form. Cancellation tokens are stored as hashes rather than readable tokens. This is not a claim about general data encryption.
The practice can specify the domains on which its website widget may be embedded. The allowed domains are applied server-side.
Personal message content and recipient data can be anonymised after a configured period; the current default is 180 days. Critical communication failures are recorded and alerted operationally.
The following are not yet product promises. They must be complete and verifiable before Tempo is used commercially with real practice or patient data.
The legal entity, company details, registered address and separate privacy and security contact points have not yet been published.
The application is designed for a self-hosted Supabase runtime, but the production host, data centre, data region and any international transfers have not yet been established.
Frequency, retention, recovery tests, recovery times and recovery points have not yet been defined as production policy.
Current operational communication alerts are not a complete security or personal-data breach process. Roles, reporting channels, timelines and customer communication still need to be defined.
Targeted mechanisms exist for communication logs, trials and practice deletion. A complete schedule for patient, appointment, billing, audit and incident data is not yet available.
The implementation uses a self-hosted Supabase runtime, Resend, Stripe and a practice-owned BulkGate account. A formal register covering purpose, data category, region and change procedure has not yet been published.
A data-processing agreement, technical and organisational appendix, termination procedure and complete export of practice and patient data are not demonstrably available yet.
The 90-day read-only period after an unpaid trial is a product rule, not a general privacy-retention policy.
Where your practice determines the purposes and means of processing, it is the controller and must choose an appropriate processor. The allocation of roles, instructions and security arrangements should be recorded in writing.
This information supports your product assessment and is not legal advice.Configure consultations, care providers and availability, then try the complete appointment flow for 30 days with no payment method or automatic charge.