Privacy Policy | Liofx
Accounts, private media, payments and optional analytics at Liofx.
Last updated: 2026-11-04
Service information
Liofx stores account and authentication details, access permissions, prompts, selected models and generation settings, uploaded files, results and task, credit and cost-reconciliation records. Session cookies maintain sign-in. A signed guest cookie and a temporary credential held in the open page protect guest tasks.
Prompts and uploaded media are private. Public reference assets are separate from personal files. Private media requires authorization and uses expiring download access. Cloud generation sends the selected provider the prompt, settings and authorized access to required media. Browser-only tools process files on your device. Uploading happens only when you explicitly choose saving or continuing in a cloud editor.
Cloud image screening
When you choose to upload a static image for cloud editing or account storage, Liofx sends the image to SeeAPI for content screening before adding it to private object storage. A static WebP is converted to PNG for this check. A declined or inconclusive check does not create a stored Liofx image. We retain a file digest, task identifier and screening status to handle retries. SeeAPI handles its copy under its data handling policy.
Local editing and downloading do not send images to SeeAPI. Animated images remain available for local processing and download. The content policy explains allowed uses.
Storage and retention
Production records use Cloudflare D1 and media uses Cloudflare R2. Local development has separate simulated storage. Guest results are normally available for one hour; signed-in or claimed results for 30 days. Uploads remain available while linked tasks need them. Downloaded copies are outside service cleanup.
Delete completed creations from your history to remove access immediately. Storage cleanup runs separately and retries failures. Scheduled cleanup removes terminal prompts and request details. Minimal guest task records are normally removed after seven days. Unresolved provider submissions retain information required for reconciliation. Financial, account and security records have separate retention purposes and do not disappear when a media result expires.
Payments
Stripe and PayPal host checkout and process payment information for the methods they provide. Liofx records product, amount, currency, discount, payment status and provider identifiers needed to deliver credits, manage renewals and reconcile refunds. Full card details are not stored in Liofx or sent to analytics. Sandbox payments and credits are separate from production.
Optional analytics
Liofx uses PVUV on liofx.com and www.liofx.com only after you accept analytics cookies. It respects Do Not Track and Global Privacy Control. Refuse or withdraw consent using Cookie settings in the footer. Refusing analytics does not prevent product use. Umami is not used.
PVUV uses first-party visitor and session identifiers. We measure approved page paths, recognized source labels, external referrer origins, basic device/language and numeric performance measurements, plus bounded events for discovering tools, choosing models, viewing quotes, submitting tasks, saving results, choosing plans, applying the promotion and starting checkout. Confirmed payments and actual completed generation are reported from server records when consent remains active.
Analytics excludes prompts, filenames, media URLs, full query strings and fragments, form contents, emails, account identifiers, tokens and payment details. Account settings, authentication, administration, Billing and payment callbacks are excluded from browser tracking. My Creations is measured only as a general workspace path, without creation identifiers or media content. Revenue reports contain the confirmed amount and product, not a card or customer identity.
Local development, previews, sandbox payments and simulated generation do not enter production conversion statistics. Withdrawing consent stops further collection, removes this browser's analytics identifiers and cancels pending server reports for that visitor. It does not erase already aggregated reports. Re-enabling analytics after withdrawal starts on a fresh page load, without replaying events accumulated while opted out.
Contact and rights
For access, correction, export or deletion requests, contact support@liofx.com. Some records may be retained for outstanding transactions, security or applicable obligations. Necessary session, security and consent-preference cookies operate separately from analytics.