Cloud Privacy
Last updated: 8 July 2026 — DRAFT pending counsel sign-off
This page explains how ISANNA TECNOLOGIA LTDA ("isanna", "we") handles an application to the free, hosted, invite-only Bia private beta. Admission is subject to manual review. Bia Core is already Apache-2.0; the hosted beta service and its Cloud/Console implementation are not yet publicly open source.
Private-beta applicant data
We collect the email address and questionnaire answers you submit so that we can review the application, communicate an invite decision, and operate the private beta. We do not use this application form to collect payment details.
Applicant retention
Applicant retention is limited to 90 days after a decision, or until you ask us to remove the application, whichever comes first. We keep a content-free operator audit record of a correction, export, or deletion request.
Bia Cloud service data
Two different roles apply to two different kinds of data:
- Tenant memory content (memory text, embeddings and associated metadata) — isanna acts as a processor. The invited organization is the controller, and isanna processes that content only on its instructions, as detailed in the Data Processing Addendum.
- Account and administration data (organization and contact details, access administration and support correspondence) — isanna acts as the controller.
Data categories and location
Memory content includes the text and vector embeddings agents write through Bia tools, plus
content-free operational metadata such as timestamps, actor or device identifiers and byte counts.
It is stored in the dedicated isanna-hivemind PostgreSQL project on Supabase in us-west-2,
reached through a non-bypass, Force-RLS application role. Hosted compute and the in-house embedder run
on Fly.io in gru.
Performance telemetry
During the hosted private beta, Bia records content-free operational telemetry for scoped tool calls: the tool class, success or failure, server-side processing duration, and timestamp. This telemetry never includes tool arguments, memory content, prompts, answers, vectors, or SQL. We use pooled statistics to understand memory write and recall reliability and latency; we do not publish per-user performance rankings.
Raw tool-call profiles and recall-event metadata are retained for 90 days. Before expired rows that support private-beta activation evidence are removed, Bia preserves the minimum content-free activation snapshot needed to keep the founder's historical evidence honest. The snapshot contains timestamps and bounded counts, not memory content or application questionnaire answers.
Service retention and erasure
Memory content is retained while an organization has private-beta access and for the wind-down period stated in its Data Processing Addendum. Deletion requests are applied as hard row deletes, not soft tombstones. A content-free, hash-chained ledger records that deletion occurred without retaining the deleted memory content. A signed erasure receipt is minted only after a supported delete path completes; a partial operation is surfaced as an error and receives no receipt.
International transfer
isanna is based in Brazil and the hosted database is in the United States. Tenant memory content is therefore transferred from Brazil to the United States on the invited organization's instructions. isanna does not onboard EU/EEA personal data until an appropriate transfer mechanism is executed for that organization.
Processor list
The third-party infrastructure subprocessors in the Bia Cloud data path are:
| Subprocessor | Role | Region |
|---|---|---|
| Fly.io | Container runtime for the hosted endpoint and embedder | gru (São Paulo) |
| Supabase | Persistent memory substrate (PostgreSQL) | us-west-2 |
The embedding model is self-hosted on isanna's Fly.io infrastructure and is not a third-party
subprocessor. This list is maintained with hivemind-cloud/SUBPROCESSORS.md and the Data
Processing Addendum.
Your rights
Applicants can ask to inspect, export, correct, or delete application data. Invited organizations remain responsible for requests concerning tenant memory content, with assistance from isanna under the Data Processing Addendum. Contact privacy@isanna.ai and include the email address used for the application when the request concerns applicant data.
Contact
Questions about this private-beta notice: privacy@isanna.ai.