Your Data. Protected at Every Step.
Conversion data flows through sensitive systems — ad platform APIs, CRM connections, client PII. TUOCA protects every layer with SHA-256 hashing, multi-tenant isolation, encrypted credentials, and a complete audit trail.
Available on: All tiers
Seven Layers of Protection
Security isn't a feature — it's the foundation. Every layer of TUOCA is built with data protection as a first-class concern.
PII Hashing
SHA-256 hashing prepares supported email and phone identifiers for enhanced conversions. Normalization and hashing help you meet the destination upload format without building that preparation into a spreadsheet.
Multi-Tenant Isolation
Workspace scoping and access controls help keep client data organized and restrict access to authorized users. Agency users can oversee the client workspaces they have permission to manage.
Role-Based Access Control
Four permission levels enforced at the API level, not just the UI. Owner — full control including billing and account deletion. Admin — manage connections, relays, clients, and team members. Member — view dashboards, trigger relays, view logs. Viewer — read-only access to dashboards and activity logs.
Authentication
JWT-based sessions with automatic token refresh. Support for Google OAuth login. Session tokens expire and refresh automatically — no persistent cookies storing sensitive data. Email invitations for team members use 7-day expiry links that become invalid after first use.
OAuth Token Management
OAuth token management helps maintain supported connections, with encrypted credential storage and refresh handling. Provider access can still expire or be revoked; check connection health and reconnect when required.
Rate Limiting
Rate-limit handling helps manage platform API constraints. If a platform rejects or delays an upload, use its execution outcome to identify what needs attention.
Audit Trail
Activity logs help you follow account and configuration changes. Use execution history to review relay runs and upload outcomes, and the activity trail to investigate who changed a setting.
Built With Trust in Mind
Data Minimization
TUOCA only processes the fields required for conversion upload. No data warehousing, no user profiling, no secondary use. Data enters, gets processed, gets uploaded. That's it.
Purpose Limitation
Your data is used for exactly one purpose: uploading offline conversions to your configured ad platforms. No analytics, no aggregation, no selling. Your data flows to where you configured it and nowhere else.
Security by Design
Security isn't bolted on — it's built into every layer from database schema (tenant isolation) to API design (permission enforcement) to data processing (automatic hashing). Every feature is designed with data protection as a constraint, not an afterthought.
Security Questions
TUOCA processes customer identifiers from your uploads and connected sources. SHA-256 hashing prepares supported identifiers for enhanced conversion uploads. Hashing is a step in that workflow, not a promise that the app never handles personal data. If your team has specific storage or retention requirements, contact us before connecting customer data.
Client data is scoped to its workspace, with access controlled by account membership and permissions. Agency users can work across authorized client workspaces from a shared dashboard.
Review the Privacy Policy and EU and UK addendum for the stated processing purposes, legal bases, transfers, and rights. If your team needs a data processing agreement or has specific retention requirements, email info@floframe.ai before connecting customer data. Hashing alone does not establish compliance for your workflow.
Revoke the app authorization in the connected provider account, then reconnect with the access you intend to grant. TUOCA uses encrypted credential storage, but removing a local connection should not be treated as proof that the provider has revoked its token.
Yes — TUOCA uses four permission levels: Owner (full control including billing), Admin (manage connections, relays, clients, and team members), Member (view dashboards, trigger relay runs, view logs), and Viewer (read-only access to dashboards and logs). Each role is enforced at the API level — not just the UI.
Ad platforms set limits on API requests and uploads. TUOCA includes rate-limit handling to help manage those constraints, but a platform can still reject or delay a request. Review failed executions and connection health when an upload needs attention.