Privacy Policy
Privacy is not a feature. It is the foundation.
Ananke builds governed AI infrastructure for organizations, partners, and identity rights holders. Our privacy approach is designed around trust, control, minimal data use, and clear boundaries around how information is collected, processed, protected, and governed.
Last updated: September 14, 2026
Our privacy commitments
Built for trust by default.
We do not sell personal data.
Ananke is not an advertising business. We do not sell personal information or build ad profiles from customer data.
Data is used to provide the service.
We use information to operate products, provide support, improve safety, enforce policy, and deliver requested functionality.
Governance stays visible.
Where AI governance decisions occur, we aim to preserve useful audit records so organizations can understand what happened and why.
Access is limited.
We design for least-privilege access, restricted internal visibility, and separation between users, organizations, policies, and protected identity records.
Information we may collect
We collect information needed to operate governed AI products and business relationships.
Account and contact information
Names, emails, organization details, roles, inquiry forms, support requests, and business contact information.
Product usage information
Usage events, workspace activity, model selection, governance events, audit logs, settings, and operational telemetry.
Customer-provided content
Prompts, responses, uploaded materials, policies, reference documents, room context, identity records, and approved knowledge sources.
Governance records
Policy evaluations, risk signals, approval states, blocked requests, routing decisions, license checks, and audit evidence.
Technical data
Device, browser, IP address, logs, performance data, security events, cookies, and similar technical information.
Identity rights data
For Origin, authorized identity materials, rights metadata, licensing rules, protected persona boundaries, and approval workflows may be stored.
How we use information
Information is used to operate, govern, secure, and improve Ananke products.
We use information in ways that support customer control, product functionality, AI governance, security, compliance, and service reliability.
Provide and operate products
Deliver Palladium Enterprise, Palladium Pro, Origin, customer support, billing, account management, and operational functionality.
Enforce governance and safety
Apply policy, detect misuse, prevent harmful or unauthorized activity, and preserve auditability when governance decisions are made.
Secure systems
Monitor reliability, investigate security events, prevent abuse, protect accounts, and maintain service integrity.
Improve responsibly
Improve usability, performance, workflows, documentation, and product quality while respecting customer controls and privacy commitments.
AI and model providers
We design Ananke to sit above AI providers, not surrender control to them.
Some Ananke products may route requests to third-party AI model providers selected by Ananke or by a customer. When this occurs, information may be processed by those providers to generate responses or perform requested functions. We work to limit unnecessary disclosure, preserve governance boundaries, and support customer control over model usage.
Unless expressly agreed otherwise, Ananke does not sell customer content, identity records, or organizational data to AI model providers. Customer-specific data handling may vary based on contract terms, selected integrations, and configured product settings.
Security and governance
Privacy depends on architecture, not slogans.
Ananke designs for secure handling of organizational context, identity records, AI interactions, and governance decisions. No system can guarantee absolute security, but our goal is to reduce risk through strong architecture and disciplined controls.
Encryption
Protected in transit and at rest
We use encryption and secure transport practices appropriate to the systems and data involved.
Access
Least privilege by design
Internal access is limited based on role, operational need, and security controls.
Isolation
Customer and identity boundaries
We design around separation between organizations, users, policies, model access, and protected identity records.
Audit
Records for accountability
Governance logs and audit events help customers understand policy decisions, access, and usage patterns.
Sharing information
We share information only when needed to operate, protect, or comply.
We may share information with service providers that help us operate Ananke products, including hosting, infrastructure, email, analytics, payments, support, security, and AI model providers when required to deliver requested services.
We may share information when required by law, legal process, security investigation, customer instruction, corporate transaction, or to protect the rights, safety, and security of Ananke, our customers, users, partners, and the public.
For enterprise, Pro, and Origin customers, specific contractual terms may further define data use, subprocessor restrictions, retention, customer controls, and confidentiality obligations.
Your choices
Customers and users should have meaningful control.
Access and correction
You may request access to or correction of personal information, subject to identity verification and legal limits.
Deletion and retention
You may request deletion where applicable. Some information may be retained for security, audit, legal, billing, or operational reasons.
Communications
You can opt out of non-essential marketing communications, while still receiving service-related notices.
Customer-admin controls
Organizations may control access, roles, rooms, policies, reference materials, and retention settings depending on product configuration.
Children and minors
Some products may support youth-facing or mixed-age environments.
When Ananke products are used by schools, families, programs, or organizations serving minors, additional controls may apply. We design youth-facing experiences with heightened safety, privacy, and governance expectations. Organizations using Ananke products with minors are responsible for obtaining any required consents and configuring appropriate access, roles, and policies.
Contact
Questions about privacy?
For privacy questions, data requests, or product-specific privacy concerns, contact Ananke. We may update this policy as our products, contracts, and legal obligations evolve.
Please include enough information for us to understand your request, verify the relevant account or organization, and route the question appropriately.
[email protected]