Tama / Private release

Data handling in the private release

An implementation summary, not a finalized privacy policy.

Publication pending. This page states the current private-release position; it is not a finalized legal agreement or policy.

What Tama stores

The application stores workspace and agent records, instruction and knowledge pages, memory, file content, tasks, proposals, reviews, approvals and audit records. Some content has revision history. This is not a promise that every provider file or session is copied into Tama.

API credentials

Provider keys saved through Settings are encrypted on the server and scoped to their owner. The normal state response does not return the stored key. A trusted worker can obtain the key for its authorized execution attempt. Removing a key from Tama does not revoke it at the provider or establish backup deletion.

Browser data

The interface uses browser storage for workspace preferences and per-window drafts. A workspace token is held by the page and can be passed to its specifically opened same-origin Code window. Configured Google login instead uses a Secure, HttpOnly browser cookie with an eight-hour session. Tama retains a bound Google subject and email, session digests, expiry and sign-in audit events. Google access and ID tokens are not stored. Google sign-out revokes that browser session; token Lock clears that window's login and drafts.

Infrastructure and provider flow

The current web service and database run on Railway. When enabled, provider execution sends the authorized task context to the configured model provider. Domain routing is managed through Cloudflare DNS. This description does not assert a fixed hosting region or complete subprocessor inventory.

Retention and requests

A public retention schedule, deletion/export procedure, backup policy, legal contact and full privacy policy are still to be finalized. No permanent-storage promise, fixed deletion deadline or guaranteed export window is made here. For the private workspace, contact the operator who supplied access.

Scope

This summary describes the new application, not the legacy data flows or a provider's own retention and training rules. Those provider rules need separate review for the selected account and service.

Updated September 21, 2026