Information Security Policy

1. Purpose and Scope

This Information Security Policy (“Policy”) describes the security controls, practices, and commitments that Ollify LLC (“Ollify,” “we,” “us,” or “our”) maintains to protect the confidentiality, integrity, and availability of the Ollify platform and Customer Data entrusted to us.

This Policy is published for the benefit of Ollify’s customers, prospective customers, and other stakeholders who wish to understand how Ollify protects data within the Service. It covers Ollify’s cloud infrastructure, application security, access controls, incident response, and vendor management practices.

This Policy applies to all systems, infrastructure, personnel, and third-party service providers involved in the delivery of the Ollify platform. It is reviewed and updated at least annually or following any material change to Ollify’s security environment.

2. Security Governance

2.1 Security Ownership. Information security at Ollify is the responsibility of the Managing Member and designated security personnel. Security responsibilities include:

1. (a)

   Establishing and maintaining security policies and controls

2. (b)

   Overseeing risk assessment and management processes

3. (c)

   Managing security incidents and response

4. (d)

   Reviewing and approving changes to security-relevant systems and configurations

5. (e)

   Ensuring personnel receive appropriate security awareness training

2.2 Security Policy Review. This Policy and all supporting security policies are reviewed at minimum annually. Reviews are triggered earlier by material security incidents, significant changes to Ollify’s infrastructure or product, changes in applicable law or regulation, or identification of material risks not addressed by existing controls.

2.3 Risk Management. Ollify conducts periodic risk assessments to identify, evaluate, and address security risks to Customer Data and the Service. Risk assessment considers:

1. (a)

   Threats to the confidentiality, integrity, and availability of Customer Data

2. (b)

   Vulnerabilities in Ollify’s infrastructure, application, and operational practices

3. (c)

   Likelihood and potential impact of identified risks

4. (d)

   Effectiveness of existing controls in mitigating identified risks

Identified risks are documented, prioritized, and addressed through remediation, mitigation, or acceptance with appropriate management approval.

3. Cloud Infrastructure Security

3.1 Amazon Web Services (AWS). The Ollify platform is hosted exclusively on Amazon Web Services (AWS). Ollify leverages AWS’s enterprise-grade infrastructure security controls, which include:

1. (a)

   Physical data center security including 24/7 security personnel, biometric access controls, and video surveillance at AWS facilities

2. (b)

   ISO 27001, SOC 1, SOC 2, and SOC 3 certified infrastructure

3. (c)

   Network infrastructure designed for high availability and redundancy

4. (d)

   Hardware security managed and maintained by AWS under the AWS Shared Responsibility Model

3.2 Infrastructure Configuration. Ollify’s AWS infrastructure is configured and managed according to the following security principles:

1. (a)

   Principle of least privilege applied to all AWS IAM roles, policies, and service accounts

2. (b)

   Production, staging, and development environments are logically separated

3. (c)

   Security groups and network access control lists (NACLs) restrict inbound and outbound traffic to authorized sources and destinations only

4. (d)

   Public access to storage resources (S3 buckets) is disabled by default

5. (e)

   AWS CloudTrail is enabled for audit logging of API activity across Ollify’s AWS accounts

6. (f)

   AWS Config is used to monitor and enforce configuration compliance

7. (g)

   Multi-factor authentication (MFA) is required for all AWS console access

3.3 Availability and Redundancy. Ollify designs its infrastructure to support high availability:

1. (a)

   Production systems are deployed across multiple AWS Availability Zones to protect against single-point failures

2. (b)

   Automated health checks and load balancing distribute traffic and detect unhealthy instances

3. (c)

   Database services are deployed in a Multi-AZ configuration with automated failover

4. (d)

   Recovery objectives are documented internally and will be formalized into published commitments as backup and recovery capabilities are validated through testing

4. Data Security

4.1 Encryption in Transit. All data transmitted between customers and the Ollify platform is encrypted in transit using industry-standard protocols:

1. (a)

   TLS 1.2 or higher is required for all connections to the Ollify platform

2. (b)

   TLS 1.0 and 1.1 are disabled

3. (c)

   HTTP connections are automatically redirected to HTTPS

4. (d)

   Ollify’s TLS certificates are issued by trusted certificate authorities and renewed before expiration

4.2 Encryption at Rest. Customer Data stored within the Ollify platform is encrypted at rest:

1. (a)

   AWS managed encryption (AES-256) is applied to all production data stores, including databases and object storage

2. (b)

   Database backups are encrypted using the same standards as production data

3. (c)

   Database encryption keys are managed through AWS Key Management Service (KMS); customer file storage uses server-side encryption with an AWS KMS key that Ollify controls and that rotates automatically

4.3 Data Isolation. Customer Data is logically isolated within the Ollify platform. Ollify’s application architecture enforces tenant isolation controls to prevent one customer’s data from being accessed by another customer. Data isolation is enforced at the application layer and validated through security testing.

4.4 Data Retention and Deletion. Ollify retains Customer Data in accordance with the Agreement and applicable law. Upon termination or cancellation of a subscription, Customer Data is retained for sixty (60) days during which customers may export their data. Following the retention period, Customer Data is permanently deleted from Ollify’s production systems, and remaining copies cycle out of backups within thirty-five (35) days, in accordance with Ollify’s data deletion procedures. Deletion procedures are designed to render data unrecoverable.

4.5 Backups. Ollify performs automated backups of Customer Data on a regular schedule:

1. (a)

   Database backups are performed daily at minimum

2. (b)

   Backups are currently stored within the same AWS region as primary production data; cross-region backup replication is on Ollify’s infrastructure roadmap

3. (c)

   Regular, documented backup restoration testing is being implemented as part of Ollify’s infrastructure roadmap

4. (d)

   Backups are encrypted using the same standards as production data

5. (e)

   Backup retention periods are defined and managed in accordance with Ollify’s data retention policies

Ollify’s current backup and recovery capabilities, their present limitations, and the improvement roadmap are described in detail in Ollify’s Backup and Recovery Policy, available at ollify.app/legal/backup-and-recovery-policy.

5. Application Security

5.1 Secure Development Practices. Ollify follows secure software development practices throughout the software development lifecycle (SDLC):

1. (a)

   Security requirements are considered during product design and architecture phases

2. (b)

   Code changes are reviewed prior to deployment to production environments

3. (c)

   Automated static analysis and dependency scanning tools are used to identify known vulnerabilities in code and third-party libraries

4. (d)

   Security-relevant changes receive additional review before deployment

5. (e)

   Production deployments follow a controlled release process with rollback capability

5.2 Vulnerability Management. Ollify maintains an ongoing vulnerability management program:

1. (a)

   Third-party libraries and dependencies are monitored for known vulnerabilities using automated scanning tools

2. (b)

   Critical and high-severity vulnerabilities are prioritized for remediation on an expedited basis

3. (c)

   Infrastructure and application components are patched and updated on a regular schedule

4. (d)

   Security patches for critical vulnerabilities are applied as quickly as practicable following vendor release

5.3 Penetration Testing. Ollify conducts or commissions security assessments of its platform on a periodic basis. Assessment findings are tracked and remediated according to severity. Customers with specific security assessment requirements should contact security@ollify.app to discuss options.

5.4 Responsible Disclosure. Ollify operates a responsible disclosure program for security researchers who identify vulnerabilities in the Ollify platform. If you have identified a potential security vulnerability, please report it to security@ollify.app. Ollify commits to:

1. (a)

   Acknowledging receipt of vulnerability reports within three (3) business days

2. (b)

   Investigating reported vulnerabilities in good faith

3. (c)

   Providing timely remediation of confirmed vulnerabilities based on severity

4. (d)

   Not pursuing legal action against researchers who follow responsible disclosure principles

6. Access Control

6.1 Employee Access. Access to Customer Data and production systems by Ollify personnel is strictly controlled:

1. (a)

   Access to production systems and Customer Data is limited to personnel with a documented business need

2. (b)

   Principle of least privilege is applied — personnel are granted only the access necessary to perform their job functions

3. (c)

   Access rights are reviewed periodically and revoked promptly upon role change or separation

4. (d)

   Multi-factor authentication (MFA) is required for access to production systems and administrative tools

5. (e)

   Access to Customer Data for support purposes is logged and auditable

6.2 Customer Access Controls. Ollify provides customers with controls to manage access to their own accounts and data:

1. (a)

   Role-based access controls allow account administrators to assign permissions to users within their organization

2. (b)

   Account administrators can add, modify, and remove user access at any time

3. (c)

   Password requirements enforce minimum complexity and length standards

4. (d)

   Multi-factor authentication (MFA) for customer accounts is not available as of this Effective Date. Ollify may introduce MFA for customer accounts in a future release; customer sign-in is protected today by rate limiting, a CAPTCHA step-up after repeated failed attempts, and immediate server-side session revocation

5. (e)

   Session management controls include automatic session timeout after periods of inactivity

6.3 Authentication. Ollify enforces the following authentication standards:

1. (a)

   Passwords are stored using industry-standard hashing algorithms (bcrypt or equivalent) — plaintext passwords are never stored

2. (b)

   Failed login attempts are rate-limited to protect against brute-force attacks

3. (c)

   Multi-factor authentication for customer accounts is not yet available; Ollify may introduce it in a future release. MFA is enforced for Ollify’s internal administrative portals

4. (d)

   API access, where offered, is controlled through token-based authentication with configurable expiration

6.4 AI Assistant Access Controls. Olli, Ollify’s built-in AI assistant, operates under the following controls:

1. (a)

   Olli can look up or change only what the person asking is already permitted to see or change, and nothing the customer has excluded

2. (b)

   Every change Olli proposes requires that person’s confirmation, is checked again at confirmation, and is recorded in the audit log

3. (c)

   Customer administrators can turn Olli’s data and action features off for the account and, on paid plans, for individual roles and people, and can exclude categories of data and individual workflows

4. (d)

   Olli has no tool that sends messages or browses the web

7. Network Security

7.1 Network Controls. Ollify’s network architecture is designed to limit exposure and contain potential threats:

1. (a)

   Production systems operate within isolated Virtual Private Clouds (VPCs) with controlled ingress and egress

2. (b)

   Public-facing components are limited to load balancers and API gateways — application servers and databases are not directly internet-accessible

3. (c)

   Network traffic is filtered using AWS security groups and network access control lists

4. (d)

   Outbound traffic from production systems is restricted to authorized destinations

7.2 DDoS Protection. Ollify utilizes AWS Shield and AWS CloudFront to provide protection against distributed denial of service (DDoS) attacks. These services provide automatic detection and mitigation of common DDoS attack patterns at the network and application layers.

7.3 Logging and Monitoring. Ollify maintains comprehensive logging and monitoring of its infrastructure and application:

1. (a)

   AWS CloudTrail logs all API activity within Ollify’s AWS accounts

2. (b)

   Application logs capture authentication events, access to Customer Data, and security-relevant actions

3. (c)

   Infrastructure and application metrics are monitored with automated alerting for anomalous conditions

4. (d)

   Application and system logs are retained for a minimum of ninety (90) days, and platform audit logs for seven hundred thirty (730) days; logs are protected against unauthorized modification

5. (e)

   Security events are reviewed and investigated in accordance with Ollify’s incident response procedures

8. Incident Response

8.1 Incident Response Program. Ollify maintains a documented incident response program to detect, contain, investigate, and remediate security incidents. The program covers:

1. (a)

   Detection and identification of potential security events through monitoring and alerting

2. (b)

   Classification of incidents by severity and potential impact on Customer Data

3. (c)

   Containment procedures to limit the spread and impact of confirmed incidents

4. (d)

   Investigation and root cause analysis of confirmed incidents

5. (e)

   Remediation and recovery procedures

6. (f)

   Post-incident review and improvement of controls

8.2 Customer Notification. In the event of a confirmed security incident that affects Customer Data, Ollify will notify affected customers in accordance with the notification requirements of the Agreement and applicable law. Notification will include:

1. (a)

   A description of the nature of the incident to the extent known

2. (b)

   The categories and approximate volume of Customer Data affected

3. (c)

   The measures Ollify has taken or is taking to address the incident

4. (d)

   Recommended steps customers may take to protect themselves

9. Vendor and Subprocessor Security

9.1 Vendor Assessment. Ollify evaluates the security posture of third-party vendors and subprocessors prior to engagement and on a periodic basis. Assessment criteria include:

1. (a)

   Review of the vendor’s security certifications and compliance documentation (SOC 2, ISO 27001, or equivalent)

2. (b)

   Review of the vendor’s data handling and privacy practices

3. (c)

   Contractual security and data protection requirements

4. (d)

   Ongoing monitoring of vendor security posture for material changes

9.2 Subprocessor List. Ollify maintains a current list of subprocessors that process Customer Data on Ollify’s behalf. The subprocessor list is available at ollify.app/legal/subprocessors and is updated when subprocessors are added or removed. Key subprocessors include:

Anthropic, PBC is an active subprocessor in production. It provides AI language-model processing for Olli, Ollify’s built-in AI assistant. The Subprocessor List and How Olli Works describe what Olli shares with Anthropic.

9.3 Contractual Security Requirements. All subprocessors that process Customer Data are required to enter into data processing agreements with Ollify that include the terms below, except for government agencies that do not offer data processing agreements in the commercial sense (see Ollify’s Subprocessor List for details):

1. (a)

   Obligations to implement appropriate technical and organizational security measures

2. (b)

   Restrictions on the use of Customer Data to the specified processing purpose

3. (c)

   Requirements to notify Ollify of security incidents affecting Customer Data

4. (d)

   Audit rights or provision of third-party security certifications

10. Physical Security

Ollify does not operate its own data centers. All physical infrastructure is hosted within AWS facilities, which maintain comprehensive physical security controls including:

1. Perimeter security with fencing, barriers, and controlled entry points

2. 24/7 security personnel and video surveillance

3. Multi-factor physical access controls including badge readers and biometric verification

4. Environmental controls for temperature, humidity, and fire suppression

5. Redundant power supplies and uninterruptible power systems

AWS physical security certifications and documentation are available at aws.amazon.com/compliance.

11. Business Continuity and Disaster Recovery

Ollify maintains business continuity and disaster recovery capabilities appropriate to its current stage, and is transparent about their present limits:

1. Critical systems are deployed across multiple AWS Availability Zones to provide redundancy against infrastructure failures; cross-region resilience is on Ollify’s infrastructure roadmap

2. Automated failover is configured for the database tier, and the application tier runs redundant instances behind load balancing; automated daily encrypted backups protect against data loss

3. Recovery procedures are documented internally; formal, scheduled restoration testing is being implemented

4. Recovery time and recovery point objectives are documented internally and will be published as formal commitments once validated through testing

5. Business continuity plans are reviewed and updated at least annually

Ollify’s Backup and Recovery Policy, available at ollify.app/legal/backup-and-recovery-policy, describes current backup and recovery capabilities and limitations in detail. Ollify’s Service Level Agreement (SLA), available at ollify.app/legal/service-level-agreement, describes uptime commitments and remedies for service availability failures.

12. Security Awareness

Ollify personnel with access to Customer Data or production systems receive security awareness training:

1. Security awareness training is provided to all relevant personnel upon onboarding

2. Training covers data handling obligations, phishing awareness, password security, and incident reporting procedures

3. Security awareness training is refreshed at least annually

4. Personnel handling Customer Data are informed of their specific data protection obligations

13. Customer Security Responsibilities

While Ollify maintains the security controls described in this Policy, customers share responsibility for the security of their use of the Service. Customer responsibilities include:

1. Maintaining the confidentiality of account credentials and API keys

2. Using strong, unique passwords, and enabling multi-factor authentication for account users once it becomes available

3. Managing user access within their organization and promptly revoking access for departed users

4. Complying with Ollify’s Acceptable Use Policy with respect to data submitted to the Service

5. Promptly reporting suspected security incidents or unauthorized account access to security@ollify.app

6. Keeping client-side software, browsers, and operating systems used to access the Service up to date

14. Contact

For security-related questions, vulnerability reports, or to request additional security documentation, contact Ollify at: