This notice applies specifically to the public marketing website at watchdogsecurity.io.
For our main privacy practices across WatchDog services, see the Privacy Policy. For public-site cookies and similar technologies, see the Cookie Policy.
What We Collect on the Marketing Site
| Category | Examples | Why We Use It |
|---|---|---|
| Contact and inquiry data | name, business email, company, phone number, message content | to respond to inquiries, demos, partnership requests, and other website submissions |
| Meeting-booking data | details submitted through Calendly or similar tools | to schedule and manage meetings or demos |
| Public-site chat data | chat messages, support or sales interactions | to communicate with website visitors where chat is enabled |
| Analytics and performance data | page views, public-site usage, performance information | to understand public-site traffic and improve website performance; managed through Complianz consent tooling |
| Consent choices | cookie and tracking preferences | to manage lawful public-site consent choices via Complianz |
| Security and technical data | IP address, browser details, logs, abuse-prevention records | to secure the site and maintain reliability |
Key Service Providers & Subprocessors
The following third-party service providers process data as part of operating the marketing website. For the full cross-service overview, see the Subprocessors & Service Providers page.
| Provider / Record Type | Purpose | Data Retention |
|---|---|---|
| Cloudways | managed cloud hosting for the WordPress site, with independent server-level security and access logs | per hosting plan settings |
| Cloudflare | edge security, DDoS protection, abuse prevention, and site reliability | up to 1 year |
| WordPress and related plugins | public-site content management, forms, and site operation | per platform settings |
| Ninja Forms Pro | contact forms and inquiry submissions within WordPress; form data is processed within WordPress and is not sent to Ninja Forms externally | per WordPress database retention |
| Google Analytics 4 | public-site analytics, managed through Complianz consent tooling; blocked until user consent where required | per Google Analytics data retention settings |
| Complianz | cookie consent management and compliance with cookie and tracking regulations | per plugin settings |
| Intercom | public-facing chat widget for non-signed-in visitors, blocked until consent where required | up to 9 months; closed or deleted conversations are removed |
| Calendly | meeting booking and demo scheduling, blocked until consent where required | up to 3 years after the last meaningful interaction |
| Pipedrive | CRM records from website inquiries, booking flows, and contact forms | up to 3 years after last contact |
| Apollo.io | company and contact information enrichment for leads from website interactions; enriched data is stored in Pipedrive CRM | WatchDog stores enriched data in CRM per Pipedrive retention; Apollo.io maintains its own database independently |
| n8n | workflow automation and data routing between website forms, CRM, and other tools; data passes through temporarily during processing | transient; data is routed and not stored long-term by n8n |
Have questions?
Our Privacy Officer is here to help clarify any points of this policy.
