Privacy Policy

How we protect and handle your data

Last updated: October 14, 2026

Quick Summary

We take your privacy seriously. We only access the data you explicitly connect, never share it with third parties for commercial purposes, and you can disconnect any service or have all your data deleted at any time. Your API tokens and credentials are encrypted and project-isolated.

1. Introduction

Welcome to SharksAPI.AI ("we," "our," or "us"), operated by Marketing Sharks OÜ. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our AI-powered marketing platform at https://sharksapi.ai.

By using SharksAPI.AI, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Account Information

  • Registration Data: Name, email address, password (encrypted)
  • OAuth Data: When you sign in with Google, we receive basic profile information (name, email)
  • Project Data: Project names, settings, and configurations
  • Dashboard Sign-in: The name, e-mail address and role of each person of your business who signs in to your dashboard. They sign in with a one-time link we e-mail them; there is no password
  • AI Agent Registration: The name of the AI agent and the e-mail address of its owner, used as the agent's identity

2.2 Connected Services Data

When you connect third-party services, we access and store data based on your explicit consent:

CategoryServicesData Accessed
AnalyticsGoogle Analytics 4, Google Search Console, Microsoft Clarity, Bing Webmaster Tools, PostHogWebsite traffic, user behavior, search performance
Local & ReputationGoogle Business Profile, Trustpilot, Google AlertsBusiness profile insights, reviews, brand mentions
AdvertisingGoogle Ads, Meta Ads (Facebook & Instagram), OpenAI Ads, Google Merchant Center, Google Data ManagerCampaign performance, spend, conversions, product feeds
Social MediaFacebook Pages, Instagram, LinkedIn, Twitter/X, TikTok, YouTube, BlueskyPage analytics, engagement, followers, posts you approve for publishing
SEO ResearchAhrefs, Semrush, SEOShark, DataForSEO, Google Trends, Google Keyword Planner, UbersuggestKeywords, rankings, backlinks, competitors, search trends
EmailSMTP/IMAP and Microsoft 365 mailboxes, Resend, ActiveCampaignEmails you send, campaigns, delivery statistics
FormsJotformForm submissions
WebsiteWordPress, web server (SFTP)Posts, pages, SEO data, site files
ProductivityGoogle Calendar, Google Drive, Google Sheets, Google DocsEvents and files you connect

2.3 LinkedIn

LinkedIn is connected by an administrator of the LinkedIn company page, who signs in with LinkedIn and approves each permission on LinkedIn's own consent screen.

  • Page analytics: with LinkedIn's Pages Data Portability permission we read the page's follower, visitor and post statistics and the page's notifications, to show them in your dashboards.
  • Publishing: when the page administrator also allows posting (permission w_organization_social), we publish, as the company page, the posts and first comments that the page owner has approved in SharksAPI or allowed to be published automatically.
  • What we store: the encrypted access and refresh tokens, the page identifier, the page's statistics and the posts we published for the page.
  • What we do not do: we do not store LinkedIn members' profile data or comments, we do not use LinkedIn data for advertising, sales, recruiting or lead generation, we do not combine it with other data to build profiles, and we do not share it with third parties.
  • Revoking access: ask your AI assistant to disconnect LinkedIn, which deletes the stored tokens, or remove the app in LinkedIn under Settings > Data privacy > Permitted services. To have the data deleted, see 6.3 How to have your data deleted.

2.4 Meta Ads

Meta Ads is connected by a person who has access to the business's ad account. They sign in with Facebook, approve each permission on Meta's own consent screen and choose the ad account.

  • Permissions: ads_read to read the performance of campaigns, ad sets and ads; ads_management to make the changes described below; business_management to list the ad accounts the person can choose from; ads_mcp_management to use Meta's ads MCP server.
  • Meta's ads MCP server: we call Meta's own ads MCP server (mcp.facebook.com/ads) for campaign reports, delivery diagnostics, anomaly signals, metric definitions and Ad Library searches. We send it only what the request needs: the connected ad account, the ids of its campaigns, ad sets and ads, dates and metric names. We never send it what you or your team write to your AI assistant, and the conversation id it asks for is a random value.
  • Only your ad account: every request is limited to the ad account chosen at connection. Before a request to Meta's ads MCP server names a campaign, ad set or ad, and before we change one, we check with Meta that it belongs to that ad account.
  • Changes to your ads: we pause or start delivery, change daily budgets and create paused ads from creatives you approved only within the autonomy level and spending limits a person of your business sets in SharksAPI. Starting delivery and changing a budget wait for that person's approval unless they have put exactly that action on autopilot.
  • Conversions API: when your business reports leads and sales back to Meta, we normalise and hash e-mail addresses, phone numbers, names and external ids with SHA-256 on our server before sending them; the raw values never leave SharksAPI. The send waits for approval.
  • What we store: the encrypted access token, the ad account id, the list of permissions granted and copies of the reports shown in your dashboards, which are refreshed regularly.
  • What we do not do: we use Meta data only for your own marketing, we do not sell it, we do not combine it with other businesses' data, and we share it only with the AI assistant your team works through (see 5.1).
  • Revoking access: remove SharksAPI in your Facebook settings under Business integrations, or ask your AI assistant to disconnect Meta Ads, which deletes the stored token. To have the data deleted, see 6.3 How to have your data deleted.

2.5 API Tokens and Credentials

  • OAuth Tokens: Encrypted access and refresh tokens for connected services
  • API Keys: Encrypted API keys for third-party integrations
  • MCP Tokens: Bearer tokens for Claude AI MCP access (project-isolated)
  • Custom GPT Tokens: Bearer tokens for OpenAI Custom GPT access (project-isolated)

2.6 Usage Data

  • Questions you send your team on your dashboard ("Ask your team") and the answers
  • Your decisions on the dashboard: approvals, autonomy levels, plan, budget and limit changes
  • API usage logs and statistics
  • MCP tool call logs
  • Error logs and debugging information

3. How We Use Your Information

3.1 Service Provision

  • Provide AI-powered analytics, insights, and automation
  • Connect and sync data from your third-party services
  • Generate reports and dashboards
  • Enable MCP (Model Context Protocol) integrations with Claude AI
  • Enable Custom GPT integrations with OpenAI
  • Process email campaigns and scheduled tasks

3.2 AI Processing

  • Send relevant data to AI providers (OpenAI, Anthropic Claude, Google Gemini) for analysis
  • Generate insights, recommendations, and summaries
  • Write the weekly summary on your dashboard and check drafts before review; we remove e-mail addresses and phone numbers from the facts before they are sent
  • Create and optimize content (blog posts, emails, ads)
Important: Your data may be sent to third-party AI providers (OpenAI, Anthropic, Google) for processing. Each provider has their own privacy policy and data handling practices. We use enterprise-grade API access where available.

4. Data Security

4.1 Encryption

  • In Transit: All data is transmitted over HTTPS/TLS encryption
  • At Rest: Sensitive data (passwords, API keys, OAuth tokens) is encrypted using AES-256
  • API Tokens: Sanctum tokens are hashed and project-isolated

4.2 Access Control

  • Project Isolation: Each project's data is strictly isolated
  • Token-Based Access: API and MCP tokens are project-specific
  • OAuth2 + PKCE: MCP connections use industry-standard OAuth2 with PKCE
  • Role-Based Permissions: Admin and user roles with granular capabilities

4.3 Infrastructure

  • Hosted on AWS in the EU (Stockholm, Sweden), including the files of your social media posts
  • Regular security updates and patches
  • Automated backups
  • Application-level monitoring and logging

5. Data Sharing and Third Parties

5.1 Third-Party Services We Use

  • OpenAI: The weekly summary, draft checks and scheduled reports
  • Anthropic (Claude): AI processing via MCP integration
  • Your AI assistant: The assistant your team works through (for example Claude, ChatGPT or Gemini) receives the data it requests through our tools, under its provider's own privacy policy
  • Google Cloud: OAuth authentication and API access
  • Meta: The Marketing API and Meta's ads MCP server, to read your ad account and change it within your limits (see 2.4)
  • AWS SES: Transactional and campaign email delivery, from the AWS US East (N. Virginia) region
  • Stripe: Payments for credit packs; your card details stay with Stripe and are not stored by us
  • Your Connected Services: We access data from services you explicitly connect

5.2 We Do NOT Share Your Data With

  • Advertisers or marketing companies
  • Data brokers or aggregators
  • Other users or projects (strict isolation)
  • Any third parties for commercial purposes

5.3 Legal Requirements

We may disclose your information if required by law, court order, or government request.

6. Data Retention and Deletion

6.1 Retention Period

  • Your Project: Your project's data is kept while the project is active
  • Synced Data: Analytics and metrics are stored for historical analysis
  • Chat History: AI conversations are stored for context
  • Agent Activity: The history of what your AI agents did (each tool call, its arguments with sensitive values masked, and its result) is kept as an audit trail while your project exists
  • Usage Records: Records of API and tool calls (time, endpoint or tool, status and response time) are kept for 12 months
  • Server Logs: Error and diagnostic logs are kept for 14 days
  • Billing Records: Invoices and payment records are kept for 7 years, as Estonian accounting law requires

6.2 Disconnecting and Revoking Access

You can at any time:

  • Ask your AI assistant to disconnect a service. After you approve it, the connection and its stored credentials are deleted
  • Revoke our access at the service itself, for example under Business integrations in your Facebook settings or under Third-party apps & services in your Google Account. Our stored token then stops working
  • Remove the SharksAPI connector from your AI app. With a SharksAPI login you can also revoke MCP and API tokens on the API Tokens page and delete your login on your profile page

6.3 How to Have Your Data Deleted

Write to office@marketingsharks.ee from the e-mail address you use with SharksAPI and tell us which project or which data to delete. This is also how you have the data we received from Facebook or Instagram deleted: removing SharksAPI from your Facebook settings stops our access, but does not delete what we already stored.

Within 30 days of your request we delete:

  • The project with its settings, plans and dashboards
  • Its connections with their stored credentials and tokens
  • The people who sign in to its dashboards and the AI agents registered to it
  • The history of what its agents did and its usage records

We keep only what the law requires us to keep, such as invoices (see 6.1). We confirm by e-mail when the deletion is done.

7. Your Rights (GDPR)

As an EU-based service (Estonia), we comply with GDPR. You have the following rights:

  • Right to Access: Request a copy of your personal data
  • Right to Rectification: Correct inaccurate or incomplete data
  • Right to Erasure: Request deletion of your data ("right to be forgotten")
  • Right to Restriction: Limit how we process your data
  • Right to Data Portability: Export your data in a machine-readable format
  • Right to Object: Object to certain types of processing
  • Right to Withdraw Consent: Withdraw consent at any time

To exercise these rights, contact us at: office@marketingsharks.ee

8. Cookies

8.1 Essential Cookies

  • Session Cookies: Keep you logged in
  • CSRF Tokens: Protect against cross-site request forgery
  • Preferences: Remember your settings and selected project
  • Dashboard Sign-in: After you open an e-mail sign-in link, a cookie keeps you signed in to your dashboard for 30 days
  • Dashboard Unlock: When a dashboard password is entered, a cookie remembers it for 24 hours
  • Analytics (only with your consent): Google Analytics cookies are set on our website only after you accept them in the cookie banner

8.2 No Third-Party Advertising Cookies

We do NOT use advertising cookies or tracking pixels from third parties.

9. MCP, Custom GPT, and AI Agent Access

9.1 MCP (Model Context Protocol)

  • SharksAPI.AI provides MCP server access for Claude AI (Anthropic)
  • MCP connections use OAuth2 with PKCE for secure authorization
  • Each MCP session is bound to a specific project
  • Tool calls are logged for security and debugging
  • You can revoke MCP access at any time by removing the SharksAPI connector from your AI app

9.2 Custom GPT Access

  • API tokens for Custom GPTs are project-specific and encrypted
  • Tokens can be revoked from the API Tokens page
  • Custom GPTs can only access data from their linked project

9.3 AI Agents

  • Your AI team (a marketing director and channel specialists, working through MarketingBot and ManagementBot) processes your data to plan, do and measure the work
  • Agents act only within the autonomy level and limits you set; work that waits for approval is done only after an authorized person approves it
  • Agent actions are logged and auditable
  • Agents operate within project boundaries only
Important: Never share your API tokens or MCP credentials publicly. Treat them like passwords.

10. Children's Privacy

SharksAPI.AI is a business tool not intended for children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Changes are posted on this page with an updated date. Significant changes are announced by e-mail or on your dashboard at least 14 days before they take effect.

12. Contact Us

If you have any questions about this Privacy Policy:

Company: Marketing Sharks OÜ

Email: office@marketingsharks.ee

Website: https://sharksapi.ai

Country: Estonia, European Union