Privacy Policy
RedAI Studios Pty Ltd, ABN 36 700 870 695. Effective 19 September 2026.
The short version. You sign in with your work Google account so we know which company you belong to. We read your email address and nothing else about you. When you submit a receipt, the file goes into your company's Google Drive folder, where the office picks it up and matches it against the bank account. If your company asks it to, ReCeipt also emails a copy of each receipt to one address your company chooses — nowhere else. It has no advertising, no analytics, and no third party is given your data.
Who this is about
ReCeipt is operated by RedAI Studios Pty Ltd (ABN 36 700 870 695), Western Australia. This policy covers the ReCeipt web app at receipts.redmatic.com.au and any ReCeipt mobile app that signs in to the same service.
ReCeipt is your company's tool, and it does one job. You buy materials for a job, you photograph the receipt, and it lands in one Google Drive folder your company owns — the folder the office already watches. They pick the receipts up from there and reconcile them against the bank account. That is what the app is for and it is the only thing it does with a receipt.
Because the folder is your company's, your company decides who can see it and how long receipts are kept. If one needs correcting or removing, the office can do it in Drive directly. RedAI Studios runs the software; it does not keep a copy.
What signing in tells us
Signing in uses Google. We request three standard scopes — openid,
email and profile — and Google returns a signed identity token that we
verify on our server against Google's published keys.
From that token we read and use exactly three things:
- your email address, which identifies you on the receipts you submit;
- whether Google has verified that address;
- your Google Workspace domain, which is what ties you to your company.
The profile scope also makes your name and profile picture available. ReCeipt does
not read, use or store either.
Signing in as a tradesman never asks for access to your Google Drive. You sign in for identity only. The receipts are written with the credential your company granted once, when somebody there connected its Drive — not yours, and not ours. So a lost or stolen phone is a session to end, not a key to your company's files: nothing on the phone can reach the Drive, and whoever connected the Drive can sign that person out of every device, or block them, from the People screen in the app.
Connecting the Drive is the one time Drive access is asked for, and it is asked of the person doing it — once, for their own company. See Connect a Drive.
What happens to a receipt you submit
The image or PDF is uploaded to the single Google Drive folder configured for your company. The file name carries the label and amount so it can be found and filed. Alongside the file, ReCeipt records these details as Drive file properties:
| What it is for | the label, whether it is a job or an overhead, the category, and the supplier |
|---|---|
| The amount | the figure, the figure that was read off the image if any, and which of the two it came from |
| Who and when | your email address, and the time it was uploaded |
| If it was amended | the email address of whoever amended it, and when |
| Integrity | a SHA-256 checksum of the file, and the app version that wrote it |
Your email address is stored against the receipt so that when the office is matching a charge on the bank statement to a docket, they can see whose purchase it was. That is the purpose; it is not used for anything else.
What ReCeipt can and cannot see in your Drive
Worth being exact about, because "an app that writes to our Drive" sounds broader than it is.
ReCeipt holds a Google credential with the scope drive.file. That is the narrowest
Drive permission Google offers: it reaches only files the app itself created.
Everything else in the Drive — the office's spreadsheets, quotes, job files, anything a person put
there — is invisible to ReCeipt. Not by our promise; Google will not serve it.
The receipts it uploaded, it can read. It has to, and it is worth saying why rather than implying otherwise:
- to notice the same docket photographed twice, by comparing checksums against what it already filed;
- to show you your own uploads;
- to let you correct an amount you got wrong.
A thing that can write a file can read that file back. So the honest statement is: ReCeipt can see the receipts it put there, and nothing else in your Drive.
It also cannot remove anything. There is no delete and no move in the app, and
test/no-fergus-address.test.mjs fails the build if either appears.
Reading the amount off a photograph
If your company has enabled it, the photograph is sent to Cloudflare Workers AI to read the total. The image is processed to return a number and is not used to train any model. If the feature is switched off, or if the reader cannot make out the total, the app says so plainly and you type the amount yourself.
What stays on your phone
So the app works in a plant room with no signal, your browser holds:
- a queue of receipts not yet uploaded, including the images, in the browser's own storage;
- the labels you have used recently, so they can be offered first;
- a cached copy of the app itself, so it opens offline.
None of this leaves your device except the receipts you submit. Clearing your browser's site data for ReCeipt removes all of it.
Who else is involved
| sign-in, and the Drive folder your receipts are stored in | |
| Cloudflare | hosts the service, and reads photographed dockets where that is enabled |
| jsDelivr | serves one small library, and only if you upload a HEIC photo that needs converting |
There is nobody else. No analytics provider, no advertising network, no error-reporting service, no customer-messaging widget.
What ReCeipt does not do
- It sends email in exactly one case: if your company sets an address to receive a copy of each receipt, one copy goes there after the receipt is filed, carrying the receipt as an attachment. It comes from ReCeipt's own address, with replies going to whoever photographed it — it cannot send as you, and holds no credential that could. Your company can clear that address at any time, and it is empty unless somebody set it.
- It does not sell, rent or share your information with anyone.
- It does not track you across other websites, and sets no advertising or analytics cookies.
- It does not delete or move files out of your company's Drive folder.
Cookies
One cookie, holding a signed session so you stay signed in. It is HttpOnly,
Secure, SameSite=Lax, and it lasts 400 days, renewed
while you keep using the app — so you are not sent back to a sign-in screen on a job. It holds a
signed statement that Google verified your address, and nothing else: no Drive access and no
folder. Signing out, or removing the app from your phone, ends it. A second short-lived cookie
exists only during the sign-in round trip. A mobile app uses a token instead, valid for 30 days.
Either way, your company is re-checked on every request. There are no other cookies.
How long things are kept
- Receipts — in your company's Google Drive, for as long as they keep them. ReCeipt has no separate copy and no database of its own.
- Your session — up to 400 days, renewed as you use it, and ended by signing out or removing the app. 30 days for a mobile app.
- If you are signed out or blocked by your company — your address, the time it was done, who did it and any reason they typed, kept until they let you back in. Whoever connected your company's Drive can do this, and can see the addresses of people who have uploaded receipts.
- On your phone — until the receipt uploads, or until you clear site data.
Google API Services User Data Policy
ReCeipt's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Access, correction and complaints
Ask the office first — the Drive folder is your company's, and they can show you, correct or delete any receipt in it directly. If you would rather deal with us, or you want to complain about how your information has been handled, write to shane@redaistudios.com and we will respond within 30 days. If you are not satisfied with our response you can complain to the Office of the Australian Information Commissioner — oaic.gov.au, 1300 363 992. (Named rather than linked: the app ships a test that fails on any outbound host other than Google sign-in and Drive, and that guard is worth more than a hyperlink.)
Changes
If this policy changes, the effective date above changes with it. If a change materially affects what happens to your information, your company will be told before it takes effect.
Contact
RedAI Studios Pty Ltd, ABN 36 700 870 695
shane@redaistudios.com