Privacy policy

The short version

• We collect what we need to run your account and write your articles: your email, the answers you give us, your app's public pages and the content you review.
• Blogs we host for you count visits and App Store clicks without cookies and without storing readers' IP addresses.
• We use AI models to research and draft articles. We tell the providers not to train on what we send them.
• We don't sell your data, and we don't use advertising or analytics cookies.
• You can ask for a copy of your data, or for it to be corrected or deleted, at hello@ollieseo.com.

Who we are

Ollie is run by Bradley Vangelder, a sole trader in Belgium (VAT BE1027064506) ("Ollie", "we", "us"). We are the data controller for the personal data of people who use Ollie: founders and the teammates they invite.

For the blogs and tracking we run on a founder's behalf, the founder decides what they are for, and we process readers' data for them. Questions about a particular blog are best sent to the company that runs it; we will help them answer.

What we collect

When you use Ollie

• Account details: your email address, and if you give them, your name, role, time zone and how you heard about Ollie.
• Your app and business: app and website links, the public pages we read from them (your App Store listing and landing page), and what you tell us during setup: your audience, goals, product description, writing style, byline, claims you want to avoid and competitors.
• Your content: article ideas, drafts, the edits and comments you make while reviewing, and photos you upload. For free photos we keep the creator, licence and source so credit stays correct.
• Connections you choose to add: a read-only Google Search Console connection, an App Store Connect API key for download reports, and RevenueCat, Superwall or Stripe webhook secrets. These are stored encrypted. From them we keep totals only: search clicks and impressions per page and query, daily downloads per campaign, and subscription events without any customer identifier. For blogs on a free ollieseo.com address, we read the same search numbers from Ollie's own Search Console account.
• Billing: if you subscribe, Stripe handles your card. We keep your Stripe customer ID, plan, billing interval and subscription status. We never see or store card numbers.
• Activity: a record of changes made in your account (who changed what, and when), so your team can see its history.
• Technical data: like any website, our hosting provider receives your IP address, browser and the pages you request. These appear in short-lived server logs used to keep the service running and secure.
• Teammates: if you invite someone, we store their email and role so they can join.
• Waitlist: if you joined the waitlist before sign-up opened, we keep the email address you gave us until you ask us to delete it.

When you read a blog Ollie hosts

When a page loads, the blog sends one anonymous event: the page, the time, a random ID for that event, and whether you arrived directly or from a search engine, social network or another site. We don't record the full referring address. A click on the App Store button is counted the same way before you are sent on to Apple. We set no cookies and use no browser storage on these blogs, and we don't store your IP address or browser details with these counts.

Blogs, the Ollie app and this website serve their fonts themselves, so no font service receives your IP address.

On a founder's own website or app

Founders can add Ollie's small script to their website to see which blog readers go on to sign up. It records the page path (without query strings), whether the visit came from their blog, and a sign-up event. It keeps a random reference in your browser's local storage for 30 days so a later sign-up can be linked to a blog visit, and a short-lived flag in session storage so a sign-up is counted once. It doesn't read cookies, names, emails or form fields. Ollie keeps the first and last visit times and the last five events.

Founders who use Ollie's app SDK send events tagged with a random install ID, which we hash before storing. These raw events are deleted after 30 days.

How we use it, and why we're allowed to

We don't send marketing emails, we don't make decisions about you that have legal or similar effects by automated means, and we don't sell or rent personal data.

AI models

To find topics and draft articles, we send AI models the material an article is built from: your product profile, writing style, competitors, the public pages and sources we researched, the draft, and the changes you ask for. Requests go through Vercel's AI Gateway to Anthropic (Claude) and Google (Gemini). Each request tells the provider not to use it for training. Don't put anything in a profile or a request that you wouldn't want processed this way.

Who helps us run Ollie

These providers process data for us under contract, only to provide their service:

When you publish, we tell search engines (through IndexNow and Google) that the public article exists. We may also disclose data if the law requires it, or to a buyer if Ollie is ever sold, under this same policy.

Data outside Europe

Some providers above are in the United States. Where data leaves the EU or the UK, we rely on an adequacy decision (such as the EU-US Data Privacy Framework for certified companies, or the EU's decision for the UK) or on the European Commission's standard contractual clauses.

How long we keep it

• Your account and content: while your account is open. When you ask us to delete it, we delete it within 30 days, except what we must keep by law.
• Billing records: as long as tax and accounting law requires.
• Public pages we read for research: 90 days, or for as long as an article or your product profile still cites them.
• Data exports you request: 7 days, then deleted.
• Raw app SDK events: 30 days.
• Blog visit and click counts: while the project exists; they contain no information about who the reader is.
• Server logs: a few days, as our hosting provider rotates them.

Cookies

Ollie uses only cookies it needs to work, so we don't ask for consent. There are no analytics or advertising cookies. This website (ollieseo.com) and the blogs we host set none.

The app also keeps your theme and recently opened articles in your browser's local storage. They never leave your device.

Your rights

Wherever you live, you can ask us to:

• give you a copy of your personal data, or send it to another service;
• correct data that is wrong;
• delete your data;
• restrict or object to how we use it, including uses based on our legitimate interests.

Email hello@ollieseo.com from the address on your account. We answer within one month. You can also download your articles, ideas and settings any time under Settings, Data. If you think we've handled your data wrongly, you can complain to the data protection authority where you live or work; in Belgium that is the Data Protection Authority. We'd appreciate the chance to fix it first.

Security

All traffic is encrypted in transit. Connection secrets such as API keys and Google tokens are encrypted again before they are stored. Sign-in uses one-time email links, so there is no password to steal, and sensitive actions ask you to confirm it's you. Access to production data is limited to the people who run Ollie. No system is perfectly secure; if a breach affects you, we will tell you and the authorities as the law requires.

Children

Ollie is a tool for businesses and isn't meant for anyone under 18. We don't knowingly collect children's data; if you think we have, email us and we'll delete it.

Changes

If we change this policy in a way that matters, we'll email account owners at least 30 days before it takes effect and update the date at the top.

Contact

Bradley Vangelder (Ollie), Belgium
VAT BE1027064506
hello@ollieseo.com