返回提示词目录第 1347 页

隐私告知透明度审查与整改

帮你核对隐私告知与实际数据处理,整理风险矩阵和整改计划,法律结论需专业确认。

完整提示词

Main objective:

> Audit privacy notices and layered disclosures for completeness, intelligibility, accuracy, timing, audience fit and consistency with actual processing.

This prompt is jurisdiction-adaptive. Use GDPR/EDPB concepts only when applicable. Do not assume the same lawful basis, deadline, transfer mechanism or notification threshold applies in every country.

## 1. INTAKE GATE

- organization and controller / processor / joint-controller or local-equivalent roles
- jurisdictions and processing locations
- data-subject and data categories
- purposes and actual data flows
- systems, processors, subprocessors and recipients
- retention periods and deletion mechanisms
- security and governance controls
- existing policies, contracts, records and incidents
- lawful bases and special-category conditions
- international and onward transfers

## map each purpose to concrete data, people, system and recipient,verify documentation against actual processing, not policy text alone,separate binding law from regulator guidance and internal best practice,test purpose limitation, minimisation, accuracy, storage limitation, security and accountability where applicable,identify processing with no owner, evidence or clear legal basis,test rights, breach, retention and transfer workflows as operational systems

- map each purpose to concrete data, people, system and recipient
- verify documentation against actual processing, not policy text alone
- separate binding law from regulator guidance and internal best practice
- test purpose limitation, minimisation, accuracy, storage limitation, security and accountability where applicable
- identify processing with no owner, evidence or clear legal basis
- test rights, breach, retention and transfer workflows as operational systems

Poseban fokus / Specialized focus:
- Audit privacy notices and layered disclosures for completeness, intelligibility, accuracy, timing, audience fit and consistency with actual processing.
- Tie every conclusion to the real processing operation, legal rule, evidence and accountable owner.
- Detect mismatches between notices, records, contracts, systems and observed behavior.
- Require a reasoned residual-risk conclusion rather than a checklist-only pass.

## 3. PROCESSING EVIDENCE

For each material processing activity capture:
```text
Processing activity:
Purpose:
Data subjects:
Data categories:
Special / sensitive data:
Source:
System:
Controller / responsible entity:
Processor / vendor:
Recipients:
Jurisdictions:
Lawful basis / legal condition:
Retention:
Security controls:
Rights impact:
Transfer mechanism:
Evidence:
Owner:
Verification status:
```

Status: VERIFIED / SUPPORTED / CONTESTED / UNVERIFIED / OUTDATED / NOT APPLICABLE.

## 4. LEGAL GATE

Use current primary law and authoritative regulator material for jurisdiction-specific conclusions. Under GDPR where applicable, explicitly test the relevant principles, lawful-basis rules, transparency and rights duties, processor requirements, security, breach duties, DPIA triggers and international-transfer rules. Do not treat guidance as legislation or a contract as proof of actual compliance.

## 5. RISK TEST

Actively test:
- undocumented processing or shadow data flows
- purpose creep
- excessive data collection
- invalid or mismatched lawful basis
- consent bundled, coerced, stale or impossible to withdraw where consent is relied on
- processor acting outside documented instructions
- uncontrolled subprocessors or onward transfers
- notices inconsistent with reality
- rights requests that cannot be fulfilled across systems
- retention schedules that do not delete copies
- breach decisions without documented risk assessment
- security controls that exist only on paper
- DPIA used as a formality instead of a risk process

Severity:
P0 - unlawful/high-risk processing or transfer with immediate material rights/regulatory exposure
P1 - systemic legal-basis, rights, breach, security or transfer failure
P2 - significant control or documentation weakness
P3 - correctable inconsistency or evidence gap
P4 - privacy engineering / governance hardening

## 6. REQUIRED MATRICES

### Processing Register
| Activity | Purpose | Data | Basis | System | Recipients | Retention | Transfer | Owner | Status |
|---|---|---|---|---|---|---|---|---|---|

### Rights & Obligations Matrix
| Trigger / right | Legal source | Workflow | Deadline | Evidence | Exception | Owner |
|---|---|---|---|---|---|---|

### Risk & Control Matrix
| Risk | Rights impact | Existing control | Evidence | Gap | Residual risk | Action |
|---|---|---|---|---|---|---|

## 7. FINDING FORMAT

```text
ID:
Severity:
Status:
Processing / system:
Jurisdiction:
Legal requirement:
Observed practice:
Evidence:
Gap:
Rights impact:
Regulatory impact:
Security / transfer dependency:
Remediation:
Owner:
Deadline:
Residual risk:
```

## 8. REQUIRED OUTPUT

1. Executive privacy-risk summary.
2. Processing and role map.
3. Applicable legal framework.
4. P0-P4 findings.
5. Required matrices.
6. Evidence and documentation gaps.
7. Remediation plan with owners and deadlines.
8. Rights / breach / transfer dependencies.
9. Residual risk.
10. Final Accountability Check.

End with **Accountability & Evidence Check** confirming that each material conclusion is tied to actual processing evidence and a verified legal source, or is explicitly marked unresolved.

This supports privacy/compliance research and preparation. It does not replace qualified legal or DPO advice in the relevant jurisdiction.

分类与标签

办公效率、隐私告知、合规审查、风险矩阵、整改计划

前往 AI 图片创作