Security & Audit
AdsCove Product & Engineering · Last reviewed August 5, 2026
AdsCove assumes that AI can make mistakes, retry requests, or be manipulated. Security is therefore enforced on the server instead of relying on the AI to behave correctly.
Read/write separation
Read tools such as reports, lists, and diagnostics run directly. Direct writes such as creating ads, changing budgets or statuses, and editing pages require explicit confirmation: the AI receives a pending approval and execution ID, reads the change back, waits, and only then calls approve_action. The only exception is a narrowly defined safety rule you separately enable in advance; it may auto-pause within the thresholds you chose. Activity is the fallback approval page, and approvals expire after 72 hours.
The AI never gets your platform keys
Platform OAuth tokens are encrypted with AES-256-GCM and stored on the server. They are decrypted only to run an operation you authorized. The AI client receives only an AdsCove API key, which you can revoke at any time. The API key itself is stored as a SHA-256 hash.
Content policy (cannot be disabled)
- Counterfeit brand terms are blocked before approval.
- Ad landing pages must belong to a connected Shopify store or a registered domain.
- Meta and Google creation produces paused resources; activation is a separate approved action.
- Deletion tools are not provided.
Duplicate prevention and rate limits
Write operations support an idempotency key, so a network retry does not create a duplicate campaign. Requests are limited account-wide across API keys, with a default minute window of 60. This is a safety limit for runaway loops, not a billing meter.
Full audit history
Every bounded tool call records a redacted or size-limited input and output plus risk level, duration, and internal protection units. Sensitive conversion identifiers are never copied into the audit row. You can review Activity; supported writes also keep before-and-after snapshots.
Data isolation and disconnecting
Connections, tokens, and logs are isolated per AdsCove user with database row-level security. Disconnecting immediately deletes AdsCove's stored token and marks the local connection revoked; revoke the provider-side grant in Google, Meta, or Shopify settings when you also want to end authorization at the provider. Shopify uses a merchant-owned custom app, so AdsCove does not claim that uninstall cleanup is automatic.