Last updated: April 2, 2026
AI Marketer ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our AI-powered marketing content generation platform.
When you create an account, we collect your name, email address, and authentication credentials. If you subscribe to a paid plan, payment information is processed securely through Stripe.
To generate marketing content, we collect product descriptions, brand guidelines, target audience details, and other business information you provide through the dashboard.
We store AI-generated marketing content including social media posts, ad copy, content strategies, outreach messages, speaker pitches, guest post pitches, affiliate recruitment emails, AI-generated images (via Flux 2 Pro / FAL), and AI-generated videos (via Kling 2.1 Pro / FAL) created through the platform.
When you use the Creator Outreach, Reddit Community Outreach, Affiliate Recruitment, Speaking Opportunities, or Guest Post Pitching features, we store your search criteria, AI-generated results (creator profiles, subreddit matches, affiliate prospects, event listings, blog matches), saved pipeline items, outreach messages, pitch drafts, and status tracking data (e.g. "pitched", "accepted", "booked"). This data is stored locally in your browser (localStorage) and is not transmitted to our servers unless you explicitly use server-side publishing features.
When you use the Email Marketing features, we store your email campaign content (subject lines, body copy, drip sequences), campaign metadata (type, status, timestamps), and your recipient email lists. Recipient email addresses you upload or enter are stored server-side for campaign sending. Email campaigns are sent via SendGrid on your behalf. We do not sell, share, or use your recipient lists for any purpose other than sending the campaigns you create. You may delete recipient lists at any time from the Email section.
If you enable email notifications, we store your notification preferences (which notification types you've enabled/disabled), your email address, and a log of sent notifications (type, subject, timestamp, delivery success). Automated emails include daily agent summaries, weekly performance recaps, goal alerts, publish digests, and task completion notices. You can disable any notification type at any time from Settings → Email Notifications. Notification preferences and logs are stored in a server-side database (notifications.db) and deleted within 30 days of account deletion.
When you use the Creator Campaign Manager to generate mass creator briefs, we process your campaign parameters (goal, creator count, content format, duration) and product information through our AI to generate campaign briefs, hook templates, posting schedules, and content guidelines. Generated briefs are displayed in-browser and not stored server-side unless you explicitly save them.
When you add entries to the Knowledge Base (product docs, FAQs, case studies), this content is stored locally in your browser (localStorage) and sent to the AI service (Anthropic Claude) as part of the generation context for each content creation request. Knowledge Base entries are not stored on our servers. Up to 3,000 characters of Knowledge Base context are included per AI generation request.
The Content Discovery feature uses AI to identify trending topics in your niche. Your product information (name, niche, audience) is sent to our AI service to generate trending content suggestions. No external websites are scraped or accessed — suggestions are AI-generated based on the AI model's training data and your product context.
If you configure messaging integrations (Slack, Microsoft Teams, Discord, WhatsApp, or SMS/iMessage), webhook URLs and phone numbers are stored locally in your browser and in a server-side configuration file. Agent notifications (daily summaries, weekly recaps, goal alerts) are sent to these channels. Message content sent to webhooks includes notification type, summary text, and timestamps. We do not read or access messages from your Slack, Teams, Discord, WhatsApp, or SMS conversations.
When you use e-commerce marketing features (product description generation, catalog-to-social content, abandoned cart email sequences, review responses), product information you provide (names, descriptions, prices, URLs, images) is processed through our AI service to generate marketing content. Product catalog data uploaded via CSV is processed in-browser and sent to the AI service per-generation. We do not connect to or access your Shopify, WooCommerce, or other e-commerce platform directly.
When you use the AI Landing Page Generator, your product information is processed through our AI service to generate landing page copy and HTML. Generated pages are displayed in-browser and can be downloaded as self-contained HTML files. We do not host generated landing pages — hosting is your responsibility via services like Netlify, Vercel, GitHub Pages, or your own web server.
When you use the Auto-Edit Video pipeline, raw video files are uploaded to Creatomate (a third-party video rendering API) for automated editing, captioning, and effects. Your video content and any associated text (scripts, captions, product names) are processed by Creatomate's servers. Rendered videos are returned to your browser for download. Creatomate's privacy policy governs their handling of uploaded content. We do not store your raw or rendered videos on our servers.
The Spark Ads Scaling Brief generator processes your product information to create TikTok advertising strategy recommendations including budget tiers, CPA targets, and creative testing frameworks. The CapCut Auto-Edit Instructions generator creates video editing guidance based on your product context. Both tools generate content displayed in-browser only — no advertising accounts are connected or modified, and no data is sent to TikTok or CapCut. These features provide strategy recommendations; all ad campaign creation and video editing is performed by you separately on those platforms.
We fetch and store comments, mentions, and replies from your connected social media accounts to display in your Social Inbox. This includes the commenter's name, handle, avatar, and message text. AI sentiment analysis is performed on incoming messages.
When you connect your LinkedIn account, we request the following OAuth scopes: openid, profile, and w_member_social. We publish posts on your behalf via the LinkedIn REST API, including text posts, document/carousel posts, polls, and image posts. We fetch engagement metrics (likes, comments, shares, impressions) from your published posts for analytics. LinkedIn comment data is imported into the Social Inbox. We do not access your LinkedIn connections, private messages, or profile data beyond what is needed for publishing and analytics. Your LinkedIn access token is stored server-side and is encrypted at rest.
When you use Reddit marketing features, AI generates Reddit-optimized post titles, body text, and subreddit recommendations based on your product information. Reddit posts are saved as drafts and published via the Reddit API when you connect your Reddit account. We store your Reddit OAuth token server-side (encrypted at rest) for publishing only. The Reddit Community Outreach feature generates AI-suggested subreddits, moderator analysis, and modmail drafts — these are AI-generated recommendations, not scraped data. We do not access your Reddit DMs, browsing history, or upvote/downvote activity.
When you connect your Pinterest account, we publish pins on your behalf via the Pinterest API, including standard pins, idea pins, and video pins. We access your Pinterest boards for pin placement and fetch pin analytics (impressions, saves, clicks, engagement rate). Product catalog data may be synced for Shopping Pins if you enable the e-commerce integration. We do not access your Pinterest following list, saved pins from other creators, or private boards unless explicitly selected for publishing. Your Pinterest access token is stored server-side and encrypted at rest.
When you use the Ad Campaigns feature to create Apple Search Ads, Google Ads, or Meta (Facebook/Instagram) campaigns, we store your campaign configurations, keywords, ad copy, budget settings, and performance metrics (impressions, clicks, conversions, CPA, ROAS). Ad platform API tokens are stored server-side and encrypted at rest. AI-generated ad creatives (copy, images, video scripts) are stored as part of your campaign history. We use aggregated, anonymized campaign performance data to improve our AI creative scoring and ROAS prediction models. We do not share your individual campaign data with other users or third parties.
When you use advanced AI features — GEO Optimizer, Digital Twin Simulation, Voice Studio, AI SDR, Brand Safety, and Workflow Builder — your product information and content are processed through our AI service (Anthropic Claude) to generate analyses, predictions, simulations, and recommendations. GEO audit results, simulation predictions, brand safety scores, and workflow configurations are stored locally in your browser (localStorage). Voice Studio audio generation, when enabled, sends text to ElevenLabs API for voice synthesis — ElevenLabs' privacy policy governs their handling of this data. AI SDR prospect data and outreach sequences are stored locally and are never sent automatically — all outreach requires manual review and sending. When you connect Google Play Console via service account, we fetch and store review data (reviewer name, rating, review text, device info, app version) for display in the Reviews dashboard. Developer replies you approve are posted via the Google Play Developer API. Google Play review data is refreshed on-demand and covers the most recent 7 days (API limitation). The ROI Proof Engine, when connected to a payment processor (Stripe, Shopify, Paddle), processes transaction data to attribute revenue to marketing content. Payment data is processed in-session and not stored permanently — only aggregated attribution results are retained. Competitive Content Arbitrage analyzes publicly available competitor social media posts to identify content gaps and generate counter-content. No competitor account credentials are accessed. The Marketing Genome analyzes your content performance patterns using anonymized, aggregated data to identify success and failure genes.
The Content Atomizer, Revenue Forecast, Schedule Health, and Retention Intelligence features process your content and marketing activity data through our AI service to generate derivatives, predictions, and risk assessments. Content atomization outputs are generated in-session and displayed in your browser. Revenue forecasts are AI estimates based on your stated marketing spend — they are not financial advice. Churn risk scores are calculated locally using behavioral signals and are not shared with third parties. The Event Bus system logs marketing events (content published, reviews received, competitor updates) in a local database for workflow automation.
When you set post conditions, we monitor your published posts' engagement metrics (likes, impressions, engagement rate) to trigger follow-up comments you've configured.
If you configure outbound webhooks, publishing events (post published, failed, approved) are sent to your specified URLs. You control which endpoints receive data.
Template variables in your posts are processed at publish time. Custom variable values you provide are used only for content substitution and are not stored separately.
When link shortening is enabled, URLs in your posts are sent to third-party shortening services (Bitly, TinyURL) to generate shortened links.
When you install the Revenue Radar tracking pixel on your website, the pixel collects: page URLs visited, UTM parameters, anonymous visitor IDs (randomly generated strings not tied to real identities), conversion events, and revenue amounts when voluntarily reported by you (the website owner). This data is stored server-side in SQLite and used solely for attribution reporting within your AI Marketer dashboard. No personally identifiable information is collected by the Revenue Radar pixel unless explicitly sent by you. Visitor IDs are anonymous random strings generated client-side and are not tied to real identities, email addresses, or any other personal data. Revenue Radar data is associated with your AI Marketer account and is not shared with other users or third parties.
When you use the Voice DNA feature, we analyze text samples you provide (writing excerpts, social posts, emails) to extract voice patterns such as tone, sentence structure, vocabulary preferences, and stylistic traits. Voice DNA profiles are stored server-side in SQLite and associated with your account. No audio is recorded or stored — only text transcripts and extracted patterns. Voice DNA profiles are used solely to personalize your AI-generated content so it matches your natural writing style.
When you use the free marketing audit tool at /audit, we collect the URL you submit and your email address. Audit results are generated by AI based on publicly available information about the submitted URL. Audit results are not stored permanently — they are generated on-demand and delivered to the email address you provide.
Sample content loaded during onboarding is pre-generated and not based on your personal data. Demo content is provided for demonstration purposes to help you understand platform capabilities before creating your own content.
When you use the Growth Experiments feature, AI-generated experiment plans (test hypotheses, audience segments, content variations, timing recommendations) are created based on your product information and marketing goals. Experiment plans are AI-generated suggestions and are not automatically executed — you choose which experiments to run. Experiment configurations and results are stored locally in your browser.
When you use the Clone Post feature and paste a post to clone, the text is sent to our AI service (Anthropic Claude) for analysis and content generation. The original pasted text is not stored permanently — it is processed in-session to generate your cloned content variations.
We access your recent Instagram post history to generate grid preview layouts.
When you use Social Listening and Streams features, we monitor publicly available social media content (mentions, keywords, hashtags, competitor activity) across connected platforms to surface relevant conversations and trends. Search queries, stream configurations, and matched results are stored server-side. We do not access private or direct messages on any platform.
When you use the Blog Publisher to create and publish articles, we store your blog content (titles, body text, SEO metadata, tags, featured images) and publishing credentials for connected platforms (WordPress, Ghost, Medium, Dev.to, Hashnode). Publishing credentials and API tokens are stored server-side and encrypted at rest. Published blog content is sent to your connected blogging platform via their respective APIs.
When you interact with the AI Agent via the chat sidebar, we store your conversation history (messages, commands, agent responses, and action logs) to provide continuity across sessions and to improve agent performance. Chat history is stored locally in your browser (localStorage) and may be transmitted to our AI service (Anthropic Claude) for response generation. You can clear your chat history at any time using the clear button in the chat panel.
AI Marketer tracks engagement metrics for gamification purposes, including experience points (XP), levels, streaks (daily usage consistency), achievements, and milestones. This data is used to provide motivational feedback and track your marketing activity progress. Gamification data is stored server-side and associated with your account.
When you connect FeedHive for social media publishing, we store your FeedHive API credentials (encrypted at rest) and transmit content (post text, images, videos, scheduling metadata) to FeedHive's servers for publishing to your social accounts. FeedHive's privacy policy governs their handling of your data once transmitted. We do not access your FeedHive analytics or account data beyond what is necessary for publishing.
We collect anonymized usage data including feature usage patterns, content generation frequency, and platform interaction metrics to improve our service.
We integrate with the following third-party services to provide our platform:
All server-side data is encrypted in transit (TLS) and at rest.
You have the following rights regarding your personal data:
To exercise any of these rights, contact us at hello@aimarketer.com.
We use cookies solely for session authentication. We do not use advertising cookies, tracking pixels, or third-party analytics cookies. Your session cookie is essential for keeping you logged in and is deleted when you sign out.
If you are located in the European Economic Area, you have additional rights under the General Data Protection Regulation (GDPR), including the right to lodge a complaint with your local data protection authority. Our lawful basis for processing your data is (a) your consent, (b) performance of our contract with you, and (c) our legitimate interests in improving the service.
If you are a California resident, you have the right to know what personal information we collect, request deletion, and opt out of the sale of personal information. We do not sell your personal information.
We implement industry-standard security measures including TLS encryption, secure authentication tokens, rate limiting, input validation, and regular security reviews. While no system is 100% secure, we take reasonable precautions to protect your data.
We retain your data for as long as your account is active. Upon account deletion, we remove your personal data within 30 days, except where retention is required by law. Anonymized, aggregated analytics data may be retained indefinitely. Social Inbox data (inbox.db), post condition data (post_conditions.db), webhook data (webhooks.db), email notification logs (notifications.db), email campaign data, recipient email lists, blog publishing credentials, gamification records, and ad campaign data are deleted within 30 days of account deletion. Outreach pipeline data (saved creators, subreddits, affiliates, speaking opportunities, and guest post targets) stored in browser localStorage is managed locally and can be cleared at any time from your browser. Agent chat history stored in localStorage can be cleared at any time using the clear button in the chat panel.
AI Marketer is not intended for use by anyone under the age of 13. We do not knowingly collect personal information from children under 13. If we become aware that we have collected data from a child under 13, we will delete it promptly.
We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the "Last updated" date. Your continued use of the platform after changes constitutes acceptance.
If you have questions about this Privacy Policy or our data practices, contact us at:
Email: hello@aimarketer.com