Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/business-tools/general-legal-assistant/skills/privacy-generator

privacy-generator

Verified

Draft a service-specific privacy notice from confirmed processing facts, source observations and scoped applicability review, with a separate evidence and unresolved-questions record. Use when preparing or revising a privacy policy. Trigger with "privacy-generator" or "create a privacy policy".

FileKindSize
SKILL.mdskill md7.2 KB
references/notice-evidence.mdmarkdown4.9 KB

references/notice-evidence.md

View on GitHub
# Privacy notice evidence and drafting

## Inventory before assurances

For each processing purpose, record the data categories and sources, collection
route, recipient/vendor, retention criteria, location/transfer facts and actual
rights/choice controls. Include source URL/path/locator, observation date, inspected
scope and one of these statuses:

- **Owner-provided fact:** supplied by an identified owner with its date/context;
  it is an assertion, not independent runtime verification.
- **Observed:** the stated tool/capture actually exposes the relevant behavior.
- **Signal:** code/import/tag/config suggests a possibility needing confirmation.
- **Unknown:** material practice or configuration was not established.
- **Proposed decision:** a requested policy choice not yet represented as actual practice.

Keep raw credentials, tokens, user records and unnecessary technical detail out of
reports. A static repository cannot establish the full backend/vendor deployment.
A page fetch cannot prove cookie behavior, network transmission or a working rights
portal unless the actual evidence exposes those facts.

## Twelve candidate notice sections

| Topic                  | Facts needed before an affirmative statement                                          |
| ---------------------- | ------------------------------------------------------------------------------------- |
| Identity/scope         | Actual entity, service and audience; verified contact details.                        |
| Information/sources    | Actual categories collected, where they originate and relevant limits.                |
| Purposes/basis         | Processing purpose and supported basis decision for the applicable regime.            |
| Cookies/tracking       | Actual active technologies, purposes, durations and implemented controls.             |
| Recipients             | Actual sharing/processing relationships and purposes; no vendor guess from an import. |
| Retention              | Confirmed periods or criteria, with relevant backup/deletion/hold limits.             |
| Applicable rights      | Which rights/conditions are relevant to the actual roles and jurisdictions.           |
| Request/choice methods | Real routes and operational capabilities, including limits needing review.            |
| Security               | Accurate appropriate-level statements, not invented safeguards or certification.      |
| International handling | Actual destinations/roles and verified safeguards where applicable.                   |
| Age/children           | Real audience practices and identified legal questions; no default age assumption.    |
| Contacts/dates/changes | Actual contacts, draft/version status and provided effective/update decisions.        |

Use relevant sections; twelve headings do not prove completeness or compliance.
Do not copy a preset count of rights or assign a basis solely because data are
financial, behavioral or collected for marketing. Keep purpose, necessity, role
and jurisdiction-specific questions explicit.

## Separate copy from review

The reader-facing draft should explain confirmed practices in usable language.
The review record contains source evidence, uncertainty, conflicts and needed
business/legal decisions. Do not paste code findings or raw scan logs into the
notice. A material unknown must remain visible in review and must not become an
unqualified public promise. Preserve existing approved decisions and resolve only
new material gaps before treating a draft as final.

Cookie-banner copy is not an implementation or compliance test. Verify actual
choices, withdrawal/opt-out paths and any required signal handling within an
authorized scope before describing them as functioning. Do not enable controls,
submit rights requests or publish a notice as part of generating text.

## Primary sources and jurisdiction

Reviewed 2026-10-25. Select current applicable sources for the actual case; this is
not an exhaustive legal checklist.

- [ICO guide to lawful basis](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/a-guide-to-lawful-basis/):
  UK-specific guidance; basis choices depend on purpose and context. Its 2026
  update is not a reason to assume identical rules for EU processing.
- [ICO privacy-information topics](https://ico.org.uk/for-organisations/advice-for-small-organisations/getting-started-with-gdpr/data-protection-self-assessment-medium-businesses/what-information-you-must-supply-under-the-gdpr/):
  UK disclosure guidance; check its scope and current status before use.
- [CPPA FAQ](https://cppa.ca.gov/faq): official agency information distinguishes
  business applicability and other recipient/service-provider roles. The FAQ is
  informational, not a substitute for applicable law or an individualized opinion.

Templates and vendor marketing can suggest questions but do not prove the
organization's facts or compliance. Verify any actual copied template's version,
license and attribution before using it.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall