# Privacy Notice Content Intake

Collect accurate processing facts, purposes, data flows, recipients, retention, choices, rights routes, security contacts, and responsible owners.

## Usage note

Use this intake to gather operational facts for qualified privacy and legal review; do not publish it as a privacy notice or treat it as legal advice. Complete it with product, engineering, security, support, marketing, vendor, and data owners who know the live system. Verify deployed behavior and contracts. Do not paste secrets, credentials, or unnecessary personal data into the worksheet.

## How to use this template

1. Define the product, audience, markets, versions, systems, and responsible owners in scope.
2. Inventory data categories with source, collection point, requirement, sensitivity, and user expectation.
3. Map purposes, systems, recipients, vendors, disclosures, transfers, and choices.
4. Document retention, deletion, rights-request routes, contacts, and update triggers.
5. Validate against the live product and qualified reviews before drafting or changing any notice.

## Blank template

### Scope and ownership

- **Product/service and version:** [Exact scope]
- **Markets and audiences:** [Regions and user types]
- **Controller/responsible entity:** [For qualified review]
- **Product owner:** [Name/team]
- **Engineering/data owner:** [Name/team]
- **Security contact:** [Role/channel]
- **Privacy/legal reviewer:** [Role]
- **Current notice and date:** [URL; YYYY-MM-DD]
- **Change triggering intake:** [Feature, vendor, field, purpose, market]

### Processing record

- **Data category:** [User-recognizable description]
- **Specific fields/examples:** [No live personal data]
- **Source and collection point:** [User, device, vendor, derived]
- **Required or optional:** [Product consequence]
- **Purpose:** [Specific activity]
- **System and owner:** [Where processed]
- **Recipients/vendors:** [Role and service]
- **Transfer/location:** [For qualified review]
- **Choice/control:** [Setting, consent, opt-out, other]
- **Retention/deletion:** [Period, trigger, method, exceptions]

### Review checks

- [ ] Inventory covers submitted, observed, derived, and third-party data.
- [ ] Technical labels are translated into understandable categories.
- [ ] Purposes are specific to real processing.
- [ ] Vendors, recipients, locations, and transfers are complete.
- [ ] Product choices and consequences were tested.
- [ ] Retention includes trigger, deletion process, and exceptions.
- [ ] Rights and contact routes work in the live experience.
- [ ] Qualified reviewers own legal conclusions and final notice wording.