Security & Data Handling

A Lean, Factual Security Baseline

We work with customers to scope data handling, access, retention, and deployment requirements for each engagement.

Customer Data

Customer data uploaded to the product is handled under customer agreements and data-processing terms. Customers retain ownership of their uploaded data.

Current Approach

We keep our public security language focused on current data handling and engagement-specific review requirements.

Engagement Review

Security, deployment, and data-handling questions are reviewed during scoping so requirements can be matched to the engagement in front of us.

Current Security and Data Handling Baseline

The items below summarize the customer-facing security and data handling commitments reflected in our public legal and product materials.

Ownership

Data Ownership

Customers retain ownership of uploaded data. We process that data to provide, maintain, secure, and improve the service as described in customer agreements and terms.

Privacy

Personal Data Handling

Personal information on the website and related services is handled under the public Privacy Policy, including how data is collected, used, shared, and retained.

Lifecycle

Retention and Deletion

Personal data is retained only as long as needed to provide services, comply with legal obligations, resolve disputes, or enforce agreements. After termination, customer data is deleted in accordance with applicable terms and policies.

Scoping

Engagement-Specific Review

If a customer has specific requirements around access, hosting, review workflow, or deployment boundaries, we assess those requirements during scoping rather than claiming a one-size-fits-all trust package.

How We Work

Working With Us

  • Security, deployment, and workflow requirements can vary by engagement.

  • Specific customer requirements should be reviewed in the context of the actual project.

  • Availability of controls or deployment models depends on the scope being evaluated.

  • Teams with procurement or review questions should bring them forward early in scoping.

Project Review

When a Customer Needs More

  • We review data sensitivity, access expectations, and workflow constraints during the evaluation process.

  • Additional legal, security, or procurement questions can be handled directly with the team.

  • Where a requirement is material to the engagement, it should be discussed early in scoping.

Security Questions?

If you are evaluating us for a specific project, share the data-handling, deployment, or review requirements that matter to your team and we will address them during scoping.