Legal
How MarketPilot handles data.
This policy explains how MarketPilot OS collects, uses and protects personal data.
1. Who we are
MarketPilot OS is operated by GK STUDIO LTD, a company registered in England and Wales with company number 16048293. Our registered office is London, UK. For privacy requests, contact founder@marketpilotos.com.
2. Information we collect
We may collect account details, authentication information, business profile information, campaign settings, uploaded media, generated marketing content, leads, messages, booking information, integration settings, usage data, billing records and support communications.
3. How we use information
We use information to provide the MarketPilot service, create and manage accounts, generate campaign recommendations, process uploads, manage leads and inbox activity, support connected integrations, process payments, maintain security, provide support, improve the product and comply with legal obligations.
4. AI processing
MarketPilot uses AI systems to help prepare recommendations, marketing content, image prompts, campaign plans, lead follow-up suggestions and performance summaries. Information you provide may be processed by AI providers only for the purposes of delivering the service. You remain responsible for reviewing and approving outputs before use.
5. Third-party services
We use trusted providers for authentication, hosting, database, payment, email delivery, AI processing, storage, analytics, monitoring and advertising-platform integrations. These may include Clerk, Vercel, Neon, Stripe, Resend, OpenAI, Cloudflare R2, Google and Meta where enabled by you.
6. Connected advertising accounts
If you connect Google, Meta, Facebook or Instagram accounts, we process the account, page, campaign, pixel, lead form and performance information needed to provide the features you enable. We do not launch adverts or external spend without the approval controls provided in the product.
7. Google Ads access
When you connect Google Ads, MarketPilot requests Google Ads access so it can list accessible advertising accounts, store your selected customer account, prepare paused Search campaign structures, read campaign performance and show reporting. We do not collect your Google password. You can disconnect Google Ads in MarketPilot settings or revoke access from your Google Account security settings.
7A. Google Search Console and Analytics access
When you connect Google Search Console or Google Analytics 4, MarketPilot requests read-only Google scopes for the service you choose. Search Console data may include verified properties, queries, pages, countries, devices, clicks, impressions, CTR, average position and sitemap information. GA4 data may include properties, sessions, users, conversions, events, landing pages, traffic sources, audience country data and realtime active users where available. MarketPilot uses this data only to show reports and prepare recommendations for your workspace.
7B. Google OAuth, disconnection and revocation
Google connections use OAuth. You can connect Google Ads only, Search Console only, Analytics only, or all supported Google services. Tokens are stored encrypted. Disconnecting Google in MarketPilot clears stored Google integration data and attempts to revoke the Google token. You can also revoke MarketPilot access directly from your Google Account permissions page.
8. Meta, Facebook and Instagram access
When you connect Meta, MarketPilot requests the permissions needed to read authorised ad accounts, Pages, Instagram Business account metadata, pixels and lead forms, create paused campaign structures, retrieve authorised lead form responses and read performance. Instagram Business metadata may include account ID, username, profile picture, connected Page and follower count where Meta returns it. We use this data only for the workspace you connect. We do not request Instagram publishing or messaging permissions. You can disconnect Meta in settings, remove the app from Meta settings, or request deletion using the contact below.
8A. Meta tokens, leads and deletion
Meta OAuth tokens are stored encrypted and are never shown in the browser. Lead data returned from authorised Meta lead forms is stored in your workspace with source attribution, including Instagram attribution where the lead is tied to an Instagram-selected campaign. Disconnecting Meta clears local token and integration settings and attempts provider revocation. Meta data deletion and deauthorisation callbacks remove matching local integration data where the signed Meta request can be verified.
8B. Instagram messaging and publishing data
MarketPilot currently keeps Instagram messaging and organic publishing disabled unless the required Meta permissions and production workflows are approved. If those features are enabled later, relevant message thread metadata, replies, media assets, captions, schedules, publish statuses and provider errors will be processed only for the workspace and account you authorise.
9. TikTok Ads access
When you connect TikTok, MarketPilot uses TikTok OAuth/Login to request the scopes needed for the features you enable. TikTok tokens are exchanged server-side, stored encrypted and never shown in the browser. MarketPilot may store connected account identifiers, granted scopes, missing scopes, selected advertiser details, destination URL, pixel ID, identity ID, budget preference, video/media metadata, publishing readiness, Ads readiness and reporting readiness. Live TikTok organic publishing, Ads campaign creation and reporting remain approval-first and are enabled only where TikTok has approved the required API access.
9A. TikTok media, reporting and recommendations
If TikTok organic publishing is enabled, uploaded or selected video assets, captions, validation metadata, publish status and provider errors may be processed to prepare or submit user-approved posts. If TikTok reporting is enabled, MarketPilot uses only real TikTok-returned metrics such as impressions, clicks, spend, conversions, leads or video views where available. AI-assisted TikTok recommendations may use connected setup details and real synced performance data, but recommendations do not automatically publish content, modify campaigns or spend money.
9B. TikTok disconnect, retention and deletion
Disconnecting TikTok clears local TikTok tokens and integration settings, and provider revocation is attempted where supported. TikTok audit, security, billing or dispute records may be retained where legally required. You can request deletion using /data-deletion or by contacting founder@marketpilotos.com.
10. Platform billing and ad spend
MarketPilot subscription fees cover the software and service workflow. Advertising spend is billed by the connected advertising platform or the customer's own advertising account, such as Google Ads, Meta Ads or TikTok Ads. MarketPilot does not take ownership of your ad account balance.
11. Legal bases
Where UK GDPR applies, we process personal data on the basis of contract performance, legitimate interests, consent where required, legal obligation, and in limited cases the establishment or defence of legal claims.
12. Data retention and deletion
We retain account and business data while your account is active. Lead, campaign, integration and operational records may be retained for up to 24 months unless a longer period is required for legal, billing, security or dispute purposes. If Google, Meta or another platform connection is disconnected, MarketPilot removes stored provider tokens and local integration settings unless lawful retention is required for audit, security or billing records. You may request deletion at founder@marketpilotos.com or review /data-deletion.
13. Your rights
You may have rights to access, correct, delete, restrict or object to processing of your personal data, and to request portability. You may also withdraw consent where processing is based on consent. Contact founder@marketpilotos.com to exercise these rights.
14. International transfers
Some providers may process data outside the United Kingdom. Where this happens, we take steps designed to protect personal data through appropriate contractual safeguards or recognised transfer mechanisms.
15. Security
We use reasonable technical and organisational measures including secure authentication, encrypted token storage where applicable, access controls, audit logs and operational monitoring. No system is completely secure and users must keep account credentials safe.
16. Changes to this policy
We may update this Privacy Policy as the service evolves. Material changes will be reflected on this page and, where appropriate, communicated through the product or by email.
Questions about this page can be sent to founder@marketpilotos.com.