Security
Your operational data deserves the same protection as your bank account.
Encryption
All data is encrypted at rest (AES-256) and in transit (TLS 1.3). Database connections use SSL. File storage uses server-side encryption.
Data Isolation
Each workspace is isolated at the database level. Expert runtimes operate in scoped environments with access only to their assigned engagement. No cross-tenant data access is possible.
No Model Training
We do not use your data to train AI models. Your files, conversations, and records are used exclusively to operate your expert services.
Infrastructure
Talea uses the following sub-processors to operate the service. Model routes can be replaced only after the production security boundary and this disclosure are reviewed together.
| Sub-processor | Purpose | Data received |
|---|---|---|
| Vercel | Application hosting and isolated expert runtime | Application requests, workspace context, and scoped runtime inputs |
| Vercel AI Gateway | Routes model requests to the configured AI provider | Scoped prompts, extracted document text, and document images when required by the selected workflow |
| Supabase | Postgres database and identity infrastructure | Account, workspace, accounting, workflow, and audit records |
| Cloudflare R2 | Encrypted object storage | Uploaded source files, generated reports, and artifacts |
| OpenAI | Provider-failure fallback for receipt and invoice digitization | Selected source text and document content required for structured extraction |
| DeepSeek | Accounting expert runtime and primary receipt and invoice digitization | Scoped accounting context, selected source text, and document content required for the task |
| Alibaba Cloud (Qwen) | Primary optical character recognition | Selected document images or rendered PDF pages |
| Zhipu AI (GLM) | Fallback optical character recognition | Selected document images or rendered PDF pages |
| PostHog Cloud (United States) | Privacy-safe product analytics, enabled by default with opt-out | Pseudonymous identifiers, cleaned routes and attribution, product usage events and connection information. No accounting contents, financial values or session recordings. |
| Stripe | Payment processing when billing is enabled | Billing contact, subscription, and payment metadata submitted to Stripe |
Access Controls
Expert runtimes receive scoped tool access through the Control Plane. They cannot access raw credentials, other workspaces, or external systems without explicit authorization. Side-effect actions (sending emails, sharing files) require user approval.
Export and Deletion
Workspace owners can export or permanently delete an Accounting Expert engagement from Workspace settings. The purge spans database records, stored files and exports, connected-source credentials, and matching transient runtime sessions, while retaining a minimal audit tombstone for proof and retry. For account-level or other data requests, email privacy@maestro.onl. Data subject to applicable legal or operational retention obligations remains limited to those purposes.
Reporting Issues
Report security concerns to security@maestro.onl.