Privacy
Two kinds of data, two different owners
Your club's data (its settings and crest, its players' names and photographs, its scorecards and the posts it makes) belongs to the club. The club decides what goes in and what it is used for; we hold and process it for the club, under the data processing agreement the club accepts when it signs up. In data protection terms the club is the controller and we are its processor.
Your own account (your name, your email address, which clubs you belong to and when you signed in) is ours to look after, and this page is about it.
What we keep about you
- Your name and email address, and your role at each club.
- When you signed in, and a record of what you did that matters: saving or removing a club's keys, publishing a post, changing the weekly plan, adding or removing people. It is kept so a club can always answer "who did that".
There is no password to keep: you sign in with a link we email you, which works once, for fifteen minutes. We store only a scrambled form of it. Card and Direct Debit payments are taken by Stripe, and we never see a card number or bank details.
Photographs
Every photograph uploaded is re-saved from its pixels alone before it is kept, which removes the location a phone writes into a photo and anything else stored beside the picture. Photographs of scorebook pages are kept privately, as the club's record: they are never published, and only the club's own people can see them.
Club stats sites
A club can choose to publish a stats site of its own players' cricket figures that anybody can see, usually linked from the club's website. It is off until someone running the club switches it on, and the club chooses which of its sides are on it. It shows each player's name and their cricket figures, the club's results and the names of the clubs it played. Each match has its full scorecard, both sides, as a scorecard is printed, so the other club's players appear on it by an initial and a surname. It shows nothing else: no photographs and no contact details. Search engines are asked not to list it unless the club chooses otherwise.
If you play for a club and do not want to be on its stats site, ask the club. It can take you off straight away, and you are then on none of the site's tables, records or searches. Your matches still count in the club's own results. You can also write to pavilion@promptlymade.co.uk and we will pass your request to the club.
Who else handles it
- Railway runs the servers Pavilion lives on.
- Cloudflare R2 holds a post's images briefly so Instagram can fetch them.
- Resend sends the sign-in email.
- Anthropic reads the photographs of old scorebook pages that a club asks Pavilion to read, and sends back what is written on them. Anthropic does not train its models on what is sent to it this way.
- Meta receives a post when the club publishes it to its own Instagram account.
- The ECB's Play-Cricket is where fixtures and scorecards are read from, with the club's own key. Pavilion only ever reads from it.
We do not sell data, show adverts, or share it with anyone else.
Keys and passwords the club gives us
A club's Play-Cricket key and Instagram token are stored encrypted, are never shown again in full, and are used only for that club's own data.
How long
For as long as the club uses Pavilion. When a club closes its account, its people lose access at once, its keys are deleted at once, and the rest of its data is erased within 30 days. The record of who did what is kept as a security record for up to 12 months after that.
Your rights
You can see, correct or delete what we hold about you. Delete your own account from Settings, People, or write to pavilion@promptlymade.co.uk. If you are unhappy with how we have handled your data you can complain to the Information Commissioner's Office (ico.org.uk).