ADpilot trust and data: security, GDPR and AI Act marking

ADpilot is built by ADpilot OÜ in Tallinn, Estonia, and runs under EU law. This page says what the product actually does with your accounts, your data and the content it makes. The Privacy Policy and Terms are the binding versions; where a point below is a promise from the policy rather than something you can see in the product, it says so.

At a glance

Platform passwords

Never asked for. Platforms connect by signing in on the platform, or with an app password or token you create for ADpilot.

Stored keys and tokens

Encrypted at rest, write-only in forms, kept out of the activity log.

Client review links

Only a hash of the link is stored.

AI images

Marked as AI-generated in the file metadata (IPTC), for every account.

AI articles

Marked as AI-generated in the article structured data.

Human review

Who approved what and when, and what a person edited, exportable as a CSV.

Website analytics

Google Analytics 4, only after you accept cookies.

Payments

Handled by Stripe.

Your rights

A form for GDPR and CCPA requests, open to anyone.

Your platform accounts

Instagram, Facebook, Threads, LinkedIn, Pinterest, X and TikTok connect by signing in on the platform itself, so ADpilot receives an access token, not your password. Bluesky, Mastodon, Telegram, Discord, WordPress and webhooks connect with an app password, token or webhook you create for ADpilot and can revoke on the platform at any time. Each one is checked with the platform before it is saved. The steps per platform are on Integrations.

Tokens, API keys and webhook secrets are stored encrypted. Forms never show a saved secret again: leaving the field blank keeps it, typing replaces it. The change history never records them, so a secret is not written out in plain text there either. Only owners and admins of a workspace can connect or change a platform.

The Privacy Policy commits that when you disconnect a platform, ADpilot stops calling it and deletes the stored token within 24 hours.

Your workspace

• Separation. Every brand belongs to one workspace, and every page and action in the app checks that you are a member of that workspace before it shows or changes anything.
• Client review links. A client can review drafts from a link without an account. Only a hash of the link is stored, so a copy of the database does not reveal working links.
• Fetching websites. When ADpilot reads a web address you or a draft supplies, it refuses private and internal network addresses.
• Sign-in forms. Sign-in, sign-up, password reset and the data request form are protected against bots with Cloudflare Turnstile and rate limits.

AI output: marked and reviewed

The EU AI Act asks two different things, and ADpilot handles them separately. What the rules say, and when they apply, is explained in how to review AI content before publishing.

• Machine-readable marking. Every image ADpilot generates carries the IPTC digital source type "trained algorithmic media" in its metadata, plus the name of the system that made it; an image that ADpilot later combines with your logo is marked as a composite. Articles published to your site carry the schema.org digitalSourceType in their structured data, and a person's edits before approval change the mark to "composite". This marking is on for every account and is not a setting.
• A visible label. Whether a post shows a visible AI label is a brand setting, because it depends on what you publish and where.
• A record of human review. When a draft is approved, ADpilot stores who approved it, when, and which parts a person edited. Approvals made by an automation you switched on are recorded as not reviewed by a person. Members of the workspace can download the whole record as a CSV.

Drafts wait in the approval queue by default. If a client approved a draft through a review link and someone edits it afterwards, that approval is withdrawn and the client sees what changed.

Personal data

• Controller. ADpilot OÜ, registry code 17376620, Ahtri tn 12, 15551 Tallinn, Estonia. Contact: [email protected].
• Analytics. This website loads Google Analytics 4 only after you accept analytics cookies; until then, no analytics request is sent. Fonts are served from adpilot.ee, not from a font service. You can change your choice under Cookie settings in the footer.
• Payments. Card details go to Stripe; ADpilot does not store them.
• Service providers and transfers. The providers we use and the safeguards for any transfer outside the EEA are listed in sections 4 and 5 of the Privacy Policy, with the retention periods in section 7.
• Your rights. Anyone, customer or not, can use the data request form to access, correct, delete or export their personal data. The policy commits to answering within 30 days under the GDPR.

What we do not claim

ADpilot does not hold a SOC 2 or ISO 27001 certificate. If your procurement needs answers beyond this page and the Privacy Policy, write to [email protected].