Or on codidact.com because they apply to the whole network. (I thought we'd done that, but I guess we only discussed it? Hmm.)

(Arghh, something funny - tabbing to post button after writing a nice long comment and it got lost, so I'll try to write again...) The software needs to have the policies either stored in text files read at startup or in the database (and then hosted on "self") or have links stored in text files read at startup or in the database. But definitely needs to be "per community".

While all of our communities will use the same policies, other instances might use different policies (therefore, don't hardcode the policies or links) and might even use different policies for different communities within an instance (therefore must be per community). (And I figured out my error - comment was too long, so Post button inactive, so Tab + Enter went to a different button, poof lost the whole comment).

These are waiting for someone to convert them to raw HTML so they can go on codidact.com. If we need to make per-community exceptions, they can be noted in the network-wide terms and referred to the community-specific policy.

Related: https://meta.codidact.com/questions/74808