Your details deserve careful handling.

1. Who handles your information

Wizard Business Support is based at Main Street, Town Center, Al Ain, Abu Dhabi, United Arab Emirates. For privacy questions or requests, email [email protected] with “Privacy request” in the subject line.

2. Information we collect

If you use the contact form, we collect your full name, email address, the company name you choose to provide, the service category you select, and the message you send. You must also actively select the required privacy acknowledgment to submit the form. The server validates that choice, but the checkbox value is not stored separately in the inquiry table; the table contains the inquiry fields and its submission timestamp.

The marketing checkbox is optional and separate from the privacy acknowledgment. If you select it, we record a separate subscription request with your email, name, request time, confirmation status, and any later unsubscribe time. A confirmation token is stored as a hash rather than as the original token. An inquiry alone does not create a marketing subscription.

Our hosting or security provider may also process ordinary technical request information, such as an IP address, browser details, requested page, and request time, to operate and protect the website. The exact logging depends on the active hosting configuration. Please do not put passwords, payment details, or other sensitive account information in the form.

The current in-site traffic report counts allowlisted public-page views in aggregate. The browser sends the page path and transient referrer information so the server can classify each view into one broad source category: direct, search, social, referral, or internal. The database stores only the UTC date, public page path, broad source category, and page-view count. Localhost and Manus Preview visits are excluded.

The current collector does not set or read analytics cookies or browser identifiers and does not estimate unique visitors or sessions. It does not store raw IP addresses, raw user-agent strings, referrer hostnames, full referrer URLs, query strings, device categories, country codes, or traffic linked to inquiry, subscriber, or campaign records. The referrer is used transiently to assign the broad source category and is not persisted.

A previous consent-based version may have saved an analytics choice cookie and browser identifier and may have written HMAC visitor hashes, hostname-only referrers, coarse device types, and country totals. The current collector ignores those old browser values and does not add to or query the consent-era traffic tables. Old browser values or database records may remain until cleared by the visitor or under the owner’s database-retention process. The control in section 7 can clear this browser’s old values and request deletion of its matching visitor-hash records; it does not delete aggregate page-view history.

3. Why we use it

We use inquiry details and your affirmative acknowledgment to accept, review, and answer your request, discuss a possible scope, and manage a business relationship if you choose to proceed. When the email service is configured, we use your email address to send the requested inquiry acknowledgment. The contact form does not automatically subscribe you to a marketing list.

We use an optional marketing request only to send a separate confirmation email. You are not subscribed unless you affirmatively confirm through that link. Only confirmed, active subscribers may receive marketing campaigns; existing and new inquiries are never added automatically. You can unsubscribe at any time using a campaign link or one-click unsubscribe control.

We may use information to protect the website, address misuse, or meet legal obligations. We do not use the form to make automated decisions about you.

Aggregate traffic statistics help us understand public-page views by UTC date, popular page, and broad source category. They are page-view counts, not counts of unique visitors or sessions. Traffic measurement is separate from optional marketing consent and is never used to add a person to a marketing list.

4. Service providers and sharing

Inquiry records are stored in the website’s MySQL database and processed by the hosting provider that runs the site. When configured, Brevo SMTP receives your email address and the name and service category used in the acknowledgment. Authorized people who handle inquiries may also access the information.

When configured, Brevo SMTP also processes the address and message information needed to send an optional subscription-confirmation email, an individual reply, or a campaign to a confirmed subscriber. Campaign emails are sent individually; recipient addresses are not displayed to other recipients.

We do not sell contact-form information. We may disclose information where required by law or where reasonably necessary to protect rights, safety, or the security of the service. If our hosting or email providers change, we will update this notice when the change materially affects how information is handled.

Current traffic aggregates (UTC date, allowlisted public page path, broad source category, and count) are stored in the website’s MySQL database and are not sent to Brevo. Consent-era dimension and visitor-hash records from the earlier version may still be present in separate tables, but the current report neither reads nor updates them. Hosting, proxy, and security providers may separately keep operational access logs as described above.

5. Retention

Inquiry information should be kept only for as long as reasonably needed to respond, manage any resulting business relationship, maintain appropriate records, or meet legal obligations, then deleted or de-identified subject to legal requirements and backup-retention practices. The appropriate period depends on whether an inquiry becomes an engagement; this notice does not promise a fixed number of days. The business must confirm and follow an actual retention and deletion process for its production database and backups.

Subscription and delivery records may be retained as reasonably needed to honor confirmation and unsubscribe choices, prevent further marketing after an opt-out, maintain appropriate records, or meet legal obligations. No fixed marketing-data retention period is promised.

Aggregate traffic counts should be kept only as long as reasonably useful for operational reporting and should be covered by the owner’s database and backup-retention process. This notice does not promise a fixed retention period. The current collector does not create browser identifiers or visitor hashes.

The current traffic table contains daily aggregate counts rather than visitor-level records. The business should review and apply an appropriate retention period for those summaries and its database backups.

The current report again reads the original aggregate `site_traffic_daily` table so its existing counts can remain visible. Separate dimension and visitor-hash tables created by the earlier consent-based version are not read or updated by the current report; those historical records may remain until the owner chooses a documented retention or cleanup approach.

6. Security and provider locations

Application safeguards include server-side field validation and parameterized MySQL queries. Brevo SMTP connections require TLS. The production operator must separately configure and verify HTTPS for visitors, database network and account restrictions, protected environment-file permissions, firewall rules, backups, and security updates for the active host. No internet transmission or storage method can be guaranteed completely secure.

The country in which information is processed depends on the hosting, database, and email configuration in use. If providers process information across borders, applicable transfer requirements must be considered for the actual deployment. Contact us if you need current provider or location details before sending information.

7. Cookies and similar technology

The public traffic collector does not set or read an analytics cookie, require a consent popup, or use a browser identifier. A visitor who used an earlier version may still have its consent cookie or local-storage value; the current collector ignores those old values. Use the control below to clear those browser values and request deletion of matching HMAC visitor hashes. The owner-only admin panel separately uses a signed, HttpOnly session cookie to protect inquiry and subscriber-management functions. Hosting or security services may use separate essential technical logs or identifiers to operate the site safely.

If you used the earlier consent-based analytics version, use this control to clear its local choice and request deletion of any matching visitor-hash records. It does not clear aggregate page-view counts:

8. Your privacy requests

Depending on the law that applies to you and the circumstances, you may be able to ask for information about how your data is used, request correction or completion, request erasure, ask for processing to be restricted or stopped, object to certain processing, or request a portable copy. Some rights have legal conditions or exceptions. We may need to verify your identity before responding.

You may withdraw a marketing choice at any time using the unsubscribe link or one-click control in a campaign email. Unsubscribing stops future marketing campaigns; it does not erase an inquiry or a separate service relationship.

Send a request to [email protected]. We will review it under applicable law and explain if we need more information or cannot complete part of the request.

9. Children and updates

This business-support website is intended for business inquiries, not for children. If you believe a child has submitted information, contact us so we can review and address it. We may update this notice when our practices change; the date at the top shows the latest revision.

10. UAE privacy information

Where applicable, our handling of personal information is subject to relevant privacy laws. The UAE Government summarizes Federal Decree-Law No. 45 of 2021 and its data-protection framework on its data protection laws page. The official legislation text is available from the UAE Legislation portal. The applicable regime can depend on the business’s licensing, location, and activity; this notice does not replace legal advice.