Data Privacy and Security Policy

Executive Summary

Our Commitment to Your Data Privacy & Security

At ZeroStone, the security and privacy of your data form the cornerstone of our partnership. As we pioneer the future of business with advanced agentic AI solutions, we recognize that our most important responsibility is upholding the trust you place in us to handle your sensitive information with the utmost care, integrity, and confidentiality.

This document outlines our comprehensive data privacy and security framework, which governs every aspect of our engagement. From initial financial analysis leveraging your data, to building solutions within your environment or ours, and through to the continuous managed services of data infrastructure and AI governance—our approach is built upon unwavering principles of security by design, data minimization, and transparent operations. We are committed to providing you with state-of-the-art AI capabilities, backed by a security posture that ensures your data is always protected, and that its use is always limited to the specific purposes you have authorized.

Across our service lines, these principles are rigorously applied:

Financial Analysis

All analyses are conducted within secure, isolated environments typically within your own cloud infrastructure, ensuring your data never leaves your control. We enforce strict access controls and prioritize de-identification and aggregation techniques to protect data while delivering critical insights.

Solution Development

Our development process is governed by strict data security and privacy protocols, regardless of where the solution is built. Whether development occurs within your cloud environment or our own secure labs, our teams operate under the principle of least privilege, ensuring access to your data is limited, role-based, and logged. We employ secure coding practices and data handling procedures throughout the entire development lifecycle to safeguard your information, guaranteeing its integrity and confidentiality are maintained at every stage of creation.

Managed Services

Our commitment to your data's security and privacy is continuous. For our managed agentic AI solutions, we apply the same rigorous security framework whether the solution operates within your cloud environment or ours. This includes continuous monitoring for threats, strict enforcement of access controls, and ongoing governance to ensure the AI solution adheres strictly to your data handling policies and regulatory obligations, guaranteeing its secure and compliant operation over its entire lifecycle.

Our goal is to empower your organization with transformative technology while providing an absolute guarantee of data protection. We view ourselves not just as a service provider, but as a dedicated steward of your data. This policy is our commitment to that stewardship.


Purpose

This document sets forth the technical and procedural measures employed by ZeroStone AI Inc. (ZeroStone) to protect client data during the machine learning and AI project development lifecycle. The policy applies to all data processing activities undertaken by ZeroStone on behalf of clients.


1. Data Transfer Security

Recommended Transfer Methods

Client data transfers should occur via one of the following recommended methods, unless alternative arrangements are explicitly authorized in writing by the client:

Secure File Transfer Protocol (SFTP)

SFTP utilizing SSH 2.0 or higher. Authentication is performed using public key cryptography with a minimum key length of 4096 bits (RSA) or 256 bits (ECDSA).

Cloud Storage with Time-Limited Access Tokens

Direct upload to enterprise cloud storage services (Azure Blob Storage, AWS S3, or equivalent) using time-limited, write-only access credentials. This method is preferred for large datasets (>10 GB) due to superior performance and resumability. Requirements include:

  • Storage containers isolated per client/project
  • Time-limited Shared Access Signatures (SAS) or presigned URLs with write-only permissions
  • Token expiration within 30 days maximum
  • Encryption in transit via HTTPS with TLS 1.2 or higher
  • Storage in Canadian cloud regions (or approved jurisdictions per Section 2)
  • Automatic access logging of all upload activities

Prohibited Transfer Methods

Data transfers via the following methods are prohibited unless explicitly authorized in writing by the client:

  • Electronic mail
  • Consumer-grade file sharing services (personal Dropbox, Google Drive, etc.)
  • Physical media (USB drives, external hard drives)
  • Unencrypted protocols (FTP, HTTP)
  • Public or anonymously accessible cloud storage

While ZeroStone strongly advises against the use of these methods due to inherent security risks, we may accommodate client-directed transfers if the client provides written authorization acknowledging these risks. Such authorization shall be documented.

All file transfer activities are logged, including timestamp, user identifier, source, destination, and file metadata.

Encryption in Transit

All data transmitted across networks should employ TLS 1.2 or higher with Perfect Forward Secrecy cipher suites. Certificates are issued by recognized Certificate Authorities and monitored for expiration. Alternative encryption standards may be accommodated with explicit written client authorization, where operationally required.


2. Data Storage Security

Encryption at Rest

All client data stored on any medium is encrypted using AES-256 symmetric encryption. Encryption keys are managed through industry-standard key management services and are stored separately from encrypted data. Key rotation occurs annually at minimum.

Storage Infrastructure

Client data is stored on infrastructure with the following characteristics:

  • Encryption enabled by default
  • Access restricted to authorized personnel via role-based access control
  • Geographic storage location as specified in client agreements
  • Database backups encrypted using identical standards as production data

Data Segregation

In multi-tenant environments, client data is logically separated by tenant. Technical controls prevent cross-client data access.

Environment-Specific Security Protocols

Operations Within Client Infrastructure

When ZeroStone personnel operate within client-controlled cloud environments or on-premises infrastructure, the following protocols apply:

  • Client Policy Adherence: ZeroStone personnel shall comply with all client security policies, standards, and procedures applicable to the client environment
  • Client Access Controls: Access to client systems is granted and managed through client-controlled identity and access management systems
  • Client Monitoring: All activities are subject to client security monitoring and logging capabilities
  • Network Isolation: Development and testing activities are conducted within network segments designated by the client, maintaining segregation from production systems where required
  • Data Residency: All data processing occurs within the client's infrastructure boundaries, ensuring data does not egress to external systems without explicit client authorization
  • Privileged Access Management: Administrative access to client systems is granted only when operationally necessary, time-limited, and subject to client approval processes
  • Security Incident Reporting: Any security incidents or policy violations are reported to client security personnel immediately upon detection

Operations Within ZeroStone Infrastructure

When client data is processed within ZeroStone-controlled environments (subject to client contractual authorization), the following protocols apply:

  • Dedicated Environments: Client projects are conducted within logically isolated environments with dedicated access controls
  • ZeroStone Security Standards: All processing adheres to the security controls defined in this policy, including encryption, access management, and monitoring requirements
  • Data Minimization: Only the minimum data necessary for the specific project phase is transferred to ZeroStone infrastructure
  • Client Audit Rights: Clients retain the right to audit ZeroStone's security controls and data handling practices, subject to reasonable notice and confidentiality agreements
  • Secure Return/Deletion: Upon project completion or at client request, all client data is either securely returned to the client or deleted in accordance with Section 8

Data Sovereignty and Geographic Storage

ZeroStone prioritizes the use of Canadian cloud regions for data storage and processing whenever operationally feasible. This approach aligns with Canadian data protection standards and minimizes cross-border data transfer considerations.

Where specific client requirements, service availability, or operational constraints necessitate the use of infrastructure located outside Canada, the following provisions apply:

Primary Jurisdiction: United States-based cloud services may be utilized as secondary options, subject to client agreement and contractual authorization.

Client Notification: Clients are informed of the specific geographic locations where their data will be stored and processed prior to project commencement. Any changes to data storage locations require written client approval.

Legal Protections: Cross-border data transfers are governed by contractual provisions ensuring that data protection standards equivalent to those required under Canadian privacy legislation are maintained. Service providers are contractually obligated to comply with applicable data protection requirements.

Data Transfer Restrictions: Data shall not be transferred to jurisdictions outside Canada or the United States without explicit written authorization from the client and appropriate legal mechanisms to ensure adequate protection.


3. Personally Identifiable Information (PII) Management

Detection Process

Prior to machine learning or AI processing, all client data undergoes automated PII detection using enterprise-grade detection frameworks. The detection process identifies:

  • Personal names
  • Email addresses and phone numbers
  • Government identifiers (Social Security Numbers, driver's license numbers, passport numbers)
  • Financial information (credit card numbers, bank account numbers)
  • Physical addresses
  • Dates of birth
  • IP addresses

PII Handling Approach

ZeroStone employs a risk-based approach to PII handling, recognizing that certain AI applications may require the processing of identifiable information to deliver business value. The specific approach is determined through consultation with the client and documented in the project agreement.

De-Identification (Preferred Approach)

Where technically feasible and aligned with business requirements, detected PII is replaced using industry-standard pseudonymization techniques with the following methods:

PII Type Anonymization Method
Names Pseudonymization with realistic replacements
Email addresses Domain-preserving pseudonymization
Phone numbers Format-preserving tokenization
Addresses Geographic region-preserving replacement
Dates Date shifting with interval preservation
Numeric identifiers Format-preserving encryption

Controlled PII Processing

Where business requirements necessitate the processing of identifiable information, the following enhanced controls apply:

  • Contractual Authorization: Explicit written authorization from the client defining the specific PII elements to be processed and the business justification
  • Purpose Limitation: PII processing is strictly limited to the authorized purposes and shall not be used for any secondary purposes without additional authorization
  • Enhanced Access Controls: Access to identifiable data is restricted to a specifically authorized subset of personnel, with all access subject to additional logging and monitoring
  • Encryption Requirements: PII is encrypted both at rest and in transit using AES-256 encryption with keys managed through hardware security modules or equivalent key management services
  • Retention Restrictions: Identifiable data is retained only for the minimum period necessary to fulfill the authorized purpose, as defined in the client agreement
  • Processing Location: Where PII is processed, such processing occurs exclusively within client-controlled infrastructure unless explicitly authorized otherwise in writing

Validation

Following automated anonymization (where applied), a manual review is conducted on a sample of the processed data (minimum 10-20 records) to verify complete PII removal. An anonymization report is generated documenting detected entity types, methods applied, and validation results.

Data Handling for De-Identified Data

Where the de-identification approach is employed, raw data containing PII is securely deleted following successful anonymization and validation. Only de-identified data is used for subsequent ML/AI operations.


4. Third-Party Service Providers

Large Language Model (LLM) Providers

When utilizing third-party LLM services, the following requirements apply:

Service Tier: Only business or enterprise tier API services are utilized. Consumer-grade services are prohibited for client data processing.

Data Retention: Third-party providers must contractually guarantee maximum data retention of 30 days, after which all inputs and outputs are automatically deleted.

Training Prohibition: Third-party providers must contractually guarantee that client data will not be used to train or improve AI models.

Security Certifications: Third-party providers must maintain recognized security certifications (SOC 2 Type II, ISO 27001, or equivalent).

Data Sent to Third-Party Providers

As a default policy, all data sent to third-party LLM providers shall have undergone PII removal as described in Section 3. However, with explicit written authorization from the client, PII may be processed through a third-party LLM provider, provided the service meets the requirements for business/enterprise tier, data retention, and training prohibition as set out in this section.


5. Access Controls

Access Management

Access to client data is governed by the following principles:

Least Privilege: Personnel are granted the minimum access necessary to perform assigned duties.

Role-Based Access Control: Access is assigned based on predefined roles rather than individual user grants.

Access Reviews: All access permissions are reviewed quarterly. Any unnecessary access is revoked immediately.

Termination Procedures: Upon separation from employment or contract termination, access is revoked within one hour.

Authentication Requirements

All personnel accessing client data must utilize:

  • Multi-factor authentication (MFA) for all system access
  • Password policies requiring minimum 12-character length and complexity requirements
  • API keys stored in secrets management systems and rotated quarterly

Activity Logging

All access to client data is logged with the following information:

  • User identifier and timestamp
  • Actions performed (read, write, delete, export)
  • Source IP address
  • Authentication method
  • Success or failure status

Logs are retained for 90 days (security-relevant logs retained for one year) and stored in tamper-evident systems with restricted access.


6. AI System and Agent Security

Agent Identity and Access Management

Each AI agent or automated system is assigned a unique non-human identity, such as a service principal or managed identity, within the operating environment. These identities are subject to the same principles of least privilege and role-based access control as human users.

  • Scope of Access: Agent permissions are strictly scoped to the resources and actions required for their specific function.
  • Authentication: Agents authenticate using secure, non-exportable credentials, such as client certificates or environment-managed identities.
  • Lifecycle Management: Agent identities are provisioned, reviewed, and de-provisioned through automated processes tied to the AI solution's lifecycle.

Secure Monitoring and Tooling

Continuous monitoring of AI agent activities is performed to ensure operational integrity and detect anomalous behavior.

  • Internal Monitoring Environments: Monitoring activities are conducted within secure, isolated environments using dedicated internal tools. Access to these monitoring systems is restricted to authorized security and operations personnel.
  • Behavioral Logging: Agent actions, decisions, and data interactions are logged for security auditing and incident analysis.

7. Risk Management

Risk Assessment

ZeroStone shall conduct regular risk assessments to systematically identify, analyze, and evaluate risks to client data and the supporting information systems. The risk assessment process includes:

  • Identification: Identifying threats, vulnerabilities, and potential impacts on the confidentiality, integrity, and availability of client data.
  • Analysis: Assessing the likelihood and potential impact of identified risks.
  • Evaluation: Comparing the level of risk against pre-defined risk acceptance criteria.

Risk assessments are conducted periodically as part of our managed services, or upon significant changes to the environment, such as the introduction of new technologies or changes in the threat landscape.

Risk Treatment

For risks identified as unacceptable, a risk treatment plan is developed. Treatment options include:

  • Mitigation: Applying security controls to reduce the likelihood or impact of the risk.
  • Transfer: Sharing the risk with a third party, such as through insurance or contractual agreements.
  • Acceptance: Formally accepting the risk, with justification documented and approved by management.
  • Avoidance: Discontinuing the activity that gives rise to the risk.

The selection of security controls is based on the results of the risk assessment and is aligned with the requirements of ISO/IEC 27001:2022, Annex A.


8. Data Retention and Deletion

Retention Periods

Data Category Retention Period Rationale
Raw client data Per client agreement or immediate deletion post-anonymization Contractual obligation or operational requirement
Anonymized ML datasets 3 years following project completion Model reproducibility and validation
System logs (operational) 90 days Troubleshooting and diagnostics
System logs (security) 1 year Security forensics and compliance
Backup data 30 days Disaster recovery

Secure Deletion

Data deletion is performed using one of the following methods:

  • Cryptographic erasure: Destruction of encryption keys rendering encrypted data permanently unrecoverable
  • Multi-pass overwrite: Following NIST SP 800-88 guidelines for data sanitization

Client-Initiated Deletion

Clients may request deletion of their data at any time. Deletion requests are processed within 30 days, and written confirmation of deletion is provided. Minimal metadata may be retained for legal or audit purposes, as documented in the client agreement.


9. Incident Response

Notification Procedures

In the event of a confirmed data breach or unauthorized access to client data:

  • Client notification occurs within 72 hours of incident confirmation
  • Notification includes incident description, data affected, remediation measures, and recommended client actions
  • A detailed incident report is provided following investigation completion

10. Compliance and Standards Alignment

Canadian Data Protection Standards

The organization's data handling practices are designed to align with Canadian privacy legislation, including:

  • PIPEDA (Personal Information Protection and Electronic Documents Act): Federal privacy law governing private sector organizations
  • Provincial Privacy Legislation: Where applicable to the jurisdiction of operations

Data processing activities incorporate principles of consent, limited collection, appropriate use, and individual access rights consistent with Canadian privacy standards.

Security Framework Alignment

Data security practices are informed by internationally recognized security frameworks and standards, including ISO/IEC 27001:2022. The organization's Information Security Management System (ISMS) is designed to be consistent with the principles and controls of ISO 27001 and SOC 2. While formal third-party certification has not yet been pursued, our security controls are designed to address:

  • Confidentiality and privacy of client information
  • Integrity of data processing operations
  • Availability of systems and services
  • Monitoring and incident response capabilities

Documentation Availability

Subject to confidentiality agreements and operational constraints, the organization may provide documentation regarding:

  • Data processing procedures and controls
  • Security assessment methodologies
  • Third-party vendor security postures
  • Subprocessor arrangements

11. Client Data Rights

Rights Under Data Protection Law

Clients may exercise the following rights regarding their data:

Access: Request copies of data held by the organization

Rectification: Request correction of inaccurate data

Erasure: Request deletion of data (subject to legal retention obligations)

Portability: Request data in a structured, commonly used format

Restriction: Request limitation of data processing activities

Objection: Object to specific data processing activities

Requests are acknowledged within 5 business days and completed within 30 days of receipt.

Google Cloud (GCP)is a leading public cloud platform, enabling organizations to build and manage systems that scale infinitely. Amongst public clouds, Google Cloud is a leader is AI/ML and data warehousing, bringing the best-in-class products from Google and the open-source community. Companies choose GCP for a modern and cutting edge cloud experience.

Ready to Transform Your Business with Agentic AI?