Scope of Use
Defines permitted marketing uses, prohibited activities (re-identification, sensitive categories), and any channel, geography, or vertical limitations.
A written Marketing Remarketing Agreement reduces legal and operational risk by specifying who controls data, how consent is obtained, and which security controls apply. It helps align marketing, legal, and engineering teams on permitted processing and measurement methods while clarifying commercial terms.
Marketers, advertising platforms, publishers, data processors, and agencies commonly use these agreements to document rights and responsibilities.
Clear role definitions in the contract streamline campaign setup, reduce disputes, and speed compliance reviews across teams.
An officer or contract manager with authority to bind the business should sign on behalf of the client. This signer should be listed by name, title, and business entity and have documented signature authority in company records.
A vendor or platform contract representative with authority to accept commercial and technical terms signs for the provider; include billing contact and technical integration lead for operational follow-up.
Defines permitted marketing uses, prohibited activities (re-identification, sensitive categories), and any channel, geography, or vertical limitations.
Specifies which identifiers (email hash, mobile ad ID, cookie/pixel data, CRM attributes) are shared and whether third-party sources or enhancement services will be used.
Documents who is responsible for collecting user consent and for honoring opt-outs consistent with applicable law and platform policy.
Sets encryption, access restrictions, incident notification timeframes, and audit support obligations for both parties.
Defines permitted measurement endpoints, attribution windows, accepted metrics, and data retention for analytics.
Allocates risk for data breaches, regulatory fines, and third-party claims; includes caps and exclusions as appropriate.
| Field | Configuration |
|---|---|
| Consent Check | Enforce consent flag on data import |
| Hashing Standard | Use SHA-256 for email hashing |
| Transfer Method | SFTP or API with TLS 1.2+ |
| Retention Setting | Auto-delete after agreed retention period |
Confirm integrations (CRM, CDP, ad platform) and keep a documented list of vendor sub-processors and their security certifications.
MM/DD/YYYY format; starts contractual obligations
Date when first audience transfer must be complete
Periodic review date for data deletion and audit
Require notification within 72 hours of discovery
Monthly or quarterly reporting cadence
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
A mid-sized ad buyer standardizes hashing and consent checks across campaigns to reduce integration errors.
A healthcare provider uses a BAA and strict data minimization clause to permit safe remarketing for patient education.