Skip to main content
Try it free for 10 days, then 35% off the first 3 months
Start now
Agent Fabrica
Legal

Privacy Policy

Last updated: 22.10.2026

1. Data Controller

Agent Fabrica Teknoloji Ticaret Limited Şirketi ("AgentFabrica", "we") is the data controller for personal data processed via our service, in compliance with GDPR (EU), KVKK (Turkey), and applicable laws.

  • Head office: Ağaoğlu My Office 212, Mahmutbey, Taşocağı Yolu Cad. No: 3 B Blok Kat: 26 Ofis: 440, 34218 Bağcılar / İstanbul
  • Registered office: Kemerkaya Mah. Öğretmen Sk. Mazlumoğlu Apt. No: 6 İç Kapı No: 8, Ortahisar / Trabzon

2. Personal Data Collected

  • Identity: name, surname
  • Contact: email, phone
  • Account: username, password hash
  • Payment: card data is processed by Stripe / PayTR — we do not store
  • Social IDs: encrypted OAuth access tokens
  • Brand profile data: logo, color, voice, audience, location
  • Generation data: prompts and generated assets
  • Technical: IP address, browser info, log records

3. Processing Purposes

  • Service delivery, account management, billing
  • Content generation (sending prompts to AI engines)
  • Social media publishing (to user-authorized accounts)
  • Customer support and communication
  • Legal obligations (tax, invoicing)
  • Service improvement and analytics (anonymous/aggregate)

4. Data Sharing

Your data may be shared with:

  • Payment processors: PayTR (TR), Stripe (international)
  • Cloud infrastructure: Supabase (Frankfurt EU), Vercel (Europe-West)
  • AI providers: Prompts are forwarded to third-party AI engines during generation
  • Email service: Resend / SendGrid for transactional notifications
  • Social platforms: Only with user authorization (Meta, TikTok, LinkedIn, X)
  • Connected AI assistants: Only the assistant you connect, within the scope described in 4c

4a. Connected Social Platforms — Data Processing Detail

When you connect your social media accounts inside AgentFabrica, we use each platform's official API via OAuth 2.0. Every authorization is consent-based and revocable at any time. We never sell your data or share it for marketing purposes with any third party.

TikTok Marketing API

  • Data we read: advertiser info, campaign / ad group / ad performance metrics (impressions, clicks, spend, conversions), audience definitions, creative asset metadata, Pixel events, conversion events.
  • Write permissions: only on the ad account explicitly authorized by the user — create and edit campaigns, ad groups, ads, and audiences.
  • Purpose of processing: campaign launch from creative briefs, A/B test winner detection, ROAS-based budget optimization, unified client reporting.
  • Retention: OAuth access and refresh tokens are stored AES-256-GCM encrypted for the duration of the active account + 30 days after cancellation; campaign and reporting data for 24 months.
  • Revocation: When you remove "AgentFabrica" from TikTok Business Center → Settings → App Authorizations, your tokens are deleted from our systems within 72 hours.
  • Brand asset compliance: TikTok logos and brand materials are used only within the AgentFabrica connection UI, in accordance with TikTok Brand Guidelines.

TikTok Login Kit & Content Posting API

  • Scopes: user.info.basic (open_id, display_name, avatar, username), video.upload, video.publish.
  • Data we read: only the public profile attributes of the connected TikTok account (open_id, display name, username, avatar URL). We do not read follower lists, direct messages, or private content.
  • Video transfer: Videos scheduled inside AgentFabrica are transferred to TikTok's official Content Posting API endpoints (/v2/post/publish/inbox/video/init/ or /v2/post/publish/video/init/) with the user's consent. Video files are not retained long-term on AgentFabrica servers; they are only delivered as draft or direct post to TikTok.
  • Captions / titles: Caption text entered by the user is forwarded to TikTok as-is; AgentFabrica does not repurpose this text for any other use.
  • Automation control: Each brand has an autoPublish flag controlled by the user; when disabled, videos are sent only after explicit approval.
  • Revocation: When you revoke "AgentFabrica Content" from your TikTok settings or disconnect the account inside AgentFabrica, both access and refresh tokens are deleted within 72 hours; pending scheduled posts are auto-cancelled.

Meta (Facebook & Instagram), LinkedIn, X / Twitter

Same framework: read/write only within the user-authorized scope, with explicit consent. Tokens are encrypted at rest; revocation triggers deletion within 72 hours. Platform-specific policy details available on request.

4b. Google Services — Data Processing Detail

When you connect your Google account inside AgentFabrica, we use Google's official APIs via OAuth 2.0. Access is limited to the properties/accounts you explicitly authorize and is revocable at any time. Information received from Google is used solely to show you your own marketing performance and to generate optimization recommendations for your own account.

Scopes we request and data we read

  • Google Analytics (analytics.readonly) — read-only: sessions, users, page views, conversions/key events, and channel, device and country breakdowns.
  • Search Console (webmasters.readonly) — read-only: search queries, clicks, impressions, average position, and page performance.
  • Tag Manager (tagmanager.readonly) — read-only: the container's tag inventory, used for a measurement-health audit.
  • Measurement setup permission (analytics.edit, tagmanager.edit.containers, tagmanager.edit.containerversions, tagmanager.publish): not requested with the connection; asked on a separate Google consent screen only when you press Grant measurement setup permission in the panel. Used to create a GA4 property and data stream, add tags to your container and publish a version, and mark conversion events.
  • Google Ads (adwords) — read and write: campaign performance (cost, clicks, conversions), search terms and keywords. Google offers no separate read-only permission for this service. Budget or campaign changes are made only through actions you take in the panel, changes you approve, or automated rules you set up.
  • YouTube (youtube.readonly, read-only): view, like and comment counts of the videos you published through AgentFabrica. Other videos on your channel are not read.
  • YouTube (youtube.upload, video upload): a video is uploaded only when you press publish in the panel or on the date you scheduled. You choose the privacy status (public, unlisted, private). If auto-publish is off for your brand, a scheduled video is not sent until you approve it.
  • Google Business Profile (business.manage): list of accounts and locations, creating and deleting posts (localPosts) for a location, reading reviews, writing and deleting replies to reviews, and performance metrics (search and map views, calls, direction requests and clicks). A review reply is first prepared as a draft; the text is sent to Google only after you review it and press send. Negative reviews never get an automatic reply.
  • Google Calendar (calendar.calendarlist.readonly, calendar.events.readonly; read-only): the list of your calendars and the upcoming events in the calendar you select. Used to show a summary of your upcoming appointments in the dashboard; no event is created, changed or deleted.

YouTube API Services

AgentFabrica uses YouTube API Services. By connecting your YouTube account you also agree to be bound by the YouTube Terms of Service. For Google's privacy practices, see the Google Privacy Policy. You can revoke AgentFabrica's access to your YouTube data at any time at security.google.com/settings/security/permissions.

Use, retention and revocation

  • Purpose: your data is processed to provide unified reporting and account-specific improvement recommendations inside your dashboard. It is never used for ad targeting, never sold, and never transferred to any party except as required to provide the feature.
  • Artificial intelligence: we do not use information received from Google APIs to develop, improve, or train generalized AI/ML models. Data is processed only to produce the recommendation shown to you.
  • Human access: humans do not read your Google user data, except with your explicit consent for support/security purposes or where required by law.
  • Retention: OAuth access and refresh tokens are stored AES-256-GCM encrypted for the duration of the active account + 30 days after cancellation; report data is cached for at most 24 months.
  • Revocation: Choosing "Disconnect" in AgentFabrica → Integrations deletes your tokens within 72 hours. You may also revoke access at myaccount.google.com/permissions.

Limited Use commitment

AgentFabrica's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4c. Connected AI Assistants (MCP)

When you connect an AI assistant such as Claude or ChatGPT to your AgentFabrica account through the MCP connector, the assistant can reach only the data of the account that allowed it. You start the connection and you grant it on the consent screen. All tools but one are read-only; that one adds a draft to the approval queue, and the draft is not published until you approve it in the panel. Setup and the tool list: MCP connector documentation.

Data the assistant receives

  • Brand details: brand name, industry, website, tone of voice and brand role.
  • Content calendar: post title, platforms, scheduled time, status and the start of the caption.
  • Approval queue: type, title and a short preview of items waiting for approval, with the panel link to review them.
  • Generated content records: type, category and date; the content itself is not sent.
  • Ad pre-test and learning data: panel score, objections, the impressions and clicks of an ad that later ran, panel calibration and the brand's learning pool.
  • Aggregate counts: quota status, lead counts by status and source, WhatsApp line status and conversation counts.

Data that is not sent

Names, phone numbers, form fields and message text of your leads and WhatsApp contacts are not sent to the assistant; those tools return counts only. The assistant cannot see brands of other accounts.

Processing by the assistant's provider

You choose which assistant to connect. Data sent to the assistant is processed under that assistant provider's own privacy policy.

Revoking access

  • From the panel: choose "Disconnect" on the Connected assistants card of the API keys page; the assistant's access closes immediately.
  • Automatically: a connection unused for 30 days closes; a connection in use asks for permission again after 90 days at the latest. Setting or changing your password, signing out of all devices and requesting account deletion close every assistant connection.

Retention of authorization records

  • What we keep: the name and return addresses the assistant app declares for itself; for each connection, your account, the connected app, its return address, and when it was connected, last used and, if so, removed. Tokens and authorization codes are never stored in plain form, only as SHA-256 hashes.
  • Tokens: an access token is valid for 1 hour and a refresh token for 30 days; their records are deleted after 2 and 31 days. An authorization code and a consent screen request are valid for 10 minutes; their records are deleted after 2 days and 1 day.
  • Connection record: deleted 7 days after the connection is removed or reaches its 90-day limit; a connection unused for 90 days is deleted too.
  • App registration: deleted once no connection uses it: 7 days after registration if it never connected, otherwise 90 days after its last use.

5. Retention Periods

  • Active account + 30 days after cancellation
  • Billing records: 10 years (Tax Code)
  • Generated assets: until user deletion
  • Log records: 6 months
  • Social platform OAuth tokens: until user revokes + 72 hours
  • Authorization records of connected AI assistants: as set out in 4c

6. Your Rights (GDPR / KVKK)

  • Right to access
  • Right to rectification, erasure
  • Right to restriction of processing
  • Right to data portability
  • Right to object to automated decision-making
  • Right to withdraw consent

Requests: privacy@agentfabrica.com

7. Cookies

We use essential cookies (session, locale, security). Traffic measurement has four layers: (1) our own counter — no cookies. Page views are counted on our own servers; visitors are distinguished by an irreversible digest of the IP address and browser string, salted with a value unique to that day. The raw IP is never stored and digests are deleted after 30 days. (2) Google Analytics — uses cookies for page view and channel statistics and runs when the site loads. Advertising personalisation stays denied until you accept in the cookie notice. (3) Meta (Facebook) pixel — uses cookies for ad measurement and runs when the site loads. We also report conversions such as sign-ups and form submissions from our own server to Meta (Conversions API): email, phone and name are never sent in clear text, only as an irreversible SHA-256 digest; the IP address and browser string are sent for matching. (4) Google Ads — a conversion tag matches conversions such as sign-ups to our ad campaigns; advertising cookies stay denied until you accept in the cookie notice and none are written before that. If you do not want analytics or advertising cookies you can use your browser's tracking protection, and you may request deletion of your data at any time at iletisim@agentfabrica.com.

Device ID cookie (af_cihaz): when you start a free trial, a random first-party ID that only the server can read (httpOnly) is set. It is used to prevent trial abuse (legitimate interest). Only a digest of the ID is kept in the trial record for 24 months; the cookie lasts 24 months.

  • Data processed: e-mail address (lower-cased; for Gmail, dots and + tags removed), phone number, the brand's web domain (root domain), IDs of business accounts you connect (Facebook page, Instagram account, ad account, Google Ads customer ID, TikTok, WhatsApp number, store domain, seller ID), card fingerprint for trials started with a card, IP address prefix (first three blocks for IPv4, first four groups for IPv6), a device ID cookie and a browser digest (browser family, time zone, language, screen size).
  • How it is stored: none of these values are stored as is; only irreversible SHA-256 digests are kept.
  • Purpose: making sure the free trial is used once per person and business, and preventing fraud and abuse.
  • Legal basis: legitimate interest of the data controller (KVKK art. 5/2-f).
  • Retention: 24 months. The digests are kept for that period even if you delete your account; after that they are not used for matching.
  • When a request looks risky the trial opens only after phone verification; the verification code is not stored as is either.

8. Security

AES-256-GCM encryption at rest, TLS 1.3 in transit, encrypted OAuth tokens, rate-limiting, and regular security audits.

9. Changes

We notify users via email and panel for material changes. This policy is reviewed at least annually.