Trust centre

Security and privacy information for informed procurement.

This page gives buyers a clear, high-level view of Engara's legal entity, certification evidence, privacy position and review process. Deployment-specific architecture and controls are shared through a scoped security conversation.

Legal entityEduSight Technologies Inc., Vancouver, Canada
Certification evidenceCurrent record linked through IAF CertSearch
Deployment reviewHosting, data flow and provider detail available on request
Independent record

How can buyers verify the current certification?

The official IAF CertSearch record for EduSight Technologies Inc. is the reference for the current ISO/IEC 27001 standard, certificate scope, certification body, certificate number and validity dates. These variable fields are kept at their source so buyers can review the current record directly.

Open the IAF CertSearch record

Privacy position

How does Engara approach privacy requirements?

GDPR and PIPEDA are privacy laws rather than independent attestations. Whether and how they apply depends on the customer, the people involved, the purpose of the journey, the information collected and the places where processing occurs.

Engara's privacy policy explains our general website and service practices. A customer remains responsible for the lawful basis, notices, permissions and decision-making requirements for its own deployment. Contractual roles and deployment-specific responsibilities are addressed during contracting.

Deployment detail

Which details depend on the customer's deployment?

Hosting providers, processing regions, connected channels, sub-processors, retention, deletion, model processing and international transfers depend on the architecture and commercial terms selected for a customer. Engara shares the relevant information during solution design and procurement.

Data flow and hosting

Ask for the systems, providers, locations and data categories involved in the proposed journey.

Retention and deletion

Confirm active-record retention, export needs and the agreed deletion lifecycle before launch.

AI and model processing

Review which model services receive information, for what purpose and under which contractual terms.

Channels and integrations

Include the privacy and security terms of connected messaging, CRM, analytics and business systems.

Security programme

How should buyers evaluate Engara's controls?

Security should be evaluated against the actual deployment rather than a generic checklist. Engara's review focuses on the information involved, access paths, integrations, operational responsibilities and evidence required by the customer.

  • Identity, access and administrative responsibilities.
  • Data transmission, storage and connected-system boundaries.
  • Change, vulnerability and incident-management expectations.
  • Customer configuration, content governance and human oversight.
  • Retention, deletion and business-continuity requirements.
Procurement

How can a buyer request more information?

Send the planned use case, regions, channels, integrations and the information categories in scope. Engara will provide the relevant answers and identify which details belong in the order, data-processing terms or implementation design.

Email support@engara.ai for security and procurement questions, or use the contact page.

Frequently asked questions

What do procurement teams ask most often?

Where can I verify Engara's information-security certification?

Use the linked IAF CertSearch record for EduSight Technologies Inc. to confirm the current standard, certificate scope, certification body, certificate number and validity dates.

Are GDPR and PIPEDA privacy laws?

Yes. GDPR and PIPEDA are privacy laws, not independent attestations. The responsibilities and safeguards that apply depend on the parties, people, data and regions involved in a deployment.

Where can Engara customer data be hosted?

Hosting and processing locations depend on the contracted deployment. Contact Engara for the provider, region, transfer and data-flow information relevant to your planned use.

How long are conversation records retained?

Retention and deletion follow the customer's contracted configuration and applicable legal requirements. Contact Engara for the lifecycle that applies to a proposed deployment.

Which security information can a buyer request?

Engara can respond to procurement and security questions with information appropriate to the planned deployment and confidentiality requirements.

Review your use case

Need deployment-specific security information?

Share the regions, channels, integrations and data categories in scope so Engara can respond with relevant detail.

Contact Engara