Scope
This notice describes the RMC Foods public website and email enquiry route. The build does not include user accounts, online checkout, embedded maps, social-media widgets, advertising code or a third-party analytics library. Hosting and email providers may process technical records required to deliver their services.
Information you provide
If you email RMC Foods, the message may contain your name, email address, delivery location, product questions and other information you choose to provide. Do not send passwords, one-time codes, payment-card numbers, government identity documents or unnecessary health information. Enquiry information is used to understand, route and answer the request and to maintain an appropriate business or rights record.
Always-on first-party base statistics
On production pages, a script requests the existing first-party /collect/ endpoint once per page load. Its approved base payload contains the browser language, a client-side timestamp, the browser-reported time zone and document referrer. The base event is designed to be cookieless and runs whether the visitor accepts, rejects, dismisses or does not interact with the Cookie panel. It is disabled on localhost during development.
Cookie choice therefore does not disable the base statistics event. A visitor’s optional-storage choice is stored locally in the browser only to avoid repeatedly displaying the panel. This build does not install optional advertising or personalisation trackers.
Server and security records
Web hosting normally creates request and security logs containing information such as IP address, requested URL, time, user agent and response status. These records may be used for delivery, troubleshooting, abuse prevention and security. No Internet transmission or storage method is guaranteed to be completely secure.
Sharing and service providers
Information may be handled by infrastructure, hosting or email providers that support the site, and may be disclosed when reasonably necessary to protect the service, users or legal rights. This notice does not claim that data is never processed outside a visitor’s state or country; provider locations and routing can vary.
Retention approach
Enquiries and technical records should be retained only for the operational, security, transaction, correction or rights purpose for which they are needed. Exact retention periods depend on provider configuration and the nature of the record. Requests to locate or delete information should identify the relevant email address, approximate date and context.
Children
The site is a general food information and enquiry service, not an account service directed at children. A child should not submit personal information without appropriate adult involvement.
Your choices and requests
You can choose not to send an email and can remove the local cookie-choice value through browser settings. For an access, correction, deletion or privacy question, write to server@rmcfoods.com. A request may require enough information to locate the relevant record without requesting unnecessary identity material.
Changes
Material changes will be reflected on this page with a substantive update date. The notice must be reviewed again during production launch to confirm that the live hosting, analytics, advertising and enquiry stack matches this description.
Legal basis and regional rights
This notice does not assign one universal legal basis or promise rights that do not apply in every jurisdiction. Depending on location and context, a person may have rights concerning access, correction, deletion, restriction or objection. RMC Foods will assess a properly scoped request against the records it can identify and the obligations that apply to the responsible operator.
Email and transaction boundaries
Email is not a secure payment channel. If an enquiry progresses to a transaction, payment instructions and the seller’s identity should be verified through an agreed channel. The public website should not receive card data. Delivery details should be shared only after the fulfilment method is confirmed and only with parties that need them.
Production launch review
Before launch, the operator must verify the actual hosting logs, /collect/ persistence, email routing, retention settings, optional trackers and any advertising technology. If any of those differ from this notice, the implementation or policy must be corrected before release. Local technical acceptance does not establish compliance in every country.