A clear account of how website data is intended to be handled.

1. Scope and identity

This draft applies to the HiqmaHub marketing website at hiqmahub.com and its project enquiry flow. The service is currently identified publicly as HiqmaHub. A confirmed legal business name and address have not been supplied and must be added before this notice is approved for production.

2. Information the enquiry form is designed to collect

If you choose to submit a project enquiry, the planned form asks for contact details and project context needed to respond. This may include your name, work email, phone number, company, service interest, budget band, timeline, message, consent timestamp, referring page, and campaign parameters.

The planned anti-spam controls may process a short-lived security token and technical request signals. HiqmaHub's application is designed not to store raw IP addresses in the lead record.

3. Why that information is used

The intended uses are limited to:

• reviewing and responding to a project enquiry;
• qualifying the requested scope and arranging follow-up;
• protecting the form from spam and automated abuse;
• maintaining an operational record of the enquiry; and
• understanding website performance and conversion only where the required analytics consent has been given.

Final lawful bases for each purpose must be confirmed during legal review for the regions in which HiqmaHub operates.

4. Planned service providers

The launch architecture is designed to use Supabase for durable lead storage, Resend for enquiry notifications and acknowledgements, Cloudflare Turnstile for form abuse prevention, and Vercel for website hosting and performance monitoring. Consent-aware Google Analytics may be enabled only after the property and consent implementation are confirmed.

These providers may process data in other countries under their own contractual and transfer safeguards. The production vendor list, agreements, locations, and links to provider notices must be verified before launch.

5. Cookies and analytics

Essential technologies may be used to deliver and protect the website. Optional analytics must remain disabled until the relevant consent choice has been made. The final site should provide a way to revisit that choice wherever applicable.

6. Retention and security

Access to stored enquiries is intended to be restricted to authorised business users and server-side credentials. A final retention schedule, deletion routine, incident process, and access-review cadence are launch inputs and are not yet stated in this draft.

7. Tools

The five utility routes currently provide informational landing pages only. They do not yet accept or process documents, text, URLs, or passwords. Their planned browser-based privacy model will need a separate technical and privacy review when each tool becomes functional.

8. Your choices and requests

Depending on where you live, you may have rights to ask about, access, correct, delete, restrict, or object to certain uses of your personal information. The final notice must explain the applicable process and any identity checks. For now, privacy questions can be sent to hiqmahubcom@gmail.com.

9. Changes to this notice

The approved notice should show an effective date and be updated when the website's data practices or service providers change. Material changes should be communicated in a proportionate way.