Legal
Privacy Policy
Last updated: September 30, 2026
1. Information we collect
We collect account information such as your name, email address, authentication details, and settings. When you connect Google Search Console, we store Google account connection details, authorized tokens, Search Console properties, and Search Console performance data such as queries, pages, countries, devices, clicks, impressions, CTR, average position, and daily metrics.
We also store generated opportunity records, AI action suggestions, subscription status, Stripe customer references, application logs, device or browser information, and product analytics data used to understand and improve the service.
When you connect an AI assistant such as Claude, we also store the assistant's app registration, the access and refresh tokens we issue to it, and a log of the tool calls it makes, as section 5 describes.
2. How we use information
We use your information to operate blogr.ai, authenticate users, sync Search Console data, show dashboards, rank opportunities, generate AI-assisted recommendations, process billing, prevent abuse, provide support, and improve product quality.
3. Google API data
blogr.ai uses Google API data only to provide and improve user-facing Search Console analytics, SEO opportunity scoring, and recommendation features. We do not sell Google API data, use it for advertising, or transfer it except as needed to provide the service, comply with law, protect users, or with your consent.
blogr.ai use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
If you connect an AI assistant, we send it Search Console performance data only when you ask it for that data, as a user-facing feature you turned on yourself. You can turn it off at any time by disconnecting the assistant.
4. AI and SEO data providers
blogr.ai uses AI models to profile your website, plan your topical map, propose titles, write and revise articles, create article images, and recommend SEO fixes. We send these providers only what each task needs:
- Anthropic (Claude) writes and analyzes your content and researches your topical map, which includes web searches about your topic and competitors.
- OpenAI creates article cover images and can also write and analyze content.
- If you add your own API key for OpenAI, Anthropic, MiniMax, or OpenRouter, your content requests go to that provider under your own account with them.
What we send them: your website's public pages and profile (description, audience, competitors, and your writing instructions), titles, target keywords, briefs, drafts, and search result data for your keywords. To generate SEO recommendations, we also send limited Search Console opportunity context: query and page information, the current title or meta description when available, performance metrics, and baseline recommendations.
For SEO data, we send keywords and domain names to DataForSEO and Serper to get search volume, keyword difficulty, and search results. When we cannot read a page of your website directly, we fetch that public page through Jina Reader.
We do not send payment card details, passwords, Google OAuth tokens, or your publishing connection credentials to any of these providers. Each one handles the data under its own terms.
5. AI assistant connectors
You can connect blogr.ai to an AI assistant such as Claude or ChatGPT through our MCP server. Nothing is shared with an assistant until you sign in to blogr.ai from it and choose Allow access.
What the assistant receives: the data you ask it for, from the websites you can open in blogr.ai and within your team role on each. That can include your websites, articles and their content, your topical map, Search Console performance data, SEO opportunities, and your plan and article allowance. It never receives your password, payment details, Google OAuth tokens, your publishing connection credentials, or your team's member list.
What the assistant can change: when you ask it to, and within your team role, it can approve, decline, add, reschedule, and edit articles in your content plan. It cannot publish or delete articles, or change billing, website settings, or team members.
What we store: the assistant's app registration (its name and the addresses it signs in from), the access and refresh tokens we issue to it, and a log of each tool call it makes: which tool ran, on which website, whether it worked, how long it took, and when. We do not receive or store your conversations with the assistant.
How we use it: to sign the assistant in, answer its requests, enforce rate limits, prevent abuse, and understand which features people use.
Once the assistant receives data from blogr.ai, the assistant's provider handles it under its own terms and privacy policy. For Claude, that is Anthropic's Privacy Policy; for ChatGPT and Codex, OpenAI's Privacy Policy. Each assistant's guide links its provider's policy.
6. Payments
Stripe processes payments, subscriptions, invoices, and related billing data. blogr.ai stores Stripe customer and subscription references, but does not store full payment card numbers.
7. Cookies and analytics
We may use cookies, session storage, logs, and privacy-conscious analytics to keep you signed in, protect the service, measure product usage, and understand which pages or features need improvement.
8. Sharing
We share information with service providers that help us run blogr.ai, such as hosting, database, AI, payment, email, security, analytics, and customer support providers. We may also disclose information when required by law, to protect rights and safety, or as part of a business transfer.
We share data with an AI assistant only when you connect it and ask it for that data, as section 5 describes.
9. Retention and deletion
We keep information for as long as needed to provide the service, meet legal or accounting obligations, resolve disputes, and protect the service. You can disconnect Google access or request deletion of your account data. Some information may remain in backups, logs, or billing records for a limited period where required or permitted by law.
AI assistant access tokens expire after 60 minutes and refresh tokens after 90 days. We delete the tool call log after 90 days.
10. Security
We use administrative, technical, and organizational safeguards designed to protect your data, including encrypted storage for sensitive connection tokens. No online service can guarantee perfect security.
11. Your choices
You may update your account information, disconnect connected Google accounts, disconnect AI assistants by removing the blogr.ai connector in the assistant, manage billing, or request access, correction, export, or deletion of personal information where applicable law gives you those rights.
12. Contact
Privacy questions or requests can be sent to hello@blogr.ai.