Privacy Policy

1. Overview

MrUsman.com is a portfolio, services and public-tools website operated from Abu Dhabi, UAE. This policy explains how information is handled when you browse the site, send an enquiry, submit a project brief or support request, use a public tool, or continue to an external payment provider.

2. Information you provide

Contact

The quick enquiry form collects your name, email address, optional phone or WhatsApp number, subject and message. It also includes limited page, intent, referral and campaign context when present in the page URL.

Project intake

The project brief can collect project and business type, goals, existing-system status and public URL, selected requirements, stage, preferred timeline, budget currency and range, name, company, email, phone or WhatsApp number, country, contact preference and limited attribution context.

Support

The support form can collect the affected system and issue type, urgency, public URL or approved reference, issue description, start period, recent changes, optional error and reproduction details, browser or device, tool-result summary, name, company, email, phone or WhatsApp number, contact preference and limited attribution context.

Accepted enquiry, project and support submissions are saved in the existing lead-management database and may be sent by email as a notification so they can be reviewed and answered.

3. Information collected automatically

The web server and hosting infrastructure may process standard request information such as IP address, browser or user-agent information, requested page, date and time, and referral information for delivery, diagnostics and security.

Public forms use an IP address for abuse controls. The lead record currently includes the submitting IP address. A separate hashed IP identifier is used for submission rate limiting and duplicate protection; those rate-control records are automatically pruned after 30 days.

First-party site and tool analytics

You can choose essential-only operation or allow analytics. With analytics allowed, random visitor and session UUIDs are stored in your browser and sent with allowlisted events such as page views, tool starts, completions, errors and exports. The system does not fingerprint your device, store a raw IP address in the analytics event, or send invoice/client content. With analytics denied, or before you choose, the page opening is still counted — which page, when, the referring host, the device class, and the country and city resolved from your address at that moment — but with no visitor or session identifier, so those records cannot be linked to each other or to you. Your address itself is never stored: it is used for that lookup and for abuse limits, both through a keyed hash, and then discarded. Referrers are reduced to their host name.

Google Analytics

Choosing “Allow analytics” also enables Google Analytics 4 on this site. The Google tag is not present in the page by default: it is requested only after you allow analytics, so if you choose “Essential only”, or close the page without choosing, no request is made to Google and no Google cookie is set.

Once enabled, Google Analytics sets its own cookies in your browser and receives the page you viewed, referral information, approximate location derived from your IP address, and device and browser characteristics. Google processes that data as described in its own privacy terms. Advertising storage, advertising user data and ads personalisation are all signalled as denied, because allowing analytics is not consent to advertising. Google Analytics receives the same allowlisted interaction names as the first-party system — never document content, client names, amounts, submitted URLs or form values.

You can withdraw consent at any time by clearing site data for this domain, which removes the stored preference and stops the tag loading again until you choose to allow it.

Page interaction events

Selected interactions are also placed into an in-page dataLayer queue. No advertising pixel and no analytics sender other than the Google tag described above is loaded by the current public build.

4. How the public tools handle data

The tools are grouped below by what they actually do with information, rather than listed one by one, so this section stays accurate as tools are added or retired. The current list is always on the tools page.

A. Tools that work entirely in your browser

Invoice Studio, Proposal & Scope Studio, Property ROI Studio, the SEO Checklist and the Google Ads Budget Calculator build documents, checklists and calculations on your device. The content — seller and client details, line items, tax settings, bank notes, proposal scope and pricing, property assumptions and financing figures, checklist ticks and notes, and advertising budget assumptions — is not sent to the MrUsman.com server. The SEO Checklist does not ask for a website address at all.

Each keeps its working drafts in your browser’s local storage, on that browser and that device only. Drafts are not synced between devices or browsers, and clearing site data for this domain removes them. Invoice Studio additionally stores a business profile only when you explicitly save one. PDF, Markdown, CSV and JSON exports are produced on your device.

Proposal & Scope Studio can hand a payment milestone to Invoice Studio. That handoff is written to your browser’s local storage and read back by Invoice Studio on the same device. It is never sent to the server, and it is cleared once imported.

Only coarse, metadata-only events are recorded for these tools, and only according to your analytics choice: which tool was opened, which template or design was selected, which export format was used, the currency code, and bucketed counts such as how many line items exist. No document text, client name, address, amount, proposal wording or financial assumption is included in an analytics event.

B. Server-side diagnostic tools

The website, SEO, DNS and email, tracking, conversion, AI-visibility and comparison checkers need a server to fetch the destination you submit. You provide a public URL or domain; the server makes bounded, read-only requests to that destination’s public HTML, response headers, DNS records, TLS certificate, robots.txt and a limited sample of sitemap locations. Nothing is submitted, logged into or changed on the destination.

Recent results and normalized public evidence may be held in a short-lived server-side cache so that repeating a check does not repeat the requests. Standard web-server logs record the request. Only submit destinations you own or are authorized to check.

C. AI Knowledge Studio

This tool needs server-side extraction, and is described separately for that reason. You submit a public website address; the server reads that site’s robots.txt and follows its rules, discovers a bounded set of candidate URLs, then fetches only the pages you select — currently up to five pages per run, from at most fifty discovered candidates, using two discovery requests.

The extraction is stateless. No job record, no raw HTML and no copy of the extracted content is kept on the server. The content is returned to your browser, and the knowledge base exists only in that browser tab until you export it.

The permission checkbox records that you have stated you are authorized. It does not verify ownership, and it does not relax anything: robots rules are followed either way, and logins, paywalls and access controls are never bypassed. Knowledge exports are reference material for your own use; they are not used to train or fine-tune any model.

D. Email capture after a result

Leaving an email address is always optional and is never required to run a tool or download an export. When you do, the request records your email address, the purpose you selected, which tool you were using, your consent choices and the page path. The document, report or assumptions you were working on are not attached.

5. How information is used

• To respond to enquiries and prepare project discussions.
• To review and follow up on support requests.
• To operate public diagnostic tools and return requested reports.
• To route notifications into the existing lead-management workflow.
• To prevent spam, duplicate submissions, abuse and unsafe requests.
• To maintain, diagnose and protect the website.

MrUsman.com does not operate an automated system that makes legal or similarly significant decisions about public visitors.

6. Payment processing

The payment page asks for an agreed payment reference, payment type, USD amount and confirmation. The MrUsman.com handoff validates those values but does not store them in a local payment record. It then redirects you to a PayPal-hosted PayPal.Me page.

Card details, PayPal login credentials and payment authorization are handled by PayPal, subject to PayPal’s own privacy terms. The current website flow does not independently verify or display payment success.

7. Third-party services

• PayPal handles the hosted payment experience after you continue from the payment page.
• Hosting and infrastructure providers, including the current hosting provider, process requests and store website data needed to operate the service.
• Email delivery infrastructure carries notification messages generated by public enquiries and support submissions.
• Google Fonts is loaded from Google’s font servers, which means a request is made to Google when the shared site design loads those fonts.
• Google Analytics receives site usage data, but only if you allow analytics. It is not loaded otherwise.

WhatsApp, LinkedIn, Behance and other external destinations receive information only when you choose to open their links or otherwise interact with those services.

8. Advertising

This site does not currently show any advertising. No ad network, including Google AdSense, is active, and no advertising cookie or advertising identifier is set by MrUsman.com today.

If advertising is enabled in the future, this section will be updated first, before any ad is shown, to name the ad network involved and explain what it does. In general terms, that would mean: a third-party advertising provider such as Google may use cookies or similar technology to serve ads and to measure their performance; some of those ads may be personalised based on your prior visits to this or other websites, unless you have opted out; and you would be able to review or opt out of personalised advertising through Google’s Ad Settings and through www.aboutads.info. The consent choice described in Section 3 governs analytics only and does not by itself grant consent to advertising; a separate advertising consent choice would be added if and when advertising goes live.

9. Data retention

Lead records do not currently have a universal automatic deletion schedule. Information is kept for as long as reasonably needed to respond, maintain operational records, prevent abuse, protect the service, or meet applicable obligations. Tool caches are short-lived as described above, and hashed public-form rate records are pruned after 30 days.

A deletion request can be considered where applicable, but some records may need to be retained for security, operational or legal reasons.

10. Security

Reasonable technical and operational safeguards are used, including input validation, rate limits, duplicate controls, safe public-URL checks and restricted tool requests. No internet service can guarantee absolute security.

11. Your choices and rights

You may contact Mr Usman to ask about personal information you submitted, request a correction, request deletion where applicable, or ask to stop non-essential direct communication. A reasonable identity check may be required before acting on a request.

You can clear local or session storage through your browser. Depending on where you are located, local privacy laws may provide additional rights.

12. External links

The site links to external websites and services. Their privacy practices, content and security are controlled by them, not by MrUsman.com. Review their policies before providing information.

13. Changes to this policy

This policy may be updated when public features, providers or data practices change. The date at the top identifies the current published version.

14. Contact