Privacy policy

The short version

We store the account and site details you give us so Crumbr can run: drafts, publishing, and signup attribution. We do not sell that data. We do not put a tracking cookie on the blogs we host.

This policy covers crumbr.co, the waitlist, the app, and the blogs we host for you. It is written for two groups of people: founders using Crumbr, and readers of those blogs. Email hello@crumbr.co if you want a copy of what we have, or want it deleted.

If you use Crumbr

We collect what we need to run your account:

• Name, email, password (stored hashed), timezone, and the workspace you last opened.
• If you continue with Google: the name, email, and account id Google shares for that login.
• The site URL you paste, pages we crawl from it, and the voice, topics, drafts, and posts in the workspace.
• Branding you upload, the hostname you connect, and DNS checks against that hostname.
• Billing details through Stripe: customer id, plan, invoices. We do not store a full card number.
• Notification preferences per workspace, and which onboarding screens you have already seen.
• API keys you create so your product can send us signup events.
• Search Console data, if you connect it: queries, impressions, clicks, and position for the property you pick.

Onboarding starts before you have an account. That session lives behind a signed cookie in your browser. We store a hash of the token, not the token itself, plus the URL you asked us to read.

Google user data

Crumbr uses Google APIs in two places, and each one is a separate consent. Granting one never grants the other, and you can withdraw either without touching the other.

Continue with Google signs you in. It asks for the openid, profile, and email scopes. From that grant we keep your name, your email address, and the Google account id, and we use them to create or match your Crumbr account and to address mail to you. Nothing else.

Search Console is optional, per workspace, and read only. It asks for https://www.googleapis.com/auth/webmasters.readonly, plus userinfo.email so we can show you which account is connected. With it we read the list of properties on your account, so you can pick one, and then for the single property you pick: search queries, impressions, clicks, click-through rate, and average position, by page and by date. We store those rows, the property URL, and the email of the Google account that granted access. We never write to Search Console.

That data does one job: it fills the search numbers in your dashboard, matches queries to the posts we published for you, tells you when a post earns its first clicks, and feeds the insights that shape your next draft. It is not used for anything else.

Writing those insights involves a model. What reaches the model is aggregate and per post: click-through rate, impressions, clicks, and average position, as figures about your own posts. We do not send it your search query text, the raw Search Console rows, or the email of the connected Google account. None of it identifies a reader, and none of it is used to train or improve any model.

Google OAuth access and refresh tokens are encrypted at rest, never returned by our API, and never shown back to you. Traffic to and from Google is over TLS. Only the workspace that connected the property can see what it pulled.

You can disconnect Search Console from workspace settings at any time. We ask Google to revoke the token and we delete the stored grant. The query rows already pulled stay, so months of history do not vanish because you unplugged a connection; email hello@crumbr.co if you want those deleted too, and we will. You can also revoke Crumbr from your Google account permissions. Deleting your Crumbr account deletes all of it.

Limited Use of Google user data

Crumbr's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In practice:

• We use Google user data only to provide and improve features you can see in Crumbr: signing in, and the search numbers in your dashboard.
• We do not use it for advertising of any kind, including serving, targeting, personalizing, or retargeting ads.
• We do not sell it, and we do not transfer it to data brokers, information resellers, or anyone assessing credit worthiness or lending.
• We do not use Google user data to develop, improve, or train generalized or non-personalized AI or machine learning models. Where a model helps write your insights, it receives aggregate performance figures for your own posts and nothing more, which is a feature of your workspace rather than model training.
• Nobody at Crumbr reads your Google user data unless you have agreed to it, it is needed to resolve a support request or a security incident, it has been aggregated and de-identified, or the law requires it.

If you join the waitlist

We ask for a name and an email, and nothing else. We keep that pair so we can invite you, and we send a confirmation and later an invite to that address. While the waitlist is on, those rows also live in Notion, which is how we mark an invite as ready.

If you read a blog we host

Those pages are public. They do not set a Crumbr session cookie. If your browser sends Do Not Track, the analytics script does not run.

When it does run, we store a daily salted hash of IP address and user agent, plus path, referrer, scroll, time on the post, and which links were clicked. From your browser's timezone we keep only the country it is in, never your location or IP address. The salt rotates every day, so the hash is not a lasting profile. We do not fingerprint devices.

A click-through token is added only to links that stay on the founder's own domain, so a signup there can be tied back to the post. We do not append that token to outbound links.

If the founder sends us a signup event, we may store a hashed identity long enough to attribute it. After that window we drop who it was and keep the count. Your dashboard never needs a name.

Cookies on crumbr.co

The app uses a session cookie so you stay signed in, and an optional remember-me cookie. Onboarding uses the signed cookie described above. Customer blogs do not get these.

We may use product analytics on crumbr.co (for example PostHog) to see which screens help founders finish setup. That is for the product, not for ads.

How we use this

We use the data to:

• Create the account, run the workspace, and send the mail you asked for.
• Write drafts, publish what you approve, and keep the blog on your domain.
• Measure posts, attribute signups, and produce insights for later drafts.
• Bill you, warn you when a trial is ending, and process cancellations.
• Keep the service secure and debug when it breaks.

Workspace-related mail (a draft is ready, a post went live, insights arrived) can be turned off per blog in workspace settings. Account mail such as a trial warning still sends. Every one of those emails includes a way to unsubscribe.

Who we share it with

We do not sell your data. We share it with companies that run a piece of Crumbr, and only for that piece:

• Stripe, for payment and plan management.
• Our email provider, for transactional mail.
• Model providers, for the text of drafts and insights. We send them the context a draft needs, not your password, not your readers' identities, and no raw Search Console rows or query text, only aggregate performance figures for your own posts.
• Keyword data providers, for topic research.
• Laravel Cloud, for hosting and custom hostnames.
• Google, if you sign in with Google or connect Search Console. What we take from Google stays with us on the terms set out above.
• Notion, for the waitlist.
• Our host and file storage, so the app and your branding assets stay up.

We may also share data if the law requires it, or if we have to protect Crumbr or another customer.

How long we keep it

Account, workspace, and published posts stay for as long as the account does. You can export posts at any time. Email hello@crumbr.co to delete the account. We will drop what we no longer need to keep a published blog reachable or to finish billing.

Waitlist rows stay until you ask us to remove them, or until they have served their purpose. Conversion identities are dropped after the attribution window. Daily visitor hashes have no life past that day.

Your choices

• Correct the name, email, and timezone from the account page.
• Disconnect Search Console, rotate or drop API keys, and change the blog hostname from workspace settings. You can revoke Crumbr's Google access from your Google account permissions as well.
• Turn off workspace notification mail, or unsubscribe from a single email.
• Export posts as Markdown. Ask us to delete the rest.

If you are in a place that grants access, correction, or deletion rights, email us and we will honour them. We may need to confirm it is your account.

Other notes

Crumbr is not directed at children under 18. Do not create an account for one.

We process data in the United States and wherever our providers run. Using Crumbr means you are comfortable with that.

The Terms of use cover the product itself. We will change this policy when the product changes. The date at the top is the current version. If we change what we do with Google user data, we will update this page and email the address on your account before the change takes effect.

Questions: hello@crumbr.co.