Security & data handling
Understanding where information goes is part of choosing a practice system. This page describes our public demo inquiry process and the security questions to resolve before a practice implementation.
Public website and inquiry data
Our public website uses HTTPS. Demo inquiries are collected through GoHighLevel/LeadConnector and managed for follow-up. Email providers support our communications. Our Privacy Policy describes collection, use, sharing, retention, and information requests.
Access and account security
Before a practice goes live, the implementation review needs to identify who requires access, what each staff member may view or change, how accounts are authenticated, and how access is removed when someone leaves. Use individual accounts and available multifactor authentication, and never send passwords through the public inquiry form.
Encryption and vendors
HTTPS protects the connection to this website. It does not, by itself, establish the security of every connected system. Encryption at rest, backups, subprocessors, data locations, and each integration's handling of data need to be evaluated for the agreed practice configuration. Contact us to discuss the documentation required for your review.
Patient information and agreements
A public demo request does not create a patient-data processing agreement. Before protected health information is used, the practice and HouseCall HQ must review the intended workflow, applicable requirements, vendor configuration, and any required Business Associate Agreement. BAA availability and coverage must be confirmed for the specific services; they should not be assumed from this website.
We do not present this website as evidence of HIPAA certification or SOC 2 certification.
Retention and incident planning
For business inquiries, see the retention section in our Privacy Policy. Practice data retention, deletion, backup handling, incident contacts, and notification responsibilities need to be documented for the implementation before patient data is introduced.
Report a concern
Email [email protected] with a general description of a suspected security issue. Do not include patient data, credentials, or other sensitive records in the initial message. This email is not an emergency medical channel.