Privacy Policy

Our representative in the EEA, the United Kingdom and Switzerland. The European Economic Area (the "EEA") is the European Union plus Iceland, Liechtenstein and Norway. "DataRep" (Data Protection Representative Limited, 77 Camden Street Lower, Dublin, D02 XE80, Ireland) has been our representative in the EEA, the United Kingdom and Switzerland since September 30, 2026. It acts under Article 27 of the European Union and United Kingdom General Data Protection Regulations and Article 14 of the Swiss Federal Act on Data Protection. If you are in one of those places, you can contact us directly, or ask a question or use your rights through DataRep:

• Email datarequest@datarep.com with "Nummbas" in the subject line.
• Use the form at www.datarep.com/data-request.
• Write to DataRep at its address in your country, listed in section 18. Address the envelope to "DataRep", not to Nummbas, and say in the letter that it concerns Nummbas.

UK VAT filing. Where UK VAT filing is available on your account, you connect Nummbas to HMRC, the United Kingdom tax authority, on HMRC's own sign-in page. We do not see or store your HMRC user ID or password, and we encrypt the access tokens HMRC gives us. A return is sent when an owner or admin submits it. Our support access does not let staff connect to HMRC or submit a return for you. With each request, the law requires us, as the supplier of the software, to send HMRC your public IP address and connection details, the time, your browser and device details (including a device ID stored in your browser), the signed-in user's email address, user ID and sign-in method, and our server's IP address and product version. If you do not want them sent, you cannot file through Nummbas.

Changes to your ad accounts. On the Scale plan, Nummbas can pause or resume campaigns, ad sets and ads in ad accounts you connected. It can also change campaign and ad set budgets, and add tracking tags to Google Ads accounts. Nummbas makes a change only after an owner or admin of your business approves it in Nummbas. It keeps a record of who approved each change, when, and the values before and after. Our support access does not let staff approve or make a change for you.

Website game. When the prize game on the website is running, it sets a cookie that identifies your device for 365 days to limit plays, whatever your cookie choice. For each play we record hashed codes made from that device ID, your network address and your browser type, and Cloudflare Turnstile checks that the player is a person. If you win, we ask for an email address to send you a link to confirm the prize and to add it to the account you then create. We delete play and prize records, including a winner's email address, 12 months after the game closes. We delete your email address sooner if you ask.

What you must provide. You must give us your email address, name, business name and a password to open an account. A trial or plan bought from us also needs a payment method, which you give to Stripe. Connecting a service, marketing email, and analytics and marketing tools are your choice, but a feature that depends on a connection does not work without it. We do not ask for information about health, religion or politics, but bank transactions and documents can reveal it.

Why we use information. The last column gives our legal basis if you are in the United Kingdom, the EEA or Switzerland.

Staff access. Authorized staff can see your account details in our admin tools and change an account, for example to reset a password. Staff with our highest admin role can open your account to troubleshoot, for up to 15 minutes at a time. These actions are recorded in our staff log.

Referral partners and FirstPromoter. FirstPromoter runs our partner program. Partners sign up and sign in at promote.nummbas.com, which FirstPromoter hosts under its own privacy notice. This policy covers what a partner sends to us directly. If an account owner arrived through a partner's link while marketing tools were on, we send FirstPromoter the owner's email address, the business ID and the referral once the email address is verified, and FirstPromoter tells the partner about the new referral. FirstPromoter reads subscription payments from Stripe to work out commissions. For that, while the partner program is running, we label each customer record at Stripe with the business ID, and new records carry the account owner's email address, whether or not a partner referred the business. For a referred business that pays through Shopify, Wix or BigCommerce, we send FirstPromoter the amount, currency, date and plan of each payment or refund.

No sale of your data. We do not sell personal information, and we do not sell or rent your business or financial data. When marketing tools are on, we send limited identifiers to advertising platforms to measure our own ads. They learn about visits and sign-ups to Nummbas and the first payment for a plan. We do not sell the data we read from your connected services. We send order details to an advertising platform only when you turn on sending to your own ad account there.

Information from Google. From Google Ads we read your ad accounts, campaigns, spend, ad text and ad images, including preview images of your ad videos. After an owner or admin approves, Nummbas can pause or resume Google campaigns, ad groups and ads, change campaign budgets, or add tracking tags to supported Google Ads links. We store this information with your other business data at our hosting provider, use it to show you your advertising results, and send it to our AI providers when the AI features in section 5 need it. Disconnecting Google Ads deletes the data we synced from it (section 8).

Where we use AI. AI is used for Nummbas-FO chat (including the files you attach and research on public web pages), the daily brief, daily opportunities, and the reports and documents Nummbas-FO generates. Where Nummbas Books is available on your account, AI also reads receipts and bills and suggests categories for bank transactions. Our AI providers are Anthropic and Google. Anthropic is our first choice. Google is the fallback, and its model also reviews answers, documents and translations.

What we send. We send your question, the conversation history and notes, the images and PDFs you attach, and the business data needed to answer, such as product sales and margins, recent orders, bank costs, ad campaigns, and contractor names and payments. For Nummbas Books, we send the receipt or bill with your business name, or the details of the bank transaction to be categorized.

What we do not send. We do not send the matching codes described in section 6, or any shopper email address from your synced orders and payments. A file you attach, a bank transaction or a Nummbas Books record can contain a person's name or contact details, and those are sent when they are needed to answer you. Web research searches for general topics and does not send your customer records. The demo sends nothing to an AI provider.

Training and benchmarks. We do not use your data to train AI models. Anthropic states that it does not use this data to train its models. We use Google's paid service, and Google states that it does not use prompts or responses sent through its paid service to improve its products. If an owner or admin turns on benchmark sharing, we add your business's monthly ad and sales figures to comparisons that combine at least 20 businesses, and turning it off removes them.

AI can be wrong. Nummbas-FO can make mistakes. Check important figures against your own records before you act on them.

Our role. We handle this information for you and on your instructions (section 1). You are responsible for telling those people how their information is used.

What we store about shoppers. For an order or payment from a store, marketplace or payment service, we store a "matching code". It is a hashed form of the shopper's email address or, where there is none, of the platform's customer ID. Amazon orders, PayPal payments and records with neither detail have no code. For orders from Shopify, WooCommerce, BigCommerce and Wix, we also store a matching code made from the shopper's phone number, where the order has one. For WooCommerce, BigCommerce and Wix orders, we also store a second matching code made from the shopper's email address in the form Google Ads uses, so that you can send the order to Google Ads. We also store the country and the state or region of the order, discount codes and tracking numbers. Where the platform provides them, we store how the shopper reached your store (such as the landing page, referring site and campaign), the payment method and the platform's customer ID. If you turn on the post-purchase survey, we also store each shopper's answer with their order, including anything they type when they choose Other.

Store tracking. If you turn on store tracking, a script from Nummbas runs on your store when the shopper allows analytics and marketing tracking under your store's cookie settings, or when your store does not ask shoppers for cookie consent. For each visit, we store the page where the shopper arrived, the referring site, information identifying the campaign or ad, the device type and a random visitor ID kept in the browser. We remove other information added after the question mark in the page address. We also store checkout and purchase events with the order number, and matching codes made from the email address and phone number given at checkout. We match each order to a recorded visit, including a visit the shopper allowed in the 30 days before, even if they declined tracking later. We use the shopper's IP address and browser details to block automated traffic. We keep them with a purchase for 8 days only when you send orders to your ad accounts, and do not store them otherwise.

Sending orders to your ad platforms. If you turn on sending, Nummbas sends each online order that store tracking recorded to your own ad accounts. We send an order only when store tracking recorded the purchase, which it does only when the shopper allowed marketing tracking or your store has no consent tool. For a shopper in the European Economic Area, the United Kingdom or Switzerland, or whose country we do not know, we send the order only when the shopper accepted marketing cookies in your store's consent banner. To know whether a shopper accepted, store tracking keeps each cookie choice your store's consent banner reports, with its time and the random visitor ID, for 12 months. We send the order's value, the time of the order, the ad click the shopper came from, the shopper's IP address and browser details, and the shopper's email in a hashed form. We do not send names, addresses, phone numbers or the items bought.

What we do not store about shoppers. We do not store shopper names, street addresses or phone numbers with synced orders. We read the shopper's email address and phone number to make matching codes and do not store them with the order or payment. There are two exceptions. We store the description of each Stripe payment as your checkout wrote it, so it can include a name or an email address. And if you turn on the post-purchase survey, a shopper can type a name or contact details into its Other box, and we store what they type. We store marketplace buyer IDs only in hashed form. From Klaviyo, Gorgias and Recharge we store counts and totals, not individual records.

The matching code is still personal information. It is a pseudonym, not anonymous. The same email address produces the same code for every business that uses Nummbas.

Nummbas Books is different. Where Nummbas Books is available on your account, it stores what you put into your books about your customers, suppliers and contractors. That includes names, email addresses, postal addresses, the email address each invoice was sent to, and a tax ID, which we encrypt apart from its type and last four digits.

Suppliers in Inventory. Where you use Inventory, it stores the supplier details you enter for purchase orders: names, email addresses, the extra email addresses you copy on purchase orders, phone numbers and postal addresses. A purchase order you send by email goes to your supplier from "your business name via Nummbas", and replies go to your own email address.

Deletion and copy requests. When a shopper asks a Shopify store to delete their data, or eBay tells us an eBay account was deleted, we clear the matching code or buyer ID, country and region on that shopper's orders. We also delete that shopper's survey answers for the orders Shopify names in the request, whether or not it includes an email address. When Shopify asks us to delete a shopper's data, we delete their recorded visits, events, order matches and matching codes, using their email address, phone number or order numbers. For a shopper using another store platform, contact us to delete their recorded visits, events and order matches. A matching code that is also on a Stripe payment is not cleared from the payment automatically. For that, and for any other deletion request from one of your customers, tell us and we will remove their matching code and location from your order and payment data. When Shopify passes on a shopper's request for a copy of their data, nothing is sent automatically. The store owner can ask us for what we hold, and we provide it within 30 days. When a store uninstalls Nummbas, Shopify asks us to erase a store, or a TikTok Shop seller removes our access, we delete the connection and its synced data (section 8).

If you are a customer of a business that uses Nummbas. Contact that business first. It decides how your information is used, and we pass on any request you send us. Where the law gives you a right to ask us directly, as Australian law can, we answer you ourselves within 30 days.

Where we store it. Our servers and database are in Singapore, hosted by Render. We disclose personal information to the recipients outside Australia in the table. The last column says whether the United Kingdom and the European Union have decided that the destination protects personal information to a similar standard (an adequacy decision).

If your subscription ends. Your account and data are not deleted. You can still open Settings to subscribe again or to close the account.

Closing your account. Sign-in access ends straight away. If the account owner closes the account, it is closed for every team member, and its share links stop working. You can ask us to restore the account for 90 days. After that we delete it, with the exceptions below.

What the automatic deletion covers. After the 90 days, a daily process deletes the account, its users, the connections, the data synced from connected services, your Nummbas Books records and files, your Nummbas-FO conversations and our email records for the account. This process does not complete for an account that has a plan billed through Shopify, Wix or BigCommerce that our records show has not ended. For such an account, we delete the account and its data when you ask.

What is kept longer or deleted on request. Some information is not removed by the automatic process:

• Security logs and billing and tax records. Kept for the periods in the table. The staff log includes the record that the account was deleted, with the business name and plan or, for a single deleted user, that user's email address and name.
• Records held by our providers. These are records held by our payment, analytics, monitoring, support chat and referral providers. We ask the provider to delete them when you ask.

• give you a copy of the personal information we hold about you, in a commonly used format, or send it to another provider where that is technically possible;
• correct information that is wrong, out of date or incomplete;
• delete your personal information;
• stop using your information while a question about it is resolved; and
• have a person review a decision our systems made on their own (section 13).

Your right to object. You can object at any time to our use of your personal information for direct marketing, and we will stop. We treat product tips and milestone emails as direct marketing for this purpose. You can also object to a use that we base on legitimate interests, including the usage events our servers record. We then stop unless we have a strong reason to continue that the law accepts.

Cost and timing. There is no fee. We answer within 30 days, or within one month if you are in the United Kingdom or the EEA. The law allows longer for a complex request, and we tell you within the first month if we need it.

If we say no. We tell you why in writing and how to complain.

Things you can do yourself. In the app you can:

• close your account in Settings. The mobile apps do not have this option, and a plan billed through Shopify, Wix or BigCommerce must be cancelled there first;
• change your profile details in Settings;
• download your Nummbas Books records and, where your plan includes it, your reports, while your plan is active;
• delete a Nummbas-FO conversation, with its files;
• disconnect a service on the Integrations page; and
• change your cookie, email and notification choices (sections 11 and 12).

Where we ask first. Essential tools are needed for the Services to work. Analytics tools measure how the Services are used, and marketing tools measure our ads and record referrals. In the "ask-first regions", analytics and marketing tools stay off until you allow them. The ask-first regions are the EEA, the United Kingdom, Gibraltar, Guernsey, Jersey, the Isle of Man, Switzerland and Canada. We also ask first if your device is set to a European time zone or we cannot tell where you are. Everywhere else, these tools run until you turn them off.

Global Privacy Control and Do Not Track. We do not respond to Do Not Track signals. We treat a Global Privacy Control signal as a request to keep marketing tools off until you make a choice.

Where marketing tools run. On the website, marketing tools can run on every page. In the app, we load them only on the sign-in, sign-up and email verification pages. A tool that loaded there can stay in the browser page until it is next reloaded, and we set it not to follow you into the app. The referral cookie is also read on the pages used to install Nummbas from Shopify, Wix or BigCommerce. We send marketing tools no events from inside your dashboard or from shared report, invoice payment or receipt pages. On the demo, only Google Ads, Meta and Microsoft Advertising run. Our servers send sign-up and purchase events to advertising platforms only if marketing tools were on when you signed up or started the plan. Any email address or name we send to an advertising platform is hashed.

Video and app store badges. The website video loads from YouTube's no-cookie address only when you press play. YouTube then receives your IP address, device details and viewing data, and may store information in your browser. The App Store and Google Play badges in the website footer load from Apple and Google, which each receive your IP address, whatever your cookie choice.

Changing your choice. In the app and the demo, use the Cookie preferences link on the sign-in and sign-up pages and in the account menu. On the website, use the floating cookie button. When you turn a group off, we stop its tools and clear the cookies and browser storage they set on the website, the app and the demo, apart from one marker that records your refusal. Cookies that a provider set on its own site stay until you clear them. Turning a group off does not recall information a provider has already received, and it does not stop the events our servers record (section 2).

One purchase event can still be sent. If marketing tools were on when you started a plan, our servers still send Meta and Reddit one purchase event when your first payment is taken, usually when the trial ends, even if you have turned marketing tools off since. Email us before then if you do not want it sent.

Who sends them. Our emails are sent by Implemit Pty Ltd, trading as Nummbas, through Resend. We do not track whether you open an email or click a link in it.

Marketing and unsubscribing. We send marketing email only if you opt in, and only about the topics you chose. Every product tip, milestone, alert and summary email has an unsubscribe link that works without signing in. We act on an unsubscribe request within 5 working days at most. You can ask us where we got the contact details we use to send you marketing.

Push notifications. The mobile apps ask for your permission before they send notifications. Notifications can show business figures, including on a locked screen, and our staff can also send them to app users. You can turn them off in your device settings or in Settings in Nummbas.

Decisions our systems make on their own. The main ones are:

• whether a business can start a 14-day free trial, which depends on whether its business email domain has already had one;
• whether paid features are available, which follows your payments and subscription status;
• deleting a closed account after 90 days (section 8);
• recording a partner's commission; and
• security limits, such as request rates by IP address and a limit of 5 signed-in sessions.

What they use. These decisions use your account, billing and referral records and the domain of your business email address. We do not use Nummbas-FO or our insights to make decisions about you. If you disagree with an automatic result, contact us. A person will review it, explain it and correct it if it is wrong.

Nummbas is for businesses. It is for people aged 18 or over and is not directed to children. We do not knowingly collect personal information from children, and we delete it if we learn that we have. Your customer records can include younger people. We handle that information only for you (section 6).

Australia. We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. Section 7 lists the countries where we disclose it overseas.

Canada, including Quebec. Your personal information is processed and stored outside Canada, including in Singapore, Australia and the United States. It may be accessible to courts, law enforcement and national security authorities in those countries.

United States, including California. We do not sell personal information for money. When marketing tools are on, we send limited identifiers to advertising platforms to measure our own ads (section 4), which some state laws may call a "sale" or "sharing". You can turn this off in Cookie preferences.

Complain to a regulator. You can also complain to a regulator. In the United Kingdom and the EEA you can do this at any time, without complaining to us first.

How we tell you. If a change to this policy is material, we tell you by email or with a notice on the website before the change takes effect. The effective date and the date of the last update are at the top of this policy. We keep earlier versions. Ask us for a copy.

Languages. This policy is published in several languages. The English version controls. If a translation says something different, tell us and we will correct it.

Mail. Write to us at:

Implemit Pty Ltd, trading as Nummbas
Attention: Privacy Officer
Level 25 Capital Square Tower 3
1 Spring St
Perth WA 6000, Australia

Our representative, DataRep. Section 1 explains how to contact DataRep. Every address below starts with "DataRep".