Clear expectations for how request and site information is handled.

Who controls site and intake information

Mirelis Food Standards is the controller of information collected through this site and its intake workflow. Questions about privacy or confidentiality should be raised through the contact flow before sensitive materials are shared.

What information may be collected

Mirelis Food Standards may collect information you submit through the site, including contact details, company information, request scope, product categories, operational context, timing, and uploaded or quoted background details needed to understand a potential engagement.

How that information is used

• Review and triage service requests.
• Prepare proposals, scope decisions, and follow-up communication.
• Support active client work once an engagement begins.
• Maintain internal records tied to subscriptions, requests, or deliverables.

Sharing and disclosure

Information should not be sold. It may be shared only as needed to operate the business, meet legal obligations, process payments, or deliver work with your awareness. If a separate NDA or client agreement applies, that agreement controls the confidentiality handling for that engagement.

Retention and deletion

Working default retention should be tied to the business purpose of the material. Intake and proposal records may be kept for up to 24 months unless a longer period is required for accounting, dispute handling, or active client work. When appropriate, Mirelis Food Standards should offer deletion or reduced retention on request, subject to legal, contractual, and accounting constraints.

Site technology and analytics

The current consulting prototype uses local assets and a lightweight front-end. No advertising technology is assumed in this version. If analytics, cookies, payment tools, or subscriber-account systems are added later, this page should be updated before public launch to reflect those tools accurately.

Client materials and secure handling

Once work is scoped, sensitive documents should move into an agreed client workflow instead of staying in general intake channels. Reasonable administrative, technical, and organizational controls should be used to limit access and reduce unnecessary exposure. If a client requires specific storage, transfer, or deletion commitments, those requirements should be set in the engagement documents before work begins.

Questions

For privacy or confidentiality questions tied to a request, use the contact flow and note the concern clearly so it can be routed before substantive materials are exchanged.