Cal.com App Verification to get permanent access to the Google Calendar API

[byebb]

Hi everyone,

For those self-hosting Cal.com and integrating Google Calendar via OAuth, I’ve noticed that while in testing mode, the login works but access expires every 7 days. To move the app to production, Google requires a verification process that includes:

• A homepage with a clear link to a privacy policy
• A privacy policy that reflects the app's actual branding (not Cal.com's)
• Hosting the privacy policy under the same domain as the app

Given that Cal.com’s default self-hosted setup doesn’t seem to include a built-in homepage or privacy policy, how are others handling this?

• Do you typically create a separate page under your domain with your own privacy policy?
• Are there any templates or examples for this specifically for Cal.com setups?
• Any tips for passing Google’s OAuth verification with a self-hosted instance?
• I would love to hear how others in the community have navigated this!

Thanks in advance!

[SysEngDan]

I'd love to see how others are handling this. The verification process also takes weeks.