Guide
Privacy policy for Cursor apps
How to write a privacy policy for an app built with Cursor, by scanning the deployed URL instead of guessing the stack.
What Cursor does not write for you
An app written in Cursor is an ordinary web app. The editor does not write the privacy policy. If the site loads Stripe, Supabase, PostHog, or an AI API in the browser, those names belong on the page.
TermsPack does not read your repository. It loads the URL you paste, the same way a visitor's browser does.
What to put on the page
Name the operator, a contact email, and every service the live site actually loads: payments, auth, database, analytics, session replay, email, ads, support chat, and AI APIs. Say how someone can ask you to delete an account. Link a refund policy if you charge.
TermsPack's free scan scores those gaps. The $29 pack drafts the pages from the detected vendors. Monitoring is $9 a month and emails you when a later scan finds a service the policy does not name.
TermsPack generates templates from what we detect on your site. This is not legal advice and does not create an attorney–client relationship. Have a lawyer review documents for your situation.