Privacy policy for Clerk apps

What Clerk does on a live site

Clerk is in the auth and database category. On sites we scan, it shows up through clerk.com, clerk.accounts.dev. Its role is to sign users in and manage sessions.

Data that may be processed: Name, email, session tokens, and sign-in method (password, code, or social login). The vendor describes the location as: United States (Clerk). Their public privacy or data-processing terms are at https://clerk.com/legal/privacy.

A privacy policy for a Clerk app should name Clerk directly and say what your own product sends to it. A phrase like "third-party tools" is not enough once this service is on the page.

Clerk's browser SDK is served from clerk.com or a *.clerk.accounts.dev host and sets a session cookie such as __client_uat. The policy should say that sign-in, including any social login you enabled, is handled by Clerk.

What you still have to type

The scan cannot know your company name, the country you operate from, or the support email you want on the page. Those go in a short form after the scan. The legal clauses around them are fixed template text, marked as a draft until a lawyer reviews them.