Privacy policy

Deleting your NIMBO account and associated data

You can ask NIMBO sp. z o.o. to delete your account and its associated data even if you cannot access the app. You do not need to install the app or sign in to send a request.

1. Email nimbosklep@gmail.com with the subject “Delete NIMBO account and associated data”.
2. Provide your NIMBO account email address and state that you are requesting deletion of the account and its associated data. Where possible, send the message from the email address linked to the account. If you no longer have access to that inbox, explain this in your message.
3. We may ask for proportionate verification that the account belongs to you. Do not send passwords, sign-in codes or payment card details. We will reply to the address you use to send the request; section 9 explains how requests are handled.

You can also delete your account in the app: after signing in, open “My account”, go to “Account deletion”, select “Delete NIMBO account” and confirm. If the app asks you to sign in again, do so and repeat this step.

What is deleted: the account deletion feature removes your email address and account, protected password hash, cloud projects and assets, sessions, verification codes, password reset links and the account’s store link from the active database. In an email request, you can also ask us to delete other data associated with you.

Data retained and retention periods: separate purchase records, data needed for accounting and abuse prevention, and records of how your request was handled may be retained as described in section 8. That section also sets out retention periods for AI reports (180 days) and selected operation data (90 days), as well as rules for disaster recovery backups and provider data. Deleting your account does not delete local workspace copies, exports or messages in your inbox.

Subscriptions: deleting your NIMBO account does not cancel a subscription purchased through Google Play or the App Store. To stop future charges, cancel it in the store where it was purchased. For Stripe purchases, we confirm cancellation of the subscription and closure of open checkout sessions before deleting the account; if you encounter problems, contact the email address above.

Deleting data without deleting your account

You can ask NIMBO sp. z o.o. to delete selected data while keeping your NIMBO account. You do not need to install the app to send this request.

1. Email nimbosklep@gmail.com with the subject “Delete NIMBO data without deleting account”.
2. Provide your account email address and specify which data you want deleted, such as particular projects and images or event information stored in them. Clearly state that you want to keep your account. Where possible, send the message from the address linked to the account; if you cannot access that inbox, explain this in your message.
3. We may ask for proportionate verification of your entitlement to the data. Do not send passwords, sign-in codes or card details. We will reply to your message and confirm the scope of the action taken on your request in accordance with section 9.

Deleting projects: you can also delete individual projects in the app without closing your account. Deleting a project removes its content from the active cloud database. The identifier, title, type, version number and deletion marker needed for synchronisation remain. They are retained until the account is deleted. Your account data and other projects remain available.

Other data and retention periods: data needed for accounting, security or handling your request, and information held by providers, are subject to the rules and periods set out in section 8. If your request covers this data, we will tell you what has been deleted and what must be retained. Also delete separate exports and local copies from the places where you saved them.

If you want to delete the whole account, follow the instructions for deleting your account and associated data.

1. Who is responsible for your data

The controller of data relating to the operation of the NIMBO app is NIMBO spółka z ograniczoną odpowiedzialnością (a Polish limited liability company), ul. Krokusowa 44, 87-700 Rożno-Parcele, Poland; KRS 0001267076, NIP 8911645496, REGON 545729561. For privacy enquiries, data access and deletion requests, email nimbosklep@gmail.com or write to the postal address above, marked “NIMBO Privacy”. Please indicate how you would like us to respond. Do not send passwords, access codes or payment details. This policy covers the NIMBO mobile app and its connections to online services. The provisions below concerning the shared account, synchronisation, PRO, data recipients, retention and your rights also cover the use of that account in NIMBO for Windows and in the browser. The policy does not cover the separate online shop or other websites you may open from the app.

2. Data stored on your device

NIMBO lets you design without creating an online account. Your profile name, decoration designs, selected photos, logo, price list, equipment, event calendar and any client information you enter are stored in the app’s storage on your device. When you work without signing in, saving your profile does not send this information to the NIMBO server. When you work without signing in, workspace backups, project files, proposals and exports leave the app when you choose to save or share them. Section 2a describes synchronisation after signing in. The provider of your chosen drive, messaging service or device backup service processes this data under its own policies. If you enter information about your clients, you are responsible for having a legal basis for processing it and providing them with the appropriate information.

2a. Shared account, synchronisation and PRO

The shared account connects the versions of NIMBO that support it on phones, Windows and the web. Sign-in and synchronisation become available when NIMBO enables the service. If the service is disabled, the app tells you that sign-in is unavailable. You can continue working with local data.

When registering, you provide an email address and set your own NIMBO password, then verify the address using a code sent through Resend. Your account is created after you enter the correct code. You subsequently sign in with your email address and NIMBO password. We do not ask for your email account password. The server stores your email address, account identifier and creation date, a protected password hash with an individual salt, hashes of verification codes, session tokens and password recovery tokens, their expiry times, and attempt counters to prevent abuse. We do not store passwords in plain text. Resend receives the recipient address, sender and the message containing a verification code or password reset link, but not your password, projects or client information. On Windows and in the browser, a session cookie keeps you signed in to your account.

After you sign in, the app may copy your local workspace to your account and synchronise changes. The NIMBO server hosted on Render stores projects, images placed in them, event information, supported client databases, equipment, price lists and settings. The range of custom elements, sets and preferences covered depends on the app version; not every media library is synchronised. Before sign-in, the app informs you that local projects will be copied. Cloud data belongs to the signed-in account and is made available to devices signed in to that account. Synchronisation does not request AI analysis.

Shared PRO access may come from an account-linked purchase verified by the App Store or Google Play in a mobile app that supports this feature, or from an online purchase as described below. NIMBO for Windows and the browser reads the verified entitlement for the same account; it does not make purchases through a mobile store. The server processes a technical access identifier, product identifier, purchase confirmation, subscription status and expiry, and AI allowance usage. It stores mobile store purchase references in encrypted form and some identifiers as hashes. This allows PRO access to be verified on other devices and prevents the same purchase from being linked to a different account. We do not receive your payment card number or your Apple or Google account password. You manage a subscription purchased through a mobile store in that store.

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.

Sign in with Google

In versions of NIMBO that support this feature, you can choose to sign in with Google. Google verifies the account’s identity and provides NIMBO with an account identifier, email address and email verification status; the standard profile scope may also include a name and photo. NIMBO stores the email address and a persistent link to the Google account identifier. It does not store the name or photo from your Google profile and does not receive your Google password. The identity token is checked during sign-in and is not stored in the account database.

If the email address matches an existing NIMBO account, linking requires additional verification that you can access that account. Depending on the existing sign-in method, this means a NIMBO password or an email code. For addresses whose current ownership Google does not verify as the email provider, NIMBO may also require an email code. Linking preserves the projects, purchases and trial usage history of the same account. Signing in with Google alone does not activate PRO or a free trial.

To secure sign-in, we use a one-time attempt valid for 10 minutes and, in the browser, a technical cookie linking that attempt to the device. Automatic cleanup deletes expired attempt data. We retain the Google link until the NIMBO account is deleted. Deleting the account removes this link but does not delete the Google account. Google also processes sign-in data under its own privacy policy.

3. Photos and artificial intelligence features

Selecting a photo for a project does not start AI analysis. Before the first transmission, the app asks for your explicit consent. After you consent and choose to create a project, we send the selected photo or crop and the description you entered through the NIMBO server hosted on Render to OpenAI, the AI model provider. When creating an illustration, we also send the photo fragment and description needed to create it. The purpose is to recognise decorations and prepare an editable project or illustration. We do not send your entire photo library, address book or workspace. Information entered in the description or visible in the selected photo, including names or images of people, may be sent to OpenAI. Before sending, remove unnecessary personal information, documents and particularly sensitive information. The service is not intended to identify faces. You can refuse consent or withdraw it in Account and profile → Privacy; you can still use features that do not require AI. Withdrawal applies to future transmissions and does not affect the lawfulness of earlier processing.

4. Test access, the catalogue and technical data

To grant test access and account for project allowances, the server receives an installation identifier, app platform and access token. The database stores hashes of identifiers and tokens, the registration date, and operation counters and identifiers. If you choose access recovery, we also store the request code, its status, creation, expiry and review dates, and a link between the hashes of the previous and new access credentials. The request does not contain photos or projects. The AI provider’s token is not included in the app. Downloading the decoration catalogue and connecting to AI produce data needed to transmit information and secure the service, such as the IP address handled by the hosting infrastructure, request time and response status. NIMBO’s records also include the model, token count, operation duration and service cost. We do not record photo content or descriptions in the server application logs. We do not carry out advertising tracking or sell data.

5. Reports and contact

You can choose “Report AI result” next to an AI result. The selected category, your report description, platform, report identifier, a link to your service access and, where available, the generation identifier are sent to the server. The form does not automatically attach a photo or the entire project. Enter only the information needed to explain the issue. Reports are used to assess safety and improve NIMBO. We use correspondence about privacy to handle the request and confirm its completion.

6. Purposes and legal bases for processing

Providing selected features, test access and allowances is necessary to perform the contract for using NIMBO — Article 6(1)(b) GDPR. Voluntarily sending a photo and description to an external AI service is based on consent — Article 6(1)(a) GDPR. Security, abuse prevention, handling reports and establishing or defending legal claims are based on the controller’s legitimate interests — Article 6(1)(f) GDPR. Meeting obligations concerning individuals’ rights and legally required records is based on Article 6(1)(c) GDPR. Providing data is voluntary, but not providing data needed for a particular feature may prevent that feature from working. NIMBO does not use AI to make decisions that produce legal effects concerning you or similarly significantly affect you.

7. Recipients and processing outside the EEA

Render provides the server infrastructure and OpenAI provides AI processing. Once sign-in is enabled, Resend (Plus Five Five, Inc.) delivers verification codes and password reset links; its privacy policy describes how the service processes data. Data may be accessible to authorised people operating NIMBO and these providers’ subcontractors to the extent necessary to provide the services. Once enabled, online payments are handled by Stripe; section 2a describes the data shared. Information entered on Stripe’s payment page and transaction data it processes are also covered by its privacy policy. Apple and Google process data relating to app distribution, store accounts, testing and any payments under their own policies. Subscription purchases and renewals are subject to the terms presented in the relevant store. Using NIMBO does not in itself provide us with your payment card number. Using global providers may involve transferring data outside the European Economic Area, including to the USA. These providers’ agreements provide safeguards for such transfers, in particular the European Commission’s Standard Contractual Clauses or other applicable lawful transfer mechanisms. You can obtain information about safeguards and how to request a copy by contacting the controller. Do not assume that choosing a European server means AI processing takes place only in Europe.

8. How long we keep data

Workspace data remains on your device until you delete it. Uninstalling the mobile app removes its local files according to the operating system’s rules; separate exports and backups must be deleted with their recipients or providers. Photos and descriptions sent to AI are processed in the NIMBO server’s memory during the request; the server does not archive them. To let you retrieve a result after a connection is lost, the server stores the generated project and the task identifier and status for 24 hours from the task’s start. The result may contain lettering, names and element descriptions derived from the submitted material; it does not contain the source photo or a copy of the prompt you entered. After 24 hours, the result is no longer available, and automatic database cleanup deletes it within the following hour at the latest. We use store=false in Responses API requests. This does not mean zero retention at OpenAI: standard abuse monitoring data may be retained for up to 30 days, with exceptions relating to security or legal requirements. By default, API data is not used to train OpenAI models unless the service customer separately agrees to share it for that purpose. We delete or unlink test generation identifiers and technical links in general AI request records after 90 days; registration and access recovery request data for a particular test programme is deleted no later than 90 days after that programme ends. Aggregate cost data not linked to an installation may be retained to account for the service. We delete AI reports 180 days after submission. We retain correspondence about individuals’ rights for the time needed to handle the request and to demonstrate that we fulfilled our obligations or defend legal claims. Infrastructure logs and disaster recovery backups expire according to the provider’s cycles; deleted data is not restored to active use from a backup without reapplying the retention rules. If legislation or specific proceedings require certain data to be kept longer, we restrict further processing to that purpose.

Once shared accounts are enabled, we retain the email address, account data and cloud projects and assets until they are deleted. Deleting a project removes its content from the active database but leaves the identifier, title, type, version number and deletion marker needed for synchronisation. The account deletion feature (“Delete NIMBO account” or “Delete account and projects”) removes the account, password hash, its projects and assets, sessions, email verification challenges, password reset links and store link from the active database. For security, it requires re-authentication within the previous 10 minutes. An email verification code is valid for 10 minutes, a one-time password reset link for 30 minutes, and a session for no more than 30 days. Verifying an email address deletes the other challenges for that address. Resetting a forgotten password invalidates existing sessions on all devices and the remaining recovery codes and links. Expired challenges, links and sessions are removed by automatic cleanup within the following hour at the latest. Sign-in attempt counters are deleted after the period to which they relate ends.

Deleting a NIMBO account does not cancel subscriptions with Apple or Google or remove the separate technical purchase records needed to verify entitlements, restore purchases and prevent their reuse. 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. Deletion takes place during hourly cleanup and no earlier than the end of the relevant billing period. Unsettled reservations remain until their costs are resolved. Cost accounting records are kept separately. Account deletion also does not remove local workspace copies on other devices, guest copies, exports or messages in your inbox. You can contact the controller about other technical data. Account-related message data is also processed by Resend and your email provider under their own policies; a code’s validity period is not the email provider’s message retention period.

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.

9. Your rights

Within the limits set by the GDPR, you can request access to your data and a copy of it, rectification, erasure, restriction of processing and data portability. You can withdraw consent and object to processing based on legitimate interests. You have the right to complain to the President of the Polish Personal Data Protection Office; information: https://uodo.gov.pl. Send your request to the controller identified in section 1. To help match technical data, you may provide a report or operation identifier shown in the app; do not send your access token. We may ask for proportionate verification of your identity or entitlement to the relevant access. We respond without undue delay, normally within one month, with an extension possible in the circumstances set out in the GDPR. Not having an online account does not limit your rights regarding data processed on the server.

10. Security, permissions and updates

Connections between the app and its services use HTTPS. The app lets users select specific files, and permissions to save an export or photo are used for the action the user has chosen. Access credentials are protected by the device’s system mechanisms. NIMBO is a design and work organisation tool; it is not a service directed at children. Changes requiring fresh consent to send data to AI trigger another consent request before transmission. In the mobile app, the current policy is available under Account and profile → Privacy and at the public address provided in the app. Version date: 26 October 2026.

Sign in with Google

You can optionally choose “Continue with Google” instead of using a NIMBO password. Google verifies your identity, and NIMBO receives your email address, its verification status and a persistent Google account identifier. We store the link between that identifier and your NIMBO account. We do not receive your Google password or access to your email, contacts, calendar or Google Drive files. Profile data shared by Google is not needed for project synchronisation; the NIMBO server does not store your Google profile picture or profile name.

Verification takes place through Google services, which process technical connection data under their privacy policies. On Android, we use the system credential picker; on iPhone and iPad, the official Google Sign-In package; and on Windows and Mac, sign-in opens in the system browser. The Apple app may store Google sign-in state in the system keychain. NIMBO’s one-time confirmations expire within 10 minutes; a return code for the desktop app is valid for no more than 2 minutes. We do not include passwords, Google tokens or NIMBO session tokens in the return URL to the app.

Linking an existing account with the same email address requires additional verification of access to NIMBO. A new account remains FREE; signing in does not activate a subscription or free trial. Deleting a NIMBO account also deletes its link to the Google identifier. You can also revoke NIMBO’s access in your Google account settings.