The Grass Bank™
where every number has a heartbeat
A Journal of Cricket

Privacy Policy

Effective — 5 November 2026

The short version

We are an independent publication, not an advertising business. We do not sell your data, we do not share it with advertisers, and there are no third-party tracking or advertising cookies on this site.

We do measure how the site is read, and we do it ourselves rather than handing it to an outside analytics company. We measure pages, not people. We can tell how many times an article was opened and how long readers stayed on it. We cannot tell which articles any particular account opened, because we do not keep that record.

We use it to decide what to write next, not to change what you see. Nothing on this site is personalised: no recommendations, no re-ordered front page, no pricing that depends on your reading.

Two things about how you use the site are tied to your account: a record of each time you sign in, and your Yorker scores.

We work out which country you are in, from your IP address, for two narrow purposes: to show you the right price, and because paid subscriptions are only offered in some countries. We do not keep a history of where you have been.

If you would rather we did not hold any of it, write to contact@thegrassbank.com and we will delete your account and its records.

This policy explains what The Grass Bank™ collects, why, how long it is kept, and who can see it. The Grass Bank™ is operated by Dreamers LLC, a Washington State limited liability company, at thegrassbank.com. Dreamers LLC is the controller of the personal data described here. It sits alongside our Terms of Service.

1. What we collect

1.1 Account information

Much of the site can be read without an account. If you create one, we collect your email address, a password (which is hashed by Google Firebase Authentication — we never see or store the password itself), a display name to appear beside your comments (one is drawn for you at random when you sign up, so that your email address is never shown; you can draw a different one), and the access level your account holds. We also record when your account was created and when it last signed in.

1.2 Subscription information

If you subscribe, payment is handled by Stripe through its Managed Payments service, under which Stripe acts as merchant of record for the transaction rather than simply processing a payment on our behalf. Stripe provides that service through a Stripe company called Sold through Link, LLC, and the name you will actually see is Link — they are the same organisation. We never receive or store your card number.

Because of that arrangement, Link — not The Grass Bank™ — holds the payment relationship with you. Link collects and holds your payment details and billing address, sends your receipt and invoice, handles refunds and disputes, and gives you an account at link.com where you can see your order history, update your card, and cancel. Those emails come from Link and we cannot change or suppress them. Stripe and Link process this data under Stripe’s own privacy policy.

What we hold is narrower: the status of your subscription — whether it is active, cancelled, or lapsed — the identifiers Stripe gives us so the two systems can refer to the same subscription, and the country in which the card used was issued (see section 1.8).

Alongside Link’s emails we send our own, because Link’s receipt does not explain how your subscription works: a confirmation when you subscribe (what you paid, when it renews and for how much, how to cancel, and the refund terms), a confirmation when you switch from monthly to annual or cancel, and renewal reminders: on the annual plan 45 days and again 30 days before each renewal, and on the monthly plan once a year. If you ask to reset your password, that email comes from us too. These are sent through Resend, an email delivery service, which receives your email address and the contents of those messages in order to deliver them, and processes them under its own privacy policy. Resend is based in the United States. These emails are not tracked — we do not record whether you open them or click their links. They are part of the subscription itself, so there is no separate opt-out; they stop when your subscription ends. We keep a note of which of these emails we have sent you, so that none is sent twice, and it is deleted with your account.

When you subscribe or switch to annual we also keep a record that you agreed to the automatic-renewal terms: which version of the wording you saw, and when. That record shows the renewal was something you agreed to. It is kept with your subscription records and, if you close your account, in the closure record described in section 3, because the law requires us to keep it for at least three years.

We also keep your cap number (or honorary number), the date of your first paid season, and a count of the seasons you have paid for. Your price each year, and whether you have become a Life Member, depend on that count (see section 5.5 of our Terms). It is a record of payments, not of reading: it says nothing about what you read or how often. We keep it after you stop renewing, so that if you come back you carry on where you stopped, and we delete it when you close your account.

Complimentary access. If we give you complimentary access, we keep whether it is for life or until a date, that end date, your honorary number if you have one, and a short internal note of why it was given. About a week before a time-limited grant ends we send you one email to say so. These records are seen only by us. The end date is removed when the grant ends; the note and any honorary number stay with your account while it is open, and all of it is deleted when you close your account.

One consequence you should know about. If you ask Link to delete your data, Stripe will cancel any subscription bought through Managed Payments and delete the associated records from our Stripe account as well as its own. That happens on Link’s side and we cannot prevent or reverse it. It does not delete your Grass Bank™ account, your comments, or anything else described in this policy — for that, write to us as described in section 6.

1.3 The newsletter

The newsletter is separate from your account, and subscribing to it is entirely voluntary. A signup box appears in more than one place — beneath articles, on the subscribe page, at the end of a Yorker quiz, on the coming-soon page, and as an unticked box when you create an account — but they are all the same list, used for the same single purpose: sending you summaries of what has been published on The Grass Bank™. Where you signed up makes no difference to what you receive, and we do not maintain a second list for any other use. We do record which box an address came from, so that we know which parts of the site people sign up from.

If you sign up we collect your email address and, if you give it, your first name, which is optional and used only to address the emails. Submitting the form is not enough on its own. We send a confirmation email, and you are added to the list only when you click the link in it; if you never click it, nothing is ever sent to you. That click is also the record that you asked for the emails — it is timestamped, as is the moment the address joins the list.

Newsletter subscriptions are stored and sent by MailerLite, our email service provider, under its own privacy policy. MailerLite is based in the European Union. MailerLite records whether you open a newsletter email and whether you click a link inside it, which is how it reports whether an issue was read. That is measurement of the email, in your mail client, and is separate from the site itself — no third-party code runs on the pages where you read (see section 5). Signing up to the newsletter does not create a Grass Bank™ account; if you also hold an account, the email address on it is held separately by us as account data, as described in section 1.1.

You can unsubscribe at any time using the link at the foot of any newsletter email, or by writing to contact@thegrassbank.com. We action unsubscribe and deletion requests promptly, and unsubscribing from the newsletter does not affect your account or subscription.

1.4 How the site is read (aggregate measurement)

We measure how the site is used, so that we can tell which writing is worth continuing and which parts of the site nobody opens. This measurement is built by us and runs on our own Firebase infrastructure. It is not Google Analytics, and no analytics vendor, advertising network, or data broker receives any of it.

It is not tied to you. The measurement counts pages and visits, not readers. A page view adds one to that page's total; a visit adds its length to a running figure for the day. What survives is a set of totals — how many times each page was opened, how long readers stayed, how much of that time was active rather than idle. We do not keep, and cannot reconstruct, a list of which pages any particular account opened. We collect:

What Detail
Page path The path of the page opened — for example /yorker.html. Anything after the ? in a web address is never recorded.
Time and duration How long a visit lasted, and how much of that time was active reading rather than idle time with the page left open. Time is counted in short intervals and only while the page is visible and has been interacted with recently.
A temporary visit identifier So that several page views in one sitting are counted as one visit, the browser generates a random identifier for the visit. It is not your account identifier and is not connected to it. It resets after thirty minutes without activity, and at midnight. The record of each visit is deleted automatically within about two days; only the totals remain.

We do not follow you across other websites, we do not buy or receive data about you from anyone else, and we do not build an advertising profile. None of this is used to personalise the site — there is no recommendation engine, no ranking that moves with your history, no article ordering or pricing that varies by account. The measurement feeds editorial decisions we make afterwards: which subjects to keep writing about, which parts of the site nobody opens. If that changes, section 8 applies — we would say so on this page before it started.

1.5 Sign-in records

Separately from the measurement above, we keep a record of each time an account signs in: the email address, a timestamp set by our server, and the page you were on when you signed in. We use these records for security and for helping readers who have trouble signing in. They record that you arrived, not what you went on to read. They are kept while your account is open and are deleted when it is closed; you can also ask us to delete them sooner.

1.6 Comments, reactions, and submissions

If you post a comment we store its text, your display name, your account identifier, and the time it was posted.

Reactions are counted, but not attributed. You need to be signed in to react — that is what keeps the counts honest — but we do not record which account reacted to what. What we store is the total on each comment and nothing else, so there is no record here, and none we could produce, of what any particular reader reacted to. Your own browser remembers your reactions locally so that a button you have already pressed still looks pressed to you; that record sits on your device, is described in section 5, and is not sent to us.

Behind the Scenes. Replies there are stored like comments and can be read by paid subscribers. Private conversations there are stored with their messages, the people in them, and the time of each message. Only the people in a conversation can read it, and the moderator is in every conversation. Conversations show display names, but we can link them to your account. They are encrypted while they travel and while they are stored, but they are not end-to-end encrypted: we can read them, and we may disclose them where the law requires (section 4).

Yorker. Playing the Yorker quiz needs a free account. When you finish an edition we store your score and your answers against your account identifier, one score per account per edition, so that you can see your result and each account plays each edition once. They are deleted when you close your account.

Submissions. If you submit a quiz question or other material, we store what you submit, the name you give, and your account’s email address, so that we can reply. Submitting requires an account, and the submission is held against your account identifier. We do not accept file uploads through the submissions page.

1.7 Technical records

The pages of the site are served by GitHub Pages (GitHub, Inc.), and our servers, sign-in, and database run on Google Firebase and Google Cloud. Pages also load Firebase’s code from Google’s servers and some code libraries from cdnjs (Cloudflare), which means your browser’s request, including your IP address, reaches those services. Our fonts are served from our own site, not from Google Fonts. Google keeps operational logs — including IP addresses, request times, and browser and device information — as an ordinary part of serving and securing a website. Google handles this under its Firebase privacy documentation. GitHub and cdnjs keep their own logs under their own policies. We use the logs we can see for security, abuse prevention, and debugging. We do not use them to identify readers, with two exceptions: our own record of which account requested the statistics data, and when, and a count of how many simulations each account runs. We use both to detect and stop copying of the data and the models (Terms section 9.1). The simulation count also sets the run limit: once an account reaches it, further runs are refused until it resets. Apart from that, these records only alert us; any action on an account is decided by a person, not automatically.

The security check on the statistics pages. Before the statistics pages load their data, Cloudflare Turnstile checks that the request comes from a real browser rather than a script copying the data. To do that it looks at technical information about your browser and connection, such as your IP address and browser type. It runs only on those pages, it usually shows you nothing (now and then a box to tick), and we receive only a pass or fail. We treat it as strictly necessary: it protects the paid service you have asked to use, it is not used to identify, profile or target you, and without it a script could copy the data those pages serve. Cloudflare handles this under its Turnstile privacy addendum and privacy policy. Section 1.8 describes the one place where we do derive your country from an IP address.

1.8 Where you are, and why we need to know

Two things about this site depend on which country you are in: the price and currency we show you, and whether a paid subscription is available to you at all — we can only sell subscriptions in the countries listed in our Service Area, because those are the countries where our payment provider handles local sales tax on our behalf.

To do that, we derive a country from the IP address of the request when you visit the subscribe page. It has to work this way round: the price must be on the screen before you type a card number, so we cannot take the country from your card. We work out the country only — not a city, a region, or a location on a map — and we do not store a history of it or attach it to your reading. The country we have detected is shown to you on the subscribe page. If it is wrong, tell us and we will put it right — the page explains how.

Separately, when a subscription is purchased, we record the country in which the payment card was issued, which Stripe passes to us. We compare it with the country we showed the price for. This is how we check that subscriptions are not bought from countries we cannot sell into, and that regional pricing is not obtained by misrepresenting location — both of which our Terms of Service prohibit. Where we find a mismatch we may cancel the subscription and refund the unused portion. We do not use this for anything else, and it tells us the issuing country of a card, not where you were standing.

These records are kept for 24 months and then deleted, together with a note of what we decided in any case we acted on.

1.9 If you write to us

Email sent to a thegrassbank.com address is received through Cloudflare, which forwards it to a mailbox we keep with Google (Gmail). Our replies are sent through Resend. Each handles your message and email address under its own policy. We keep correspondence for as long as it is useful for answering you and running the site, and you can ask us to delete it.

2. Why we collect it, and on what basis

Purpose Basis (UK/EU GDPR)
Running your account and giving you the access you hold Performance of our contract with you
Taking payment and managing subscriptions Performance of our contract; legal obligation for tax and accounting records
Understanding, in aggregate, how the site is read, so we can decide what to publish Our legitimate interest in running and improving an independent publication
Keeping the site secure, and enforcing our Terms Our legitimate interest in protecting the site and our work
Working out which country you are in, to show the right price and to check whether we may sell to you Performance of our contract; legal obligation in respect of sales tax; and our legitimate interest in enforcing our Terms
Sending emails you asked for Your consent, which you can withdraw at any time

Where we rely on legitimate interests, you have the right to object on the basis of your particular situation. The measurement described in section 1.4 is not tied to your account, so there is no record of your reading to stop or delete. What is tied to you is the sign-in record in section 1.5, and you can ask us to delete the records we hold for you.

3. How long we keep it

4. Who can see it

Internally: only the site's administrators. The measurement collections are written by our servers rather than by your browser, and the security rules that govern them permit reading only by an administrator account. The aggregate figures contain nothing that identifies a reader. Private conversations on Behind the Scenes are different: only the people in a conversation, including the moderator, can read it; other administrators cannot.

Externally: we do not sell personal information, and we do not share it for advertising. The only third parties that handle your data are the service providers we need in order to operate — GitHub (serving the site’s pages), Google Firebase and Google Cloud (our servers, sign-in, and database), Google also for the mailbox that receives your emails (section 1.9), Cloudflare (forwarding email to us, some code libraries, and the security check on the statistics pages in section 1.7), Stripe, including its Managed Payments entity Sold through Link, LLC (subscription payments, as merchant of record — see section 1.2), Resend (delivery of our subscription and account emails, and our replies — see sections 1.2 and 1.9), and MailerLite (the newsletter) — and each only to the extent needed to provide that service. We may also disclose information where we are legally required to, or where it is necessary to establish or defend a legal claim.

The Grass Bank™ is operated from the United States and the data described here is processed there. If you are in the UK or EU, that is a transfer outside your jurisdiction; our providers operate under standard contractual clauses and their own transfer frameworks.

5. Cookies and local storage

There are no advertising cookies on this site, no third-party tracking cookies, and no cookie banner — because there is nothing we would need to ask your consent for. No page on this site loads a third-party tracking or advertising script. The one outside script that runs is Cloudflare Turnstile on the statistics pages, which is a security check, not tracking (section 1.7). What we use ourselves is strictly functional: a token that keeps you signed in, and a small amount of browser storage that remembers things like whether you have already reacted to a comment, whether you have played this month’s Yorker, the temporary visit identifier in section 1.4, and whether this visit has already been counted as a sign-in. Clearing your browser storage signs you out; it does not delete anything we hold.

6. Your rights

You can ask us to:

Write to contact@thegrassbank.com. We will action requests promptly and will not charge you or make you give a reason. Depending on where you live you may also have a right to complain to a data-protection authority — in the UK, the Information Commissioner's Office — and we would rather you came to us first, but that is your right either way.

We will confirm any request with the account holder before acting on it, using the email address on the account. Because closing an account cannot be undone, we will ask you to confirm that specifically before we delete anything. Closing your account ends any access it holds, so cancel an active subscription first if you want to use out the time you have paid for.

There is a second route we do not control. Because Stripe is the merchant of record for subscriptions (section 1.2), you can also ask Link directly to delete your data. If you do, Stripe will cancel the subscription and remove the payment records from its systems and from our Stripe account. That is Link’s process, not ours, and we cannot reverse it — and it will not delete your Grass Bank™ account, your comments, or your sign-in records, which are separate and which only we can remove. If you want everything gone, write to us as well.

We do not discriminate against anyone for exercising these rights: your subscription, price, and access stay exactly the same.

7. Children

The Grass Bank™ is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has given us personal data, contact us and we will delete it.

8. Changes to this policy

We may update this policy. The version on this page is the one in force, and the effective date at the top changes when it does.

Where a change materially affects how we collect, use, or share your personal information, we will publish notice of it prominently on the Site at least 30 days before it takes effect, so that you have time to decide what you want to do before it does. Corrections and clarifications that do not affect how we handle your data take effect when posted.

This policy describes what The Grass Bank™ does today. We currently run no advertising and no third-party analytics service. If that changes — if we introduce advertising on the freely available pages, or bring in an outside analytics provider — we will update this page and say so before it starts, and we will put in place whatever consent mechanism the law where you live requires. We will not quietly begin doing something this page says we do not do.

9. Contact

Questions about this policy, or any request under section 6:

Email: contact@thegrassbank.com

Post: Dreamers LLC, 522 W Riverside Ave #10867, Spokane, WA 99201, USA

Operated by: Dreamers LLC, Washington State, USA