Your projects and data

Information about NIMBO for Windows and the browser. Updated: 26 October 2026.

Full privacy policy for your shared account — Windows, browser and phone

Projects on your computer

Without signing in, projects, uploaded images and settings are saved locally in the app profile. They are not uploaded to an account. You can download a project copy as a file. Uninstalling the app preserves its profile, so remember your saved files when using a shared computer.

Images and projects from photos

Object cutouts, recognition of text and inspiration colours, and composition matching run locally. Image recognition downloads model files on first use in the browser; the Windows installer includes them in its package. These tools do not upload photos. The AI-powered “Project from photo” feature requires separate consent before sending a photo and starting the operation. Its history stores the photo, description and returned result on the device and in the full workspace backup.

Shared account and synchronisation

The shared account is available once NIMBO enables the service. When sign-in is disabled, the app tells you it is unavailable; you can work on local projects. When registering, you provide an email address and set your own NIMBO password. We create the account after you verify the address with a one-time email code. You subsequently sign in with that address and password. On your first sign-in, projects from this device are added to your account. Synchronisation covers saved projects, images referenced in projects, custom elements, sets, client databases, inventory, price lists and business settings. Do not upload third-party personal information that you do not need for your project.

The email verification code and forgotten password reset link are delivered by Resend, which receives the recipient address, sender and message content, but not your projects or password. The NIMBO server hosted on Render handles account and project data. We do not ask for your email account password. A verification code is valid for 10 minutes, a password reset link for 30 minutes, and a session cookie keeps you signed in for up to 30 days. The server stores passwords only as protected hashes with individual salts, along with hashes of codes and tokens. It does not store passwords in plain text. Resetting a forgotten password invalidates existing sessions on all devices. Automatic cleanup removes expired challenges, links and sessions within the following hour at the latest.

PRO and purchases

In a mobile app that supports this feature, you can link your NIMBO account to a purchase verified by the App Store or Google Play. The server checks the purchase with the original store and makes verified PRO access and a shared AI allowance available to devices signed in to that account. Windows and the browser do not make purchases through a mobile store. Deleting a NIMBO account does not cancel subscriptions with Apple or Google.

Once online purchases are enabled, PRO can be purchased through Stripe in the browser and on Windows. When you start a purchase, we send Stripe your verified NIMBO account email address and technical identifiers for the account, billing relationship and purchase attempt. The NIMBO server processes Stripe customer, checkout session, subscription, invoice and transaction identifiers, subscription statuses and dates, and information about payments, refunds or disputes. This data is used to process payments, confirm PRO access for the same account and prevent duplicate purchases. You enter card details directly on Stripe’s website; NIMBO does not receive the full card number or CVC. You manage a subscription purchased through Stripe in its billing portal, accessible from NIMBO.

The payment provider’s data processing practices are described in Stripe’s privacy policy.

Control over your data

We retain account data, cloud projects and assets until they are deleted. Deleting a project removes its content from the active database but leaves the metadata and marker needed for synchronisation. The “Delete account and projects” feature requires re-authentication within the previous 10 minutes and removes the account, password hash, its sessions, email verification challenges, password reset links, projects, assets and store links. It does not remove separate technical purchase records needed to verify and restore entitlements, or guest copies, exports and data on other devices. Messages in your inbox and email data held by providers have separate retention policies.

Before deleting an account with a Stripe purchase, NIMBO confirms cancellation of its Stripe subscription and closure of open checkout sessions; if this cannot be confirmed, account deletion is paused. Technical payment records retain Stripe identifiers and their links to technical identifiers of the deleted account, information about cancellations, refunds and disputes, and a protected email address hash (HMAC) linked to PRO history. The hash allows a previously used trial entitlement to be recognised if someone registers again with the same address, including where the known PRO history came from a linked mobile store. Retained records allow delayed payment notifications to be handled and prevent access being granted again after a refund or account deletion. Deleting a NIMBO account does not automatically delete customer data or billing history in Stripe.

We delete identifiers for completed or released PRO operations and links between their elements 90 days after creation; for older entries, the period runs from the end of the short operation reservation. Cleanup takes place hourly and after the end of the relevant billing period. Unsettled reservations remain until their costs are resolved; cost accounting records are kept separately. The full policy also describes AI processing, recipients and other retention periods. To request access to, correction or deletion of data, contact the controller identified above.

To prevent repeated use of the free trial by creating additional accounts, we store a protected hash of the device identifier and information that the offer has been used. Android and Windows provide a hash of the system installation identifier, while iOS provides a random identifier stored in the keychain. The browser stores a separate protected cookie identifying the browser for up to 400 days. We do not use this data for advertising or tracking across other services. Trial usage history remains after sign-out and account deletion for as long as the offer is available, to prevent the trial being granted again. Creating an account alone does not activate PRO or a trial; a subscription with a payment method must be confirmed.