Privacy information

About this preview

UseJevAI is currently a development preview. This page explains how the preview handles data. It is not the final privacy policy for a paid public service. Operator details and a privacy contact must be confirmed before launch.

Playground inputs

Browsing a preset displays a saved example and makes no model call. When running is available, your text and questions pass through our server to OpenRouter. The application stores your input, questions, result, status and input-token usage so you can view your run history. Only your account can read its run details through the application. Signing in can temporarily preserve a draft in browser session storage. Avoid personal or confidential information in development tests.

Batch files

Selecting and previewing a Batch file happens in your browser. Submitting a batch, when live inference is enabled, saves the selected row inputs and questions to the server queue. Each executed row is sent to OpenRouter and its result is stored with the task.

Accounts and payments

We use cookies to keep you signed in. Email and security checks help prevent repeat trial claims. For these checks, we store a keyed hash of your email and a hash of the security check, not its original token.

Payment testing is limited to administrators using PayPal Sandbox. We store orders, payment references, and token activity. Real payments are not open.

Before public launch

Completed Playground and Batch inputs, question settings and results are available for 90 days after completion. You can delete completed runs or batches from Run history sooner. Deletion removes their saved content, while request identifiers and billing records remain for account reconciliation. Active or unresolved runs cannot be deleted until processing and billing are resolved.

Tokens & usage shows the last 12 calendar months of activity. This viewing window does not delete the financial ledger or change your balance. API requests are not listed in Run history; their technical data retention must be finalized before public launch. Scheduled cleanup runs hourly in the local worker, and expired history cannot be opened even before the next cleanup. Copies in backups and upstream providers have separate retention practices that must be finalized for production.

The final privacy policy will identify the service operator, service providers and the contact for privacy requests.