OpenAI advertising measurement

    Allow OpenAI to measure page views and completed contact requests, including a hashed email address and, when available, a hashed customer ID from your contact record for matching? The contact form works either way. Your choice applies only to OpenAI advertising measurement. Privacy notice

    Change this choice any time using Advertising measurement settings in the footer.

    Emergency TriageExperiencing system crashes, corrupted TPS files, or sudden developer departure?
    Privacy notice

    A clear account of messages and site usage.

    This notice describes the information collected by the Clarion Programming Help contact form, page-usage and ad measurement, and the embedded YouTube video on the homepage.

    Last updated: November 6, 2026

    01 / The form

    Information the contact form collects

    If you choose to send a message, the form collects the information you enter. The current fields are:

    • Name
    • Email address
    • Company, optional
    • Message

    02 / Site usage

    Analytics and page usage

    Google Analytics loads immediately on every public page, including when you move between pages on this site. It may use cookies or similar identifiers and receives general page-usage information, such as page views, the page URL, browser and device details, and referring context. This helps us understand how the site is used and where visitors arrive from.

    Google Analytics receives page-view information, and the site does not add custom Google Analytics events. The site does not put the name, email address, company, or message content from the contact form into analytics event data. Contact-form information is handled through the separate contact flow described in this notice.

    The OpenAI Ads pixel loads on public pages. With your permission, it can record page views and completed contact requests to measure advertising. The site does not add form fields to pixel event parameters. OpenAI may also receive browser, device, and connection information through the pixel, and automatic advanced matching may detect and hash supported information if enabled in OpenAI Ads. Read OpenAI’s Privacy Policy for more information.

    If you allow OpenAI advertising measurement and complete the contact form, we also send a server-side lead event to OpenAI. We trim and lowercase your email address and convert it into a SHA-256 hash before sharing it for matching. When available, we also trim the customer ID from your contact record and convert it into a SHA-256 hash before sharing it for matching; the ID retains its original letter case. The event may also include OpenAI's browser and ad-click reference identifiers when available, the time and a unique event ID. We do not send your name, company or message in that event. The browser and server events share an ID so OpenAI can deduplicate them. We attempt the server event first; if it cannot be delivered, the browser event may be received without the email or customer ID hash.

    Your choice is stored in your browser. If you allow measurement, the pixel may use first-party OpenAI browser and click-reference cookies. When you withdraw permission, the pixel is told to stop measurement and remove those cookies, and this site stops new OpenAI measurement and retries for the affected submission. Withdrawal cannot recall events already sent. The site keeps a short-lived signed receipt in memory during delivery and retries; it contains a hashed email, a hashed customer ID when available, and measurement identifiers, not your message.

    More information is available in Google’s Privacy Policy.

    03 / The purpose

    How the information is used

    The information is used to understand the situation described in your message and to respond to your enquiry. It is also used to maintain the contact record and support the next practical conversation.

    • Respond to the email address you provide.
    • Understand whether the request concerns developer support, an urgent issue, an integration, or phased modernization.
    • Save the submission in the project Contacts/CRM record, including the company and message in the contact notes.
    • Log a clarion_contact_request event for the submission.
    • Send a notification to mike@sterlingdata.com. The visitor email is set as the reply-to address for that notification.

    04 / The handoff

    Service-provider sharing

    To operate the current contact flow, the information is transmitted through service providers that host the site, save the contact record, and deliver the owner notification email. Those providers receive the information needed for those functions. This notice describes the functions involved without naming providers that are not identified in the current site experience.

    The homepage also includes an embedded YouTube video. When the player loads or is played, your browser connects to YouTube, which may receive device, connection, and usage information. See Google’s Privacy Policy for more information.

    The contact flow described here is limited to the contact information and message you submit, the Contacts/CRM record, the contact event, and the owner notification described above. Page-usage and ad measurement are described separately in the Analytics section.

    05 / Your choices

    Choices and requests

    You choose whether to submit the form. The company field is optional. If you have already sent a message, you can email mike@sterlingdata.com to ask a question about the information associated with your contact record, request a correction, or request that the record be deleted. Include enough context for the record to be located.

    Use Advertising measurement settings in the footer to allow or withdraw permission for OpenAI advertising measurement at any time. You can submit the contact form without allowing it. This choice does not control Google Analytics or YouTube. Your light or dark display preference is also saved in your browser so it can be remembered on future visits.

    06 / A plain limitation

    Security

    Online forms, email, and hosted services cannot be treated as guaranteed secure channels. Please do not include passwords, credentials, payment details, private source code, or other sensitive material in the contact form. If more sensitive information is needed to understand a support request, discuss an appropriate transfer method first.

    07 / Keeping this current

    Updates to this notice

    This notice may be updated when the contact flow, analytics setup, or the way submitted information is handled changes. The date at the top shows when this version was last updated. Please check the current notice before sending information if that detail matters to you.

    Questions about privacy

    Ask before you send.

    For questions about this notice or a contact request, email mike@sterlingdata.com.

    Return to the homepage