Privacy Policy

1. Introduction

Welcome to Food Blog Studio, operated by Food Blog Coaching (“we,” “our,” or “us”). We are committed to protecting your personal information and your right to privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our AI-powered food blogging platform (“Service”).

By using Food Blog Studio, you agree to the collection and use of information in accordance with this policy. If you do not agree with our policies, please do not use our Service.

2. Information We Collect

2.1 Information You Provide

• Account Information: Email address, first name, and last name when you create an account
• Billing Information: When you subscribe, payments are processed by Stripe. We do not store your full card details; we retain a billing customer reference and your subscription status
• Content You Create: Recipes, blog posts, social media captions, email newsletters, and other content you generate using our AI tools
• Personalization Data: Your Ideal Reader Profile and Voice Tone Profile, including writing samples and audience information you provide to personalize AI responses
• Uploaded Content: CSV files for analysis, writing samples, and sitemap URLs you submit to our tools
• Connected Blog Content: If you connect your WordPress blog, we import the published posts on it: each post's title, web address, publish and update dates, whether your SEO plugin marks it noindex, its text, its recipe card, and the links it makes, both to other pages on your blog and to other websites (including whether a link is marked as sponsored or nofollow). We also import your blog's categories and the addresses of its pages. Your browser reads these directly from your site's public WordPress feed. We never ask for or use your WordPress login, and password-protected posts are skipped. Our servers make a small number of requests to your site's public pages: when you connect, to check whether your site can be reached, and if your browser can't read the feed, to find your blog's correct address or its public sitemap. If your linking list comes from your sitemap instead, our servers read that sitemap once a day to keep it current. When you attach an imported post to a message, the relevant part of that post is sent to our AI provider along with your message
• Conversation History: Messages and interactions with our AI writing tools
• Feedback and Votes: What you send through Share Feedback (the type you pick and your message), stored with your name and email address so we can follow up, and the ideas you vote for. Other members never see who sent feedback or who voted
• AI Connections: If you connect your own Claude or ChatGPT (section 5A), we keep a record of each time you agree on the connect screen, which app you connected, when you connected it, when it last contacted us, and when you revoked access. We also keep a short record of each tool it uses: which tool, when, which app, whether it worked, and which update it logged, if any. We don't keep what it asked for or what it got back. We use these records to show you your connections, keep the feature secure, and help you if you ask for support

2.2 Information Collected Automatically

• Usage Data: Token usage, feature usage, and interaction patterns
• Device Information: Browser type and operating system, collected in aggregated, anonymous form through cookieless analytics
• Log Data: IP address, access times, and pages viewed (standard server logs kept by our hosting provider)
• Advertising Measurement: On our marketing website and public checkout pages (not inside the signed-in app), the Meta Pixel records page visits and actions such as starting checkout or completing a purchase, and a scrambled (hashed) copy of an email address or name typed into a form on our marketing website, so we can see which of our ads work and show them to people who visited. When you sign up through our checkout, our servers also send Meta your sign-up directly (see section 5)
• Cookies: See our Cookie Policy for details

3. Google User Data (Analytics Dashboard)

Food Blog Studio includes an optional Analytics Dashboard, included in the Food Blog Studio plan and in free Analytics trials (and a beta for Food Blog Coaching members). If you choose to connect your Google account to use it, this section describes exactly what Google user data we receive and how we handle it.

3.1 What We Access

If you choose to connect Google, we request read-only access to your Google Analytics 4 data (scope: analytics.readonly) and your Google Search Console data (scope: webmasters.readonly), plus your Google account email address. We never receive write access and cannot change anything in your Google account.

3.2 How We Use It

We use this data only to show you your own blog's traffic and search performance, to give you insights about your own content, and to answer your own Claude or ChatGPT when you've connected it (sections 3.4 and 5A). We don't use Google user data for advertising, sell it, or share it with any other third party except the service providers that host our infrastructure.

3.3 Storage and Retention

We sync daily traffic, page, and search-query metrics into our database (hosted by Supabase in the United States) so your dashboard loads without contacting Google on every visit. OAuth tokens are stored encrypted at rest. Search Console data, including the searches that led people to your posts, is kept for up to 16 months, the same history Search Console itself keeps. Google Analytics data is kept for up to 24 months, so you can compare this year with the last. Older data is deleted automatically.

3.4 Google Data and AI

Food Blog Studio never sends your Google user data to any AI model provider on its own. We never use it in our own AI writing tools, and we never use it to develop, improve, or train AI or machine learning models.

If you have Analytics and connect your own Claude or ChatGPT (section 5A), it can ask for your Google data so it can answer you while you chat with it. We give it only the answer to what it asked, only for your own blog, and only while it's connected. That includes what Food Blog Studio figures out from your data, like Opportunities and the results of your updates. Nothing happens until you click Connect, and you can stop it any time with Revoke access. After that, your AI app's own terms decide what happens to your data, including whether your chats are used to train its models (section 5A).

3.5 Human Access

Our staff do not read your Google user data except for security or abuse investigations, to comply with applicable law, or with your explicit consent when you ask us for support. This covers our staff. Whether your AI app's company may review your chats is up to its own terms (section 5A).

3.6 Disconnecting and Deletion

You can disconnect Google at any time from the Analytics section of the Personalization page, which revokes our access token with Google. You can also choose “Disconnect and delete synced data,” which permanently deletes all Google Analytics and Search Console data we have stored for your blog. You can additionally revoke access at https://myaccount.google.com/permissions. If you delete your account, stored Google user data is deleted as well. Disconnecting Google here also stops your AI app from reading your Google numbers until you connect Google again. If you remove our access only in your Google account, your AI app can still read what we already synced until you disconnect Google here or click Revoke access.

3.7 Limited Use

Food Blog Studio'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. That includes the Google data your own AI app asks for after you connect it (section 5A). You turn this on yourself, and your AI app gets your Google data only when it asks, and only for your own blog.

3A. Ad Network Data (Raptive)

If your blog's ads are run by Raptive, you can connect it to see what each post earns. You create a Client ID and Secret in your Raptive dashboard and paste them into Food Blog Studio. By connecting, you ask us to read your own Raptive reporting for you and confirm your Raptive account allows it. We read your site's and each page's daily earnings, pageviews, sessions, RPM and ad impressions. We never ask for your Raptive password.

Your earnings are shown only to you and to an AI app you connect yourself. We never sell them or share them with anyone else, and Food Blog Studio never sends them to any AI model provider on its own. If you connect your own Claude or ChatGPT (section 5A), it can ask for your Raptive data (your earnings, RPM, and the pageviews and sessions Raptive counts). We give it only the answer to what it asked, only for your own blog, and only while it's connected. Your Client ID and Secret are stored encrypted. Earnings are kept for up to 24 months. Disconnecting stops syncing, deletes your key, and stops your AI app from reading your earnings. Removing the key only in Raptive stops new syncing, but your AI app can still read the earnings we already synced until you disconnect Raptive here or click Revoke access. “Disconnect & delete earnings” also deletes your earnings, and so does deleting your account. You can also remove the key in Raptive at any time.

4. How We Use Your Information

We use your information to:

• Provide, maintain, and improve our AI-powered content generation services
• Process your content through our AI systems (Anthropic Claude) to generate responses
• Answer your own Claude or ChatGPT when you've connected it, and add the updates it logs for you (section 5A)
• Personalize your experience based on your Ideal Reader Profile
• Track and manage your usage limits (weekly token allocation)
• Process subscription payments and manage your billing
• Send you service-related communications
• Show our ads on Facebook and Instagram (see section 5)
• Respond to your inquiries and provide customer support
• Monitor and analyze usage patterns to improve our Service
• Detect, prevent, and address technical issues or abuse

5. AI Processing and Third-Party Services

Important:

When you use our AI writing tools, your content is processed by Anthropic's Claude AI. This means:

• Your prompts and content are sent to Anthropic's servers for processing
• Anthropic may use this data in accordance with their own privacy policy
• Your use of our Service is also subject to Anthropic's Usage Policy
• We recommend reviewing Anthropic's Privacy Policy and Anthropic's Usage Policy

Everything above is about Food Blog Studio's own AI writing tools. A Claude or ChatGPT you connect yourself works for you, not for us, so it isn't our service provider, even though Anthropic makes Claude (section 5A).

We also use the following third-party services:

• Firebase (Google): Authentication and database storage
• Stripe: Subscription billing and payment processing
• Vercel: Hosting and analytics
• Supabase: Database hosting for Analytics Dashboard data (United States)
• WorkOS: Issues the sign-in keys your Claude or ChatGPT uses to connect (United States). WorkOS gets your account ID, a stand-in email address made from it, which apps you've connected, and standard browser information like your IP address while you connect. It never gets your real email address, your password, your posts, your Google data, or your earnings
• Resend: Transactional email delivery (welcome and password-reset emails, and account notices such as an AI app being connected)
• Meta (Meta Pixel and ads): Advertising measurement on our marketing website and public checkout pages only. Meta receives the pages visited and actions such as a completed purchase (amount and currency), with standard browser and device information, and a scrambled (hashed) copy of an email address or name typed into a form on our marketing website, to match visits to Meta accounts. When you sign up through our checkout, our servers also send Meta the sign-up (a trial start or purchase, with its amount and currency) and, later, a trial becoming a paid subscription, with a scrambled (hashed) copy of your email address, name, postal code, country and billing customer ID, plus the IP address, browser and Meta Pixel cookies from your checkout. It never receives your writing, chats, blog content or Google data
• Meta (ad audiences): We send Meta scrambled (hashed) email addresses of our members, trial users and email subscribers so our Facebook and Instagram ads reach people like them and skip current members. Meta uses them only to find matching accounts, then deletes them. To opt out, see section 9.3
• Kit: Email newsletters and onboarding emails, including the emails we send during a free trial. Kit receives your email address, your first name and, during a trial, when it ends. You can unsubscribe from these emails at any time
• Zapier: Connects our tools. When you start a free trial, Zapier passes your email address, first name and trial dates from Stripe or Food Blog Studio to Kit
• Slack: Our team's messaging app. When you send feedback through Share Feedback, your name, the type you picked and your message are posted to a private team channel so we see it quickly. Your email address is not sent
• PromoteKit: Affiliate program management. If you subscribe using an affiliate's promo code, PromoteKit records it so the affiliate can be credited. It is connected to our Stripe account and can access customer and transaction records there to attribute and calculate commissions

5A. Connecting Your Own Claude or ChatGPT

You can connect your own Claude (including Claude Code) or ChatGPT to Food Blog Studio, then ask it about your blog. Nothing is connected unless you connect it yourself. AI connections come with plans that include Analytics.

Your app gets your data only when it asks. Food Blog Studio never sends your data to any AI app on its own. Once you connect an app, it can ask for your data while you chat with it. We give it only the answer to what it asked, only for your own blog, and only while it's connected.

How you connect. You add our connector in Claude or ChatGPT, click Connect, and sign in with your normal Food Blog Studio login. One screen lists what the app will be able to see and do. It's all or nothing: Connect gives it everything listed, and Cancel gives it nothing. We record when you agreed and what the screen listed. WorkOS (section 5) may then show a short screen of its own. Your app's sign-in key carries your account ID (a random code), never your real email address.

What it can see:

• Always: your imported posts and recipe cards (their text, their links, and your internal-linking list), your blog's name and address, which sources are connected and when they last synced, and your writing style (Voice & Tone Profile, Ideal Reader Profile, and writing samples)
• With Analytics: your Google Analytics and Search Console data, including the searches people use to find your posts, and what Food Blog Studio figures out from it, like Opportunities, Promotion, and your updates and their results
• With Analytics: your Raptive data (your earnings, RPM, and the pageviews and sessions Raptive counts), once Raptive is connected

If your plan stops including Analytics, the app loses access within about a minute, and gets it back if Analytics comes back. Connecting Google or Raptive later doesn't need a new connection. If we add a new kind of data, click Revoke access, then connect again to include it.

What it can never see. Your password, your billing or payment details, your email addresses, your Raptive key, your chats with our own writing tools, or other members' data, including posts they share in Community Backlinks.

What it can change. Only your Updates log, and only if you have Analytics. It can add an update to one of your posts, just like Log update on the Updates tab, and the update is marked “logged from Claude or ChatGPT”. We tell it to check with you first, but we can't see your chat, so set that tool to need your approval if you want to be sure. It can't edit or delete updates, or change your blog, Google, or Raptive accounts. Like Log update, adding an update clears a matching change from “We noticed changes” (within 7 days of the update), and deleting the update doesn't bring it back.

What we see and keep. We see only the requests your AI app sends us, like the name of a post it wants, never the rest of your chat. For each tool use we keep which tool, when, which app, and whether it worked, for about 90 days, but not what it asked for or got back. Our hosting provider also logs each request's IP address (section 2.2). That's usually Anthropic's or OpenAI's servers, or your own computer for Claude Code.

Your AI app works for you. The company behind it (Anthropic for Claude, OpenAI for ChatGPT) isn't our service provider for this. Your agreement with that company covers what it does with your data, including training, how long it keeps your chats, and whether its staff may review them. If you use a work account, your organization's agreement applies. Check your AI app's privacy settings before you connect.

Copies in your chats. Data your AI app reads stays in that chat. It can also end up in the app's memory or, for Claude Code, in files on your computer. Revoking access or deleting data in Food Blog Studio doesn't delete those copies. You can delete them in your AI app.

Your control. Depending on the app, you can block its Food Blog Studio tools in its own settings, or make it ask you first. Personalization > AI connections lists each app you've connected, when you connected it, and when it was last used. Click Revoke access to stop one right away. We email you each time an AI app is connected.

Access pauses within about a minute if your plan ends, a payment fails, your account is disabled, or we pause AI connections, and comes back once that's fixed. Logging out of every device or changing your password doesn't remove a connection. Use Revoke access for that. Disconnecting your blog stops new imports, but your app can still read the posts already imported until you click Delete my posts.

While an app is connected, anyone who can use that Claude or ChatGPT account can reach your Food Blog Studio data, so connect an account that's only yours.

6. Community Backlinks (Optional Sharing With Other Members)

Community Backlinks is an optional feature available only to Food Blog Coaching members. If you turn on sharing, the following information is visible to other participating members:

• Your first and last name
• Your blog's name and domain
• The titles and URLs of the posts you've ticked in your internal-linking list (information that is already public on your blog). Posts marked noindex are never shared.

We never share your email address, billing information, conversations, profiles, or usage data through this feature. The text and recipe cards of your imported posts are never shared through Community Backlinks or with any other member. Sharing is off by default. You can turn it on or off at any time from the Community Backlinks page, and your posts stop being shared as soon as you turn it off, delete your imported posts, or your account is deactivated. Only members who also share their own posts can browse shared posts.

7. Data Retention

We retain your personal information for as long as your account is active or as needed to provide you services. Specifically:

• Account Data: Retained until you delete your account
• Conversation History: Retained to provide context for ongoing conversations
• Usage Data: Token usage is tracked weekly and cumulatively
• Billing Records: Subscription and payment records are retained by us and Stripe as required for accounting and tax purposes
• Uploaded Files: Content you paste or upload for one-off analyses (such as CSV files) is processed to produce your results and is not retained afterward; however, writing samples and profiles you save in Personalization are stored in your account until you change or delete them
• Ad Network Earnings (Raptive): Kept for up to 24 months while Raptive is connected. Disconnecting keeps what was loaded. “Disconnect & delete earnings” deletes it
• AI Connections: We keep your connect-screen agreements and your list of connected apps (including revoked ones) until you delete your account, and each tool-use record for about 90 days. We also keep small usage counters (counts and dates only) to enforce limits. WorkOS keeps your account ID, stand-in email address, and connected apps until you delete your account. Revoke access removes that app at WorkOS too, and deleting your account deletes your WorkOS record and the counters
• Connected Blog Content: Stored in your account and kept up to date while your blog is connected. We check your blog for new, edited and deleted posts when you use the app (at most once a day) and whenever you choose Sync now. A post you delete from your blog is removed from your account once we confirm it's gone. Disconnecting your blog stops these updates and keeps what was already imported. Choosing Delete my posts in Personalization permanently deletes your imported posts, recipe cards and internal-linking list from your account. Text from a post you've already attached to a chat stays in that conversation until you delete the conversation

8. Data Security

We implement appropriate technical and organizational measures to protect your personal information, including encryption in transit (HTTPS), secure authentication through Firebase, and access controls. However, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.

9. Your Rights

9.1 All Users

You have the right to:

• Access the personal information we hold about you
• Correct inaccurate personal information
• Request deletion of your account and associated data
• Request a copy of your data in a portable format

To exercise any of these rights, contact us at the email address below and we will respond within a reasonable timeframe.

9.2 European Economic Area (EEA) and UK Residents

Under GDPR and UK GDPR, you have additional rights including:

• Right to restriction of processing
• Right to object to processing
• Right to data portability
• Right to withdraw consent at any time
• Right to lodge a complaint with a supervisory authority

Our legal basis for processing your data includes: consent, contract performance, and legitimate interests in providing and improving our services.

9.3 California Residents (CCPA)

California residents have the right to:

• Know what personal information is collected
• Know whether personal information is sold or disclosed
• Opt out of the sale or sharing of personal information. We do not sell your data for money. We share limited information with Meta for our ads (see section 5), which California law can treat as “sharing”; to opt out, email hello@foodblog.studio, or block cookies and trackers in your browser. If your browser sends a Global Privacy Control signal when you check out, we send Meta nothing about you
• Access your personal information
• Request deletion of your personal information
• Not be discriminated against for exercising your rights

Connecting an AI app isn't a sale or sharing. You direct us to give your data to your own app, and we receive nothing for it. You can stop it any time with Revoke access.

9.4 Canadian Residents (PIPEDA)

Canadian residents have rights under PIPEDA including access to your personal information, the ability to challenge its accuracy, and to withdraw consent (subject to legal restrictions).

10. International Data Transfers

Your information may be transferred to and processed in countries other than your own, including the United States, where our service providers are located. We ensure appropriate safeguards are in place for such transfers, including standard contractual clauses where required by law.

11. Children's Privacy

Our Service is not intended for children under 16 years of age. We do not knowingly collect personal information from children under 16. If you are a parent or guardian and believe your child has provided us with personal information, please contact us.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the “Last updated” date. You are advised to review this Privacy Policy periodically for any changes.

13. Contact Us

If you have any questions about this Privacy Policy or wish to exercise your rights, please contact us at:

Email: hello@foodblog.studio