Privacy
Privacy Policy: What This Site Collects and Where It Goes
This page describes what actually happens to information you send through runmotoapparel.com. It is written to be read rather than to be defensible, and it covers the whole of what this site does: one enquiry form, two third-party services, and no advertising or analytics tracking of any kind.
Last updated 17 September 2026 · Operated by Wuhan Beiyi Network Technology Co., Ltd, trading as Run Moto Apparel
- The five fields you type into the enquiry form, and nothing you did not type.
- Two invisible anti-spam values that are discarded once the check is done.
- Artwork, rosters and measurement sheets, if you choose to send them.
- The technical minimum any web server sees while serving you a page.
- Sell, rent or share your details with anyone for marketing.
- Run analytics, advertising pixels or social tracking tags on this site.
- Set a cookie that follows you to another website.
The short version
Four sentences, and the rest of the page is detail
If you read nothing else here, these four cards are the whole policy. Everything below them exists so that each one can be checked rather than taken on trust.
Only what you type
The enquiry form, plus any file you choose to attach. There is no hidden collection layer on this site.
To answer you, then to run the order
Your message reaches the person who replies. If it becomes an order, the same record follows it through production.
No selling, no sharing, no tracking
Nothing here is passed to a marketing platform, and nothing on the page follows you once you leave it.
Ask, and we show or delete
One email to [email protected] gets you a copy of what we hold, a correction to it, or its removal.
What the form collects
Five fields you fill in, and two you never see
Every one of them is listed below with the reason it exists. If a field is not on this table, this site does not ask for it — there is no hidden second form and no profile being assembled behind the one you can see.
| Field | Why it is there |
|---|---|
| Your name | Because a reply has to be addressed to someone. |
| Email address | The reply route, and the only field we genuinely cannot work without. |
| Phone or WhatsApp | Optional. Most people fill it in because it is faster than email in both directions. |
| Buyer type | A dropdown — team, club, brand, dealer, centre or other. It decides which colleague reads your enquiry first. |
| Your message | Whatever you write, including any specification, quantity or date you paste in. |
| HoneypotHidden | A field you cannot see and never type into. It must arrive empty; anything that fills it is a bot. |
| Submission timeHidden | Seconds between the page loading and the form being sent. Both this and the honeypot are discarded once the spam check is done. |
Where it goes
Into our own system, read by the person who answers you
The diagram below is the honest answer to "where does my enquiry go". There is no branch in it that leads to a third party, because there is no such branch on this site.
Who actually reads it
Anna reads every enquiry first. If it becomes an order, the same record is read by the colleagues who work on it — production planning, the pattern room, and whoever needs the specification you sent. That is the complete list of people with access.
It is not read by anyone outside the company, and it is not copied into any marketing tool, mailing platform or customer database belonging to a third party.
What the server records
The technical minimum, which is not nothing
Every web server records the requests it serves, and ours is no exception. A policy claiming to collect no data at all from visitors is describing something that does not exist, so here is the actual line.
| Recorded | What it is for | Joined to you |
|---|---|---|
| IP address | Delivering the page, and identifying traffic attacking the form rather than using it. | No |
| Page requested | Confirming pages are actually being served rather than failing quietly. | No |
| Time and response code | Spotting errors and outages on a page nobody has complained about yet. | No |
| Browser string | Checking that the site renders on what people actually use. | No |
Why we do not build visit histories out of them
Because we would have to build something to do it. Server log lines are not a usable record of a person's behaviour until someone writes the tooling to stitch them together, store them and query them. We have not built that and have no reason to: the commercially useful information on this site arrives through the enquiry form, where you knowingly handed it over.
What the lines get used for is narrower than that and duller: error rates, and patterns that look like an attack on the form. They are not exported anywhere and are not used to work out which pages a particular person read.
Files you send us
Artwork, rosters and measurement sheets stay yours
Anything you attach is used to quote and to produce your order, and for nothing else. It is not shown to other customers, not used in our own marketing, and not published on this site or anywhere else unless you ask us to.
Rosters in particular are worth naming separately, because they contain other people's names, sizes and sometimes numbers. We treat that list as your data to control, which means a deletion request from you covers it.
A team roster is twenty people's data in one file. It gets handled that way.
One form, two third parties, zero tracking — and a deletion request answered inside 24 hours by the same person who answers everything else on this site.
Everything above this line is the complete list of what is collected. Everything below it is how each item on that list can be checked, kept or removed.
The two third parties
Two services are involved, and here is what each one sees
Naming them is the point. A policy that says "we may share data with trusted partners" is a policy that has told you nothing.
Google Fonts
Our form endpoint
Cookies and storage
This site does not set tracking cookies
There is no cookie banner here because there is nothing to ask you about. We set no analytics or advertising cookies, and nothing on these pages follows you to another site.
- Interface state only. The top bar, the menu and the WhatsApp button are served from our own domain and may use your browser's local storage to remember something you closed.
- It stays in your browser. That storage is never transmitted to us and is cleared whenever you clear site data.
- No identifier is assigned to you. Nothing on this site gives your browser a number it carries between visits.
Who can get into it
Access is a short list of named people
Your enquiry lives in our internal ERP, reached through individual accounts rather than a shared login — so every record that is opened is opened by a particular person, not by "the office". Nobody has a reason to browse enquiries belonging to somebody else's customer, and the system is not arranged to make that convenient.
- No enquiry lists exported to spreadsheets. That habit is how customer data actually leaks — far more often than anything dramatic — so it is named here rather than covered by a line about taking security seriously.
- No copies left on personal devices once an order is finished. Your files live with the order record, not in somebody's downloads folder.
- If something did go wrong, we would contact the people affected directly with what happened and what was in it, rather than publishing a notice and hoping it was read. You would hear it from Anna, in the inbox you already use.
How long it is kept
Enquiries stay while they are live business, then they go
Retention here is tied to whether a conversation is still a conversation, rather than to a fixed number of months that would be invented for the sake of having one.
| What it is | How long it stays |
|---|---|
| Enquiries that became orders | As long as the commercial relationship and the records that go with it require. |
| Enquiries that did not | While there is a realistic prospect of the conversation continuing, and removed when there is not. |
| Files you sent | Kept with the order they belong to, and removed together with it. |
| Spam and automated submissions | Deleted. |
Access and deletion
Asking us to show or delete what we hold
One email, answered inside the same 24 hours as anything else on business days.
Write from the address you used
Email [email protected] and say which you want: a copy of what we hold, a correction to it, or deletion.
We find the record and act on it
The enquiry, any files attached to it and the order record it became are all part of the same search.
We tell you what we cannot delete, and why
If something is attached to a live order we will name it and give you the date it can go, rather than deleting around it and telling you it is gone.
Children and changes
Two things that deserve their own paragraph
This site is not directed at children
This is a business site for teams, clubs, brands, dealers and training centres, and we do not knowingly collect information from children.
Where a team roster includes the names and sizes of junior riders, that list reaches us from the adult placing the order, and is handled as part of that order — including when it is deleted.
The date at the top changes when the page does
If this policy changes, the date at the top changes with it. We do not quietly edit this page and leave the old date standing.
A material change to what we collect or who can read it gets described here in the same plain terms as the rest of the page, rather than summarised as "updates to our privacy practices".
Who to contact
Anything on this page reaches the same desk
There is no separate privacy inbox that nobody reads. Data requests go to the person who answers enquiries, and they are answered in the same 24 hours.
- A copy of what we hold, in plain text you can read.
- A correction, if something in it is wrong.
- Deletion, with the parts we cannot remove named and dated.
Wuhan Beiyi Network Technology Co., Ltd
Room 1801-1804, Block B
Aerospace Business Plaza
Jiang'an District, Wuhan 430014
Hubei, China