Legal

Privacy policy.

This site has no backend, no analytics and no cookies, so most of what a privacy policy normally has to explain does not happen here. This page says what does happen, specifically enough that you can check it against the page you are reading.

Last updated 6 September 2026. It applies to chrio.site.

The short version

Five things, before the detail.

Each one is a statement about this site's own code, and the sections below say how it was established.

What this policy covers.

It covers chrio.site: the pages you are reading, served from this domain. That is the whole scope, and everything below is about those pages and nothing else.

It does not cover what happens once you follow a link off the site, and it does not describe the CritShot (Live) demo at critshot.chrio.site, which is a separate deployment this page cannot speak for.

It also does not cover how Chrio's products handle broadcast footage at a venue. CritShot is Live, CritDRS is In development and CritRate is In development, and where Chrio runs any of them for a competition, what that system does with footage is set by the agreement covering that deployment, not by this page.

What this site collects.

Reading a page here creates nothing that Chrio holds. There is no analytics call, no tracking pixel, no iframe and no third-party embed. Every script the page loads comes from this domain. There are two: the one that runs on every visit, and a small animation module fetched only on a wide screen with more than four processor cores and reduced motion switched off.

The contact form is the only place on the site where you can hand Chrio anything, and it asks for seven things: your name (required), your work email (required), your organisation (required), your role (a menu), the product you are interested in (a menu), your competition and fixture window (optional), and a free text box labelled "Anything we should know" (optional).

Pressing the button posts none of it. The handler cancels the normal submit, puts your answers into a subject line and a message body, and points your browser at a mailto: link addressed to abdullahzubair@chrio.site. Your own email client opens with a draft. Nothing has left your machine at that point. When you press send in that client, your answers travel as ordinary email, from your address to that inbox, exactly like any other message you write. Chrio receives it the way it receives any email, and no earlier copy sits on a server in between.

The form depends on JavaScript, and it is worth saying what happens without it. The form carries no action attribute and its method is dialog, which is the HTML way of declaring a form that submits nowhere. With JavaScript turned off the button does nothing: no draft opens, and nothing is sent. Earlier this was not true. The form had no method at all, so a browser with JavaScript off fell back to the default and sent all seven answers to the host as a query string, where a server log would have recorded them. That is fixed. If the button does nothing for you, write to abdullahzubair@chrio.site or saffimuhammadhashir@chrio.site directly.

Five things are read from your browser while you are on a page, purely to decide how it behaves: whether you have asked your system to reduce motion, how many processor cores your browser reports, whether data saver is switched on, how wide the window is, and whether the tab is currently visible. Reduced motion and window width decide whether background video and scroll animation run, and the third turns off prefetching the next page. None of the three is sent anywhere. The copy buttons write to your clipboard and never read from it.

Why any of it is asked for.

To answer you, and for nothing else. The fields exist because a first reply is more useful when it already knows which competition you run, which product you are asking about and roughly when your season is. That is the entire purpose.

What you send does not go to a mailing list, an advertising audience, a lead-scoring tool or an automated decision of any kind. No such system exists here to send it to.

The legal basis.

Where a data protection framework applies to you, the basis Chrio relies on is its legitimate interest in replying to a message you chose to send, together with your own act of sending it. The processing that follows is the whole of it: read the email, reply to the email.

No basis is claimed for anything else, because nothing else happens. There is no consent to gather for measurement or advertising, because there is neither. This page names no specific statute, because Chrio has not established which framework binds it for a given visitor, and naming one it had not checked would be a claim rather than a fact.

Who it is shared with.

Nobody. Chrio does not sell personal information, does not share it for advertising, and has no analytics vendor, no customer relationship system and no marketing platform receiving anything from this site. None of those exist here to receive it.

One party is unavoidably in the chain, and honesty requires naming the role. Once your email is sent it sits in an ordinary mailbox, and whoever provides mail service for the chrio.site addresses handles it the way any mail provider handles mail. That is the same exposure as any email you send to any address anywhere: a fact about email rather than about this site.

How long it is kept.

This site keeps nothing, so nothing here has a retention period. There is no record to age out and no table to purge.

An email you send is kept for as long as the conversation needs it and a reasonable period after, in case you come back to it. No number of months appears on this page, because Chrio has not published a retention schedule and a figure invented for a policy page is one that nothing enforces. If a defined period matters to you, ask for it in writing, and ask for deletion once the conversation is finished.

Third parties, and where these pages are served.

One third-party origin loads automatically, and it is Google Fonts. The typeface is Poppins, requested from fonts.googleapis.com, and the stylesheet that comes back points at font files on fonts.gstatic.com. Both requests carry your IP address and your browser's user agent to Google, and both happen as the page loads, before you have done anything on it. What Google does with them is covered by Google's own privacy policy, not by this one.

Blocking those two domains does not break the site. The page falls back to the typeface your system already has, and everything else keeps working.

Everything else comes from this domain: the stylesheet, the one script, every image and every video. There is no iframe, no embedded player and no third-party widget anywhere on the site.

The pages are served by Vercel. As with any host, the infrastructure that delivers a page processes connection data, including your IP address and the time of the request, in order to serve the page and to keep the service secure. That happens underneath this site's own code. No retention period is stated for it here, because Chrio has not published one for the hosting layer.

Links out are links out. The site links to dhundo.store, to critshot.chrio.site, to Chrio and its founders on LinkedIn, and to a founder's profile on GitHub. Following one is a visit to that site, under that site's own policy, and Chrio has neither visibility into it nor control over it.

Cookies and browser storage.

None, in either direction. This site sets no cookie of its own, reads no cookie, and writes nothing to localStorage, sessionStorage or indexedDB. Nothing here identifies you from one page to the next, or from one visit to the next.

There is no consent banner, because there would be nothing for it to ask about. A banner asking permission for tracking that does not exist is theatre, and this site would rather be checkable: it loads one script, from this domain, and your browser's developer tools will show you that script and an empty cookie jar.

Your rights.

Because this site stores nothing about you, most of these have nothing to act on here. They apply to what you have actually emailed Chrio, and Chrio will honour a request about that whichever framework you are relying on.

• Access Ask what Chrio holds about you. In practice that is the emails you have sent and the replies to them.
• Correction Ask for something inaccurate about you to be corrected.
• Deletion Ask for the messages you sent to be removed from the inbox that received them.
• Objection and restriction Ask Chrio to stop using your message for anything beyond replying to it.
• Portability Ask for a copy of what you sent, in a form you can take elsewhere.
• Complaint If the answer does not satisfy you, you are entitled to raise it with the data protection authority that covers you.

Chrio does not sell or share personal information, so there is no opt-out to exercise and nothing to withdraw.

How to ask for deletion or a copy.

Write to abdullahzubair@chrio.site and say what you want done. Naming the address you wrote from, and roughly when, is enough to find the messages. Chrio will not ask you for identity documents to answer a request about an email you sent from your own address.

Chrio's stated reply time for enquiries is two working days, and a deletion request goes to the same inbox. You will be told what was found and what was removed, rather than only that it was handled.

Changes to this policy.

If what is collected changes, or why, or who receives it, the date at the top of this page changes with it and the section that changed says what is different. There is no notification list to join, because there is no list.

This page describes the site as it stood on the date at the top. If you are reading a cached or archived copy, check the live page before relying on it.

Contact

How to reach us.

Chrio has not designated a separate data protection contact. Questions, requests and complaints about this policy go to either founder, and both addresses reach someone who can act on them.

Go to the contact page Terms of use