Skip to content
Privacy tools

Privacy policy generator for apps with Sign in with Apple

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

Prepare the privacy page App Store review expects when your app offers account sign-in. Start with your public site, then add the account data your app keeps.

Updated 2 Oct 2026 against official Apple 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. A privacy policy link in two places

    Apple asks for the link in the App Store Connect metadata and inside the app, in an easily accessible way.

  2. A login option that limits data

    Guideline 4.8 asks for an equivalent login service that limits data collection to name and email and lets users keep their email address private.

  3. Account deletion inside the app

    If your app supports account creation, Apple says you must also offer account deletion within the app.

What to account for

  1. What, how and why

    The policy must identify what data the app collects, how it collects it, and all uses of that data.

  2. Retention and deletion

    Apple asks the policy to describe how a user can revoke consent or request deletion of their data.

  3. Third parties named

    The policy must confirm that third parties that receive user data give the same protection the policy promises.

Common mistakes to check

  1. Only Google or Facebook login

    An app that offers third-party login without a login option that meets guideline 4.8 can be rejected.

  2. Deletion that only emails support

    The deletion route must live inside the app. A policy that names only an email address does not replace it.

Your review checklist

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

  1. List the account data you keep

    Write down name, email, identifiers and anything else tied to the account, where you store it and for how long.

  2. Scan your public site and draft

    Scan the site that hosts the policy. Review the suggested vendors, answer the business questions, then add the app data by hand.

  3. Test deletion from a fresh account

    Create an account, delete it inside the app, then check the data is gone as the policy says.

Example

  1. Fictional app: Harbor Habits

    Assume a habit tracker with email sign-up and Sign in with Apple. The scan sees analytics on the marketing site; the owner confirms what the app stores.

  2. A useful next action

    Add the deletion steps to the draft, then link the published page in App Store Connect and in the app settings.

Questions before publishing

  1. Is a policy enough, or also privacy labels?

    Apple also asks for app privacy details in App Store Connect. Keep them in line with your policy.

  2. Can the scan see what my app stores?

    No. The scan reads your public website only. It cannot see your backend or stored accounts. 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 Apple'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.