PRIVACY POLICY.

Information you provide

• Account data: required full name, email address and password. The password is stored only as a secure hash and is never returned by the API.
• Checkout data: first and last name, phone number, optional email, street address, commune, wilaya and delivery method.
• Order data: selected product and variant snapshots, references, quantities, prices, promotion and delivery totals, payment method and status history.

Browser and security data

• An HttpOnly authentication cookie keeps signed-in sessions persistent.
• A locale cookie remembers the chosen language, and browser storage keeps the current cart on the device.
• A versioned browser-storage choice records whether optional marketing tracking was accepted or rejected.
• Request information such as a client address may be used for security and rate limiting.

How information is used

• Create and secure customer accounts.
• Price, validate, prepare, confirm and deliver orders.
• Provide customer support and maintain historical order records.
• Protect the service, enforce administrator authorization and diagnose failures.

Optional marketing analytics, Meta Pixel and Conversions API

• Meta Pixel in the browser and Meta Conversions API on Numyra’s server are enabled only after you accept marketing. Neither channel is used for rejected or undecided choices, and neither is used in the Numyra administration area.
• Before a choice is made, allowlisted campaign parameters such as UTMs may be kept only in the current page’s memory to preserve attribution. They are not persisted or sent to Meta unless marketing is accepted.
• With consent, events may describe page and product views, a deliberately submitted and sanitized search, completed registration without form values, successful cart additions, checkout progress and a successfully created purchase. Event data may include stable public product or variant references, product categories, quantities, numeric totals in DZD and the public order reference used to prevent duplicate purchase events. Meta may also receive standard browser, device and request information when its service is contacted.
• After consent, Meta may set or read marketing cookies and browser identifiers such as _fbp and, when an eligible Meta click identifier is present, _fbc. Server events may use the original _fbp or _fbc value, the bounded browser user-agent and the request IP address for technical event matching; these values are not hashed or derived from account or delivery data. Numyra does not invent _fbc when no valid Meta click identifier exists.
• Events awaiting temporary server delivery are kept in a short-lived, access-controlled retry outbox containing only the sanitized event and necessary technical matching context. Technical matching data is removed after delivery or permanent failure, and operational records expire automatically.
• A random first-party consent-instance identifier is used only to apply a withdrawal to queued delivery retries. Numyra stores only its domain-separated SHA-256 hash on the server; it is not derived from an account or database ID and is never sent to Meta. Once withdrawal is acknowledged, still-pending payloads for that consent instance are canceled and purged; an event Meta already accepted or a request already in flight cannot be recalled.
• Numyra does not send Meta names, full names, email addresses, phone numbers, delivery addresses, wilayas, communes, passwords, free-form customer input, MongoDB identifiers, or raw or hashed customer form data. Automatic advanced matching is not enabled.
• You can change or withdraw marketing consent at any time through Cookie preferences in the footer. Withdrawing consent prevents subsequent Numyra marketing events; essential storefront storage continues to operate.

Who receives order information

Order and delivery details may be provided to staff and delivery providers only as needed to fulfil and support the order. Numyra does not currently collect payment-card data through the storefront.

Retention and choices

Account and order information is retained while needed for service operation, security and applicable record-keeping obligations. Contact Numyra to ask about your information or request an account-related change. Some order snapshots must remain intact so completed transactions can still be understood.