Privacy policy

GeoBrief Weekly is the data controller for the information described here. You can reach us about anything on this page at geobriefweekly@gmail.com.

Account details

Your email address, the display name and optional school name you give us, and the exam boards, teaching levels and topics you choose to follow.

Why: To sign you in and show you the briefs relevant to what you teach.

Subscription records

Which plan you are on, its status and renewal date, and the customer and subscription references Stripe gives us. We never see or store your card details.

Why: To give you the access you have paid for, and to handle renewals and cancellations.

Saved briefs and downloads

The briefs you save, and a record of the packs you download.

Why: To restore your saved briefs across devices, and to plan which specification areas need more coverage.

Department seats

If you run a department plan, the email addresses you invite and whether each invitation has been accepted.

Why: To give your colleagues access under your plan.

Your edits

On plans that allow it, the changes you make to a brief — your own summary, notes, questions and links.

Why: So your version is there next time you open the brief. These are private to your account.

We do not collect information about students, and accounts are intended for school and college staff only.

• Contract. Account, subscription and access data — we cannot provide the service you have paid for without it.
• Legitimate interests. Aggregate usage data used to decide what to publish next, and to keep the service secure.
• Consent. The weekly newsletter. You can withdraw it at any time from your account or the unsubscribe link in any email.
• Legal obligation. Records we have to keep for tax and accounting.

We keep the list of processors short:

• Stripe takes payments. Your card details go to Stripe directly and are never held by us. Stripe tells us only which plan is active and when it renews.
• Supabase hosts the database and handles sign-in.

We do not sell your data, and we do not share it with advertisers. Some processors operate outside the UK; where they do, transfers rely on the safeguards those providers offer, such as the UK addendum to the standard contractual clauses.

If your access comes through a department plan, the plan owner can see that your seat exists and whether you have accepted the invitation. They cannot see your saved briefs, your downloads or your private edits.

If you invite colleagues to a plan, you are asking us to email an address you have provided. Please make sure they are content to hear from us.

Data is held in an access-controlled database. Row-level security means each account can read only its own saved briefs, subscription and download history. Editorial staff can see aggregate usage, not individual browsing behaviour.

• Account data: while your account is open, and deleted when you close it.
• Saved briefs, downloads and your private edits: deleted with the account they belong to.
• Records of payments: kept for as long as tax and accounting rules require, normally six years, even after an account is closed.

You can ask for a copy of your data, ask us to correct it, ask us to delete it, object to how we are using it, or ask for it in a portable form. Write to geobriefweekly@gmail.com and we will respond within one month. Deletion removes your profile, saved briefs, private edits and download history.

If you are unhappy with how we have handled your information you can complain to the Information Commissioner’s Office at ico.org.uk. We would appreciate the chance to put it right first.

We use only the cookies required to keep you signed in and to complete a payment. We do not run advertising trackers, and we do not build a profile of what you read. Because these cookies are strictly necessary for a service you have asked for, we do not show a consent banner.

If we change how we use your information we will update this page and change the date at the top, and we will let account holders know about anything material. How we handle other people’s material is covered separately in our copyright and source policy.