INPUT-01Submitted fields
Name, company, business contact details, country, material, SKU context and message are stored when supplied. Limited referral, visit, device and security signals support the record.
AcuPep data-handling protocol
Effective 25 August 2026. This protocol describes the data boundary for registry visits and qualified inquiry submissions.
USE-02Authorized purposes
Data is used for response, quotation, evidence matching, security, operational history and aggregate performance measurement. Inquiry data is not sold.
SCOPE-03Processing boundary
Authorized staff and contracted infrastructure providers may process data for these purposes. Centralized administration may be used while preserving the originating site identifier on every record.
CTRL-04Retention and control
Browser storage holds visitor and session identifiers. Records are kept only as long as reasonably needed for response, security, operations or legal duties. Applicable access, correction and deletion requests may be submitted by email.
SESSION-05Draft and message state
Unsubmitted inquiry data is retained in session storage within the active browser tab, then removed after a successful submission or at the end of that tab session. The visitor identifier scopes any private follow-up thread to the recognized browser.
EVENT-06Telemetry boundary
AcuPep uses first-party telemetry and Google Analytics 4 for page views, controlled CTA use, searches and successful inquiry journeys. Google Signals and advertising personalization are disabled. Analytics events exclude inquiry field contents, business contact values, inquiry references and copied text.
CONTROL CHANNEL: info@acupep.com. Include the inquiry reference when available.