[II2II]

There are many categories to consider here. Three examples:

- Products that don't require any of this stuff.

- Products that require some form of registration since it stores user data remotely. The person registers so they may secure, modify, or remove that data. The handling of personal data should serve this role exclusively.

- Products that require some form of initial setup and onboarding will facilitate that setup for the vast majority of people. The user should still be able to bypass the onboarding in case their use case doesn't reflect the common use case.

When marketing becomes involved, things become problematic. That friendly offer of assistance to get started usually reflects marketable features rather than any form of genuine training. That collection of personal information is used to harass the person using the product rather than to facilitate the use of the product. (Heck, I have companies contacting me over a decade after I last used their product to try to make a sale.)