Privacy Policy

PeelBrief (“we”, “the service”) is available at https://peelbrief.app. For privacy questions, email hello@peelbrief.app.

This policy explains what we process when you use the PeelBrief website, account area, API, and browser extension.

Account: email, display name, user id. If you sign in with Google, we receive the name and email Google shares with your consent (OAuth).

Content you create: idea text, attachments (images, txt/md/pdf within limits), wizard answers, brief drafts, generated research and specs. Signed-in users’ briefs are stored in our database; drafts may also stay in the browser’s localStorage.

Service usage: project type and research market, quota counters (ideas, specs), subscription plan, technical request logs (time, status — never your password).

Payments: Stripe processes payment details. We receive payment status, Stripe customer/subscription ids, and related email — we do not store card numbers.

Browser extension: only text you explicitly send (within the character limit), the page URL/title, and UI locale go to our API. Extension history stays local in the browser.

Technical data: auth session cookies (Supabase), UI locale cookie/localStorage, and standard host access logs (IP, user-agent) on Vercel.

to create and maintain your account, authenticate you, and show the dashboard;

to generate ideas, validate niches, run research, and produce specs at your request;

to enforce Free-tier quotas and deliver paid plans;

to send transactional email (signup confirmation, password reset) via Resend;

to keep the service secure, prevent abuse, and maintain reliability;

to answer support requests.

We do not sell personal data. Processors required to run the product:

Supabase — auth, profiles, briefs, attachment storage;

Vercel — application hosting;

OpenRouter — LLM calls for ideas, research, and specs (your idea text and related wizard context are sent in the prompt);

SerpAPI, Yandex Wordstat / Yandex Cloud, Google Ads Keyword Planner, DataForSEO — market and search data for keywords/domains you or the pipeline specify (not your password or payment data);

Stripe — subscription payments;

Resend — email delivery;

Google — if you choose “Continue with Google”.

Providers process data under their policies and our agreements. If you publish an idea to the public catalog, that content becomes visible to other users.

Session cookies are required for sign-in (Supabase Auth). Without them, the account area and authenticated wizard do not work.

UI locale (RU/EN) is stored in a cookie and localStorage. Wizard drafts may remain in localStorage until synced to your account.

We do not run separate advertising trackers. If we add optional analytics later, we will update this policy and request consent where required.

Account data and briefs are kept while the account is active. After account deletion or a request to hello@peelbrief.app, we delete or anonymize data within a reasonable time, except where retention is required by law (e.g. payment records held by Stripe).

Infrastructure logs are retained for a limited period by the host. You can clear browser and extension local data yourself.

You may request access, correction, export, or deletion of your account by emailing hello@peelbrief.app. You can also change your password and manage sessions in the account area.

If you are in the EU/EEA or another jurisdiction with similar rights, you may object to or restrict processing and lodge a complaint with a supervisory authority. We may need to verify account ownership before fulfilling a request.

The service and some providers may process data outside your country (including the US and EU). By using PeelBrief you acknowledge such processing. We use established vendors with contractual data-protection safeguards.

PeelBrief is intended for adults (18+). We do not knowingly collect children’s data. If we learn an account belongs to a child, we will delete it after contact at hello@peelbrief.app.

We may update this policy. The current version is always on this page with the update date above. Material changes will be communicated by email or in-product notice when practical.