Privacy Policy

Section 01 / 13

Overview

This local template sets out the topics for the website’s future privacy notice. It is not an effective policy. The business owner and adviser must approve wording that matches the services and processes actually used before publication.

The proposed website supports business quotation and sample enquiries. It does not provide an online checkout. Enquiry collection and live contact actions are not active in this preview.

Section 02 / 13

Information for enquiries

The planned enquiry journey asks for a company, contact name, email and relevant requirements, such as product, quantity, destination and packaging. Optional supporting files depend on upload readiness.

The final notice must explain the fields actually collected, which are required, and what is received when someone contacts the business through another channel.

Section 03 / 13

Purposes and enquiry handling

The intended purpose is to understand a business requirement, review a quotation or sample request and support follow-up. Sending an enquiry would not confirm availability, pricing, a sale or a shipment.

The owner and adviser must confirm the applicable processing grounds and disclosures. This template does not establish a legal basis or make a compliance claim.

Section 04 / 13

Separate marketing choices

The approved design keeps optional marketing separate from enquiry handling, with an unchecked choice. An enquiry must not automatically enrol someone in marketing.

Marketing delivery and a working withdrawal process need separate implementation and verification. No subscription is created by reading this template.

Section 05 / 13

Supporting files

Uploads are not available here. The planned file flow requires private storage, safety checks and permitted staff access before files can be reviewed. Buyer attachments must not become public downloads.

If uploads are enabled later, the notice must reflect the actual file types, limits, scanning, access and deletion practices. It must also explain the route available when a buyer has no file.

Section 06 / 13

Staff access

The approved access model limits enquiry information to the owner and permitted staff. Content-editing access alone must not grant access to private buyer information.

Hosted identity and access verification remain pending. This template does not claim that a live staff system, security certification or privacy officer appointment has been completed.

Section 07 / 13

Providers and processing locations

The final notice must identify the providers actually used for hosting, storage, email, translation, abuse prevention and monitoring, along with relevant processing locations and transfers.

The technical plan selects Azure hosting, MongoDB Atlas, Microsoft 365, Resend, Google Cloud Translation, Cloudflare Turnstile and monitoring services. This is a planned service inventory, not confirmation that these services are active or that data stays within one country.

Section 08 / 13

Public translation and private information

The translation design applies to approved public website text. Buyer-entered names, email addresses, requirements, attachments and private staff notes must not be sent to public-content translation services.

This preview displays English source text and identifies unavailable translations. Selecting another language does not approve a translated legal notice or submit an enquiry.

Section 09 / 13

Language preference and browser storage

When browser storage is available, the current language selector saves a language code and expiry in local storage under mahala_lang. The preference expires after 180 days and is refreshed when saved. It contains no enquiry details.

Browsing and language selection still work when storage is blocked. Clearing site storage removes the saved preference. Any future draft storage, cookies or non-essential technologies must be described accurately and reviewed before release.

Section 10 / 13

Analytics and operational logs

The approved plan uses limited first-party aggregate measurement and redacted operational logs. Buyer names, email addresses, free text, filenames and private references must stay out of analytics.

No analytics integration is activated by this template. The final notice must reflect actual events, providers, log retention and any required choices; this draft makes no promise of complete anonymity.

Section 11 / 13

Retention and deletion

Retention periods, exceptions and deletion procedures require owner and adviser approval and must match implemented storage and provider settings. No final retention schedule or deletion deadline is published here.

The completed notice must distinguish active records from backups and justified audit records. Removing active information does not instantly remove every recovery copy. Retention and recovery tests remain release requirements.

Section 12 / 13

Privacy questions and requests

A verified privacy contact and request-handling process are pending. The final notice must explain how to ask about information, request corrections or deletion, and how identity and retention obligations are checked.

The Contact page currently describes setup status only. No privacy request is collected or sent through this template, and no unverified mailbox is offered as a working destination.

Section 13 / 13

Policy updates and version history

The effective date, last review date and approved policy revision are pending. Local template v1 is an implementation reference, not a published legal version or evidence of earlier reviews.

Before publication, the owner and adviser must approve the final service inventory, contact, purposes, retention and wording. A future enquiry flow must reference the applicable approved notice revision.

Related page: Website Terms preview