Data and boundaries
What Alotime processes, who can see it, where the system refuses to act, and — plainly — which formal certifications are not in place yet.
Alotime is an early-stage system. Standard practices — encryption in transit, access logging and data minimization — are built in from day one. Formal certifications (including HIPAA attestation) are not yet in place; this page will be updated the moment any of them is.
Alotime processes call and message content, basic patient identifiers (name, phone), appointment status and the clinic's own scheduling data. It does not request financial information, and clinical questions are never answered by the system — they are handed to your team.
The system does not give clinical advice and it does not make clinical decisions. It gathers information, reminds and routes — and hands anything clinical, financial or unusual to your team with the whole conversation attached.
Where it stops is configured with you, in writing, during setup: certain topics, certain phrasing, any sign of distress, or simply the patient asking for a person.
In managed cloud infrastructure with access limited to your clinic's own configured team.
The system does not give clinical advice or make clinical decisions — it gathers information and hands ambiguous cases to your team, by design.
Yes. Your clinic can request deletion of stored conversation and patient data at any time.
Yes — assistant accounts are scoped to conversations, appointments and patients by default. Automation configuration and reports stay with the clinic owner.
Security and data questions are common in the first conversation — bring them to the discovery call.
Founder-led · built for dental clinics
I build Alotime for the hours a dental practice cannot cover. If something in the system gets a patient conversation wrong, that is mine to fix — and you will always know who to call.
Get Alotime. Get more smiles.
