Who is responsible?
This website uses the trading name TMJ IT Solutions and is aimed first at UAE businesses. The registered controller’s legal name, business address, and privacy contact have not yet been supplied. The demo Dubai map is not an office address.
The currently configured enquiry address is hello@tmgitsolutions.com. Its availability must be verified before live use. No Data Protection Officer or EU/UK representative has been appointed or identified on this site.
Information you choose to provide
The contact form asks for your name, email, optional business name, emirate/location, service interest, budget range, language needs, project brief, and interest in the proposed launch offer. Please do not include sensitive customer records, credentials, payment information, or unnecessary personal data.
The form prepares a mailto draft in your browser. Clicking Prepare my enquiry does not send it to a website backend. Opening your email app passes the draft to that application; it is sent only if you choose to send it there. Copying the brief writes it to your device clipboard, which may be managed or synchronised by your operating system.
Form values and drafts are held in page memory, not deliberately saved by this application to browser storage. They are discarded when the form is reset or unmounted. Browser autofill, session restoration, clipboard, and email-app storage are controlled separately by those tools.
Technical information and browser preferences
Serving pages necessarily involves network requests containing information such as an IP address, requested URL, and browser headers. Hosting, network, and email providers may retain security or delivery logs. The production providers, locations, logging configuration, and retention periods remain to be confirmed; this notice does not claim that no server logs exist.
A theme preference may be stored in localStorage. It contains neither your enquiry nor a tracking identifier. The homepage introduction uses no localStorage, sessionStorage, or cookies and replays on each visit, except when reduced motion is requested. Search and capability selection are processed locally; service and offer selections can also appear in the contact URL.
The current application includes no analytics tags, advertising pixels, session replay tools, account registration, payment checkout, or embedded third-party map. Fonts are served by the application through Next.js, not requested from Google Fonts by the visitor’s browser. The decorative map is a local SVG.
Purposes and legal grounds
If you send an enquiry, its intended purposes are to respond, understand your requirements, prepare a proposal, and manage any resulting business relationship. Technical processing supports page delivery, security, troubleshooting, and requested preferences. The offer checkbox expresses interest in a quote; it is not consent to marketing.
Where GDPR applies, processing necessary to take requested steps toward a contract may rely on Article 6(1)(b); business-contact correspondence or site security may instead require an assessed legitimate interest under Article 6(1)(f). Legal recordkeeping may rely on Article 6(1)(c). Optional marketing or tracking would need its own lawful basis and, where required, prior consent. The operator must validate and document the basis for each actual activity before launch.
Applicable UAE rules must be assessed independently, including federal personal data protection law and any relevant free-zone or sector-specific regime. This draft does not assume that a GDPR lawful basis automatically satisfies UAE law.
Recipients and international transfers
An email you send is handled by your email provider, the recipient’s email provider, and the authorised people responding to it. Hosting and technical suppliers process requests needed to deliver the site. Professional advisers or authorities may receive information where necessary and lawful. The actual supplier inventory and contracts have not been verified.
Providers may process information outside the UAE or, where relevant, outside the EEA/UK. Before live processing, the operator must identify the destinations, assess applicable transfer restrictions, and put suitable safeguards in place. This site does not assert that adequacy decisions, standard contractual clauses, or other transfer measures are already in place.
Retention and security
Enquiry emails should be kept only as long as needed for the enquiry, relationship, or applicable recordkeeping and dispute obligations. The exact enquiry, client, backup, and log retention schedule is not yet approved and must be completed by the operator.
Access restrictions, supplier controls, secure transport, and incident-handling procedures must be verified in the deployed service. No website can promise absolute security. Do not submit confidential production data through an initial enquiry.
Your choices and rights
You can choose not to send the prepared email, remove browser preferences, or ask the responsible controller about information it holds. Depending on the applicable law and circumstances, rights may include access, correction, erasure, restriction, objection, portability, and withdrawal of consent. Some rights have exceptions; withdrawal does not invalidate prior lawful processing.
For the GDPR-specific scope, deadlines, and complaint routes, see the GDPR & Data Rights page. The privacy contact must be verified before it is used as a live request channel. Supply only enough information to identify your request; do not email identity documents unless a justified secure verification process has been arranged.
Children, external links, and changes
This is a business-services website, not a service directed to children, and the enquiry form should not be used to provide children’s personal information.
External links, including OpenStreetMap, official legal resources, and your email application, have their own privacy practices. They are not loaded as embedded trackers by this application.
This draft must be updated when the controller details, suppliers, data uses, tracking tools, or legal requirements change. The review date identifies this draft’s revision date, not the date a legally complete policy took effect.