Effective date: 15 July 2026.
This notice explains how the OreLynx marketing website handles technical request data, business-enquiry information and optional analytics. Product and customer-data processing is governed separately by the applicable customer agreement and deployment privacy terms.
The origin, hosting and content-delivery services receive request information such as IP address, request time, requested URL, referrer, user-agent string and security events. This information is used to deliver, protect and troubleshoot the website and is retained according to the operating provider's security and log-retention settings.
The assessment form asks for contact details and qualification information that you choose to submit. It posts to https://payment.cisin.com/cis-leads/leads.php for routing into the CIS lead-management process and a background confirmation message.
The information is used to understand your request, qualify product fit, respond, prepare a scope and maintain the business relationship. Access is limited to people and systems involved in those purposes. Retention follows the applicable sales, legal and operational record requirements.
The release site loads Google Tag Manager container GTM-NVJGDB9Q without an analytics-choice popup. Tags configured in the published container may create analytics requests, cookies or other browser storage. Preview builds omit live tags.
The assessment form includes controlled source, campaign, form and content identifiers in the CRM submission. Names, email addresses, phone numbers, messages and workflow answers must not be sent through the analytics data layer.
The authenticated OreLynx application is a separate surface at web.orelynx.com. Its customer-data categories, account processing, cookies, infrastructure, subprocessors, locations, retention, deletion, security controls and contractual roles are defined for the selected customer deployment.
You may ask about access, correction, deletion, restriction, objection or another applicable privacy right. Use the assessment form, choose the closest enquiry type and begin the message with “Privacy request.” We may need to verify identity and authority before acting on a request.