TryKrea3 / privacy

Privacy Policy

What TryKrea3 collects, why it is used, which providers receive it, and how to request access or deletion.

Oct 16, 2026Independent Krea 3 interface

This Privacy Policy explains how TryKrea3 (the “site”, “we”, or “us”) handles information when you use https://krea-3.com. It applies to this website and its account, image generation, billing, and support features.

Effective 17 October 2026. Privacy requests: support@krea-3.com.

TryKrea3 is an independent third-party visual workspace that executes Krea 3 (krea/k3-edit) and Krea 2 (krea/krea-2-medium-turbo) through the OpenRouter API. We are not Krea AI, do not operate Krea AI's models directly, and are not affiliated with or endorsed by Krea AI.

0. Three direct answers

Are prompts and images used to train our own model? No. TryKrea3 does not operate a foundation training cluster or sell a dataset made from your prompts, reference uploads, or generated outputs. A generation is securely relayed to OpenRouter so the requested image can be produced. OpenRouter does not train AI models on paid API prompts.

Can paid users use their output commercially? Yes, subject to the Terms, the rights you have in your reference inputs, and standard legal constraints. All paid credit packs include full commercial licensing rights.

Do failed or refused generations cost credits? No. A failed, timed-out, or upstream-refused run is returned to your account ledger automatically and immediately.

1. Information we collect

Account information

  • Email address, name, avatar, and encrypted credentials when supplied by you or your sign-in provider.
  • Google sign-in identifiers when you choose social authentication.
  • Locale and signup IP metadata used for anti-abuse and rate limiting.

Generation information

  • Prompts, reference images (Base, Item, Face, Style slots), resolution, aspect ratio, thinking tier, and pixel lock flags.
  • Output images, generation latency, model identifier, credit debit, and task status.

The active image model identifiers are krea/k3-edit (multi-reference editor) and krea/krea-2-medium-turbo (text-to-base generator).

Billing information

Stripe handles payment authentication and card details with 256-bit encryption. We store only the customer token, purchased credit pack ID, credit movement ledger, tax country, and transaction receipt. We do not store complete credit card numbers.

Usage, device, and security information

We collect page navigation events, approximate network country, browser logs, and Cloudflare Turnstile bot verification signals.

2. How we use information

We use collected information to execute image transformations, maintain your permanent credit balance, process Stripe payments, prevent automated abuse, debug errors, and fulfill legal or tax requirements.

We do not sell personal data and never use your reference images to train machine learning models.

3. Third-party infrastructure providers

Provider or partyPurpose
OpenRouter APISecurely relay generation requests to Krea 3 and Krea 2 inference nodes
Google OAuthOptional social sign-in authentication
StripePayment processing, tax calculation, invoices, and credit pack transactions
Cloudflare Workers, D1, and R2Host the web application, SQLite edge database, and object storage for temporary assets
Cloudflare TurnstileNon-intrusive CAPTCHA to detect bot abuse and brute-force attacks
AuthoritiesOnly upon valid, legally binding court orders

4. Retention & Deletion

Generated images remain associated with your account until you delete them or request account closure. Security logs and temporary rate limit counters rotate automatically. You may delete individual creations from your dashboard at any time.

5. Your choices and rights

You may request access, correction, export, or complete deletion of your account and visual assets at any time. Email support@krea-3.com from your registered account address. We respond to all verified privacy inquiries within 30 days.

6. Security

We enforce HTTPS across all endpoints, secure HttpOnly session cookies, cryptographic asset hashing, and strict role-based access for operational databases.

7. Changes and contact

We may update this policy periodically to reflect infrastructural changes. Material changes will be noted on this page. Inquiries can be sent to support@krea-3.com.

Written and maintained by TryKrea3 EditorPublished Last updated

Your first Krea 3 2K edit is free upon signup

Launch Krea 3 Editor