Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardized TOS clauses #743

Open
zkat opened this issue Sep 10, 2023 · 1 comment
Open

Standardized TOS clauses #743

zkat opened this issue Sep 10, 2023 · 1 comment
Labels
feature A user-relevant platform feature.

Comments

@zkat
Copy link
Contributor

zkat commented Sep 10, 2023

There should be a standard list of common TOS clauses of interest that a studio can pick from, on top of the full text TOS, that would allow for arbitrary filtering/searching by those clauses.

For example: commercial use, copyright transfer, artist self-promotion/portfolio usage, etc. We can also add to this the "immutable" ones defined at the Banchan level, like the AI ban, the refund policy, the rejection/cancellation policy, etc.

@zkat zkat added the feature A user-relevant platform feature. label Sep 10, 2023
@kouhaidev
Copy link

kouhaidev commented Sep 10, 2023

Original thread: https://discord.com/channels/993888331320541264/1150363001732468796/1150363001732468796

Other thoughts:

  • It'd be helpful if the selected standardized clauses were explicitly separated out by UI.
  • Show standard commission terms by default? I didn't know that some of those clauses were standard.
  • Parameterize commission terms? I.e. **Usage Rights: __Personal__** vs `Usage Rights: Personal, Commercial
  • Some artists include "will/won't do" in TOS - this seems like a great attribute to pull out for discoverability.

Operational thoughts:

  • When deploying new clauses, it'd be nice if there was UX that encouraged migration to standard clauses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A user-relevant platform feature.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants