Collect less. Keep it briefly. Never turn a lead form into a scan.

What we collect

• Pilot requests: work email, optional preview URL, critical journey, authorization attestation and limited campaign attribution.
• Site analytics: page and funnel events such as CTA clicks and successful requests. PostHog autocapture, profiles and session recording are disabled; analytics uses in-memory rather than persistent cookie storage.
• Pilot artifacts: scoped browser actions, screenshots, outcomes and reports created during an approved engagement.
• Infrastructure data: IP address and request metadata may be processed transiently by Vercel and used in a pseudonymous abuse-control bucket.

How we use it

We use request data to evaluate and respond to your pilot inquiry, deliver the agreed service, secure the site and improve JinuGen. Customer content and artifacts are not used to train or benchmark JinuGen unless you separately opt in in writing.

Who processes it

JinuGen currently relies on Vercel for hosting, Supabase for private intake storage, Google Workspace for operator notification, PostHog for limited product analytics, and the model provider agreed in a pilot scope. We disclose additional processors before they receive scoped customer data.

Retention

Pilot intake records default to deletion after 90 days. Raw run artifacts default to deletion within 14 days after delivery and redacted reports within 30 days. Active customer records, invoices and records required by law may be retained longer.

Your choices

You may request access, correction or deletion by emailing privacy@jinugen.com. Do not submit secrets, credentials, customer personal data or a target you are not authorized to test.

Changes

Material changes will be dated on this page. A signed pilot order may provide stricter project-specific handling; where it conflicts with this general notice, the signed terms control for that pilot.