Privacy policy

01Who we are

FluxNative is a product of InspireUI Ltd (“InspireUI”, “we”), the company behind FluxStore and FluxBuilder. We are the data controller for the personal data described in this policy. You can reach us at hi@inspireui.com.

02What we collect

We collect the minimum needed to run the service and support you:

• Account data: name, email address, avatar, and a password hash. If you sign in with Google or GitHub we receive your name, email address and profile picture from that provider, never your password there.
• Organization data: organization and team names, members, roles and invitations.
• Project data: the prompts you write, images and Figma frames you import, generated source code, previews, versions, builds and exports.
• Connection data: settings for services you connect to an app, such as Supabase, Firebase or a WooCommerce site. Secrets you enter are stored encrypted and are only used to set up your app.
• Usage data: pages visited, features used, device and browser type, IP address and error reports.
• Billing data: plan, credit purchases and invoices. Card details are handled by our payment provider and never reach our servers.
• Dev Kit devices, if you buy the Dev Kit: the name and an identifier of each machine you sign in with fluxnative-kit login, when it last checked for updates and when it was signed out. They are deleted with your account.
• Voice in the FluxNative phone app, if you turn it on: your phone turns what you say into text on the device, and only that text reaches FluxNative, as a chat message. We never receive or keep the audio. Apps you run inside the phone app never get the microphone.
• Support data: messages you send us and the context you attach.

03How we use it

We use personal data to provide the service (generate, store, preview and build your apps), to keep accounts secure and prevent fraud, to bill you, to answer support requests, to tell you about important changes, to understand which features are used so we can improve them, and to measure how our advertising performs.

Your prompts, projects and generated apps are used to produce your own apps. We do not sell them, share them with advertisers, or use them to train shared models.

04Legal basis

Where the UK or EU GDPR applies, we process account, organization, project and billing data to perform our contract with you; usage and security data on the basis of our legitimate interest in running a reliable, secure service; and marketing emails, and advertising cookies in the regions named under Cookies and local storage, only with your consent, which you can withdraw at any time.

05Who we share it with

We share data only with providers that help us run FluxNative, under contracts that limit what they may do with it:

• Cloud hosting, database and file storage for accounts, projects, previews and builds.
• AI model providers (Anthropic, OpenAI and Google) that process your prompts, designs and references to generate apps. We use their paid APIs: they process content on our behalf, do not train on it under those terms, and keep it only for a limited time.
• Lemon Squeezy, which acts as our payment provider and merchant of record for subscriptions, credit top-ups and invoices.
• Email delivery for account, billing and support messages.
• Error monitoring, configured to minimise personal data.
• GitHub, for issue tracking: a bug report you send is filed in our private GitHub repository with your account and organization ids, your description, the page address without its query, the app id, your browser details if you include them and recent errors from the page. Your name and email address stay in FluxNative.
• Google and GitHub, when you choose to sign in with them.
• Google, for advertising measurement: Google Ads, Google Tag Manager and Google Analytics receive visit and conversion data as described under Cookies and local storage.

We may disclose data when required by law, or when we believe in good faith that it is necessary to protect the rights and safety of our users or the public. We never rent or sell personal data.

06Your designs and Figma files

This covers the Figma files, designs, screenshots and images you bring into a project.

• Figma: the FluxNative plugin sends only the screens you check, and only after you choose Send. FluxNative never calls Figma's API and holds no Figma account, token or file link. The plugin signs in to FluxNative once per computer; its token can only list your apps and send screens to them, and stops working 90 days after its last use or when you sign out. Screens sent for a new app are deleted after 24 hours if you do not start building. The plugin's own policy is at fluxnative.app/privacy/figma.
• Where it is kept: in your project, with its pictures in our encrypted file storage, until you remove the design or delete the project.
• How we use it: only to provide the service for your project, such as building, previewing and releasing your app, and support you ask for. We do not put it in our templates, Explore, our marketing or other customers' apps without your written permission.
• AI model providers: Anthropic, OpenAI and Google receive the screens and images a task needs, to do that task. We use their paid APIs, under which they do not train on your content and keep it only for a limited time, for example to check for abuse.
• Our records: agent traces keep no images, prompts or source files.
• Who can open it: members of your workspace, by the roles you give them. No staff screen shows the designs or Figma files you send. In our admin console, staff in the owner, Support and Ops roles can open an app's details, with a picture of the built app's home screen and its store screenshots; each opening is recorded, and the console cannot edit an app or open its source. Other access is limited as described under Security.
• Share links: a link exists only when you make one. Anyone with it can open your app's preview until you turn it off or it ends after 30 days.
• Deletion: deleting the project or your account deletes the design, on the schedule under How long we keep it.

07How long we keep it

Project data is kept for as long as your account or organization exists. A deleted project stays in Trash for 7 days so you can restore it, then it is deleted from our database; deleting your account deletes its workspaces' projects at once. Files a project stored, such as images and design pictures, are deleted 30 days after that. Backup copies age out within 14 days after each deletion, so a deleted project is gone within about 60 days. Usage and error logs are kept for up to 13 months.

Billing records (plan payments, credit purchases and the credit history they paid for) are kept for 7 years from each record, which covers the six years after the end of the financial year that UK tax law requires. This includes the records of a deleted account; they are kept without your name or email address, then deleted. So that welcome credits and sign-up bonuses are given once per email address, we also keep a keyed hash of a deleted account's email address, never the address itself, for the same period.

Referral program, when we offer one: when a friend joins with your invite link, we keep a record linking the two accounts, with the link's code, when the friend joined, qualified and first paid, the credits granted and, if a referral is held for review, the reason. The person who invited you sees on their Invite friends page whether you joined, finished a first design or earned the reward, and gets an email when your workspace's first payment earns them a bonus; they see your first name only while your own Show my first name is on, which also shows it to friends who open your link. To prevent abuse we compare networks, never addresses: we keep a keyed hash (HMAC) of the network part of the IP address a friend signed up from on that record for 90 days after they joined, and, while the program runs, keyed hashes of the last 10 networks each account signed in from, kept no longer than 90 days after the account's last sign-in. We also compare the visitor identifier described under Cookies and local storage between the two accounts. When you delete your account, its network list is deleted and its invite link stops working; referral records stay, linked only by account ids, because the credits they granted are part of the billing records.

08Your rights

You can correct your profile and delete projects or your whole account from Settings. You may also ask us for a copy of your data, to restrict or object to processing, or to transfer your data to another service. California residents have the rights given by the CCPA; we do not sell personal data. Email us and we will respond within one month. You can also complain to your local data protection authority.

09Cookies and local storage

We use cookies and browser storage to keep you signed in, remember preferences such as theme, and protect the service.

To measure how our ads perform and which visits lead to a sign-up, a first or second message to our AI or a purchase, our public pages (such as the home page, pricing, templates, the blog and the docs) use Google Ads and Google Tag Manager, which also loads Google Analytics. They never run in the desktop app. In the signed-in app, the editor and the admin pages they load only at the moment a sign-up, your first or second message to our AI (never what they say) or a purchase is recorded; once loaded in a browser tab, they keep running until that tab is reloaded or closed, including on app pages you open from it. These Google tools set cookies and receive the pages you visit, your browser details and your IP address. In the EU and EEA, the UK, Switzerland and Brazil they set no cookies and use no ad data until you choose Accept in the cookie banner (until then Google receives only cookieless signals without identifiers); elsewhere they are on by default. You can turn them off or on at any time with Cookie settings in the site's footer; the choice is kept in your browser. While ad data is allowed (after Accept, or by default outside those regions), your account's email address may be sent to Google, hashed in your browser and never as plain text, so Google can match a sign-up, a first or second message or a purchase to an ad click (enhanced conversions); Reject stops it.

To count visits, our own site keeps a random visitor identifier and a 30-minute session identifier in your browser's storage. So that only people are counted, a page is reported only after you move the pointer, touch, scroll with a wheel or type, and a flag in the tab's storage remembers that you did. With each page you open we record that page's path, the site that referred you, campaign tags in the link, your country as reported by our network provider, and your device, browser and operating system type. In this visit record we do not store your IP address or your full browser details, we do not share it with anyone, and we keep it for up to 400 days. Clearing your browser's site data resets the identifier.

We also measure how our public pages (such as the home page, pricing, templates, the blog and the docs) are used with Notifuse, an analytics tool that runs on our own server (notify.fluxbuilder.com). It does not run in the signed-in app, the editor, the admin pages or the desktop app, and pauses while you are there. It keeps a random visitor identifier and a session identifier in your browser's storage (keys starting with nf_), sets no cookies, and with each public page you open it receives the page's address, the site that referred you, campaign tags and ad click identifiers in the link, how long the page stays open and how far you scroll, and your browser, language, time zone and screen size; like any server, ours sees your IP address when your browser connects. It follows your choice for Google's tools: in the EU and EEA, the UK, Switzerland and Brazil it loads only after you choose Accept in the cookie banner, elsewhere it is on unless you choose Reject, and Cookie settings in the site's footer turns it off or on. It never receives your email address or account id, and we do not share this data with anyone.

When you open a friend's invite link, your browser's local storage keeps that link's code and when you first opened it, for 30 days, so that the invite counts if you sign up later. Clearing your browser's site data removes it.

When our site runs an offer, such as a greeting bar for visitors from some countries or a discount on the pricing page, your browser asks our server which offer to show. To choose it we use your country as reported by our network provider, which works it out from your IP address; we do not store the country or the IP address with that request. If you claim credits from an offer, we keep a record with your account of the offer, the credits and when you claimed them, together with the country the offer was shown for and the country the claim came from, so we can spot offers passed on to others; it holds no name or email address and, like your credit history, stays linked only by account id after you delete your account. We also keep daily totals for each offer (offers shown, sign-ups, claims and refusals) that identify no one. Your browser's local storage keeps the offer you chose to claim until you sign up, for up to 48 hours; that you closed the offer bar, for 30 days; that you claimed an offer; and a pricing discount code you chose to apply, until you remove it or the offer ends. Clearing your browser's site data removes them.

10FluxNative for Shopify

This section covers the FluxNative: AI Chat & App app for Shopify stores. For the data of a store's shoppers and customers, the store (the merchant) is the controller and we process it on the store's behalf, under Shopify's API terms and the store's instructions.

• From the store: its Shopify address and name, the access Shopify granted the app, a Storefront access token the app makes for the store's mobile app, product and collection counts for the FluxNative channel, the store's chat settings and contacts, and the store owner's email address from Shopify, used only to notice when the store changes owners. When a staff member opens the app, Shopify tells us their name and email address; we use the address only to link or create the store's FluxNative account when they choose Continue as.
• From shoppers who use the AI store chat: the messages they type, the page and product they are on, the store's language and country, a random visitor identifier kept in their browser, and their IP address, which we hold in memory for up to an hour to limit abuse and pass to Shopify with the store's product reads so Shopify can protect the store from bots. Each message is sent to an AI model provider to write the answer; they process it on our behalf and under their API terms do not train on it. We do not store conversations: an answer to a common first question may be kept for up to 10 minutes without anything that identifies the shopper, and we log only counts such as how long a reply took. Shopify product data is read live and never used to train models.
• From shoppers who use Leave a message in the chat: their email address, question and the page they asked on, sent with their consent by email to the verified email address of the FluxNative account the store is linked to, with their address to reply to. We do not keep a copy; our email provider keeps its delivery record, and the hourly limits hold their IP address in memory for up to an hour.
• From customers who sign in to a store's FluxNative mobile app with the store's customer accounts: their name, email address, phone number, addresses and orders are read by the app on their phone from Shopify with their own sign-in. They are not stored on our servers. When a signed-in customer asks the chat in the app about an order, their last five orders are read for that answer only.
• Requests and removal: we answer Shopify's customer data and erasure requests for a store (we hold no shopper data at rest, so there is nothing to send or erase today), delete the app's Shopify sessions when the app is uninstalled, end the link to the FluxNative account when the store chooses Disconnect, and delete the store's record, token and chat settings when Shopify asks 48 hours after an uninstall. The store's FluxNative account and apps stay the owner's until they delete them. Records of purchases made through Shopify's billing (the store's address, the FluxNative account, amounts and Shopify's charge ids) are accounting records and are kept after that; they hold no shopper data.

Shoppers and customers should contact the store first; the store, or anyone, can reach us at support@fluxnative.app.

11Security

Data is encrypted in transit and at rest, and secrets you give us are encrypted separately. Access to production systems is limited to staff who need it. No system is perfectly secure; if we become aware of a breach affecting your data we will tell you as the law requires.

12FluxNative for WordPress

This section covers the FluxNative WordPress plugin (FluxNative – AI Chatbot, Product Writer & Mobile App for WooCommerce). It works without a FluxNative account and sends us nothing until the site's owner links the site. It has no usage tracking, statistics or calls home. For the data of the site's visitors and customers, the site's owner is the controller; when the site spends FluxNative credits, we process that data on the owner's behalf.

• Linking a site: when the owner chooses Use FluxNative credits, the plugin sends us the site's address, its name and a random install id, and shows a code. The owner approves the code on fluxnative.app while signed in, so no FluxNative password is typed into WordPress. We check that the address is the site that asked, then give it a token that can only make AI calls and read its credit balance. We store only hashes of its tokens.
• AI calls on FluxNative credits: each call sends the content the task needs, such as a visitor's question and the last messages of the chat (and, for a signed-in shopper who turned on the assistant's memory, the preferences it keeps for them), the product, policy or article passages the chat found, or a product's facts and keywords for the writer, with the site's address and install id. We pass it to an AI model provider, which processes it on our behalf and under its API terms does not train on it. We do not store the content; we keep the site's credit use (calls and credits per month) with the workspace's billing. Photos sent for photo search are processed in memory and never stored.
• Search by intent on FluxNative credits: once the owner starts it on the plugin's AI tab, the site sends us its published products' texts (name, categories, tags, options and descriptions) in batches, and later a visitor's search words. Our own embedding model turns them into numbers (vectors) in memory, on our servers, with no outside provider; we keep neither the texts nor the vectors, which are stored only in the site's own database.
• Push notifications: the site sends each push for its own app straight to Firebase Cloud Messaging or Apple's push service, with the phone's push token and the message (title, text and the screen it opens). Push tokens are kept on the site and do not pass through FluxNative.
• What stays on the site: the owner's own AI provider key (encrypted with the site's salts and sent only to that provider; with it, AI calls go from the site to the provider and never reach us), chat logs (kept only when the owner turns on Keep chats, off by default, for 30 days unless changed), the chat's counts and the questions it could not answer (without who asked, 90 days), a signed-in shopper's assistant memory (only after they turn it on; they see, change and delete it in the app or under My account), search data, messages between shoppers and the store, and app sign-in sessions.
• Unlinking and deletion: Unlink on the plugin's AI tab, or Revoke under Profile › Connected sites, ends the site's tokens at once. The site's credit use stays as a billing record (How long we keep it); its address, name and install id are deleted with the workspace.

Visitors and customers should contact the site first; the site's owner, or anyone, can reach us at support@fluxnative.app.

13International transfers

Our team and some providers are located outside the UK and the EU. Where personal data is transferred internationally we rely on adequacy decisions or standard contractual clauses.

14Children

FluxNative is not directed at children under 16 and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will remove it.

15Changes to this policy

We will post changes here and, for material changes, email account owners before they take effect. The date at the top shows when the policy last changed.

16Contact

Questions about this document can be sent to hi@inspireui.com. InspireUI Ltd operates FluxNative.