1. Scope
This draft explains the intended handling of information submitted through the OEMerge website, particularly an industrial AI visibility benchmark request. It does not replace jurisdiction-specific legal advice.
2. Information intended to be collected
The request forms may collect name, work email, company, company website, country or region, role, primary goal, priority capability and an optional message. When a visitor submits a form, the form may also include the landing path, detected referral category, supplied UTM source, medium and campaign, plus a self-assessment score and weakest dimension where applicable. The first step does not request a phone number, budget, employee count, drawing or confidential manufacturing file.
3. Intended purposes
- Respond to a benchmark or service inquiry.
- Assess whether the company and requested scope are a reasonable service fit.
- Prevent spam, secure the website and diagnose submission problems.
- Measure aggregate landing-page, CTA, form-start and form-submit behavior after consent and configuration where required.
4. Legal basis
The operator must define and disclose the applicable legal basis before launch. Depending on jurisdiction and purpose, this may include taking steps at the requester’s direction before a contract, legitimate interests or consent.
5. Service providers and transfers
Inquiry forms are sent to a same-origin server function and stored in the operator's PostgreSQL inquiry database. The operator must list the production hosting and database providers, their roles, retention and cross-border transfer mechanisms before launch.
6. Retention
No retention schedule has been provided. Before launch, the operator must define how long inquiry records, spam logs, analytics events and commercial correspondence are retained and how deletion is applied.
7. Rights and choices
Depending on location, individuals may have rights to access, correct, delete, restrict or object to processing, and to withdraw consent. A verified privacy contact must be added before data collection begins.
8. Analytics, cookies and local storage
See the Cookie Notice. Google Analytics receives page views and interaction events but is not intentionally sent form-field values or individual assessment answers. The site also uses session storage to preserve first-touch landing and campaign labels during the current browser-tab session, including recognized AI or search referral categories. Assessment answers remain in the page; the calculated score is attached only if the visitor submits the optional review form.
9. Contact
The owner must add a verified legal entity, postal address and privacy contact before production. Until then, do not use this draft site to collect personal information from the public.