Files
skills/commands/privacy-policy.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

2.2 KiB

description, argument-hint, source
description argument-hint source
Draft a privacy policy covering data collection, usage, storage, and compliance requirements <product and data handling context> phuryn/pm-skills

/privacy-policy -- Privacy Policy Generator

Draft a comprehensive privacy policy for your product. Covers data types, jurisdiction, compliance (GDPR, CCPA), and marks clauses needing legal review.

Invocation

/privacy-policy SaaS analytics tool that collects user behavior data — serving US and EU customers
/privacy-policy Mobile app with location data and third-party integrations

Workflow

Step 1: Gather Context

Ask:

  • What product or service?
  • What data is collected? (personal info, usage data, cookies, location, payment)
  • Where are your users? (determines applicable regulations: GDPR, CCPA, etc.)
  • Any third-party data sharing? (analytics, advertising, integrations)
  • Data storage: where and how long?
  • Age restrictions? (COPPA considerations)

Step 2: Draft the Policy

Apply the privacy-policy skill:

Generate sections covering:

  • What data is collected and how
  • How data is used (purposes)
  • Legal basis for processing (GDPR)
  • Data sharing and third parties
  • Data retention and deletion
  • User rights (access, deletion, portability, opt-out)
  • Cookie policy
  • Security measures
  • Children's privacy (if applicable)
  • International transfers
  • Contact information
  • Policy update process

Step 3: Deliver

## Privacy Policy: [Product]

[Full policy text]

### Compliance Checklist
| Regulation | Status | Notes |
|-----------|--------|-------|

### Clauses Requiring Legal Review
| Clause | Why | Priority |
|--------|-----|----------|

### Implementation Checklist
- [ ] Cookie consent banner
- [ ] Data subject request process
- [ ] Data processing records
- [ ] DPA with processors

Save as markdown. Offer DOCX export.

Notes

  • This is a template — legal counsel should review before publishing
  • GDPR and CCPA have specific requirements that can't be approximated — flag where expert review is essential
  • Privacy policies should be in plain language, not legalese
  • Update the policy when data practices change, not just annually