Skip to main content
Rana Huzaima Imtiaz
Back to home

Last updated: April 11, 2026

Privacy Policy

This policy describes how personal data may be handled when you visit Rana Huzaima Imtiaz's portfolio site or get in touch about work. It is not legal advice; have counsel review if you need a binding enterprise agreement.

This site is operated by Rana Huzaima Imtiaz (Full-Stack Engineer), based in Lahore, Punjab, Pakistan. The site is a professional portfolio and contact point, not a consumer app with accounts.

If you email or message using the contact details on this site, you may share your name, email address, phone number, company, and any other details you choose to include in your message. That information is used to respond and, if you become a client or collaborator, to administer the relationship.

Do not send passwords, government ID numbers, or highly sensitive personal data by email unless we have agreed on a secure channel first.

Like most websites, hosting and infrastructure providers may process technical data such as IP address, browser type, approximate region, and timestamps when you load pages. This helps deliver the site securely and diagnose errors.

This portfolio does not run first-party advertising or analytics cookies by default. Third-party features (below) may set their own cookies or similar storage.

This site may embed a live chat widget (Tawk.to) so visitors can ask questions. Tawk.to may process conversation content, technical data, and cookies according to their own policies. Do not submit confidential or regulated data through chat unless we explicitly agree.

Links to LinkedIn, GitHub, or other sites are governed by those platforms’ privacy policies once you leave this site.

Processing is generally based on legitimate interest (operating a portfolio, responding to inquiries, security) and, where applicable, steps prior to a contract or performance of a contract.

Data is not sold. It is not used for automated profiling or unrelated marketing unless you separately opt in to something we describe at the time.

Emails and chat logs may be kept for as long as needed to respond, manage projects, meet legal obligations, or resolve disputes, then deleted or archived according to reasonable business practice.

Depending on where you live, you may have rights to access, correct, delete, or restrict certain processing of your personal data. Contact huzaimadigital@gmail.com to make a request. You may also lodge a complaint with a supervisory authority where applicable.

This site is aimed at professionals and businesses. It is not directed at children under 16, and personal data from children is not knowingly collected.

This policy may be updated when the site or practices change. The “Last updated” date at the top will be revised when material changes are made.

Questions about this policy: huzaimadigital@gmail.com.

Frequently asked questions

Remote delivery, the kinds of projects I take on, and how to start a conversation—without the agency fluff.

Do you work remotely?
Yes. I work with teams worldwide from Lahore, Pakistan. Time zone overlap and async communication are normal for how I ship.
What kinds of projects do you take on?
Custom web applications, APIs and backends (Node.js, Laravel), Next.js and React front ends, e-commerce and marketplace work, Shopify Liquid and WordPress migrations, payments and third-party integrations, and AWS-style cloud delivery when the product needs it.
How do I start a conversation about a project?
Use the “Discuss a project” email link on this site. The subject line is pre-filled so inquiries are easy to triage. A short note with goals, stack, and timeline is enough to begin.
Can you work with our existing codebase?
Often, yes. I regularly join products that already have users—documentation, migrations, performance work, and feature delivery in brownfield codebases are a core part of my experience.
What is your typical engagement model?
Scoped milestones or ongoing product work, usually on a contract basis. Details depend on the brief; we align on scope, communication rhythm, and deliverables before writing code.