DATOS DE SOLICITUDES

Aviso de privacidad.

Este aviso explica cómo MAR&PET utiliza los datos enviados mediante los formularios de oferta, colaboración y Vision 3D.Version: 26 September 2026 · GDPR / Legea 190/2018 · contact and product analytics 2026.09

The sections below are provided in English.

01

Controller and contact

The controller for this website is MAR & PET GRUP S.R.L., fiscal ID 15455744, trade-register number J2004001290293, EUID ROONRC.J2004001290293. Its registered office is 41 Școlii Street, Drăgănești village, Drăgănești commune, 107210, Prahova, Romania. Privacy requests may be sent to partener@marpet.ro. See company information.

02

What we collect and why

We process the contact details, project description, page and campaign attribution, and—when used—the validated Vision 3D technical snapshot you submit. The purpose is to review your request, contact you, prepare a quotation, maintain a reliable Lead ID audit trail and measure platform-originated opportunities. We do not use a request as a marketing subscription without separate consent.

03

Legal bases and required information

For an individual asking about a potential contract, we use information supplied in an enquiry to take steps at that person’s request (GDPR Article 6(1)(b)); without contact details and a description we cannot respond. For business representatives and limited security, abuse-prevention and lead-audit data, we rely on the legitimate interest in answering enquiries and protecting the service (Article 6(1)(f)), subject to your rights. Optional product and contact-click analytics use your separate consent (Article 6(1)(a)), which you may refuse or withdraw. Contractual, accounting or legal records are processed where a legal obligation applies (Article 6(1)(c)). Romanian Law 190/2018 supplements the GDPR where applicable; it does not replace these grounds. There is no solely automated decision with legal or similarly significant effect: Mara and Vision 3D do not approve offers, prices or technical feasibility.

04

Lead ID and returning-visitor key

Each accepted request receives a unique Lead ID whether or not optional analytics is accepted. Only after optional consent, a first-party, HTTP-only pseudonymous cookie may be retained for up to 24 months to link later enquiries. After refusal, the enquiry still works without this cookie. The database stores only a one-way fingerprint, not its raw value.

05

Who receives the data

Operational notifications are sent to the approved MAR&PET and PXP500 recipients responsible for commercial follow-up and reporting. Infrastructure providers include Supabase for the lead register and authentication, Cloudflare for network delivery, Hetzner for application hosting, and Resend for transactional email.

06

International processing

The lead database is hosted by Supabase. Transactional notifications sent through Resend include the lead’s contact and request content as well as delivery metadata; Resend may process this information in the United States under its contractual transfer safeguards. Strict EU-only processing is therefore not claimed for the current notification path.

07

Optional analytics: product journeys and commercial contact clicks

Only if you accept optional analytics, content-free lifecycle events record the product, language, an allowlisted step and a random first-party browser UUID. The UUID contains no account or contact data, stays in localStorage for no more than 30 days, and is then rotated; the server stores only a separately domain-separated HMAC. Reports count active pseudonymous browser clients, sessions and sessions per client. These are not people or accounts: one person can be counted on several browsers or devices, several people can share a browser profile, and clearing storage creates a new client. We may also record activation of an explicitly marked commercial email or telephone link. That event contains the channel, selected MAR&PET contact, link placement, pathname, language, limited UTM values and time. Neither telemetry path contains your message or call content, email address, telephone number, full URL, referrer, raw IP address, User-Agent or the cookie key used for leads. A separate one-way rate-limit token derived from the network address is retained for no more than 48 hours and is never shown in the report. A click indicates contact intent only: it does not prove that a message was sent or a call was made and does not create a Lead ID, commercial alert or marketing subscription. Contact-click events and content-free product telemetry have an approved 90-day retention period. You may decline or withdraw permission at any time from Analytics settings without affecting product use or contact links.

08

Retention

The attribution cookie is kept for no more than 24 months. Prospect lead records with personal data have an approved retention period of 365 days from their latest recorded activity. Converted or won customers follow the separately applicable contract, dispute, accounting and legal-obligation periods.

09

Your choices and rights

You may request access, correction, deletion, restriction, portability where applicable, or object to legitimate-interest processing, and may withdraw consent where it is the applicable basis. You may complain to the Romanian supervisory authority, ANSPDCP, or another competent authority. Withdrawing consent does not affect processing already performed lawfully. Our cookie policy explains browser storage and how to change analytics consent.

10

Security and data minimisation

Access to the lead register is restricted to five approved identities with role-based permissions and an immutable event trail. Vision 3D submissions store a reduced technical snapshot; locally selected photographs and raw editor history are not included in the lead record.

11

Tu conversación con Mara

Mara conserva localmente un máximo de 24 mensajes, separados por idioma y pestaña. La sesión caduca y se elimina automáticamente en 24 horas; «Nueva conversación» la elimina de inmediato.

Solo con la IA del servidor activa pueden enviarse a OpenAI el mensaje y el historial reciente. Antes de la moderación y generación se sustituyen automáticamente patrones detectables de nombre declarado, correo, teléfono, dirección y código postal. La redacción es una protección adicional y no garantiza anonimizar cualquier texto libre: no introduzcas datos personales. Las solicitudes usan store: false. La dirección de red se convierte en un HMAC efímero y se elimina en 60 segundos; la dirección original no se almacena.

Antes de generar la respuesta, el mensaje y el historial reciente proporcionado por el cliente pueden ser revisados por el servicio de moderación de OpenAI. Las líneas marcadas se eliminan del contexto enviado para la generación. Para los controles de seguridad, una cookie first-party HttpOnly contiene un UUID aleatorio, está limitada a /api/mara y se conserva un máximo de 30 días; OpenAI recibe solo un HMAC derivado, nunca el UUID original, la dirección de red del visitante ni el User-Agent del navegador. Cuando el servicio interno de medición está activo, la telemetría sin contenido incluye el ciclo de sesión, idioma y paso permitido y, para llamadas de IA, operación, estado, modelo, versión del prompt, latencia exacta y tokens. El coste solo aparece con una tarifa versionada configurada; si no, figura como «neinstrumentat». El identificador de sesión se transforma con HMAC y no se almacenan mensajes ni historial. Con consentimiento para análisis opcionales, un UUID aleatorio first-party del navegador se guarda en localStorage y rota en un máximo de 30 días; el servidor conserva solo un HMAC separado. Mide clientes de navegador seudónimos activos y sesiones por cliente, no personas ni cuentas, y una persona puede aparecer varias veces en distintos dispositivos. La política aprobada conserva la telemetría sin contenido durante 90 días.

Los datos de contacto del formulario de oferta no se copian automáticamente en la conversación. El contexto de página enviado para el análisis incluye solo una ruta pública permitida, sin parámetros URL ni el fragmento después de #.

El campo en lenguaje natural de Vision 3D se interpreta primero de forma local. Solo si está activo el refinamiento opcional con IA, la solicitud redactada y una configuración técnica reducida pueden enviarse a OpenAI con store: false; se excluyen los datos de contacto y las imágenes, y el modelo no puede imponer valores técnicos autoritativos.