Privacy Policy for Image2Image AI

1. Local image preview

Selecting, dropping, or pasting a JPEG, PNG, or WebP creates a preview in your browser. The page may show its filename. Choosing or removing a preview does not submit a generation request or change the original file.

2. When you generate

With enabled access, clicking Generate sends your image, prompt, and output settings through this site’s server to Kie for Nano Banana 2.1 processing. Kie’s terms and privacy notice apply to its processing.

Kie describes uploaded files as temporary for 24 hours. Result links are also temporary. Removing a preview or History entry does not delete provider files. Do not submit sensitive documents, credentials, or unnecessary personal information.

3. Generation records and History

Successful account results are kept for seven days after success is confirmed. Private-code tasks and results use a seven-day window from task creation. Unconfirmed account task records may be kept while their outcome and reserved credits are resolved. Expired files are periodically cleaned up. History shows up to 50 successful tasks for the current Google account or private-code browser session. The same Google account can access its History across browsers. Download results you want to keep.

Task records include identifiers, ownership, model, status, timestamps, result addresses, provider-reported credit use, and a duplicate-request fingerprint. They do not persist the original image, filename, or prompt text. “Remove from history” hides an entry; it does not cancel tasks, delete remote files, erase payment records, or restore credits.

4. Google accounts and private access

When Google sign-in is enabled, we store a hashed Google identifier, email, name, optional Google-hosted profile image URL, login timestamps, credit balance, and hashed session tokens. Account cookies last up to seven days. Signing out ends the current account session without deleting the account, balance, or other browser sessions.

A private access code uses a separate seven-day browser session. Clearing that session does not delete tasks or restore allowance; authorizing again creates a new owner and cannot recover its old History. A private-code session does not become a Google account or transfer its History to one.

5. Payments and credit records

When checkout is enabled, Stripe processes one-time credit purchases. We send your email and order details to Stripe and store order identifiers, package, amount, currency, payment status, Stripe session and event identifiers, and credit reservations and ledger entries. This site does not collect card details.

Account, order, payment, and credit records are separate from generation files and may be retained beyond seven days for account operation and reconciliation. Signing out or hiding a History entry does not delete these records.

6. Browser storage, providers, and contact

The browser may store the last task identifier and its time for status recovery, and briefly pass prompts through session storage. Copy buttons write to the clipboard. Editing or copying a prompt does not generate an image.

Opening pages requests site files; hosting services may keep access logs. No separate analytics or advertising integration is used. Google, Stripe, Kie, and external links have their own data handling. The support panel shows available contact details; opening it does not send a message.