Effective 3 November 2026
Privacy Policy
This is the whole policy, written to be read. It describes what Numulo (numulo.com) actually does with data, not what a template says a website might do.
- The free generator does not need an account. The invoice you build is sent to our server only to render the PDF and is not stored.
- We keep basic usage records about free PDFs (country, total, item count, which template) for 90 days, including the IP address, to stop abuse. Never the invoice contents.
- If you make an account, we store what you put in it: your business details, clients, invoices, expenses, photos, and the receipt photos you scan for expenses. Your data is never sold and is never used for advertising.
- These outside services do work for us: Cloudflare (hosting, and the gateway to the AI model), Resend (sending email), Anthropic (the AI model), and OpenRouter (a backup route to the same AI model). Google serves our fonts.
- We count visits anonymously: a number per page per day, with no cookie and nothing that identifies you (details under Counting visits).
- No third-party analytics scripts and no trackers for normal visits. One cookie, only when you are signed in. The single exception: if you arrive by clicking one of our ads, that advertiser's conversion tag loads for that visit so we can tell whether the ad led to a download or a signup. We advertise on Google and on Facebook, and only the one you clicked is ever loaded (details below).
- Some pages carry one of our how-to videos, which are hosted on YouTube. The page shows our own still image and loads nothing from YouTube until you press play. Then the video plays from YouTube's privacy-enhanced domain (youtube-nocookie.com) under Google's privacy policy. We count that a video was started, with no identifier, the same way we count page views.
- You can delete documents, clients and expenses yourself in the app, delete every invoice at once from Settings, and ask us to delete your whole account.
The free generator (no account)
What stays in your browser
Your business name, address, phone, email, logo, accent color, and currency are saved in your browser's local storage so you do not have to retype them. Client details, line items, and dates are not saved anywhere between visits. Your theme choice (light or dark) is also stored locally. None of this is sent to us until you download or email an invoice.
What is sent to our server, and what we keep
When you download a PDF, the invoice is sent to our server, rendered, returned to you, and discarded. We do not store the invoice contents. We do keep one usage record per PDF for 90 days: the date, which template or tool it came from, the country, the currency, the total, the number of line items, whether it had a logo, whether the AI helper was used, a random per-tab identifier (so we can tell that an AI draft led to a download), and the IP address. The IP address is there to rate-limit and to investigate abuse. A separate aggregate counter (with no IP address) keeps overall totals by template and country.
If the PDF endpoint is unreachable, the PDF is generated inside your browser instead and nothing is sent at all.
The AI Invoice Helper
The job description you type is sent to Anthropic's Claude model to draft line items. It travels through Cloudflare's AI Gateway, or through OpenRouter when that route is unavailable. We send the description and the trade (for example "plumber"); we do not send your business name, client, or any other invoice fields with it. We log the request for 90 days (date, trade, length of the description, outcome, token counts, IP address), not the text itself. Anthropic, and whichever of Cloudflare or OpenRouter carried the request, process the text to produce the response under their own terms; we do not use it to train anything.
Before the request is made, Cloudflare Turnstile runs a bot check in your browser. Turnstile is operated by Cloudflare under Cloudflare's privacy policy.
"Email it to me"
If you ask us to email you the PDF, we first send a short message to the address you give, with a link that works once for one hour, and send nothing else until that link is used. Until then we hold the invoice and the address for that hour only, and if the link is never used both are deleted. Once you confirm, we send the PDF through Resend and do not keep it. We then store the address, the date, and which template it came from, and send exactly one follow-up email the next day. Every such email has a one-click unsubscribe link; once you use it we keep the address only as a do-not-email record so it is never emailed again, even if it is entered a second time. Each address can be sent at most three of these confirmation messages a day, and this feature also runs a Turnstile bot check.
Saving an invoice to an account
If you choose "Save it to my account" after downloading, the invoice you made (everything in the form except your logo) is sent with your sign-up or sign-in request and kept with that link until you use it. When you open the link it becomes a draft in your account, and any business details your account does not have yet are filled from it. If you never open the link, the invoice is deleted with the sign-up request after at most 30 days.
The live demo
The demo at numulo.com/demo creates a temporary account filled with made-up sample data. You do not give an email address to use it. Whatever you type into the demo is stored in that temporary account and is deleted, with the account, 24 hours after you started it, or sooner if you press Reset. The demo sets the same sign-in cookie as a real account, for that period. Nothing sent from a demo account is emailed to anyone, and its AI drafting is limited. If you sign a sample proposal or change order as the pretend customer, the approval record (typed name, time, IP address, browser) is deleted with the demo. If you choose Keep this account and confirm your email, the demo becomes an ordinary account and everything below applies from then on; records you signed before that point are then kept like any other approval.
Starting a proposal at numulo.com/start without an account works the same way, without the sample data: a temporary account holds your draft for 24 hours, nothing in it can be sent or shown to a customer, and it is deleted with everything in it unless you press Send and confirm your email, which makes it an ordinary account with your draft in it.
Accounts (trial, Free, Pro and Team)
Signing in
There are no passwords. You sign in with a one-time link we email you through Resend. The link works once, for 15 minutes, or 24 hours when it creates a new account. Asking for another link does not cancel an earlier one that has not been used yet. When a new address asks for an account, we check its domain (the part after the @, never the full address) against public lists of temporary inbox services, and look up when the domain was registered through the public RDAP directory at rdap.org; temporary inboxes and domains registered in the last 60 days cannot open an account. New accounts can be opened only from the United States, Canada, Mexico, the UK, Ireland, Australia and New Zealand, judged from the country our hosting provider reports for your connection; signing in to an existing account works from anywhere. To stop one network opening many accounts, we keep a one-way fingerprint of the IP address a new account signed up from (made with a secret key, so it cannot be turned back into the address) for 30 days. When an email you send to a customer bounces or is reported as spam, our email provider tells us, and we use that to spot accounts sending unwanted mail. If you ask for a sign-up link and do not use it, we keep your address and send one reminder with a fresh link about an hour later; the address is deleted when you sign up, or after 30 days if you never do. Signing in sets one cookie, nm_sess, which keeps you signed in for 30 days and is used for nothing else. Signing out removes it. While you are signed in we note when you last used the app and which app page you had open (updated at most once a minute, only while the page is visible), so we can see who is using it and help when something goes wrong. It is kept with your account and is never shared.
What we store
- Your email address and when the account was created. During a trial in which nothing has been created yet, we send up to two short tips (around day 2 and day 7), each with a one-click opt-out, and a notice the day before the trial ends.
- Your business profile: name, address, phone, email, logo, accent color, currency, invoice numbering, default tax rate, payment link, review link, and your settings (reminders, late fees, review requests, AI suggestions).
- Your clients, invoices, estimates, recurring schedules, and expenses, exactly as you enter them, plus their status history (sent, viewed, paid, approved) and timestamps.
- The payments you record against invoices (amount, date, how it was paid, and your note), and the ways to pay you that you save in Settings, which are printed on your invoices.
- When a customer taps "I've paid" on an online invoice: the time, how they say they paid, and their note. It is shown to you and marks nothing as paid until you confirm it.
- Change orders on accepted proposals and, like proposal acceptances, a permanent record of each approval: the typed name, any signature drawn on screen (kept as the pen strokes), the time, the IP address and browser, the agreed content and totals, and the consent wording.
- A permanent record when a customer agrees to receive and sign documents electronically before reviewing a proposal (the time, the IP address and browser, and which version of that wording was shown), and when you or a teammate sign a proposal for the business (the typed name and title, who signed, the time, the IP address and browser, and a fingerprint of the content signed). We remember the name and title you last signed with, to offer them next time.
- Forms you upload for customers to sign (PDF files and where you placed boxes on them), and your customer's answers on them, kept with the signed acceptance; for a form signed on an invoice page, a permanent record of the typed name, the time, the IP address and browser, and the answers.
- Job photos you attach to invoices, and your logo, in Cloudflare R2 storage.
- A scan or photo of a proposal your customer signed on paper, if you add one when you record the paper signature, kept in Cloudflare R2 storage with that signing record. Only logins of your business can open it.
- Receipt photos you scan or snap for an expense, kept with that expense in Cloudflare R2 storage, and the text read from each one (the store, items, prices, totals and date as printed), kept with the expense so you can search your expenses by what is on the receipt. They are deleted when you delete the expense or the account, and they go in the tax package you download. Expenses you type in by hand have no photo.
- A count of each AI feature you use (tokens and timing, not the content), so we can see what the product costs to run.
On a Team plan, everyone you invite sees the same clients, invoices, and reports. Billing and team management stay with the account owner. When a teammate is removed, their sign-in stops working immediately and the documents they created stay with the account.
Bank statements and imports
To match bank deposits to invoices you upload a CSV export from your bank. We never connect to your bank and never ask for bank credentials. The file is read on our server for that request and is not stored. We keep only the statement lines you act on (the date, description, amount, and whether you matched it to an invoice, made it an expense, or ignored it), so the same line is not offered twice if you upload the statement again. Importing customers, a price list, or unpaid invoices works the same way: the file is read, you choose the rows, and only those rows are saved. Importing never emails anyone.
Email we send on your behalf
When you send an invoice or estimate, request a review, or have automatic reminders turned on, we email your client through Resend. Those emails go out from a Numulo address with your business email set as the reply-to, so replies come to you. They contain the document, the amounts, and a link to the online copy. Reminders are opt-in, at most one a week per invoice and four in total.
Email we send to you
A welcome email when you sign up, a notice the day before a free trial ends, and a notice one to three days after it ends. These are about your account, not marketing lists, and we do not send newsletters.
Connecting an AI app (Pro)
You can connect an AI assistant such as ChatGPT or Claude to your account from Settings, AI apps. When you do, you choose what that app may use through our connector, from: your invoices, estimates and payments; proposals and change orders; your customers; expenses; your price list; your reports; your warranties; and, only if you tick it, creating drafts, which lets it read your saved templates and save new draft proposals, estimates and invoices in your account. Your business name, currency and settings are always included. Unless you also choose to share real customer names and contact details, each customer appears to the app as a code such as C-482913 instead of a name: we replace customer names, email addresses and phone numbers wherever we can recognise them, including inside descriptions and notes, and leave out their addresses. A code is separate for each business and opens the customer only inside your own Numulo account. A nickname or a first name on its own written into a note may not be recognised. It cannot send anything to anyone, or change or delete anything; a draft it creates stays in your account, marked in its private notes with the app that made it, until you send it yourself. It never receives your private notes or the links that open your customers' pages. Each person on an account connects for themselves and the app sees only what that person sees in Numulo.
What the app reads is sent to the company that runs it and is handled under that company's terms and privacy policy, not ours; we do not choose or control what it keeps. Your customers' details are personal information you hold about them, so connect only an app you trust with it. You can see every connected app in Settings, change what it may read, or disconnect it, which ends its access at once; and suspending an account ends every connection. We keep the connection itself (which app, which person, when) and a record that it was made or ended, never a copy of what the app read. Access tokens are stored only as one-way hashes.
AI features for accounts
Each AI feature sends only what it needs to Anthropic's Claude (through Cloudflare's AI Gateway, or OpenRouter as the backup route), and nothing is stored on the AI side by us:
- Receipt capture sends the photo you upload so the amount, date, vendor, and category can be read and the receipt's printed text transcribed, in one request. We keep the photo and that text with the expense (see What we store); the AI provider does not keep either for us. If the photo cannot be read, the photo is still kept and the expense is marked for you to fill in.
- Estimate drafting and the invoice helper send your job description.
- Follow-up drafts for overdue invoices send the invoice number, amount, due date, client name, and your business name.
- Price sanity-check, which is off unless you turn it on in Settings, sends a line item's description, quantity, and rate as you finish typing it.
- Bank statement categories: money-out lines that our own keyword rules cannot place are sent as the description and amount only (at most 60 lines per upload) so a bookkeeping category can be suggested. Money-in lines, your customers, and your invoices are not sent. Bank descriptions are whatever your bank printed, which can include a merchant name and the last digits of a card.
- Old invoice photo on the import page sends the photo you upload so its customer, dates, and line items can be read into a draft. The photo is not kept.
- Insights on the Reports page, which is off unless you turn it on in Settings, sends aggregated figures for your last 24 months: totals by month and quarter, counts, percentages, how quickly invoices get paid, proposal win rates, expense totals by category, the names of the items you bill, and the 5-digit ZIP codes taken from your customer addresses. Your customers are replaced by labels ("Client A", "Client B") before anything is sent, and the list of which label is which customer stays on our side and is only ever sent back to your own browser. No invoice, no document, no customer name, address, email, or phone number is included.
Client portal and statement links
Every sent invoice or estimate has an online copy at a link that contains a long random token. Anyone with the link can view that one document, the same way a shared document link works, so treat the link as you would the invoice itself. Opening it marks the document as viewed. If your client approves an estimate, we store the name they typed and the time. Client statements work the same way.
Customer pages and customer sign-in
A business on a paid plan can give each of its customers one page, at a link with a long random token, that lists that customer's sent invoices, estimates, proposals, change orders, payments and receipts with that business, plus the business's payment instructions. It never shows drafts, private notes, or anything about other customers. Anyone with the link can view the page, so treat it like the invoices themselves; the business can replace the link at any time, which stops the old one working. We record the day the page was last opened so the business can see it. A customer who lost the link can enter their email address at numulo.com/c. If a business has that address on a customer record, we email a one-time link that lasts 15 minutes and opens a list of those businesses (name and logo only); each choice opens that business's own page, and no page ever combines businesses. We do not keep the address you typed unless a link is sent, and then only until the link is used or expires. We give the same answer whether or not the address is on file. A business can choose not to be listed.
Payments
Numulo does not process payments and never sees card numbers. If you add a payment link (for example a Stripe Payment Link, PayPal.me, or Venmo), it is placed on your invoices as a button and QR code and your clients pay you directly through that provider under its terms.
A business on a paid plan can connect its own Stripe account so that its customers can pay an invoice by card or bank transfer. Stripe processes those payments for the business. When a customer presses Pay by card we send Stripe the amount, the invoice number, the business's name, the customer's email address when the invoice has one, and our own reference numbers for the invoice and the account. The customer then enters their card or bank details on Stripe's page; those details never reach Numulo. Stripe tells us when a payment succeeds, fails, is refunded or is disputed, and we keep Stripe's reference for the payment, the amount, the date and whether it was a card or a bank payment, so the invoice can show as paid. For the business we keep its Stripe account reference and whether Stripe has enabled it to take payments.
If you subscribe to a paid plan, the subscription itself is handled by Stripe. Stripe collects and stores your card details; we store only a Stripe customer reference so we know which account is paid.
Counting visits
To see which pages people read and where they stop before signing up, the site counts a few moments: a page being viewed, a Start free trial, Create my first proposal or live demo click, the homepage email box, the save-to-account box after a free download, and a draft from numulo.com/start being started, edited, downloaded or sent. Each count is one number for that page, that day, and whether the visit came from one of our ads or not. Nothing else is recorded: no cookie, no IP address, no browser or device details, no email, and nothing that links one count to another or to you. Automated browsers are not counted.
Push notifications
Off until you turn them on in Settings, separately on each phone, computer, or copy of the Numulo app. Turning them on gives us that device's push address and encryption keys, kept with your account. We then notify you of the events you leave switched on (a customer opening, accepting or declining a proposal, opening an invoice, approving a change order, saying they paid, or a payment arriving online) with the customer's name, the document number, an amount, and a link into the app. On Android and in browsers the message is encrypted so the push service in between cannot read it; on iPhone it travels through Apple's push service. Turn them off in Settings or in your device's notification settings; we delete a device's address when its push service reports it is gone. Demo accounts never get notifications.
Cookies and local storage
One cookie, nm_sess, set only when you sign in. No social media pixels and no third-party analytics scripts. Local storage holds the business details and theme described above, on your device only.
If you arrive from one of our ads (the link carries a click ID from the platform you clicked on), we load that platform's conversion tag for that visit and for return visits from the same browser within 30 days. From Google that is the Google Ads tag (gtag.js); from Facebook or Instagram it is the Meta pixel. The tag sets that platform's advertising cookies and reports back to it when you download a PDF, request a sign-in link, create an account, create or share a proposal, a customer opens one, or you subscribe, so we can tell which ads work. It reports that the step happened, never what the document says or who the customer is. The ad link also carries the ids of the campaign, the ad group or ad set, and the keyword or ad the click came from; if you then create an account, those ids are kept on it so we know which ads bring customers. They identify the ad, not you.
If you arrive from one of our postcards (the QR code or the web address printed on it, which open numulo.com/mail), no advertising tag of any kind is loaded. Your browser remembers for 30 days that the visit came from a postcard, along with the mailing batch and trade printed in the QR code, and if you create an account those two labels are kept on it so we know which mailing worked. They identify the mailing, not you. We got your business address from the public Johnson County contractor licensing roster or from your public Google business listing; tell us and we will take you off the list.
Only the platform you actually clicked is ever loaded: a Google click never loads Meta's pixel and a Facebook click never loads Google's tag. Neither is loaded for visits that did not start with an ad click. Google describes its handling of this data in its advertising policy, and Meta describes its own in its privacy policy.
Who else handles your data
| Service | What it does for us | What it sees |
|---|---|---|
| Cloudflare | Hosts the site and the API, stores account data (D1 database, KV, R2), runs the Turnstile bot check, and keeps the aggregate usage counter | All traffic to the site and everything stored in an account |
| Resend | Delivers every email we send | Recipient addresses and the email contents, including PDF attachments in transit |
| Anthropic, reached through Cloudflare or OpenRouter | Run the AI features | Only the inputs listed above, per request |
| Google Fonts | Serves the typefaces | Your IP address and browser details when the font files load |
| Google Ads | Conversion measurement, only for visits that began with a click on one of our Google ads | Google's click ID and cookies, and which of our pages a download, signup, or subscription happened on. We keep the campaign, ad group, and keyword ids of the click on an account created from it |
| Meta (Facebook and Instagram) | Conversion measurement, only for visits that began with a click on one of our Facebook or Instagram ads | Meta's click ID and cookies, and which of our pages a download, signup, or subscription happened on. We keep the campaign, ad set, and ad ids of the click on an account created from it |
| Push services (Google, Apple, Mozilla, depending on your device) | Deliver notifications to devices where you turned them on | The device's push address and the message (encrypted end to end on Android and in browsers) |
| Stripe | Subscription billing for paid plans, and card payments on invoices for businesses that connect their own Stripe account | Your card and billing details, held by Stripe, not by us. For an invoice payment: the amount, invoice number, business name and customer email we send, and the card or bank details the payer gives to Stripe directly |
These providers process data to deliver the service, under their own privacy policies. We do not sell data to anyone, and we do not share it with advertisers or data brokers.
How long we keep things
- Free-generator usage records and AI helper logs: 90 days.
- Error logs (which may include an API path and a message, not invoice contents): 30 days.
- Captured email addresses: until you unsubscribe, after which only the do-not-email record remains.
- Unused sign-up requests, including an invoice being saved to the account: until you sign up, or 30 days.
- Anonymous visit counts: kept, since they identify no one.
- Account data: for as long as the account exists. If a trial or paid plan ends, the account moves to the free plan: invoices from accepted proposals and the free plan's 3 invoices a month stay usable, other saved invoices, clients and expenses become read-only, and all of it is kept so it is there if you come back.
- Backups: nightly copies of the database and stored files are kept for 30 days, so deleted data can persist in a backup for up to 30 days after deletion.
- Signing records: every time a proposal is accepted, a change order or estimate is approved, a business countersigns, a customer agrees to sign electronically, or a form is signed, a copy of that record (the typed names, the time, the IP address and browser, the consent wording, what was agreed and any answers given, and the original file of a signed form) is also kept in a separate locked archive in Cloudflare R2 storage for at least seven years from the signing. During those seven years it cannot be changed or deleted, by you or by us, even if the document or the account is deleted, and we do not delete it afterwards. It is there so that either side can prove what was signed, and it is used for nothing else.
Deleting your data
Invoices and estimates: Settings has a "Delete all invoices" action that permanently removes every document and its photos. Individual documents can be deleted from the invoice list.
Proposals and clients: delete them one at a time from the Proposals and Clients pages.
Expenses: deleting an expense on the Expenses page also deletes its receipt photo and the text read from it.
Your account: send a message through the support form from the email address on the account and we will delete the account, its clients, documents, expenses, files, and settings, and confirm by email. Signing records stay in the locked archive for at least seven years from each signing, as described above. The team member or removed-teammate rules above apply to Team accounts. The steps are also on the account deletion page.
Captured email address: use the unsubscribe link in the email, or ask through the support form.
You can also ask what we hold about you or ask us to correct it, through the same form.
Security
Everything is served over HTTPS. Sign-in links, portal links, and unsubscribe links are long random tokens that expire or can be revoked. Account data lives in Cloudflare's infrastructure, and the app is a small codebase we review ourselves. No system is perfectly secure; if you find a problem, please tell us through the support form and we will act on it.
Children
Numulo is a business tool and is not directed at children under 16. We do not knowingly collect their data.
Changes to this policy
If how we handle data changes, this page changes and the date at the top moves. Significant changes to what we collect will also be mentioned in the app.
Contact
Questions, requests, and deletions: the support form. A person reads every message.