Encryption
Clinic sign-in and patient-facing pages run over HTTPS, so information is encrypted while it is moving between the browser and EyeconX.
The controls we can describe from how EyeconX is built. Last updated: October 3, 2026.
Eye care clinics trust EyeconX with operational and patient-related information. This page states the controls we can support from the product as it is built. It is not a certification, and it is not a substitute for a signed security questionnaire or a BAA where one is required.
Clinic sign-in and patient-facing pages run over HTTPS, so information is encrypted while it is moving between the browser and EyeconX.
Staff see what their role allows. Roles include manager, doctor (ECP), staff, and admin, and features can be turned on per clinic.
Each clinic signs in with its own username and password. Accounts are isolated to that clinic.
Clinics can review what was sent. Text messages show a delivery status: accepted, queued, sent, and then delivered, undelivered, or failed. Communication history is available when you need to check a patient or the clinic.
EyeconX is built for clinics in Canada and the United States. Clinics can set communication preferences, offer unsubscribe, and use consent-aware outreach. The clinic remains responsible for privacy laws that apply to its patients, including PIPEDA in Canada and provincial health privacy rules where they apply.
Read the Privacy Policy for how information is collected and used.
Report a suspected account compromise or a privacy concern to support. Use the contacts below.