Legal
Privacy Policy
Last updated: 21 August 2026
RIDERNIP is designed to work without accounts, behavioural advertising or visitor profiles. This policy explains the limited information involved when you use the service.
1. Who we are
RIDERNIP is operated by MERCURY ROAD EQUIPMENT PTY LTD. ABN 36 614 422 187, ACN 614 422 187. It is an Australian Private Company, active from 6 September 2016, GST registered from 1 July 2022, with its main business location listed as NSW 2140, Australia.
The public service is at https://ridernip.info. Privacy enquiries can be sent to vlad@b-seen.net.
2. Information we handle
The service handles only a small amount of visitor information:
- search terms and filters submitted to search, including autocomplete requests;
- a client IP address supplied in request headers for page and autocomplete rate limiting; RIDERNIP immediately converts it to a shortened SHA-256 hash for the rate-limit bucket and does not place the raw address in that bucket;
- standard request information in reverse-proxy logs: IP address, date and time, request method, full requested URI, response status and size, user agent and referrer;
- request-related diagnostics in reverse-proxy error logs and application process output when an error occurs; and
- structured application request records containing the path, response status and processing duration, but not the visitor IP address. A small sample can include an incomplete prefix of a search term with its length; the full search term is never written by the application logger;
- information you choose to send by email, including your address and message.
RIDERNIP has no visitor accounts, login, cart or checkout. It does not process orders or payments. The application contains no audience analytics, advertising technology or third-party tracking pixels.
3. How we collect information
Request information comes directly from your browser when you open a page, search or ask for autocomplete suggestions. Email information comes directly from you when you contact us. We do not buy personal information from data brokers and do not track you across other websites.
Search and product pages can load product images from a store or catalogue image host. That host receives the information normally sent with an image request, such as your IP address and user agent, and may apply its own privacy practices.
4. Why we handle it
We handle this limited information to:
- return search results and suggestions for the current request;
- operate, diagnose and secure the service;
- rate-limit public page and autocomplete requests and prevent abuse; and
- respond to enquiries, corrections and privacy requests.
We do not currently retain an application-level search dataset to profile visitors, personalise advertising or train a recommendation system.
5. Search queries and retention
The application does not create a separate query dataset. It trims a submitted main search to 200 characters and an autocomplete query to 100 characters for processing. Its structured request logger samples only a small proportion of searches and, when sampled, records an incomplete prefix and the original character count rather than the full term. Application logs do not include a visitor IP address. Search terms are not linked to an account, name or profile because the service has none.
Search terms are sent in the requested URL. The reverse proxy logs the full URI as received alongside the requesting IP address. Access logs rotate weekly and retain four rotated files, which is normally about five weeks including the active file. Error logs rotate weekly and retain ten rotated files, normally about eleven weeks, and may contain request diagnostics. A query in those logs is therefore associated with an IP address even though it is not associated with a RIDERNIP account. The The reverse proxy’s full-URI logging is separate from RIDERNIP’s deliberately truncated and sampled application logging described above.
The public request limiters keep only the shortened IP hash and request count for a 60-second window. They use Redis when available and bounded process memory otherwise.
6. Cookies and similar technologies
RIDERNIP application code does not set cookies and does not use local storage, session storage, browser fingerprinting or analytics identifiers. It does not use advertising cookies. External image hosts and sites you choose to visit through a retailer link are separate services and may use their own technologies under their own policies.
7. Disclosure
We may disclose or make limited information available to:
- hosting and infrastructure providers that deliver, secure and log requests to the service;
- external image hosts when your browser requests an externally hosted product image;
- our email provider when you contact us; and
- regulators, courts, law-enforcement bodies or other recipients where required or authorised by law, or where reasonably necessary to protect rights or safety.
We do not sell visitor personal information.
8. Overseas disclosure
RIDERNIP does not intentionally send search queries or rate-limit records to an overseas analytics or advertising service. Product images can be served by stores and content-delivery networks located outside Australia. This can disclose your IP address and request metadata to those operators. Their countries vary with the product image source, so it is not practicable to list every country in this policy.
Email may also be processed in countries used by the sender’s and operator’s email providers. Internet traffic may be routed through other countries without the information being disclosed to a recipient there. Contact us if you want current details relevant to a particular request.
9. Security
The public deployment uses HTTPS. The application sends restrictive content, framing, referrer and browser-permission headers. Autocomplete rate limits use a one-way shortened IP hash, and the application avoids creating accounts or long-lived visitor identifiers. Reverse-proxy logs are kept on the deployment host and rotated on the schedules described above.
No internet service can promise absolute security. We cannot guarantee that transmission, storage or third-party systems will never be accessed, lost or misused.
10. Access and correction
You may ask to access personal information we hold about you or ask us to correct it. Send the request to vlad@b-seen.net with enough detail for us to locate the information. Because RIDERNIP has no accounts and keeps little identifying data, we may be unable to connect a record with you. We may need to verify your identity before releasing information and will explain any lawful reason for refusing access or correction.
11. Privacy complaints
Send a written complaint to vlad@b-seen.net. Explain what happened, when it happened and what outcome you seek. We will investigate and aim to respond within a reasonable time, usually within 30 days.
If you have first complained to us and are not satisfied with our response, or we have not responded within a reasonable time, you may contact the Office of the Australian Information Commissioner (OAIC). The OAIC accepts written online complaints and can be contacted on 1300 363 992.
12. Automated decision-making
From 10 December 2026, Australian Privacy Principle 1.7 requires certain privacy policies to describe automated decisions that significantly affect individuals and use their personal information. RIDERNIP does not perform that kind of decision-making.
RIDERNIP automatically matches listings, ranks search results and orders recorded prices. These processes concern products and store listings. They do not use personal information to make, or assist in making, decisions that significantly affect an individual’s rights or interests. RIDERNIP makes no automated decisions about individuals.
13. Children
RIDERNIP is a general motorcycle-gear information service and is not directed at children. It does not knowingly create profiles of children. The same limited request handling described in this policy applies to every visitor.
14. Changes to this policy
We may update this policy when the service or the law changes. The revised policy will be published here with a new “Last updated” date. Because RIDERNIP has no accounts or mailing list, changes are notified on this page rather than by direct message. Material changes may also be highlighted on the site.
