Your work should be understandable to you—including how its data is used.

Account information

We store your name, email address, optional company name and mobile number, country, time zone, account status, email-verification state, plan, and whether you accepted the terms. Passwords are stored as hashes, not as readable passwords.

Project and conversation information

We store project names and settings, prompts, chat messages, analysis results, generated source and versions, build and verification results, preview and publication records, and the changes you request. This history lets limewAI reopen a project and improve the app you already built.

Uploads

When you attach an image or supported file, we store the file, its name, type, size, checksum, and its link to the project message. Images may be resized and compressed for web use. If image understanding is enabled, the image and your message are processed together to produce a short description used by the build.

Usage and technical records

We record jobs, AI operations, token and cost usage, credit ledger entries, preview activity, publication activity, audit events, and operational logs. Authentication records may include session identifiers, browser information, and IP address.

Billing records

We store the plan or credit pack, basket and order identifiers, amount, currency, purchase status, callback history, provider transaction reference, invoice or receipt number, and plan renewal information. Payment details entered during hosted checkout go to PAY2M and are not collected as card records by limewAI.

• Create and secure your account, keep you signed in, verify your email, and help you recover access.
• Understand your request, generate and validate app source, show previews, apply edits, and publish the version you choose.
• Read an attached image when the feature is enabled, or keep it as a visible attachment when it is disabled.
• Measure AI and platform usage, reserve and charge credits, settle purchases, manage subscriptions, and produce receipts.
• Detect failures and abuse, investigate technical problems, improve reliability, and keep an audit trail of administrative actions.
• Send account, payment, renewal, and service messages needed to operate your account.

limewAI uses OpenAI for parts of request analysis, app generation, corrections, translation, semantic verification, and image understanding. The information sent can include your prompt, a compact description of the project, selected existing source files, validation errors, and attached images when image understanding is enabled.

We send the context needed for the operation rather than your complete account record. The resulting source, analysis, descriptions, and usage details are recorded in limewAI so the build can continue and its cost can be accounted for.

When you start a payment, limewAI sends the order amount, currency, basket ID, description, email address, and mobile number to PAY2M. The hosted payment page handles the payment step. limewAI verifies the callback against the stored order before credits or plan changes are applied.

The browser return page alone does not grant credits. limewAI keeps payment callbacks and settlement records so duplicate callbacks do not grant the same purchase twice and an administrator can review a payment when automatic verification is unavailable.

limewAI uses first-party cookies and browser local storage for signed-in sessions. The customer access token is set for up to 24 hours and the refresh token for up to 30 days. A short-lived, HttpOnly, SameSite=Lax cookie is used during Google sign-in, with the Secure flag in production.

We also use local browser storage for small interface choices, such as whether a project naming prompt was dismissed. The current site does not load an advertising-cookie system in the application code.

Account and project records remain while the account and project are active so that you can reopen work, review its history, and continue editing. A customer can delete an owned project when it has no active build job; linked project records are then removed through the project deletion relationships.

Interactive preview machines are temporary and are stopped during cleanup, while version source and saved preview material are retained so the project can reopen. Free-plan published apps are eligible for removal after 30 days without recorded activity. Paid publications do not use that free-plan inactivity limit.

Platform application logs are configured for 14 days. The production runtime database keeps seven days of automated backups. Runtime backup objects are versioned; non-current backup versions expire after 90 days.

Plan, publication, and renewal settings can be changed by the owner in limewAI’s admin settings. The current value shown inside your account applies where it differs from a starting default described here.

You can view and update account details made available in Settings, see your projects and their history, download generated source, export a project to a connected GitHub account, remove project media, and delete an owned project when no build is active.

If you need a copy or correction that is not available through those controls, or want an account-level deletion request reviewed, use the signed-in Support area. Some billing, security, audit, and legal records may need to be retained after other account data is removed.

limewAI is intended for adults and for people using the service with the authority of their organization. A child should not create or use an account without the involvement and permission of a parent or legal guardian.

We do not intentionally ask for a child’s age or design the service to collect children’s personal information. If a parent or guardian believes a child supplied personal information, they can use the signed-in Support area to ask for review and deletion.

We may update this policy as limewAI’s features, providers, or legal obligations change. The current version will remain available at this address, and material account-related changes may also be communicated inside the service.

Last updated: 13 October 2026.