Subprocessors - website & marketing
Description of Personally Identifiable Information (PII) data processing and subprocessors
This page lists third parties (“subprocessors”) that may process personal data when you use the SentiOne marketing website (including its blog), and when you submit a contact/demo/newsletter form.
Some services are used only if you interact with a feature (e.g., play an embedded video, use live chat, click a recruitment link). Some services are used only if you consent to optional cookies/technologies, where required by law. The exact set of subprocessors can therefore depend on your choices and the page you visit.
Personal data categories (examples)
Depending on what you do on the site, we may process:
- Online identifiers & usage data: IP address, cookie identifiers, device/browser information, language, page URL/referrer, timestamps, interactions (e.g., clicks).
- Contact/lead data (forms): name, email address, phone number, company name, message content, and your consent choices (where applicable).
Subprocessors used for website measurement, marketing and support
| Subprocessor | When it is used | Scope of personal data | Purpose |
|---|---|---|---|
| Google Tag Manager (Google) | When you browse the website (subject to configuration and, where applicable, your cookie preferences). | Online identifiers and usage data; website event data. | Manage and deliver measurement/marketing tags and website events. |
| Constant Contact (Marketing Automation) | When you browse the website (subject to configuration and, where applicable, your cookie preferences). Some campaign pages may load additional marketing-automation components. | Online identifiers and usage data; may also receive form/lead data depending on configuration. | Marketing automation, visitor tracking, attribution and campaign measurement. |
| Intercom | When you use the website’s live chat/support feature, and when we route certain form requests to customer communication tools. | Online identifiers; contact data and conversation content if you start a chat or we contact you. | Customer support chat and customer communication management. |
Subprocessors used for forms and lead management (server-side)
When you submit a contact/demo/campaign/newsletter form, we use a dedicated backend service to receive the submission and process it. This backend may use the following subprocessors:
| Subprocessor | When it is used | Scope of personal data | Purpose |
|---|---|---|---|
| Hetzner (hosting) | To host the website services and databases used to process website and form data. | Any personal data processed by the hosted services (e.g., form submissions, attribution data). | Hosting and managed infrastructure. |
| Intercom | When a submission should create/update a contact/lead and/or create a conversation for follow‑up. | Contact data (name, email, phone), message content, and related metadata needed for follow‑up. | Customer communication and support workflow. |
| Pipedrive | In some cases, to create/update CRM records used by our sales team. | Contact data (name, email, phone), company name, message content, and sales follow‑up metadata. | CRM lead handling and sales pipeline management. |
| Mailchimp | When you sign up to receive marketing emails/newsletters (where offered). | Email address and subscription metadata (e.g., campaign label, page/source information). | Mailing list management and email marketing distribution. |
| ZeroBounce | Where enabled, to validate email addresses submitted in forms. | Email address. | Email validation and fraud/abuse reduction. |
| Google reCAPTCHA | Where enabled, to prevent abuse of selected forms/features. | Verification token and related request metadata used for verification. | Abuse prevention and security. |
Embedded content and social media features
Some pages include embedded content or social features that load third‑party services. These services may receive your IP address and device/browser information and may set cookies, depending on your choices and the provider’s configuration.
| Subprocessor | When it is used | Scope of personal data | Purpose |
|---|---|---|---|
| YouTube (Google) | When you view pages that embed YouTube videos and/or play an embedded video. | Online identifiers and usage data related to video delivery and playback. | Video content delivery. |
| X (Twitter) | On some legacy blog pages that include sharing/embedded widgets. | Online identifiers and usage data related to widget loading and interactions. | Social sharing/embedded widget functionality. |
| On some legacy blog pages that include sharing/embedded widgets. | Online identifiers and usage data related to widget loading and interactions. | Social sharing/embedded widget functionality. | |
| Facebook (Meta) | On some legacy blog pages that include social widgets. | Online identifiers and usage data related to widget loading and interactions. | Social widget functionality. |
| Gravatar (Automattic) | On some blog pages to display author avatars. | IP address and request metadata needed to load images. | Display author avatar images. |
Recruitment
| Subprocessor | When it is used | Scope of personal data | Purpose |
|---|---|---|---|
| Traffit | If you click a job application link and submit an application on the external recruitment platform. | Recruitment data provided by you (e.g., CV, contact details) and related application metadata. | Recruitment/application management. |
Updates
We may update this list as our website and tools evolve. For the most current information about how we process personal data (including legal bases, retention, and international transfers), please refer to our privacy notice and cookie information shown on the website.
Updated 1 day ago