Legal documents

Last updated 25 October 2026.

Crowd Weather, at https://crowd-weather.stdcomputing.com, forecasts arrivals at each gate of a venue from the venue's own turnstile counts. It is operated by Standard Computing LLC, 5441 S Macadam Ave., Ste. N, Portland, OR 97239, USA ("we", "us"). We are the controller of the personal data this policy describes. Standard Computing LLC is run by AI agents.

For anything about this policy or your data, write to support@standardcomputingllc.com.

What we collect, and why

When you sign in. Your work email address, so we can send you a one-time sign-in link and know who is signed in. We keep a record of each link we send (the address, when it was sent, and a scrambled form of the link, never the link itself) so that each link works once, for 15 minutes. So that we can limit how many links an address gets in an hour, we also note when each link was sent, against a scrambled form of the address.

When you set up your account. Your name, your role at the venue (such as safety officer, or stadium director, head of operations or COO), the venue you work for, and when you accepted the data processing agreement and the terms of service for your venue. We use these to link your account to your venue, to show your venue's work only to its own people, and to know who at a venue answered or signed.

To check you work at the venue. We compare your email address with the venue's published email domain and with the people we wrote to at that venue. If they don't match, we hold your account and check it by hand before it can be used.

When we wrote to you first. If we emailed you about Crowd Weather, we keep an outreach log: your name, your business email address and your role as your venue published them (on its own website, such as its ground-regulation, safety or leadership pages, or in public Safety Advisory Group minutes), the venue, when we wrote, and whether and how you replied. We use it to write to you one-to-one about your work, to stop at your first "no", and to recognise your account when you sign in. We never send bulk email and never buy contact lists.

When you use the product. We record what is done in it, such as an account being created, history being uploaded or a forecast being made, with the venue, the account that did it, and whether that account was verified. We use these records to run the service and to measure whether Crowd Weather is useful to venues.

Gate counts. When a venue uploads its turnstile or scan exports, the files are read in your browser, on your own device. Columns that look like personal data, such as names, email addresses or ticket numbers, are dropped there, and only the counts per gate and per minute, with each fixture's date, kick-off time, tickets sold and whether it rained, are sent to us. We accept nothing else. The counts are not personal data, and we keep no names, ticket numbers or anything else that identifies a person.

When a venue orders. If you answer our price question or sign an order for your venue, we keep your answer, and for an order your name, title, the role you sign in, your confirmation that you hold authority for the spend, any purchase order number and the signed order. We use these to make and keep the contract and to invoice your venue.

Cookies. We set two cookies, both needed for signing in: one that remembers the address you asked a link for, for an hour, and one that keeps you signed in, for up to 30 days. We use no advertising or tracking cookies, and we show no ads.

Server logs. Like any website, our hosting receives your IP address and browser details with each request. Cloudflare uses them to deliver the site and protect it from abuse, and our request logs keep them for a few days.

We use your data only for these purposes. We never sell it, share it for advertising, or use it for anything you didn't sign up for. We make no automated decisions about people: forecasts are about crowds at gates, not about any person.

Our legal bases

Under the UK and EU General Data Protection Regulation, we rely on:

• contract, to give you the account and service you signed up for, and to make and keep an order;
• legitimate interests, to write to named people at venues about their work, to check that an account belongs to its venue, to keep the service secure, and to measure whether it is useful; you can object at any time;
• legal obligation, to keep order and invoice records for tax and accounting.

Who processes it for us

• Cloudflare, Inc. hosts the application, its database and its files, and records product events.
• Resend sends our sign-in and account emails.
• PayPal sends and collects invoices, only if your venue places an order.

Each acts only on our instructions and under a data processing agreement. We will update this policy before we add another processor.

Where it is processed

We are in the United States, and so are our processors, though Cloudflare may serve and store data in other countries. When personal data leaves the UK or the European Economic Area, we and our processors protect it with the European Commission's standard contractual clauses and the UK's addendum to them, or with another safeguard the law recognises.

How long we keep it

• Sign-in links: each expires 15 minutes after we send it. We delete its record as soon as it is used or replaced by a newer link, and otherwise within an hour of it expiring. The note of when links were sent to an address is deleted within two hours.
• Sign-in sessions: 30 days, and their records deleted within two days of expiring.
• Your account and your venue's gate counts: for as long as you and your venue use Crowd Weather, or until you ask us to delete them. If we stop running Crowd Weather, we delete accounts and counts within 90 days.
• Accounts we could not confirm: if your venue tells us an account is not one of its people, we delete the account and its data and tell you by email.
• Uploaded files: the files you upload never reach us. We receive and keep only the counts per gate and per minute.
• Outreach log: until 12 months after we last wrote to you. If you told us "no", we keep only your address and that answer, so that we never write to you again.
• Product events: with your account for as long as the account exists. When it is deleted, we remove your account from them. Cloudflare's analytics keeps a copy without any account for about three months.
• Orders and invoices: seven years after the order ends, as tax and accounting law requires.
• Server logs: a few days.

Your rights

Wherever you are, you can ask us to show you the personal data we hold about you, to correct it, or to delete it. Under the UK and EU GDPR you can also ask us to restrict how we use it, object to our using it, or give it to you in a portable form, and you can withdraw any consent you gave.

Write to support@standardcomputingllc.com from the address on your account, or tell us which address it is. We answer within one month. When you ask us to delete your data, we delete your account, sessions, sign-in records and outreach record, and remove your account from product events. We keep only order and invoice records the law requires us to keep.

You can also complain to your data protection authority: in the UK, the Information Commissioner's Office; in Ireland, the Data Protection Commission; elsewhere in the EU, your country's authority.

Children

Crowd Weather is for people who work at venues. It is not for anyone under 16, and we do not knowingly collect their data.

Changes

When we change this policy, we publish the new version here with a new date. If a change affects how we use data you have already given us, we email the people it affects before it takes effect.

Last updated 24 October 2026.

This agreement is between the venue named when its account was set up (the "venue") and Standard Computing LLC, 5441 S Macadam Ave., Ste. N, Portland, OR 97239, USA ("we", "us"), which operates Crowd Weather at https://crowd-weather.stdcomputing.com. The person who sets up the venue's account accepts it on the venue's behalf and confirms they may do so. It applies for as long as the venue's people use Crowd Weather, alongside our terms of service; where they differ on personal data, this agreement decides. Standard Computing LLC is run by AI agents.

Our privacy policy describes the personal data we hold as controller, such as the details people give us to sign in and our outreach log. This agreement covers the personal data we process for the venue, on its behalf, as its processor.

1. What we process

• Subject matter: providing Crowd Weather to the venue: storing its uploaded gate history; making its forecasts, backtests and reports; live mode; and its price answer and orders.
• Duration: while the venue uses Crowd Weather, and until the data is deleted under section 9.
• Nature and purpose: storage, calculation and display, only to provide Crowd Weather to the venue.
• Data subjects: the venue's staff and contractors who use Crowd Weather or whom the venue invites, such as a budget holder; and any person who appears in a file the venue uploads.
• Personal data: names, work email addresses, roles and job titles, and anything a file the venue uploads contains. Crowd Weather keeps uploaded turnstile and scan counts only as counts per gate and per minute, so the venue should not upload names, ticket numbers or other details that identify people.
• Special category data: none. The venue must not upload health data or any other special category data.

2. Instructions

We process the venue's personal data only on its documented instructions. This agreement and the venue's use of Crowd Weather are those instructions. If the law requires us to process it otherwise, we tell the venue first unless the law forbids it. If we believe an instruction breaks data protection law, we tell the venue.

3. Confidentiality

Only the AI agents that run Standard Computing LLC, and the people who run them, can access the venue's data, only to run the service, and all of them are bound to keep it confidential.

4. Security

We protect the venue's data with measures suited to the risk, including:

• all traffic encrypted in transit with TLS, and data encrypted at rest by our hosting;
• sign-in only by single-use links that expire after 15 minutes, with no passwords, and links and session tokens stored only as hashes;
• session cookies the page's scripts cannot read, and checks that refuse cross-site form posts;
• each venue's data shown only to accounts verified as belonging to that venue;
• administrative access limited to a secret we hold, and to what each task needs.

5. Sub-processors

The venue authorises us to use these sub-processors:

• Cloudflare, Inc. (United States): hosting, database, file storage and analytics;
• Resend (United States): sending email;
• PayPal (United States): invoicing, only if the venue places an order.

We bind each to data protection terms no less protective than this agreement, and remain responsible to the venue for them. We email the venue at least 30 days before adding or replacing a sub-processor. The venue may object on reasonable data protection grounds; if we cannot meet the objection, the venue may stop using Crowd Weather and have its data deleted.

6. Transfers

We and our sub-processors are in the United States. For personal data transferred from the European Economic Area, the European Commission's standard contractual clauses (Decision 2021/914, module two, controller to processor) are incorporated into this agreement, with the venue as data exporter, us as data importer, Irish law as their governing law and the courts of Ireland for disputes under them. For personal data transferred from the United Kingdom, the UK Information Commissioner's International Data Transfer Addendum to those clauses is incorporated too. Section 1 (the transfer), section 4 (security) and section 5 (sub-processors) complete the clauses' annexes.

7. Helping the venue

We help the venue, as far as we reasonably can, to answer people exercising their data protection rights, to keep its data secure, and with any data protection impact assessment or consultation with a regulator that concerns Crowd Weather. If someone writes to us directly about personal data we process for the venue, we pass the request to the venue.

8. Personal data breaches

If we become aware of a breach affecting the venue's personal data, we tell the venue without undue delay, and within 48 hours, with what we know of its nature, the data and people affected, its likely consequences and what we are doing about it, and we keep the venue informed as we learn more.

9. Deletion at the end

When the venue stops using Crowd Weather, or asks us to, we delete its personal data within 30 days, returning it first if the venue asks, unless the law requires us to keep it, as it does for order and invoice records.

10. Records and audits

We give the venue the information it needs to show that this agreement is kept, and answer its reasonable questions about our processing in writing. Where the law requires more, we allow and contribute to an audit by the venue or an auditor it appoints, on reasonable notice and under confidentiality.

11. Contact and changes

The venue reaches us about this agreement at support@standardcomputingllc.com. We email the venue's account holders before any change to this agreement takes effect. Where this agreement and the standard contractual clauses conflict, the clauses prevail.

Last updated 24 October 2026.

These terms are between Standard Computing LLC, 5441 S Macadam Ave., Ste. N, Portland, OR 97239, USA ("we", "us"), and the venue named when its account was set up (the "venue"). They cover Crowd Weather at https://crowd-weather.stdcomputing.com. The person who sets up an account accepts them on the venue's behalf and confirms they may do so. Everyone who uses Crowd Weather for the venue must follow them. Standard Computing LLC is run by AI agents.

1. What Crowd Weather is

Crowd Weather is a web service for stadiums and arenas. A venue uploads its past per-gate, per-minute turnstile or scan counts. Crowd Weather uses them to forecast how many people will arrive at each gate 15 and 30 minutes ahead, with a range around each forecast. It shows how accurate those forecasts would have been on the venue's past fixtures, lets the venue upload scan exports during doors-open so that the forecasts refresh, and makes a one-page report comparing forecast and actual arrivals after an event.

Crowd Weather is decision support only. It is not a safety system. Our decision-support disclaimer, published with these terms, explains what that means, and it forms part of these terms.

2. Accounts

• Crowd Weather is for venues and the people who work for them. Use it only for your work, not as a consumer.
• You sign in with a one-time link sent to your work email. Keep your sign-in links and your signed-in devices to yourself.
• Tell us the truth about who you are, your role and your venue. We check that an account belongs to its venue. Until we have, the account cannot upload counts or sign an order.
• The venue is responsible for what its people do in Crowd Weather. If someone should no longer act for the venue, write to us and we will close their account.

3. Using Crowd Weather fairly

You must not:

• upload names, ticket numbers, health data or anything else that identifies a person; upload counts only;
• upload data you have no right to share with us;
• try to see another venue's data, get around our security or the venue checks, or test our systems for weaknesses without our written permission;
• copy, scrape or resell Crowd Weather, or use it to build a competing product;
• use Crowd Weather in a way that breaks the law or harms anyone.

We may suspend an account that breaks these rules. We will tell the venue why, unless the law stops us.

4. Your data

• The venue keeps all rights in the counts and other data it uploads. It gives us the right to store and process that data only to provide Crowd Weather to the venue.
• Our data processing agreement covers the personal data we process for the venue. Our privacy policy covers the personal data we hold for ourselves, such as your sign-in email. Both are published with these terms.
• The venue may use and share its forecasts, backtests and reports as it likes for its own operations, including with its Safety Advisory Group, licensing authority, police and other safety partners.
• Crowd Weather itself, its software and its forecasting methods belong to us.

5. Price and payment

We do not charge for an account. A venue pays only under an order form signed in Crowd Weather by someone with authority to commit the venue to the spend. Each order form states, before anyone signs: the price, what is included, the start date, how it renews, how and when it is paid, and the only way to cancel it. If an order form and these terms disagree, the order form decides for that order.

Invoices are sent through PayPal. Taxes such as VAT are shown and handled on the invoice.

6. Availability and changes

We work to keep Crowd Weather running and accurate, but we cannot promise it will always be available, fast or free of errors, including during an event. A venue must not depend on Crowd Weather alone at any time; the disclaimer explains why.

We may improve or change Crowd Weather. We will not take away what a signed order includes during that order's term.

7. Liability

Nothing in these terms limits liability that the law does not allow to be limited, such as for death or personal injury caused by negligence, or for fraud.

Otherwise:

• the venue remains responsible for its crowd safety decisions and for how it uses forecasts, flags and reports;
• neither the venue nor we are liable for indirect or consequential loss, or for loss of profit, revenue or goodwill;
• our total liability to the venue under these terms and any order, however it arises, is limited to the amount the venue paid us in the 12 months before the claim.

8. Ending

• The venue may stop using Crowd Weather at any time and ask us to delete its data by writing to support@standardcomputingllc.com. A signed order still runs, and is paid, as the order form says.
• We may close a venue's account if it seriously or repeatedly breaks these terms, after telling it why.
• If we stop running Crowd Weather, we will tell venues by email before it stops, and we delete accounts and counts within 90 days, as our privacy policy says.
• Sections 4, 7 and 8 continue after an account ends.

9. Changes to these terms

If we change these terms in a way that matters, we will email each venue's account holders at least 30 days before the change takes effect. A change does not alter a signed order during its term. If a venue does not accept a change, it may stop using Crowd Weather before the change takes effect.

10. Contact

For help, questions about these terms, or to stop using Crowd Weather, write to support@standardcomputingllc.com.

Standard Computing LLC, 5441 S Macadam Ave., Ste. N, Portland, OR 97239, USA.

Last updated 24 October 2026.

Crowd Weather is operated by Standard Computing LLC, 5441 S Macadam Ave., Ste. N, Portland, OR 97239, USA, a company run by AI agents. This disclaimer forms part of our terms of service. It applies to everything Crowd Weather shows: forecasts, ranges, backtests, flags in live mode, and reports.

Decision support, not a safety system

Crowd Weather helps a venue's staff plan and watch gate arrivals. It does not control gates, turnstiles or stewards. It does not detect crowd density, crushing, disorder or any emergency, and it raises no alarms outside the page you are looking at.

It does not replace any part of a venue's crowd safety management: its safety certificate and the conditions in it, its safety management plan, its safety officer and stewards, CCTV and ingress monitoring, its Safety Advisory Group, or guidance such as the Guide to Safety at Sports Grounds. Every decision about opening, closing or staffing gates, and about the safety of spectators, stays with the venue and its safety officer.

What a forecast is

A forecast is a statistical estimate of how many people will arrive at a gate, based on the venue's past counts, tickets sold, kick-off time, day of the week and whether it is raining. It is not a measurement.

• Ranges are not limits. Each forecast comes with a range that the actual count should fall inside about 8 times in 10. About 2 times in 10 it will fall outside, sometimes far outside.
• Past accuracy does not promise future accuracy. The backtest shows how forecasts would have done on the venue's past fixtures. A fixture unlike those, such as a cup final, a new away crowd, a changed gate layout, transport disruption, extreme weather or an incident, can be forecast much less well.
• Forecasts are only as good as the counts. Missing, late, wrong or wrongly mapped counts give wrong forecasts. The venue is responsible for the counts it uploads.

Live mode and flags

In live mode, forecasts refresh only when someone uploads a new scan export, so they are only as current as the last upload. A flag shows when a gate's forecast passes a level the venue sets. A flag can be late, can be missed, or can be raised when nothing is wrong. No flag does not mean a gate is safe. Crowd Weather may be slow or unavailable at any time, including during an event, so every venue needs its usual monitoring and plans in place without it.

Reports

A forecast-versus-actual report records how Crowd Weather's forecasts compared with the counts the venue uploaded. It is not an assessment of the venue's safety, and it is not advice to its Safety Advisory Group.

Questions

If you have a question about what Crowd Weather shows, write to support@standardcomputingllc.com.