Privacy Policy | Automatrix Engineering

Introduction

Automatrix Engineering ("we", "our", or "us") provides industrial engineering, automation, SCADA, IIoT, and energy-intelligence services. This policy explains how information is handled when you browse the website, use the PV-DG estimator, submit a technical assessment, upload a document, or contact our team.

Information You Choose to Provide

When you submit an enquiry or technical assessment, we may receive your name, company, business email, phone number, city, service requirement, operating details, and any technical documents you choose to upload. Estimator inputs remain in the browser until you explicitly submit an assessment.

Essential Website Functions, Attribution and Coarse Journey Context

Essential functions include security, rate limiting, form processing, session reliability, bounded first-party campaign attribution, and a limited first-party journey record. Campaign parameters such as UTM values and advertising click identifiers may be stored in your browser for up to 90 days.

The journey record contains only approved coarse events such as estimator viewed, estimator completed, report prepared, form section completed, contact path selected, repeat visit, or technical attachment provided. It does not contain form values, estimator values, file names, identity fields, message text, precise location, or device fingerprint data.

Campaign attribution and coarse journey context are not persisted in our lead database until you explicitly submit a form. At submission, they may be attached to that enquiry so we can understand its source and apply a transparent rule-based engagement score.

Lead Prioritization

The engagement score is capped at 100 and every contributing factor is visible to authorized administrators. Repeated events do not add duplicate points. The score is a workflow-prioritization aid, not an automated eligibility, credit, employment, pricing, or contractual decision.

Names, company, email, phone, city, address, free-text messages, sensitive traits, precise location, and protected characteristics do not contribute to the score. Administrators remain responsible for reviewing the actual engineering requirement and contacting the customer fairly.

Optional Measurement

Google measurement, Microsoft Clarity, Cloudflare Web Analytics, and anonymous engagement events are optional. They load only after you choose Allow measurement. You can continue using the website with Essential only and can change the choice through the Privacy settings control.

Optional events use a random first-party session identifier that lasts only for the browser session. We do not create a device fingerprint. Event payloads are restricted to coarse labels such as estimator started, report printed, form step completed, or contact method selected.

We do not send names, email addresses, phone numbers, city, company, free-text messages, estimator values, uploaded files, precise location, or full query strings to advertising analytics.

How We Use Information

Respond to enquiries and arrange technical discussions.
Prepare quotations, engineering proposals, and project scope.
Review submitted SLDs, load profiles, fuel logs, and other technical documents.
Protect the website and prevent abuse or duplicate submissions.
Prioritize explicit enquiries using transparent coarse engagement factors.
Measure anonymous website and campaign performance when permission is granted.
Improve estimator usability and the industrial-service journey.

Retention

Privacy preference: retained in first-party browser storage until you change it or the consent version is replaced.
Anonymous measurement session ID: retained only for the current browser session.
First-touch/latest-touch campaign attribution and coarse browser journey: automatically expire after 90 days.
Optional measurement events: policy maximum of 14 months; provider settings must be kept consistent with this limit.
Enquiries and submitted technical attachments: scheduled for retention review 24 months after submission or the latest review, unless required for an active project, quotation, warranty, contractual, accounting, legal, or security purpose.
Secure post-submission upload token: expires after 24 hours.

Authorized owners can record a retention review, request deletion, cancel a deletion request, and permanently delete a lead with its private PV-DG attachments. These actions require explicit confirmation and create a bounded audit record that excludes contact details and message text.

Security and Access

Technical attachments are stored outside the public web root and are not given public download URLs. Lead intelligence is restricted to authorized administrators; permanent deletion and retention controls are owner-only. We use rate limits, signed upload tokens, file validation, restricted storage permissions, role-based access, and audit logging.

Location

We do not enrich analytics or lead scores with precise or coarse server-side location. Any future location enrichment requires a documented privacy and legal review before implementation.

Your Choices and Rights

You may use the website with Essential only, change measurement consent, request access or correction, ask for deletion where applicable, or object to marketing communication. A deletion request may be limited where retention is required by law, contract, security, or an active project.

Contact

Website Privacy Controls

The following controls apply even when an administrator has supplied customized policy text:

Essential only: security, form delivery, service-worker reliability, bounded first-party campaign attribution, and PII-free coarse journey context remain available.
Explicit submission boundary: attribution and journey context are persisted with a lead only after a form is submitted.
Transparent score: every point comes from an approved coarse factor; repeated events do not add duplicate points and identity, message, sensitive-trait, and location fields are excluded.
Allow measurement: consent-gated Google measurement, Microsoft Clarity, Cloudflare Web Analytics, and coarse anonymous engagement events may load.
No fingerprinting: the anonymous session identifier is randomly generated and does not use device, network, browser, IP, or behavioral fingerprint signals.
No form-content analytics: names, emails, phone numbers, city, company, messages, estimator inputs, files, precise location, and full query strings are blocked from optional event payloads.
Change your choice: use the Privacy settings control shown on the website after a preference has been saved.

Privacy-control implementation last reviewed: August 4, 2026.