PRIVACY

Privacy Policy

Last updated 11 October 2026

Goal2Crew is operated by David Beacall, trading as Goal2Crew.

39 Jessamine RoadRock FerryWirralCH42 5PR

Support and refunds: support.goal2crew@gmail.com. Do not send card numbers by email.

Two places data can live

Most of your work stays on the device. The account, if you create one, is the part Goal2Crew stores on its server. This version does not sync projects or audits to the account. Signing in on a new device does not bring those projects with it.

This policy describes the product as it works now. It is not a promise that a breach is impossible, or that every browser extension will leave local data alone.

Stored on this browser

These stay in local storage on that browser unless you clear them or the browser removes them:

  • goals and questionnaire answers
  • project names
  • crew structures and role instructions
  • pasted setups
  • audit contents and revised crew packs

Goal2Crew does not upload that text when you sign in, run an audit, or buy Pro. A bot report is separate. Connected reporting stays off until it is turned on for the account, and a report only exists if a code is then created.

Bot reports, if you turn them on

Creating a reporting code is optional, and only after connected reporting is turned on for the account. If you do, a bot can submit a report to Goal2Crew. The server then stores the bot name, the period, the report text, the time it arrived, and a short reading of the numbers and notes in that report, against your account. That copy is not only on your device. Only the signed-in account that created the code can read it. The bot cannot read reports back. The code cannot change your account, payment, goal, projects, or older audits.

A routine report can update the progress charts on the account without you pressing Accept. Those charts are labelled as bot-reported. They are not treated as proven facts. A report that does not look like an ordinary progress note stays in My Bot Reports until you add it, leave it out, or delete it. Leaving a report out removes it from the charts and keeps the original text until you delete it. Goal2Crew does not schedule your bots, does not share these reports publicly, and does not use them to train a model.

Opening a report as an audit copies it into a new review on that device. It does not replace older reviews, and Goal2Crew does not upload reviews that were already on the device. There is no self-serve button that deletes the whole account. To delete the account itself, email support.goal2crew@gmail.com. Reports are tied to the account, so removing that account removes them. This description matches the product as built. It is not a lawyer’s sign-off, and it is not legal advice.

Stored on the server

If you create an account, the server may store:

  • an account id
  • the name you type, if you type one
  • your email address
  • a password hash, if you use email and password — not the password itself
  • session information, which can include a session token, expiry, and the sign-in system’s IP address and browser type
  • whether Goal2Crew Pro is active, and whether that came from Stripe or from the owner
  • Stripe purchase identifiers, amount, currency, and status
  • if you start a Pro checkout: your account id, the time, the consent version, and the checkout session id for the immediate-supply confirmation

Google or X sign-in is handled through the existing sign-in broker. Goal2Crew stores the account record those providers return for sign-in. It does not receive your card.

Payments

Stripe processes the card payment for Goal2Crew Pro. Goal2Crew does not store your card number. Stripe’s own privacy terms apply to the payment details they hold. We keep the checkout and payment identifiers we need to know whether Pro was paid or refunded.

Cookies

A signed-in session uses a cookie so the server can recognise the account. It is an authentication cookie, not an advertising cookie. The private owner dashboard can set a separate cookie so that browser is left out of product counts. Ordinary use of the product does not set that owner cookie.

Product analytics

Goal2Crew counts product events on its own server, such as a visit, a crew being created, or an audit being completed. Events can include an anonymous id stored on the device, a session id, and a coarse bucket such as device size or crew size. They are not sold, and they are not used for advertising profiles.

The event list does not accept goal text, project names, pasted bot text, audit contents, email addresses, or card data. A completed purchase is counted from the payment record, not from text you typed into a project.

What we do not do

Goal2Crew does not sell personal information. It does not run third-party advertising trackers. It does not take a copy of your projects in order to train a model. It does not read a bot report unless you created a reporting code. A pasted audit is not sent to the server.

Your choices

You can delete local projects in the product, or clear this site’s data in the browser. That does not close a server account. You can sign out, which ends the session in this browser. To access, correct, or delete the account data held on the server, email support.goal2crew@gmail.com. Because projects are not on the server, deleting the account does not delete them from your device, and deleting them on the device does not require the server.

If Goal2Crew is used in the UK, you may have rights under UK data protection law to access personal data, ask for correction or deletion, and complain to the Information Commissioner’s Office. The operator’s name and postal address are on this page. No company number, VAT number, or ICO registration number is published, because none is held.