Privacy policy

Frogpost is run by Federico Cella, who is the data controller for the personal data described here. For anything in this policy, including requests to access or delete your data, write to cella.fed@gmail.com.

Postal address: Carrer del Poeta Cabanyes, 40, 08004 Barcelona, Spain.

Account data. Your email address, and if you sign in with Google, your name and profile picture. Created when you register and kept while your account exists.

Your projects. Each blog you connect is a project. For each one we keep the CMS connection (for Contentful: the space, environment and content type, and the access token Contentful issues when you authorize Frogpost, or the token you paste in), your website address, where your posts live, the description of your business you write, and the fields and values you tell Frogpost to fill.

What we read from your website. When you ask Frogpost to read your site, it visits your public pages (never your blog) and keeps a summary, the text of those pages split into sections, descriptions of the images on them, and your brand: logo, colors and heading font. This is what posts are written from.

What Frogpost writes for you. Your queue of topics, the posts written (title, text, SEO fields, the pages they were based on, and their cover image), and your conversations with the assistant on the home screen. Covers Frogpost draws are stored at unlisted public addresses, because your CMS fetches them from there when it copies them in.

Google Search Console data. Only if you connect it. See section 5.

Payment data. Handled entirely by Stripe. We receive a customer id, your subscription status and when it renews. We never see or store your card number.

Usage data. Pages viewed, features used and errors encountered, collected with PostHog, tied to your account once you sign in.

Support messages. Anything you send us by email.

To run the service: your account, your projects, reading your site, writing posts and publishing them to your CMS when you ask or on the schedule you set, and showing how your posts do on Google. Legal basis: performance of our contract with you.

To keep records tax law requires (invoices and transaction history). Legal basis: legal obligation.

To keep the service secure and working (preventing abuse, debugging). Legal basis: our legitimate interest in operating a service that works and is not abused.

To understand how the product is used, so we know what to fix and improve. Legal basis: our legitimate interest in improving the product. You can object at any time by writing to us.

Frogpost writes with AI, so the material a post is written from is sent to AI providers. We use Anthropic (Claude) to suggest topics, write and fact-check posts, describe the images on your site and read your brand, and to run the assistant. What it receives is what that task needs: your business description, passages and image descriptions from your site, your topics, your Search Console queries when suggesting topics (section 5), and your messages to the assistant.

We use OpenAI to turn the text of your posts and of your site's sections into embeddings, which is how Frogpost finds the passages relevant to a topic and the posts to link to.

Both process this data under their API terms, which do not allow them to use it to train their models.

You can connect a project to Google Search Console from its settings. Frogpost asks Google for read-only access (the webmasters.readonly permission) plus your Google account's email address, so you can see which account is connected. Frogpost can never change anything in Search Console.

What we read

• The list of Search Console properties your Google account can access, so you can pick the one for your blog.
• For the property you pick, the last 28 days of search data: the searches your site appeared for, the pages that appeared, and their impressions, clicks and average position.
• Whether Google has indexed each of your published posts, and Google's reason when it hasn't.

How we use it

• To suggest post topics built on searches your site already appears for but no page ranks well for, and to avoid topics an existing page already ranks for. For this, those searches with their impressions and positions are sent to Anthropic as part of the request that generates topic ideas.
• To show each post's impressions, clicks, position and index status in your Posts list.

That is the only use. We do not sell it, use it for advertising, use it to train AI models, or share it with anyone other than the processors in section 7 that are needed to provide these two features. No person at Frogpost looks at it unless you ask us to for support, or where needed for security or to comply with the law.

Storage and deletion

The access Google grants (a refresh token) and the numbers above are stored in our database in the EU, and the numbers are refreshed at most twice a day. Disconnecting Search Console in your project settings, or deleting the project, deletes the token and all stored Search Console data for that project and revokes our access at Google (unless another of your projects is still connected with the same Google account). Deleting your account deletes all of it. You can also remove Frogpost's access at any time from your Google Account, under Security, Your connections to third-party apps and services.

Frogpost'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.

We do not sell personal data. We share it with the processors below, each of which handles it on our instructions and for no other purpose.

Posts go to the CMS you connect (Contentful today), which you hold an account with under its own terms. We send it only what you ask Frogpost to publish or save there.

We may also disclose data where we are legally required to, or to establish or defend legal claims.

Several processors above are in the United States. Where personal data leaves the EEA or the UK, the transfer relies on the European Commission's Standard Contractual Clauses, the UK Addendum where applicable, or the provider's certification under the EU-US Data Privacy Framework.

Account data, projects and what Frogpost wrote: for as long as your account is open. Deleting a project removes its CMS connection, queue, schedule, what was read from your site and its Search Console connection. Posts already published stay in your CMS, which is yours, and in your post history until you delete your account. To delete your account and everything in it, email cella.fed@gmail.com.

Payment and invoice records: as long as tax law requires, which is normally several years after the transaction, regardless of whether your account is still open.

Analytics: in line with our PostHog retention settings, and deleted on request.

If you are in the EEA or the UK you have the right to access your data, to correct it, to have it deleted, to restrict or object to how we use it, and to receive it in a portable format. If you are in California or another US state with similar law, you have the right to know what we collect, to have it deleted and to correct it. We do not sell personal data.

To exercise any of these, email cella.fed@gmail.com. We will not charge you or treat you differently for asking.

You also have the right to complain to a data protection authority. Ours is the Agencia Española de Protección de Datos (AEPD) in Spain. You can also complain to the authority where you live: in the UK that is the Information Commissioner's Office, and every EU country has its own.

Frogpost is not intended for anyone under 16. We do not knowingly collect data from children. If you believe a child has given us data, email us and we will delete it.

We may update this policy. The date at the top always reflects the current version. If a change affects what we collect or why, we will tell you before it applies.

Questions about this policy or about your data: cella.fed@gmail.com. See also our Terms of service.