Privacy Policy

[TO DRAFT: Registered legal entity name, jurisdiction of incorporation, business address, and the contact route for privacy requests. The site currently publishes only a phone number, so an email address for data-subject requests needs to be established.]

[TO DRAFT: Disclose the Snitcher visitor de-anonymization script (cdn.snitcher.com, profile sg1ZmAyqGf), which identifies visiting companies from IP data. Cover what it collects, the lawful basis, and retention.]

[TO DRAFT: Any analytics, cookies, and local storage. Confirm whether a consent banner is required for the visitor identification given the jurisdictions in scope.]

[TO DRAFT: Business contact data sourced from third-party providers for cold outreach on behalf of clients. Name the categories of data, the sources, and the retention period.]

[TO DRAFT: Describe the controller/processor relationship. SetWize sends on behalf of clients, so the policy needs to state who is the controller for prospect data and what the client's own obligations are.]

[TO DRAFT: Outbound targets the US and Canada. CASL requires consent or a documented business relationship for Canadian recipients and carries personal liability. US state regimes (CCPA/CPRA, and the Virginia, Colorado, Connecticut, Utah and Texas acts among others) each set their own thresholds and rights.]

[TO DRAFT: Confirm whether any EU/UK recipients are in scope. If so, GDPR applies and this section must expand accordingly.]

[TO DRAFT: The unsubscribe mechanism in outbound email, the suppression-list process, and the route for access, correction, and deletion requests. State the response window each applicable regime requires.]

[TO DRAFT: List the vendors that process personal data on SetWize's behalf, including the sending platform, enrichment and verification providers, the visitor identification vendor, and the calendar booking provider.]

[TO DRAFT: Notification method and the effective-date convention.]