1. Overview

Ardyn Intelligence Systems INC. builds infrastructure for autonomous intelligence. This policy describes how we handle identity, memory, evidence, and data within the Ardyn platform.

2. Identity Data

The platform integrates with identity providers (OIDC, SPIFFE, AWS, Entra, GCP) for authentication and authorization. Identity data is used only for policy evaluation and access control within the tenant scope.

3. Memory & Evidence

Actas organizational memory stores claims, intents, context, and evidence. All data is tenant-isolated. No cross-tenant data access is possible. Evidence is tenant-private by default.

4. Tenant Scope

Each tenant's data is logically isolated. API keys, rate limits, and migrations are tenant-scoped. Tenant members access only their own tenant's data.

5. Retention

Evidence and memory are retained according to the tenant's configuration. Exclusions can be set to prevent specific data from being retained. Data deletion is tenant-controlled.

6. Evidence Visibility

By default, evidence is private to the tenant. Tenants may optionally configure selective disclosure to designated parties or public anchoring of evidence digests. Public anchoring is never automatic — it must be explicitly configured.

7. Subprocessors

The platform uses PostgreSQL with pgvector for data storage. Infrastructure providers are used for hosting. A current list of subprocessors is available upon request.

8. Security

Transport security, API key authentication, rate limiting, and tenant isolation are enforced. Security concerns should be reported to compliance@ardyn.ai.

9. Contact

For privacy inquiries, contact compliance@ardyn.ai.