Trust

Security

This page describes security practices that apply to the public Zarire website (zarire.com) while the Zarire Platform remains in Technical Preview.

Last updated: 2026-08-06

Zarire aims to engineer carefully, keep the public surface limited, and communicate honestly about what exists today versus what may be documented later for a production platform.

About this Security page

This page is not a certification statement, audit report, or guarantee of secure operation.

What this page covers

In scope for this page:

The public zarire.com website
How that site is hosted and delivered
Development and deployment practices for the public website
Boundaries for professional services engagements (authorization and related principles)
How to report security concerns

Not claimed on this page:

Production Zarire Platform multi-tenant controls
Customer infrastructure data protection as a processed data plane on this website
Customer agent enrollment and related security
Platform monitoring, backups, or guaranteed response times for security incidents

The public website does not currently provide customer accounts, authentication, checkout, subscriptions, a customer portal, a public API, or customer agent enrollment, and it does not process customer infrastructure data through the public website.

Hosting and transport security

The public website uses HTTPS to protect information in transit between visitors and the website.

Development and deployment practices

Zarire uses controlled development and deployment practices and reviews relevant security and dependency issues as part of maintaining the public website.

Secret and credential handling

Zarire reviews the public website for secrets and credentials to reduce the risk of embedding them in client-delivered assets. The public website is not intended to embed API secrets or similar credentials in those assets.

Access and operational boundaries

Relevant current boundaries:

No public customer authentication on the website
No customer portal on the website
No public API on the website
No customer agent enrollment through the public website
No processing of customer infrastructure data through the public website
No production customer telemetry collected through the public website as a product pipeline

Ordinary technical logs related to website visits or email may exist at infrastructure or email-provider layers. See the Privacy Policy.

Professional-services security boundary

When Zarire performs professional services under a separate agreement, the following principles apply:

Remote access requires customer authorization
Production changes require customer approval
Credentials must not be transmitted through insecure channels
Backups remain the customer’s responsibility unless separately agreed
There is no guarantee that a reported issue will be resolved

These engagements do not include Managed Services, 24×7 monitoring, SOC or NOC operations, or a platform uptime SLA.

Current limitations

No website or system can be guaranteed completely secure. Security reviews or automated checks cannot catch every issue, and professional services engagements are not risk-free.

Security work continues as the project evolves. Report suspected issues through Responsible Disclosure.

Compliance and assurance

Zarire does not currently claim independent security certifications or attestations. As the platform evolves, relevant security, privacy, and compliance information will be published when applicable and supported by appropriate evidence.

Reporting security concerns

Please report suspected security issues affecting the public Zarire website (zarire.com) and other Zarire-operated public web properties via Responsible Disclosure and email security@zarire.com.

Do not use public channels to share exploit details that could put others at risk before coordination.

Future platform security documentation

When the Zarire Platform moves beyond Technical Preview into production offerings, Zarire may publish additional security documentation covering topics such as identity and access, multi-tenant operations, agent security, auditability, and customer data handling—as those systems exist and can be described accurately.

Until then, treat platform-oriented diagrams or copy on the marketing site as Technical Preview information, not as a live control attestation.

Contact

Security reports: security@zarire.com

General inquiries: info@zarire.com