Don't silently use cal.com account to fill name and email field for booker

[yanamal]

Is your proposal related to a problem?

When I test my cal.com booking page, I noticed that it does not ask me (as the booker) for my name or email. Instead, it seems to use the fact that I'm logged into cal.com and silently, without confirming or asking, uses the name and email from my cal.com account.

This is a problem because I don't want bookers who happen to have a cal.com account of their own to be forced to use this. I am trying to run a study without collecting PII, including names or emails. This study is run through Prolific, and they take care of the communication aspects using Prolific IDs (which are used in place of name and email). Prolific also explicitly forbids collecting PII in their studies.

Describe the solution you'd like

Don't do that. Do not skip the name and email section just because the user has a cookie that shows they are logged in to cal.com.

At least have an option (somewhere that's discoverable) to disable this.

Perhaps just prefill the cal.com email and name into the fields, but allow the users to change it (and if I embed it in a widget with other prefills, then respect my prefills)

If prefills already work this way, document this somewhere discoverable

Describe alternatives you've considered

Using a different system which does not have a (silent, hidden, and non-optional) different behavior for logged in users.

Maybe there's some hacky workaround where if I ask an additional question, it is forced to show the name and email fields, and the user can change them? but I still need to be able to prefill them with the prolific info.

Maybe prefills already work this way, and when actual users go through my actual flow, they will be prefilled correctly? but this is not documented anywhere discoverable, and I will not know until I build out my entire flow.

---

House rules

• If this issue has a 🚨 needs approval label, don't start coding yet. Wait until a core member approves feature request by removing this label, then you can start coding.
  • For clarity: Non-core member issues automatically get the 🚨 needs approval label.
  • Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.
  • Follow Best Practices lined out in our Contributor Docs

[sohel7709]

/attempt