What this policy covers
This policy applies to the Jenna website, private design workspace, Vibe Library, voice experience, and support provided by the Jenna team. Jenna is currently a private beta.
Information we handle
- Account and workspace data: email address, authentication identifiers, workspace membership, plan status, and service usage.
- Project content: conversations, project briefs, project notes, selected vibes, instructions created from your request, designs Jenna makes, shortlists, and project status.
- Files and references: images, logos, product photos, filenames, links, and other material you choose to upload or share.
- Voice data: microphone audio sent for live transcription and responses, plus transcripts saved to the project conversation.
- Technical data: necessary cookies, session information, request metadata, error details, job status, and security or abuse signals.
- Team interactions: requests for human help and records of team members joining a conversation.
If a generation request fails, your browser may temporarily retain the request and attachment names in session storage so you can retry. That information normally clears after success or when the browser tab is closed.
How we use information
We process information to provide and secure Jenna: signing you in, remembering project context, interpreting requests, generating or editing images, storing and transforming previews, delivering downloads, running retryable jobs, enforcing beta limits, providing support, and improving reliability and design quality.
Jenna uses generative services behind the scenes. Your instructions, relevant project context, and reference images may be sent to those providers to plan work, transcribe voice, respond, and create designs. Review every design before you rely on it.
Providers and human review
We use service providers to operate Jenna:
- Supabase for authentication, database, storage, and related infrastructure.
- OpenAI for language, image generation and editing, and realtime voice features.
- Trigger.dev for long-running and retryable background generation work.
- Vercel for website and application hosting.
Authorized Jenna team members can review customer, conversation, project, and job information when providing requested help, investigating a failure, preventing abuse, or operating the beta. We limit this access to legitimate product and support work. Do not include sensitive personal information that is unnecessary for the design task.
Storage, retention, and security
Project records and generated assets are generally kept until you delete the project or the beta workspace is retired. Deleting a project removes its product records and schedules associated stored assets for cleanup. Provider security or abuse logs may follow each provider’s own limited retention schedule.
We use access controls, private storage, short-lived links, row-level database rules, server-held provider credentials, and encrypted network connections. No system is perfectly secure, and the beta should not be used to store regulated or highly sensitive information.
We do not currently use non-essential analytics or advertising cookies. If that changes, we will update this policy and add consent controls where required.
Your choices
You can archive or permanently delete individual projects in the workspace. You can also download generated assets and remove designs from a shortlist. A self-service account export and account-deletion flow is not yet available in the beta.
For access, correction, deletion, or privacy questions, use Stuck? Ask the Jenna team inside your authenticated Jenna workspace. If you cannot sign in, contact the person who arranged your beta access. We will verify requests before acting on account data.
Children, regions, and changes
Jenna is intended for adults and business use, not children. Do not use the beta if you are under 18. The beta is operated online and data may be processed in countries where our providers operate.
We may update this policy as the beta changes. Material changes will be reflected by a new effective date and, when appropriate, an in-product notice.