Clear about the data
behind every interaction.

Cookies and similar technologies

Cookies are small text files stored on your device. We use cookies and local storage to keep the website functioning, protect forms and sessions, remember your privacy choices, understand website usage, and—where you provide permission—measure relevant marketing activity.

Cookie categories

• Necessary: required for security, WordPress functionality, forms, sessions, and saving privacy choices. These cannot be disabled through our consent controls where the website depends on them.
• Analytics: help us understand visits, pages viewed, device information, and actions taken on the website. Google Analytics 4 is used only after the applicable consent choice.
• Advertising: may measure advertising performance and support remarketing through Google advertising services, only after the applicable consent choice.

Google Analytics website measurement

When analytics consent is granted, Google Analytics 4 may use first-party identifiers such as the _ga cookie to distinguish visitors and sessions. Measurement may record page views and actions such as successful form submissions, WhatsApp, telephone, email, certificate, webinar, and product interactions. We configure analytics not to send contact-form contents, telephone numbers, email addresses, certificate credentials, or other deliberately entered free-text values to Google Analytics.

Your cookie choices

You can accept all optional cookies, reject them, or manage analytics and advertising preferences separately. Select the Privacy choices button displayed on the website to change your choice at any time. Your preference remains on your device until you change it or clear your browser storage.

Information you provide

Depending on the form or communication channel, we may process your name, organisation, role, work email, telephone or WhatsApp number, city, submitted message, application area, selected workflow, career information, and the source page of the request. We use this information to respond, provide requested resources, coordinate technical or commercial follow-up, support calibration or certificate enquiries, and manage recruitment communications.

Service providers and data sharing

We may use service providers for website hosting, security, analytics, communications, advertising, and authorised internal analysis. These may include Google services and an authorised OpenAI Codex workspace used by Intralab personnel. Google API data is processed there only when an authorised Intralab user requests an internal analysis. We do not sell personal data, Google user data, or OAuth credentials, and we do not allow service providers to use them for their own advertising purposes.

Internal Google API and OAuth access

Intralab uses an internal application called Intralab Codex MCP to analyse data owned by Intralab through Google OAuth 2.0. It connects to:

• Google Search Console using webmasters.readonly to read verified-site search performance and indexing information.
• Google Analytics 4 using analytics.readonly to view and download analytics reports and property information. It cannot create, edit, or delete Analytics data or settings.
• Google Ads using the Google Ads adwords OAuth scope. Google provides no separate read-only Ads scope; Intralab therefore limits the installed MCP to account listing, GAQL reporting queries, and metadata tools. Campaign-creation, editing, and deletion tools are not exposed in our local MCP configuration.

The data is used solely for Intralab's internal website, SEO, content, conversion, and campaign-performance analysis. It is not used to build advertising profiles for third parties.

OAuth credential storage and security

OAuth client credentials and access or refresh tokens are stored in credential files on an authorised local device used to operate the integration. Access is restricted to the authorised operating-system user. Credentials and tokens are not stored in public WordPress content or a public source-code repository. Google API connections use encrypted HTTPS/TLS transport. Report results may be displayed in the authorised internal workspace or saved locally when an Intralab user explicitly requests an analysis.

Google API Services User Data Policy

Intralab's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is accessed only for the disclosed internal analytical functions, with the minimum access reasonably required.

Retention, deletion, and revoking access

We retain information only for as long as reasonably required for the purposes described here, business records, security, and applicable legal obligations. OAuth tokens are retained while the internal integration is authorised. You can revoke the integration through Third-party connections in your Google Account. To request deletion of stored tokens or data associated with the integration, use our Contact us page or email [email protected] and identify the message as a privacy or data-deletion request.

Your privacy rights

Subject to applicable law, you may request information about, correction of, or deletion of personal data associated with you. We may need to verify your identity and the relevant interaction before completing a request.

Changes to this policy

We may update this policy when our website, analytics, advertising tools, internal integrations, or legal obligations change. The latest version will be published on this page with its last-updated date.