Privacy Policy URL
Get URL

How to add a Privacy Policy URL for a Zapier integration

By Paul Cranmer, Founder · Last verified October 2026 · Zapier Developer Platform · Publishing

Zapier's publishing requirements are about branding, HTTPS, ownership and a test account; they do not add a separate privacy policy field. What they do require is a Homepage URL that is a real marketing site, and that site, together with your OAuth consent screen, is where users and reviewers expect your privacy policy to be one click away. Every user who connects the integration grants access to their account data, and the enterprise customers who follow will ask for the policy link in their security questionnaires. This page puts the pieces in order.

Who this is for

  • Developers taking a private Zapier integration public
  • SaaS teams whose Homepage URL was rejected for pointing at a login page
  • Anyone preparing the integration for customer security reviews

Not for

  • Private integrations used only inside your own company
  • A walkthrough of building triggers and actions

What the platform requires

  • The Homepage URL in your publishing settings must be your marketing website, not the app URL or a login page.
  • The owning Zapier account must be associated with your company: at least one admin team member with an email on the app's or API's top-level domain, or proof of ownership on request.
  • All endpoints must use HTTPS; the integration must be publicly launched (not beta or invite-only) and include API documentation links in the submission.
  • A non-expiring test account for integration-testing@zapier.com, and English for all user-facing text.

Get a live URL first

A Zapier integration is an API connector, which is on our free path: choose API/SDK, name the integration and the account data it reads and writes, and you get a stable HTTPS policy URL for your homepage footer and your OAuth consent screen.

Get the integration policy URL (free)

Step-by-step: paste your privacy policy URL

  1. Create the hosted privacy policy URL. Generate it as API/SDK with the integration's name, the account data each trigger and action touches, retention and a support contact. Copy the live URL.
  2. Link it from your homepage and your OAuth consent screen. Zapier sends users to your Homepage URL and your authorization page. Put the policy link in the site footer and on the consent screen so it is visible before anyone connects.
  3. Open the integration in the Developer Platform. Log in to the Platform UI, select the integration, and open Publishing. Set the Homepage URL to the marketing site that carries the policy link.
  4. Pass the ownership, HTTPS and branding checks. Confirm an admin on the owning account has an email on your domain, every endpoint is https://, and the name and description follow Zapier's branding rules.
  5. Publish and submit for review. In Integration Home click Publish, complete the form (including API documentation links and the test account), then Submit for Review. Respond to PublishBot and reviewer notes.
  6. Keep the link stable for security reviews. Customers' vendor questionnaires will cite the policy URL. Edit the text behind the same URL when triggers or actions touch new data; never move it.

Field labels to look for

Publishing → Homepage URL
Marketing website only. Not the app, not a login page. This is where reviewers look for the policy link.
Team members
At least one admin with an email on your domain; Zapier may ask for proof of ownership otherwise.
Publish → Submit for Review
Online form with API docs links and the test account; PublishBot runs automated checks first.

Common reasons the form fails

  • Homepage URL set to the app login page
  • Consent screen with no policy link, so users grant access blind
  • Policy that does not list the account data the triggers and actions read
  • Owning account not tied to the company domain

No field, still required in practice

Zapier's own checklist does not ask for a policy URL field, so do not wait for a reviewer to request it; the gap shows up later in customer security reviews and OAuth consent. Put the link in place before you submit.

Get the integration policy URL (free)Learn more

FAQ

Does Zapier require a privacy policy URL field?

The published requirements do not include one. They require a marketing Homepage URL, HTTPS and company ownership. The policy belongs on that homepage and on your OAuth consent screen.

Can I use the same policy for Make, n8n and Zapier?

Yes. One policy that names the integrations and the account data they handle covers all of them. Keep a single URL.

Related

Sources