Informativa sulla privacy

Information submitted in a quote request

The quote flow collects the name, email address, company, delivery country, requested manufacturer and part, quantity, certification requirements and any equipment details or notes you provide. Optional PDF or image attachments are stored privately with the request. Requests are saved in the app’s database with a request reference. Do not include payment card information, passwords or unnecessary sensitive personal information in notes or attachments.

Why this information is used

The information is used to review and manage your sourcing request and clarify part compatibility, availability, delivery and warranty requirements. An email address is collected as contact information, but this website does not send emails or email confirmations. The on-screen reference is your record of submission.

Operational Google Chat alerts

New quote requests generate an operational alert in our private Google Chat workspace. The alert contains the request reference, company, part/brand, quantity, delivery country, and whether certificates or attachments were requested or supplied. Contact names, email fields, free-form notes and attachment contents are not included in these alerts; request details remain in password-protected administration. Administrator sign-ins and catalogue image updates also generate operational alerts. These business alerts are separate from optional browser analytics.

Cookies and preferences

Essential cookies remember your delivery country and privacy choices and support quote confirmation. A separate functional session cookie protects signed-in administration. These are not a substitute for records stored on the server. Removing a cookie does not delete a saved quote request. You can accept or reject optional browser analytics and change or withdraw that choice at any time using Cookie preferences in the footer.

Optional browser analytics and session replay

Only after consent, first-party browser analytics record page paths without query strings, pseudonymous visitor and session identifiers, referrer host, broad device category and engagement time. Stored first-party identifiers are hashed on our server. These counts describe consented browser identifiers, not verified unique people. OpenReplay session replay is also consent-gated and configured in private mode to mask page text and ignore input values. Quote forms and administration pages are not replayed. Session replay data is sent to the configured OpenReplay ingestion service at d3.dev.opsima.com. Rejecting or withdrawing consent stops optional browser tracking. Do Not Track and Global Privacy Control signals are respected.

Google Analytics 4

On opsiparts.com, Google Analytics 4 (G-6X2Q2DRCRV) loads only after you accept analytics cookies. It is not loaded before consent, on preview/development hosts, on pages with query strings (including catalogue searches), or on quote and administration pages. We supply page locations without query strings or fragments and only the referrer origin; we do not send quote form contents, names or email fields. Advertising storage, advertising personalization and Google Signals are disabled. Google may process consented visits, device/connection information and first-party analytics cookies according to Google’s privacy policy. Withdrawal disables further Google collection, removes this integration’s analytics cookies and reloads the page without optional tags.

Country and language preferences

The site can suggest a region using the CDN’s coarse country estimate or, when unavailable, browser language/region settings. It does not request precise device location. Automatic country preferences are stored for up to one day; an explicit country/language choice is stored for up to one year and takes precedence over later location estimates. These functional preferences remain available when analytics are rejected.

Server-side request statistics

Operational server request logs and aggregate page-request statistics are separate from optional browser analytics. Server page views can include bots, reloads and repeated requests and must not be interpreted as unique people. Availability of historical data depends on the hosting platform’s retained logs.

Access, infrastructure and sharing

Submitted requests are stored on the app’s hosting infrastructure for request handling. The hosting platform may also record technical request logs. Do not assume a particular country of storage, fixed deletion period or independent privacy certification: none is specified here. Any disclosure needed for supplier quotation, fulfillment or warranty handling must be assessed and explained by the operator for the actual transaction.

Privacy requests and retention

To ask about access, correction or deletion, use the contact request flow, mark the notes as a privacy request and include the relevant request reference. Avoid repeating information that is not needed to identify the request. The operator must verify the request and assess any legal recordkeeping duties. No automatic deletion schedule is promised by the current site.

Status of this notice

This draft describes the built-in request flow, not a complete jurisdiction-specific compliance statement. A verified legal entity, direct privacy contact, lawful bases, actual recipients, international-transfer arrangements and retention rules need to be supplied and legally reviewed for the live business.