Private work should stay private

Data we process

Omnable processes account identifiers from Clerk, initial inquiries, questionnaire answers, optional prior-model outcomes, private attachments, research and generation jobs, saved prompts, artifact versions, usage records, and operational security metadata.

Do not submit secrets or regulated personal data unless you are authorized to process it and the intended AI use is appropriate.

How data is used

We use this data to authenticate requests, operate the prompt workflow, enforce usage limits, reconnect durable jobs, preserve version history, prevent abuse, and fulfill deletion requests.

Normal application logs do not contain raw prompts, attachment contents, provider responses, access tokens, or private account data.

Private AI processing

Initial inquiries, questionnaire answers, optional prior-model outcomes, and relevant source material are sent to configured AI providers only to perform an acceptable-use check or the requested research, question preparation, generation, or internal quality evaluation. Every new prompt journey is checked before its bounded online search begins, and every generated prompt receives a hidden acceptable-use verdict before publication. Omnable may place a temporary quota hold to make the check idempotent; a blocked or unavailable check releases that hold without consuming a journey.

Your runs remain private to your account and do not automatically become shared examples or model-training material managed by Omnable.

Storage and service providers

Clerk provides authentication, Neon provides the PostgreSQL data store, Vercel Blob stores private attachments, and Vercel infrastructure operates the application and durable workflows. Configured AI Gateway providers process generation requests.

Before you submit a questionnaire, unfinished selections and additional context are stored only in this browser tab's session storage for that session and question batch. The draft is cleared after the server confirms the answers and is not synchronized across tabs, devices, or accounts.

Attachments upload directly from your browser into a private, account-scoped Blob path. Omnable checks the declared size, filename, content type, digest, image signature, or text encoding before making a file available to a generation.

Durable workflow execution records are encrypted by Vercel but may contain step inputs and outputs needed to recover a run. Authorized project operators can access those records. Their retention follows Vercel's applicable service contract and any supported project controls verified by the operator; Omnable does not promise a configurable Workflow retention window unless Vercel exposes and confirms one for the deployed project. Each provider handles data under its own contractual and security obligations.

Retention and deletion

Product records and accepted attachments are retained while needed to provide your workspace and satisfy security or legal obligations. Upload authorizations expire after five minutes. Rejected file objects are queued for immediate removal from private Blob storage, and pending or rejected validation records carry bounded expiry markers for cleanup.

Account deletion can be queued from Settings and covers Omnable's primary sessions, messages, jobs, artifacts, saved prompts, learning records, caches, and private attachment objects. Encrypted workflow history, provider processing records, and backups follow their configured or contractual retention periods and may expire after primary product data is removed. Durable deletion queues may require a limited completion period.

Your controls

You can review saved work, remove individual sessions and prompts, and queue deletion of your account data. Omnable does not sell personal data or use private prompts for advertising.

Policy changes will be reflected on this page with a revised effective date.