Security & Trust

The controls we can describe from how EyeconX is built. Last updated: October 3, 2026.

Encryption

Clinic sign-in and patient-facing pages run over HTTPS, so information is encrypted while it is moving between the browser and EyeconX.

Access controls

Staff see what their role allows. Roles include manager, doctor (ECP), staff, and admin, and features can be turned on per clinic.

Authentication

Each clinic signs in with its own username and password. Accounts are isolated to that clinic.

Activity logging

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.

Privacy requirements

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.

If something looks wrong

Report a suspected account compromise or a privacy concern to support. Use the contacts below.

  • Email support@eyeconx.net
  • Call 1-866-533-2669 ext. 706
  • Use a strong password and limit admin access to people who need it
  • Keep practice-system data and patient contact details accurate
  • Set patient preferences and obtain the consents your practice requires

What else is in place

  • Gateway API keys are scoped to the clinic’s authorized business number
  • Outbound texts are queued, and failed messages can be reviewed and resent
  • Email sending domains can be authenticated so messages are more likely to arrive
  • Support works with clinics through these support channels