Privacy Policy — Prompt Jargon Studio
Last updated: July 31, 2026

Who we are

This Privacy Policy describes how Prompt Jargon Studio (“the App,” “we,” “us”) handles information when you use our browser extension (Chrome / Firefox), desktop app, or related web UI.

Operator / privacy contact: janlongerichofficial@gmail.com

This policy is written for transparency with store reviewers and users. It is not legal advice.

Summary

• We do not sell your personal data.
• We do not run advertising trackers or third-party analytics SDKs in the App.
• API keys you enter stay on your device and are never uploaded to our servers.
• When you are signed out, your ideas and prompts stay on your device (except what you send to a model provider you choose when you click Generate).
• When you are signed in, we store account, billing, and an optional workspace backup so your saved work can restore across devices.
• Optional “Send to PJ Studio” / page selection is only used when you invoke it; we do not scrape the open web in the background.

What the App does

The App helps you turn casual ideas into domain-specific technical prompts. Depending on your plan and settings, it may call third-party AI model APIs (for example OpenRouter, OpenAI, Anthropic, or Google) using a key you provide (BYOK) or, on certain plans, hosted credit flows we configure.

Browser permissions (extension)

The Firefox / Chrome extension may request:
• storage — save preferences, session helpers, and on-device data locally.
• identity — Google / OAuth sign-in when you choose to sign in.
• activeTab — limited interaction with the active tab when you use a feature that needs it (for example screen-snip / inject helpers).
• contextMenus — “Send to PJ Studio” on selected text when you use that menu item.
• Host access to AI provider APIs and our Supabase project — only to call those services when you use sign-in, sync, or Generate.

We do not use these permissions to continuously read your browsing history or all page content.

Information we process

A) On your device (local)
• API keys and provider settings you enter.
• Ideas, drafts, generated prompts, working style, vaults, favorites, hotkeys, continuity buffers, and similar preferences while you use the App unsigned-in — or as a local mirror when signed in.
• Temporary pending text from “Send to PJ Studio” / hotkeys (cleared after the App consumes it).
• Attachments you add for a Generate (parsed in-browser); file bytes are not uploaded to Prompt Jargon Studio servers as a permanent archive.

B) Account & authentication (if you sign in)
• Email address, display name, and OAuth profile metadata provided by your identity provider (via Supabase Auth).
• Authentication tokens / session data needed to keep you signed in.

C) Billing & entitlements (if you purchase)
• Subscription / plan status, credit balances, and related billing identifiers synced from Lemon Squeezy webhooks into our database (we do not store your full payment card number in the App).

D) Signed-in workspace backup (if you sign in)
• A backup of app workspace data such as saved generations, brand vaults, working style, project context, favorites/hotkeys, and related preferences — so your work can restore across devices and updates.
• Prompt text in that backup is stored only for this restore purpose.

E) Website / page content (only when you ask)
• Selected text you send via the context menu, or content you deliberately attach / paste / snip for a prompt.
• We do not crawl or index websites in the background.

Information we do not collect

• We do not sell personal information.
• We do not include third-party advertising networks.
• We do not collect precise geolocation for marketing.
• We do not upload your BYOK API keys to our servers.
• We do not operate a mandatory product-analytics / telemetry pipeline in the shipped App. Optional technical & interaction metrics (if ever enabled in a future build and consented where required) would be described here before use; they are off by default today.

How we use information

We use the information above to:
• Provide, maintain, and improve the App.
• Authenticate you and sync your workspace when signed in.
• Process subscriptions and enforce plan entitlements.
• Send your prompts / attachments to the model provider you (or your plan) use — only when you trigger Generate or a related AI action.
• Respond to support, security, and legal requests.
• Comply with law and protect against abuse or fraud.

Legal bases (EEA/UK where applicable)

Where GDPR / UK GDPR applies, we typically rely on: contract performance (providing the App you requested), legitimate interests (security, product integrity, basic operations) balanced against your rights, consent (for example optional OAuth sign-in or future optional metrics), and legal obligation when required.

Third parties & processors

We share data only with processors needed to run the service, under their respective terms/policies:
• Supabase (authentication & database) — https://supabase.com/privacy
• Lemon Squeezy (payments / merchant of record for paid plans) — https://www.lemonsqueezy.com/privacy
• Model providers you or your plan use when you Generate (examples: OpenRouter, OpenAI, Anthropic, Google). Content you submit in a Generate request is processed under that provider’s terms. We do not control how those providers train on or retain API inputs; review their policies if that matters to you.
• Google (if you choose Google sign-in) — for authentication only.

We do not sell your data to data brokers.

International transfers

Our processors may store or process data in the United States or other countries. Where required, we rely on appropriate safeguards offered by those providers (for example standard contractual clauses) as described in their documentation.

Retention & deletion

• Local data remains until you clear it in Settings, clear site/extension storage, or uninstall the App.
• Account and workspace backup data are retained while your account is active and for a reasonable period afterward for backups, disputes, or legal compliance, then deleted or anonymized.
• To request deletion of your account and associated server-side personal data, email janlongerichofficial@gmail.com with the subject “Delete my Prompt Jargon Studio account” from the email on the account. We will process reasonable requests within applicable legal timelines.
• Uninstalling the extension removes local extension storage but does not by itself delete your cloud account.

Your rights

Depending on your location (including GDPR, UK GDPR, and CCPA/CPRA where applicable), you may have rights to access, correct, delete, export, restrict, or object to certain processing, and to withdraw consent where processing is consent-based. California residents may have rights to know, delete, and correct personal information and to opt out of “sale”/“sharing” as those terms are defined by law — we do not sell personal information. To exercise rights, contact janlongerichofficial@gmail.com. You may also lodge a complaint with your local supervisory authority.

Children

The App is not directed to children under 16 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us personal data, contact us and we will take appropriate steps to delete it.

Security

We use industry-standard measures appropriate to a client app and managed backends (HTTPS, access-controlled databases, on-device storage for API keys). No method of transmission or storage is 100% secure. See also the in-app “Data & Security” summary.

Changes

We may update this Privacy Policy from time to time. The “Last updated” date at the top of the in-app document will change when we do. Material changes may also be noted in release notes or store listing text. Continued use after an update means you acknowledge the revised policy.

Contact

Privacy questions or requests: janlongerich@proton.me

Paid customers may also reference the contact on their Lemon Squeezy receipt.

Same content is in the app under Privacy. Rebuild/rezip if you want the store build to match before upload. Say if you want a public URL version hosted somewhere for the AMO “Privacy Policy URL” field.