Skip to content
Privacy tools

Privacy policy generator for Zoom Marketplace apps

Policy generation is paused. Check your existing policy against your website.

Prepare the privacy page your Zoom Marketplace listing links to. Start with your public site, then add what your app reads from Zoom accounts.

Updated 2 Oct 2026 against official Zoom documentation

Start with your website

I have the link to my privacy policy

Optional. If you paste the direct link, we read that page instead of looking for it, so the check is more exact.

By scanning, you confirm that you own this website or are authorized to test it, and you agree to our Terms.

No account needed.

What the store reviewer checks

These checks come from the store's published rules. Open each source before you submit. The scan above checks your website, not your app or extension.

  1. Pages on your own domain

    Zoom says the listing links must be hosted on fully qualified domain names owned by your company.

  2. A support page

    All published apps must give a support URL with clear information on how users get ongoing support.

  3. A company name that matches

    The company name in the terms of use page must match the app's company name.

What to account for

  1. Data subject rights

    The privacy policy must tell users about their data subject rights and how to exercise them.

  2. Removal instructions

    Documentation must explain how to remove the app from a Zoom account and how user data is handled after removal.

  3. Encryption

    Zoom's security page asks you to encrypt data in transit, for example with TLS 1.2 or higher, and at rest. Say what you do in the policy.

Common mistakes to check

  1. Legal pages on shared storage

    Zoom says hosting these documents on third-party platforms like Google Drive or Dropbox is not permitted.

  2. A thin long description

    Zoom says apps may be rejected if the long description lacks enough detail.

Your review checklist

Our suggested review process. The linked requirements above explain the platform or legal basis.

  1. List what the app reads from Zoom

    Write down each scope, the data it returns, where you store it and for how long.

  2. Scan your public site and draft

    Scan the company site that will host the page. Review the suggested vendors, answer the business questions, then add the Zoom data flows by hand.

  3. Check the company name everywhere

    Compare the name in the terms, the policy and the app listing. They must match.

Example

  1. Fictional app: Harbor Notes

    Assume an app that saves meeting notes for 60 days. The scan sees analytics on the marketing site; the owner confirms what the app stores.

  2. A useful next action

    Add the 60-day retention and the removal steps to the draft, then publish it on your own domain.

Questions before publishing

  1. Can I host the policy on Google Drive?

    Zoom says no. Use a page on a domain owned by your company.

  2. Can the scan see my Zoom data?

    No. The scan reads your public website only. It cannot see tokens, scopes or what your backend stores. You confirm those facts yourself.

  3. Is the draft reviewed by a lawyer?

    No. A lawyer has not reviewed our templates. The draft is a starting point that you check and adapt against Zoom's current rules.

Source review and changes

First edition: platform requirements, implementation checks and fictional worked example. Sources reviewed on the date above; verify changes before relying on them.