We know your mobile number or email — that is how you sign in. Your company's work sits on our server sealed, and the keys sit there with it, so a new phone can bring your company straight back. We could read it. We never look.
That is the same arrangement most apps have. The difference is we say so.
Phones get lost, dropped in slabs and run over. When that happens to your office phone, you should be able to pick up a new one, type your mobile, and have your company back — your rate book, your crew, your numbering, your company details — without ringing anyone. The same goes for the office computer and a crew member's phone.
A new phone that has nothing but your mobile number cannot open anything on its own. For it to get your company back, the keys that open your company's sealed files have to be kept somewhere it can reach once it proves who you are — and that somewhere is our server. The text message you get when your boss adds you carries nothing secret on purpose, so a text read over your shoulder, or sent to the wrong number, opens nothing.
The only other way to build it is to keep the keys on your phones alone. Then a lost office phone means starting again from your last backup file, and every lost crew phone means the office adding the man again by hand. We chose the lost phone coming home. That choice is why we could read your company's files — and it is why we tell you so, and promise that we never look.
On your own (Just me) you don't need to sign in, and none of your work goes on our server. If you do sign in — to bring back a store buy or a founding deal — we check it against our list. If you subscribe, your phone checks the subscription with us now and then. A docket you send a client to sign is the only work that travels, and nobody can open it but you and your client (below).
You sign in with your mobile or your email. A code is texted, or a link is emailed — no password, ever. Google's Firebase does the texting and the emailing, so it holds your mobile or email and a made-up number that means "this person" on any phone — never a rate, a client, an invoice or a docket. Google's sign-in helper is fetched from Google's servers when you sign in, and again whenever this phone or computer has to show it is still you — to fetch your company's files, say. When you press Send me a code, Google's robot-check (reCAPTCHA) may appear to make sure you are a person; it can set Google's own cookies, and Google's own Privacy Policy and Terms apply to that check.
On a computer, the office side locks after an hour away from the desk, or the moment someone presses Log out — the calculators stay open. Whoever sits down next taps their own face and gets back in by signing in, by their own PIN, or by the computer's own Touch ID or Windows Hello, and gets only what the owner lets them do. The PIN is kept on that computer as a salted hash — never the numbers themselves, and never sent to us. The fingerprint or face never leaves the computer: Cutulator is only told "yes, that was them". Said plainly: the lock covers the screen. The office's work is still saved in that computer's browser, so the computer's own login still matters. Phones do not lock — a phone already has its own lock.
Every parcel and pile below is sealed on your device before it leaves (AES-GCM, 256-bit). Some records are not sealed, and none of them holds any work: who you are, your fortnight date, the counters, the company's list, a founding deal, an office computer's ask to join, a buzz's push address and which company it is for, and on an invite the mobile or email, the company's name, the role and the key to its parcel. Here is all of it, and how long each thing lasts:
"Stops opening" is enforced by the server's own rules: after that date nobody — not you, not us through the app — can read the record back. Invites, crew updates, the day's jobs and signing links are then deleted, usually within a day.
Take it: Setup → Back up gives you one file with everything on that device — rates, clients, dockets, quotes, invoices, tickets and company details. It restores onto any phone or computer. The file is not sealed: anyone who has it can read it. On an office machine it also holds the company's keys, so it can open your company's files on our server. Keep it like a key — where only you can get to it, not in an email to someone else.
Delete it: in the app, Setup → Delete my account. It deletes your sign-in and what is yours on our server straight away, except the things listed below — usually in under a minute — and the app tells you when it's done. Before it does, it offers Back up so you can keep your own copy first. Your own tools and work on that phone or computer stay on it; if you are on a company's books, that device lets go of the company's copy, and the company keeps its own. Pressing it sends your sign-in proof and this phone's push address to our delete function on Google's servers in Sydney, which keeps nothing.
Five things stay after you delete:
Parcels already sent to someone else's phone, and signing links already sent to a client, stop opening on their own dates (7 days and 30 days) and are then deleted.
If you own a company and anyone else is on its books, make someone else an owner first — a company always has one.
No longer have the app? Email support@cutulator.com from the mobile or email you sign in with, and we will delete your account the same way, within 30 days. The same email deletes a company's sealed files too, if you own it. A real person answers it.
If your office takes you off its books, your phone lets go of the company's papers, and the company's invite to you is switched off.
Cutulator contains no analytics, no advertising, no tracking pixels, no third-party marketing SDKs and no crash reporting that identifies you. Nothing about you or your work is sold or shared, and nobody is profiling you.
Because a half-honest page is worse than none:
If you buy Cutulator through the App Store or Google Play, Apple or Google handles the purchase under their own privacy policies, and we receive no payment details.
If you buy on our website, Stripe handles the payment. Stripe collects your email and your card to process it; we never see a card number. Your purchase makes an unlock code, and your receipt — with the code — lives with Stripe and in your email.
Card payments to a company. When a company using Cutulator connects its own Stripe account, its clients can pay invoices and quotes by card. The card is typed on Stripe's own page and goes to Stripe — never to Cutulator. To open that page our server passes the company's Stripe account, the company's name, the paper's number, the amount and the currency to Stripe for that moment, and keeps none of it. The money goes straight to the company's own Stripe account.
When a company connects Stripe, our server passes the name, business number (ABN, EIN, VAT, company number or NZBN), address, phone and email from its Company card to Stripe so Stripe's sign-up starts filled in, and keeps none of it. Stripe also keeps, with that account, the made-up number that tells us which Cutulator account it belongs to — never a rate, a client or a paper.
When the office checks what has been paid by card, our server asks Stripe for the company's recent card payments. Stripe's answer includes the payer's name, email and card brand and last four digits; our server passes back only the paper's number, the amount, the currency and when it was paid, and keeps none of it.
You can say no to these and keep using everything else.
PDFs, spreadsheets and backup files the app makes are yours. Where they go — email, a message, your accountant, your cloud drive — is your choice, and once they leave the app they are governed by the service you send them through.
Cutulator is made by Jarrod Rapson, a sole trader in New South Wales, Australia, who is the controller of the information above. The services that carry it for us are Google (Firebase and Google Cloud), Stripe and Netlify; their servers may be outside your country.
We use your information only to give you the service you asked for: signing you in, putting you on your company's books, bringing your company back to a new phone, and keeping the free trial fair.
Wherever you are, you can ask us for a copy of what we hold about you, to correct it, or to delete it — email support@cutulator.com. If you are not happy with our answer, you can complain to your privacy regulator: in Australia the OAIC (Office of the Australian Information Commissioner), in the UK the ICO (Information Commissioner's Office), and in the EU your country's data protection authority.
Cutulator is made for people working in the trade. It is not meant for children, and we do not knowingly collect information from anyone under 16.
Cutulator's calculations have been carefully developed and tested by experienced concrete cutting professionals. However, all results should be treated as a guide and verified on-site before use. Job conditions, material variations, and site-specific factors can affect outcomes.
The App developer accepts no liability for loss arising from reliance on App results without independent verification. This includes but is not limited to:
Weights and lifting figures are estimates. Always work to the SWL / WLL of your own lifting gear and verify before lifting.
If this policy changes, the new version goes up at this address with a new date.
Questions about any of this go to the person who built the app:
Jarrod Rapson
support@cutulator.com