Core pillars
Prohibited use categories
Safety, authenticity, and integrity expectations
Enforcement and account action framework
Legal
Responsible use policy for realistic AI creator operations.
Potsticker defines explicit standards for impersonation, harmful content, fraud, harassment, privacy abuse, and prohibited automation workflows.
We publish policy boundaries and enforcement posture while keeping detection signatures, reviewer tooling, and abuse-response internals private.
What you get
Responsible use principles
User obligations, restrictions, and examples
Policy-linked legal and trust references
Launch checklist
Align legal copy with real product and billing behavior.
Confirm misuse and trust-report channels are active.
Review privacy statements for all live connectors.
Add update date and owner for each policy page.
Run a legal copy check before each major release.
Verify primary CTA route: /terms
Detail lane
What this page covers
Potsticker defines explicit standards for impersonation, harmful content, fraud, harassment, privacy abuse, and prohibited automation workflows.
Prohibited use categories
Safety, authenticity, and integrity expectations
Enforcement and account action framework
Detail lane
Soft launch deliverables
These are the deliverables that should be complete before expanding invite volume.
Responsible use principles
User obligations, restrictions, and examples
Policy-linked legal and trust references
Detail lane
Open kitchen boundary
We publish policy boundaries and enforcement posture while keeping detection signatures, reviewer tooling, and abuse-response internals private.
Keep terms consistent with pricing and product scope
Define escalation and support obligations
Maintain version history for policy updates
Common questions
What outcome should I expect from legal?
Potsticker defines explicit standards for impersonation, harmful content, fraud, harassment, privacy abuse, and prohibited automation workflows.
What is intentionally not disclosed publicly?
We publish policy boundaries and enforcement posture while keeping detection signatures, reviewer tooling, and abuse-response internals private.
Where should I go next?
Use "Review terms" first (/terms), then "View security" (/security) for deeper context.