Where your data is stored
Everything LDOO stores lives in LDOO’s PostgreSQL database, managed by Supabase, where row-level security walls off every account. Marketing data, conversations, reports, portals, alerts, learned corrections, baselines, and seasonal patterns—all in one place, all under your account.
LDOO does not replicate your data to a separate data warehouse, analytics service, or third-party storage system. When you delete your account, support can restore it for 30 days; after that its data and files are permanently deleted, and the deletion reaches the database backups within 7 days as they roll over.
How your data is encrypted
Credentials are encrypted at rest. Data moves over encrypted connections. Passwords are hashed and not reversible.
AES-256 is the same encryption standard used by banks and government agencies. It is the industry baseline for data at rest. LDOO does not use weaker alternatives.
How clients are separated
If you manage multiple clients, each one is isolated from the others at the database level. This is not an application feature—it is a structural guarantee enforced by PostgreSQL.
Row-Level Security (RLS) runs inside the database engine. Every query—whether from the application, the AI pipeline, a background job, or an API call—is filtered before results are returned. This cannot be bypassed by application code.
What LDOO can access on each platform
LDOO connects to 13 supported sources across analytics, advertising, CRM, commerce, video, spreadsheets, and behavioral analytics. Every query LDOO sends is a read query. LDOO cannot modify campaigns, budgets, bids, or account settings on any platform.
Each connection uses standard OAuth—the same authorization flow used by Google, Meta, and Shopify for all third-party apps. You authorize access explicitly, and you can revoke it at any time from within LDOO or from your platform settings. For Google, LDOO appears alongside every other connected app on your Google Account connections page, where removing access takes effect immediately.
What the AI sees and does not see
Here is exactly what Anthropic's Claude receives for each answer, what it never sees, and what happens to the payload after the request completes.
Anthropic's data retention policy: API inputs and outputs are automatically deleted within 30 days. They are not used for training, fine-tuning, or any form of model improvement. This applies to all data LDOO sends.
Who can access what
LDOO has three types of users: account owners, team members, and external recipients (clients viewing a portal or report). Each has different access levels.
Client-facing surfaces—portals and shared reports—are designed so recipients see only what you intend. No LDOO navigation, no other clients, no agency data. Clients do not need an LDOO account. Access is controlled by the link, optional passwords, and expiry settings.
Infrastructure and operations
LDOO runs on production-grade infrastructure with automated backups, error tracking, and rate limiting.
What LDOO will never do
Clear boundaries, stated plainly.
If you have questions about data handling, security, or compliance that are not covered here, get in touch. For details on how the AI pipeline works, see How it works.