Privacy Policy

When you create an account: your email address (used only for sign-in and product email).

When you upload a resume: the PDF and the LaTeX source we extract from it. The PDF is processed in memory and discarded - we only store the extracted LaTeX. You can re-upload or edit it at any time from your account page.

When you tailor a resume: the job description text you paste, the company and role we extract from it, and the generated PDF.

When you pay: billing details are handled by Stripe - we never see your card number. We store the Stripe customer ID so we can match payments to your account.

We do not collect: cookies for advertising, third-party trackers, location data, contacts, or anything not listed above.

We use your data to deliver the service you signed up for. Specifically:

• Resume LaTeX is read each time you run a tailor.
• Job description text is sent to our LLM provider (currently DeepSeek) to extract company/role/skills and to rewrite the Skills section. We do not train models on your data.
• Generated PDFs are stored so you can download them later.
• Email is used for magic-link sign-in and, if you opt in, product updates.

• Generated PDFs: 7 days, then auto-deleted by a scheduled job.
• Job description text: 90 days, then auto-deleted.
• Resume LaTeX: as long as your account exists, or until you delete it.
• Account: until you ask us to delete it.

We share data only with the service providers we need to run the product:

• Stripe - billing
• DeepSeek - LLM calls for extraction and tailoring
• Vercel - hosting
• Neon - database hosting
• Fly.io - LaTeX compilation

We do not sell your data. We do not share it for advertising.

• Edit or delete your resume at any time from your account page.
• Cancel your subscription at any time via Stripe's portal.
• Email privacy@example.com to request account deletion. We'll honor the request within 30 days.

Note: Jiablo is not currently available in the EU, UK, EEA, or Switzerland. Visitors from those regions are redirected to a placeholder page.

We use TLS everywhere, hashed session tokens, and bearer-token authentication on internal services. We don't store passwords (auth is via email magic link). Billing is delegated to Stripe.

No system is perfect. If you find a security issue, please email security@example.com before disclosing publicly.

If we materially change what we collect or how we use it, we'll update this page and email account holders before the change takes effect.

For any privacy question: privacy@jiablo.com. For account/billing support: support@jiablo.com.