footer compliance #12

New issue

Open

opened 2026-05-15 17:56:57 +00:00 by NakataModem · 0 comments

NakataModem commented

2026-05-15 17:56:57 +00:00

Owner

!!! Copyright / DMCA ← soon after launch
Refund Policy ← when first dispute happens
Acceptable Use Policy ← when moderation starts
Security ← when creators ask
Tax Disclaimer ← when creators start earning

Must Have (pre-launch)
Page	Why
Contact	GDPR requires a way to reach you. Also just good practice.

You already have Privacy Policy and Terms of Service done, so you're covered.
Should Have (early post-launch)
Page	Why
Copyright / DMCA	If even one creator uploads someone else's work, you need a visible takedown process. It's also a trust signal for serious creators. Low effort to add.
Nice to Have (as you grow)
Page	Why
Refund Policy	Could live inside Terms, but a dedicated page is clearer if disputes arise. Especially relevant given crypto's finality.
Acceptable Use Policy	If you ever need to ban someone, pointing to a clear, detailed AUP is stronger than a vague ToS clause. Useful once moderation becomes a thing.
Security	A simple page describing how you handle content security, wallet safety, no plaintext storage, etc. Builds trust with creators.
Tax Disclaimer	Once creators start earning meaningfully, they'll ask. A short page that says "you're responsible for your own taxes, consult a professional" covers you.
Probably Skip (until you need them)
Page	Why
Cookie Policy (separate)	You already explained it in Privacy Policy and the banner. A separate page is redundant unless you get complex later.
Affiliate / Referral Program	Only if you launch one.
Transparency Report	Nice PR move for privacy platforms, but only when you have enough requests to report.

https://chat.deepseek.com/a/chat/s/ce9db411-2326-4f4e-aa11-c6aa0db09cc7

- [ ] !!! Copyright / DMCA ← soon after launch - [ ] Refund Policy ← when first dispute happens - [ ] Acceptable Use Policy ← when moderation starts - [ ] Security ← when creators ask - [ ] Tax Disclaimer ← when creators start earning ``` Must Have (pre-launch) Page Why Contact GDPR requires a way to reach you. Also just good practice. You already have Privacy Policy and Terms of Service done, so you're covered. Should Have (early post-launch) Page Why Copyright / DMCA If even one creator uploads someone else's work, you need a visible takedown process. It's also a trust signal for serious creators. Low effort to add. Nice to Have (as you grow) Page Why Refund Policy Could live inside Terms, but a dedicated page is clearer if disputes arise. Especially relevant given crypto's finality. Acceptable Use Policy If you ever need to ban someone, pointing to a clear, detailed AUP is stronger than a vague ToS clause. Useful once moderation becomes a thing. Security A simple page describing how you handle content security, wallet safety, no plaintext storage, etc. Builds trust with creators. Tax Disclaimer Once creators start earning meaningfully, they'll ask. A short page that says "you're responsible for your own taxes, consult a professional" covers you. Probably Skip (until you need them) Page Why Cookie Policy (separate) You already explained it in Privacy Policy and the banner. A separate page is redundant unless you get complex later. Affiliate / Referral Program Only if you launch one. Transparency Report Nice PR move for privacy platforms, but only when you have enough requests to report. ``` https://chat.deepseek.com/a/chat/s/ce9db411-2326-4f4e-aa11-c6aa0db09cc7

NakataModem self-assigned this

2026-05-15 17:56:57 +00:00

NakataModem added this to the kanban project

2026-05-15 17:56:57 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

NakataModem/px#12

No description provided.

Rows
Columns