Security

Jev API security: understand your data path.

Understand Jev API Pro authentication, input handling, stored decision history, provider processing, and available controls before sending business messages.

What we store

Account email, hashed session tokens and API keys, credit ledger entries, order records, and decision results are stored in Cloudflare D1. Decision input text is not saved in history; a request hash supports idempotency. Results can still contain sensitive labels you define.

Where submitted text goes

Classification input is sent server-side to OpenRouter and its model provider. Their processing terms also apply. Do not submit passwords, payment details, regulated records, or confidential material unless you have assessed and accepted the complete processing chain.

Controls and limitations

Requests have size limits, authentication checks, timeouts, and usage limits. Payment callbacks use HMAC signatures and amount checks. We do not claim SOC 2 certification, dedicated tenancy, or a contractual uptime guarantee. Report security concerns to contact@jevapi.pro.

contact@jevapi.pro
Ask about plans & usage

Find a product answer

Answers come from the published product guide. For account-specific questions, contact support.

Contact
DAILY BONUS

2 free credits, every day

Claim 2 free credits each UTC day — 14 across seven claims. No purchase needed. Credits do not expire.

    Resets at 00:00 UTC. No streak required.

    Try a decision →

    Take the next decision into your workspace.

    1 anonymous attempt per day · 20 signup credits · No card for the trial

    Sign in ↗

    Tell us what you need

    Describe the workflow you want to classify, the volume you expect, and the outcome you need. We reply by email.

    10–2,000 characters. Never include passwords, API keys, or payment details.