പ്രധാന ഉള്ളടക്കത്തിലേക്ക് പോകുക

Trust center

Review the evidence for your deployment.

Security, privacy, compliance, and operational information for organizations evaluating Zof for production use.

Content reviewed November 8, 2026. Contractual commitments are defined in your executed agreement.

This reference is currently available in English. The same English text is shown here so security and legal information remains consistent across languages.

01Start with the system you intend to operate

Zof supports AI testing and governed remediation across software systems. A security review should cover what the platform can read, where tests execute, which actions require approval, what evidence is retained, and how access is removed. These decisions matter as much as the selection of a hosting region.

Use this trust center to assemble a review package for engineering, security, privacy, legal, and procurement. Begin with the intended environment and data classification, then map each requirement to an applicable document, configuration, or contractual commitment.

  • Architecture: execution placement, control and intelligence services, integrations, and permitted network destinations.
  • Data protection: source code, test inputs, logs, traces, screenshots, model requests, retention, and deletion.
  • Governance: user and service identities, roles, credentials, approval policy, and evidence export.
  • Operations: support contacts, incident escalation, recovery expectations, and the service schedule in your agreement.

02Assurance and regulatory scope

Zof does not have a SOC 2 report or a penetration test report today. Ask security@zof.ai which evidence is available for the service in scope, and record anything unavailable in your vendor assessment.

GDPR and HIPAA are legal frameworks, not certifications supplied by a security badge. A GDPR assessment depends on the processing purpose, parties, locations, safeguards, and applicable law. Do not submit protected health information without an agreed scope and any required agreement.

03Deployment and data boundaries

Zof runs as a managed cloud. On-prem deployment is available as a scoped proof of concept, and other private deployment options are scoped per engagement. Execution location alone does not establish where every piece of data is processed.

Review control-plane communication, model-provider requests, artifact uploads, logging, support access, and connected tools separately. Identify what leaves the execution boundary, the destination and purpose, and who approves the flow. Confirm the implementation and service scope for your deployment with the Zof team.

04Documents for legal and procurement review

Each document addresses a different part of the relationship. Read the privacy notice for website and business-contact data, the DPA for customer personal data, the subprocessor information for service-provider review, and the agreed service schedule for availability and support.

05Request a security review

Send your company name, business contact, intended deployment, data classification, procurement deadline, and the questions or questionnaire you need addressed. Identify any mandatory assurance, residency, contractual, or sector-specific requirements before a pilot begins.

Security materials may contain confidential information. We will confirm which materials apply to your evaluation, their availability, and any confidentiality terms. Review the named service, assessment date, coverage period, exclusions, and customer responsibilities in each document; a document about a hosting provider is not an assessment of Zof itself.

Do not send credentials, production datasets, health information, or complete vulnerability exploits in an initial procurement email. Request a suitable transfer method if sensitive material is necessary.

06How to use this information

This page supports vendor evaluation and describes the topics to confirm for your use of Zof. The applicable Terms of Service and DPA, together with any executed agreement, order form, and service schedule, define the commitments for your organization according to their order of precedence. Public security descriptions do not amend those terms or extend a commitment to every deployment.

Security depends on the selected service, configuration, integrations, and customer environment. Confirm the controls and evidence for the actual scope you will purchase before transferring regulated information or enabling production access.

01തെളിവും നിയന്ത്രണവും

നേതാക്കൾക്കും ഓഡിറ്റർമാർക്കും ബോർഡിനും യഥാർത്ഥത്തിൽ ഉപയോഗിക്കാവുന്ന തെളിവ്.

Every verification run, policy evaluation, approval, and outcome is recorded as durable evidence, exportable for release reviews, compliance packs, and executive readouts.

PROVENANCE

Who, what, why

Every decision attributable to policy and a named approver.

ഓഡിറ്റ്-റെഡി

കംപ്ലയൻസ് പാക്ക്

നിങ്ങളുടെ സ്വന്തം അവലോകനത്തിനുള്ള തെളിവ് ട്രെയിൽ.

കേഡൻസ്

ഷെഡ്യൂൾഡ്

നിങ്ങളുടെ ഷെഡ്യൂളിൽ സ്വയം ജനറേറ്റ് ചെയ്തത്.

AUDIT-READY/reports
ഓരോന്നിനും Generate, Schedule ആക്ഷൻ, Generated Reports, Saved Views, Scheduled ടാബുകൾ സഹിതം Weekly Release Summary, Coverage Trends, Risk Assessment Report, Compliance Evidence Pack — നാല് ടെംപ്ലേറ്റ് കാർഡ് കാണിക്കുന്ന Zof റിപ്പോർട്ടുകൾ പേജ്.
ഉദാഹരണ റിപ്പോർട്ട് കാഴ്ച · /reports · നാല് സ്ഥാപനതല ടെംപ്ലേറ്റുകൾ.