Privacy

What we collect, and why.

We try to keep this short. Blog Hands writes blog posts for small businesses. To do that we need a small amount of information from you. Here is exactly what, and exactly why.

Last updated September 29, 2026.

What we collect

The URL you submit to the Topic Plan tool. We fetch the page, parse the visible text and metadata, and use it to draft a brand readout you can edit.
What you type into our free tools — the keyword you enter in the Blog Topic Research Tool, or the content you check in the Blog Grader. You don’t need an account to use them, and we don’t tie this to a person. Where that input goes is under “Who else touches it” below.
Your IP address, briefly — we check it to rate-limit and block abuse of our free public tools. It’s held only transiently and isn’t tied to your account.
Anonymized grade records — when you run the Blog Grader, we store the graded page’s host and path (never the query string), the inferred keyword, and the scores — with no name or account attached. It helps us calibrate the grader and build an aggregate picture of blog quality.
The brand readout you confirm — business description, audience, offerings, voice tone, any rules you add. This is what makes posts sound like you instead of a generic AI.
Your name + email when you claim the free post or sign in.
The posts we generate for you and the topic ideas you choose. They live in your dashboard.
A session cookie so you stay signed in.
Anonymous usage analytics — we use Google Analytics to count page views and understand which pages people find useful. It sets a first-party analytics cookie and collects your IP address (anonymized by Google). No third-party advertising pixels, and we never tie this to your name or account.

Who else touches it

A small set of vendors handle pieces of the work. Each one only sees the data that piece needs.

Anthropic — generates the brand readout, topic ideas, and post drafts. The brand details and topic input pass through their API.
Supabase — stores your account, brand data, and posts.
Vercel — hosts the site itself.
Unsplash — supplies the featured image. We send a short visual phrase to find a photo; no account data goes to them.
Stripe — processes subscription and agency payments. Your card details go straight to Stripe; we never see or store them.
Resend — delivers transactional email, like the post-ready notification, to your inbox.
Google, DuckDuckGo, and Wikipedia — when you use our free research tools, the keyword you enter is sent to these services to fetch search suggestions, public-interest data, and recent news. It’s the same as typing that term into their search box; no account data goes to them.
Google Analytics — aggregate, anonymized traffic measurement (page views, referrers). No account data or post content is sent to them.

We do not sell your data. We do not share it with anyone outside the vendors above.

Agencies and client data

Agency workspaces are invite-only. Agencies use Blog Hands to write posts for their own clients. This section covers the client material an agency brings in.

Who’s responsible for it. The agency decides what client material to add. By adding it, the agency confirms it has the right to share it with us. We process that material on the agency’s behalf, only to provide the service. A data processing agreement is available on request through our contact form.

What we do with it

The client’s website. When an agency adds a client, it gives us the site’s address. We read the home page’s visible text and details to draft a brand readout. If the page won’t load or has too little text, we look the business up with Anthropic’s web search instead.
Briefs. An agency can upload a brief as a .docx, .md or .txt file, or paste the text. We pull out the text and send it to Anthropic to draft the readout. We don’t keep the file. We keep the readout the agency saves.
Links to the client’s own pages. When Paige writes a post, she reads the client’s sitemap to find pages the post can link to. If there’s no sitemap, she reads the home page and blog index.
Research. Paige runs on Anthropic’s Claude. She searches the web and opens public pages to find sources for each post. We save those sources with the post.
What we store. The client’s name and website, the brand readout, author profiles the agency adds, topics, drafts, sources, Paige’s notes and score for each post, and a delivery record with the date each post was ordered, written, approved and delivered.

Who can see it. Every member of an agency workspace can see all of that workspace’s clients and posts. Blog Hands staff can open a workspace to give support and to check posts Paige flags for a person to review.

Client material goes only to the vendors listed above, and each gets only what its part of the work needs. Stripe handles agency payments; card details go straight to Stripe and we never see or store them.

Removing a client or a workspace. Send a request through our contact form from the address on the workspace account. We will remove that client’s data (or the whole workspace) within 14 days and confirm in writing.

How long we keep it

As long as your account exists, plus a brief window after closure so we can recover from operational issues. Sessions expire on a rolling basis. Logs that include URLs or generated content are kept for up to 90 days for support and abuse review.

Removing your data

Send a deletion request through our contact form using the address on your account. We will remove the account, brand data, and posts within 14 days and confirm in writing.

Changes

If we change this policy materially we will post the new version here and update the "last updated" date above. Continued use of the product after that constitutes acceptance.

Contact

Questions about anything on this page go through our contact form. We read every one.

What we collect

The URL you submit to the Topic Plan tool. We fetch the page, parse the visible text and metadata, and use it to draft a brand readout you can edit.

What you type into our free tools — the keyword you enter in the Blog Topic Research Tool, or the content you check in the Blog Grader. You don’t need an account to use them, and we don’t tie this to a person. Where that input goes is under “Who else touches it” below.

Your IP address, briefly — we check it to rate-limit and block abuse of our free public tools. It’s held only transiently and isn’t tied to your account.

Anonymized grade records — when you run the Blog Grader, we store the graded page’s host and path (never the query string), the inferred keyword, and the scores — with no name or account attached. It helps us calibrate the grader and build an aggregate picture of blog quality.

The brand readout you confirm — business description, audience, offerings, voice tone, any rules you add. This is what makes posts sound like you instead of a generic AI.

Your name + email when you claim the free post or sign in.

The posts we generate for you and the topic ideas you choose. They live in your dashboard.

A session cookie so you stay signed in.

Anonymous usage analytics — we use Google Analytics to count page views and understand which pages people find useful. It sets a first-party analytics cookie and collects your IP address (anonymized by Google). No third-party advertising pixels, and we never tie this to your name or account.

Who else touches it

A small set of vendors handle pieces of the work. Each one only sees the data that piece needs.

Anthropic — generates the brand readout, topic ideas, and post drafts. The brand details and topic input pass through their API.

Supabase — stores your account, brand data, and posts.

Vercel — hosts the site itself.

Unsplash — supplies the featured image. We send a short visual phrase to find a photo; no account data goes to them.

Stripe — processes subscription and agency payments. Your card details go straight to Stripe; we never see or store them.

Resend — delivers transactional email, like the post-ready notification, to your inbox.

Google, DuckDuckGo, and Wikipedia — when you use our free research tools, the keyword you enter is sent to these services to fetch search suggestions, public-interest data, and recent news. It’s the same as typing that term into their search box; no account data goes to them.

Google Analytics — aggregate, anonymized traffic measurement (page views, referrers). No account data or post content is sent to them.

We do not sell your data. We do not share it with anyone outside the vendors above.

Agencies and client data

Agency workspaces are invite-only. Agencies use Blog Hands to write posts for their own clients. This section covers the client material an agency brings in.

What we do with it

The client’s website. When an agency adds a client, it gives us the site’s address. We read the home page’s visible text and details to draft a brand readout. If the page won’t load or has too little text, we look the business up with Anthropic’s web search instead.

Briefs. An agency can upload a brief as a .docx, .md or .txt file, or paste the text. We pull out the text and send it to Anthropic to draft the readout. We don’t keep the file. We keep the readout the agency saves.

Links to the client’s own pages. When Paige writes a post, she reads the client’s sitemap to find pages the post can link to. If there’s no sitemap, she reads the home page and blog index.

Research. Paige runs on Anthropic’s Claude. She searches the web and opens public pages to find sources for each post. We save those sources with the post.

What we store. The client’s name and website, the brand readout, author profiles the agency adds, topics, drafts, sources, Paige’s notes and score for each post, and a delivery record with the date each post was ordered, written, approved and delivered.