Skip to main content

Privacy Policy

Last updated: September 30, 2026

AdLauncher by PATI Group is committed to protecting your privacy. This policy explains how we collect, use, and safeguard your information.

1. Introduction

AdLauncher ("we," "our," or "us") is operated by PATI Group and provides an ads management platform that allows businesses to create, launch, and manage their Meta and Google advertising campaigns efficiently.

By using AdLauncher, you agree to the collection and use of information in accordance with this Privacy Policy. If you do not agree, please do not use our services.

2. Information We Collect

2.1 Information You Provide

  • Account Information: Name, email address when you register.
  • Organization Data: Organization name, slug, and team member information.
  • Ad Content: Creative assets (images, videos), ad copy (headlines, descriptions, primary text), and campaign configurations you create within the platform.
  • Profile Data: Avatar, display name, and preferences.

2.2 Information from Facebook/Meta

When you connect your Facebook account, we access:

  • Facebook User ID, name, profile picture, and email address
  • Facebook Pages associated with your account
  • For Pages you connect: the name and profile picture of people who message your Page, used only to show who you are replying to in the Page Manager inbox
  • Ad Accounts and Business Manager accounts
  • Advertising performance data (spend, impressions, clicks, conversions)
  • Creative assets uploaded to your ad accounts
  • Product catalogs associated with your Business Manager
  • OAuth access tokens for ongoing API access

2.3 Information from Google

When you connect a Google account, we access:

  • Google Ads customer accounts you can access, with their campaigns, ad groups, assets, and performance data
  • Files you choose to import from Google Drive (read-only, only the files you pick)
  • OAuth access and refresh tokens for ongoing API access

2.4 Automatically Collected Information

  • Usage Data: Pages visited, features used, and interaction patterns.
  • Device Data: Browser type, operating system, and IP address.
  • Session Cookies: Authentication tokens for keeping you logged in.
  • AI Agent Activity: Which API key or connected agent made a request, the tool it called, and when.

3. How We Use Your Information

We use your information to:

  • Provide, maintain, and improve our ad management services
  • Create and manage Meta and Google ad campaigns on your behalf
  • Upload creative assets to Meta's and Google's advertising platforms
  • Display advertising performance data and analytics
  • Enable collaboration between team members within your organization
  • Answer requests from AI agents you connect, within the limits described in Section 6
  • In the Page Manager inbox, sort customer messages and comments by topic and suggest replies for your staff to review
  • Send invitation emails and important account notifications
  • Authenticate your identity and maintain session security
  • Respond to support requests and inquiries

4. Facebook/Meta Data Usage

We access Facebook data solely to provide our advertising management services. Here is how each permission is used:

ads_management

To create, edit, duplicate, pause, and manage your Meta ad campaigns, ad sets, and individual ads on your behalf.

ads_read

To retrieve campaign performance metrics (spend, impressions, clicks, ROAS, CPA) and display analytics within the platform.

business_management

To access your Business Manager, retrieve connected ad accounts and business assets, and manage campaigns across your business portfolio.

pages_show_list

To display your connected Facebook Pages so you can select which page to advertise from when launching campaigns.

pages_read_engagement

To read page-level engagement data and enable the Best Performing Organic Post automation trigger. Also used to sync historical comments for moderation.

pages_read_user_content

To read comments that customers and visitors post on Facebook Pages you manage, so your team can see and respond to them in the Page Manager support queue.

catalog_management

To access and manage your Meta product catalogs for dynamic product ads and catalog-based campaigns.

pages_manage_engagement

To reply to and hide/unhide comments on Facebook Pages you manage, for customer support and moderation inside Page Manager.

pages_messaging

To receive and send Facebook Messenger messages on Pages you manage through the AdLauncher unified inbox.

pages_manage_metadata

To subscribe your Facebook Pages to webhook notifications so AdLauncher can deliver realtime Messenger and comment events.

pages_manage_posts

To publish organic posts to Facebook Pages you manage from AdLauncher Posts Ops.

We do not sell or rent your Facebook data, and we do not share it with third parties except with AI agents that you or an Admin of your organization connect (see Section 6). We do not use your Facebook data for any purpose unrelated to providing our services.

5. Google Data Usage

We use Google Ads data to show performance, build and launch campaigns you create, and manage the Google Ads accounts you connect. Google Drive access is read-only and limited to the files you choose to import.

AdLauncher's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data or use it for advertising to you.

6. AI Agents (MCP)

You can connect AI assistants such as Claude, Cursor, or Codex to AdLauncherthrough our Model Context Protocol (MCP) server. A connected agent acts as the person who connected it, inside that person's organization and role.

  • Read access: An agent can read the workspace data you can see, such as ad accounts, campaigns, performance, media library, and automation rules. Signing in with AdLauncher gives read-only access.
  • Write access: An agent connected with an AdLauncher API key can write only what an app Admin has granted that key, on named ad accounts: saving Launch and Campaign drafts, and pausing or resuming campaigns. Write access is available for Meta only.
  • No launches: An agent can never launch a campaign. Drafts it writes wait for a person to review and launch them.
  • Where your data goes: Data an agent reads is sent to the AI provider you chose and is handled under that provider's own terms and privacy policy. We send data only to agents you or your organization connect.
  • Records: Drafts and actions made by an agent are labelled as agent activity in AdLauncher.
  • No Page inbox data: Agents connected over MCP cannot read Page messages, comments, or the names and profile pictures of people who message your Page.

7. Data Storage and Security

  • Data is stored securely using Supabase (hosted on AWS infrastructure) with row-level security policies ensuring only authorized users can access their data.
  • Facebook and Google access tokens are encrypted at rest and transmitted only over HTTPS.
  • All data transmission uses TLS 1.2+ encryption.
  • Access to organization data is strictly limited to authorized team members within the same organization.
  • AI agent API keys are scoped to one organization and provider, and can be deleted at any time.
  • We regularly review our security practices and update them as needed.

8. Data Sharing and Disclosure

We do not sell your personal information. We share your information only in the following circumstances:

  • Meta/Facebook: To create and manage advertising campaigns as directed by you through the Meta Marketing API.
  • Google: To create and manage advertising campaigns as directed by you through the Google Ads API.
  • AI Agents You Connect: The AI assistant you or your organization connect over MCP receives the data it requests, within the access described in Section 6.
  • Your Team Members: Organization members can view shared creative assets and campaign data within the same organization workspace.
  • Service Providers: Trusted third-party services including Supabase (database hosting) and Resend (transactional email) that process data strictly on our behalf and under confidentiality agreements.
  • AI Processing Providers: To sort Page Manager messages by topic and to suggest replies, we send the text of a customer message or comment, and for suggested replies the customer's name, to Typesafe, OpenAI, or Google Gemini. They process it only to return the result to AdLauncher, under their API terms. We do not send profile pictures, and we do not use this data for advertising.
  • Legal Requirements: If required by applicable law, regulation, court order, or to protect the rights and safety of our users.

9. Data Retention

We retain your data for as long as your account is active or as needed to provide our services. Specifically:

  • Account data is retained until you delete your account.
  • Creative assets and campaign data are retained until you delete your organization.
  • Facebook and Google access tokens are deleted immediately upon disconnecting the account or deleting your organization.
  • Page Manager messages, comments, and the names and profile picture links of people who message a Page are deleted when Facebook sends us a data deletion request for your account.
  • AI agent API keys are kept until you delete them. Drafts written by an agent are kept until they are discarded or launched.
  • Execution logs are retained for 90 days for debugging purposes.

10. Your Rights

You have the following rights regarding your personal data:

  • Access: Request a copy of the personal data we hold about you.
  • Correction: Request correction of inaccurate or incomplete data.
  • Deletion: Delete your account and all associated data through the Settings page. Deletion is permanent and irreversible.
  • Disconnect Facebook or Google: Revoke our access at any time through Settings → Connectors, which immediately removes all stored tokens.
  • Revoke AI Agent Access: Delete an API key in Settings → API, or remove the AdLauncher connector in your AI assistant. An Admin can withdraw an agent's write access in Settings → API at any time.
  • Data Portability: Request your data in a structured, machine-readable format.
  • Opt-out: Opt out of non-essential communications at any time.

To exercise any of these rights, contact us at thomas@patigroup.com.

11. Cookies

We use only essential cookies required for authentication and session management. We do not use tracking, advertising, or analytics cookies. Specifically:

  • Session cookies: To keep you logged in during your session.
  • CSRF tokens: To protect against cross-site request forgery attacks.

12. Children's Privacy

AdLauncher is intended for use by businesses and individuals aged 18 and older. We do not knowingly collect personal information from individuals under 18. If you believe a minor has provided us with personal information, please contact us immediately.

13. Changes to This Policy

We may update this Privacy Policy periodically to reflect changes in our practices or legal requirements. When we make material changes, we will notify you via email or an in-app notification and update the "Last updated" date at the top of this page. Your continued use of AdLauncher after any changes constitutes acceptance of the updated policy.

14. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy, please contact us:

Company: PATI Group

Product: AdLauncher

Email: thomas@patigroup.com

Website: https://ads.patigroup.com