I'm not sure if this is the right forum but I just ran into a potential issue with DNN setup.

When creating many Portals, it turns out the Terms of Use and Privacy Statement use the [PortalName] token in each Terms of Use and Privacy Statement on Portals.  This can be potentially embarrassing.

I have set up some political sites to oppose ObamaCare and naturally, in the Admin Dialogue Box the easiest way to administer the sites is by Representative name.  This sets the Terms of Use and Privacy Statement documents such that it appears the Representative in the US House knows about and endorses the site.

My recommendation is to alert whoever is installing DNN, from within the setup routine, how their Terms of Use and Privacy Statement will appear.  Naturally, these should be configured, in the case for myself, to avoid using [PortalName].  It would have been nice to see during setup something like this:

"Under Terms of Use, Senator Blutarsky will be the name showing in clauses such as 'You will not hold Senator Blutarsky ... such and such ... so and so ... etc.  Change the token from [PortalName] if you wish to have Terms of Use and Privacy Statement read different from the default."

I just happened to locate this on my own, being a "heads down" coder and not a lawyer.

I recommend that setup, installation, upgrade routines be revised to advise each user how these documents read and to prevent the installation, upgrade of any site without it being acknowledged that this is what each end user wants.

This would be a short addition to the DNN setup and be quite helpful for anyone making multi-portal sites where the PortalName could end up creating inadverent misrepresentation.