Privacy Policy
Last updated: 21 August 2026
Two other things leave the phone without reaching us: what you type into an address field goes to Google to fetch suggestions, and Android's own backup copies the app's data to your Google account unless you switch it off. Both are described below, under "Address suggestions" and "Android's own backup".
This policy explains what stays on your device, what leaves it if you ask it to, and how to get rid of everything.
What we collect
With cloud backup off: nothing. There is no account, no analytics, no advertising and no crash reporting in GigFee. Turn the app on, use it for years, never sign in, and we receive nothing about you at all.
That is about us. Separately, and whether or not you use cloud backup, typing in an address field sends what you have typed to Google to fetch suggestions. We do not see those queries and nothing is stored from them. See "Address suggestions" below for exactly what is sent and when.
With cloud backup on, two things reach us:
- An account. Signing in with Google creates a GigFee account holding your email address, your Google display name, and an internal user ID. We use it for one purpose: to tell your backup apart from somebody else's. There is no password, and we never see your Google password.
- One backup file. A single archive of your GigFee data, replaced each time it changes. There is one per account, not a history.
What is in a backup
Everything the app holds, which is what makes it worth restoring:
- Your business details, ABN, GST status, bank details, super fund details and logo
- Your clients' names, contact details, addresses and ABNs
- Your invoices, line items, amounts, GST and superannuation figures
- Gigs, venues, band members and fee splits, and recurring schedules
- Documents attached to bills other people sent you
- Your app settings and invoice numbering
Generated invoice PDFs are not included. They are rebuilt from the invoice when you open it, so nothing is lost by leaving them out.
Some of this is other people's personal information: your clients' details, and anything imported from your phone's contacts or calendar. Once it is in GigFee it is part of your data and is included in a backup like everything else.
Where it is stored, and who can read it
Backups are held in Google Cloud Storage, in a Firebase project we operate, in Google's australia-southeast1 (Sydney) region. Your backup file does not leave Australia.
Access is enforced by server-side security rules that allow a file to be read or written only by the account that owns it. That check runs on Google's servers on every request, not in the app, so it cannot be bypassed by a modified copy of GigFee. No other GigFee user can reach your backup.
We will be straight with you about the limit of that: as the operators of the project we hold administrative access to the storage bucket, in the same way any company hosting your data does. We do not open, read, analyse or share the contents of anyone's backup, and there is no feature, tool or process in GigFee that does. But "we cannot" would be too strong a word, and we would rather say so than imply otherwise.
Your account record (email address, display name and user ID) is held by Firebase Authentication, which Google does not run on a region-specific basis. That means it may be stored or processed outside Australia. Your backup file is not.
Data is encrypted in transit using HTTPS, and encrypted at rest by Google Cloud Storage.
Deleting your data and your account
You can delete everything we hold, at any time, from inside the app:
- Open GigFee.
- Go to Settings → Backup & restore.
- Under Automatic cloud backup, tap Disconnect.
- Choose Delete everything.
That removes the backup file and closes your GigFee account in the same step. It happens immediately, and it cannot be undone.
If you no longer have the app (a lost phone, an uninstall), email us at the address at the bottom of this page from the Google account you signed in with, and ask for your GigFee data to be deleted. We will delete the backup file and the account and confirm when it is done, within 30 days and usually much sooner. We may ask you to confirm the request from that email address; that is the only check we can make that you are who you say you are.
What is deleted: the backup file, and the account record holding your email address, display name and user ID. Everything.
What is kept: nothing. We hold no separate archive, no analytics profile and no record of the contents of anyone's backup. Google's own infrastructure may retain a deleted file briefly as part of normal storage operation, after which it is gone.
What is not affected: the copy on your phone. Deleting your cloud data never touches your local records, and disconnecting is not the same as deleting. You can stop syncing and keep the cloud copy for your next phone if you prefer.
Uninstalling GigFee deletes everything held on the device. If you had cloud backup on, use one of the routes above as well, or the cloud copy will remain.
If you want the data gone for good, turn off Android's own backup too. Otherwise your phone may hold a copy in your Google account and restore it the next time you install the app. See "Android's own backup" below.
Choosing not to use cloud backup
Cloud backup is off until you turn it on, and every other part of GigFee works without it. Manual backup, a file you save and keep yourself, is available on every plan, including the free trial and a lapsed subscription. These are tax records you are required to keep, and being unable to pay should never mean being unable to get them out.
Contacts (optional)
If you use "Import from contacts", GigFee reads your device address book so you can pick clients to add. The reading happens entirely on your device, and only the entries you explicitly select are saved into the app. Those saved clients are then part of your GigFee data, and are included in a cloud backup if you have one turned on. You can decline this permission and use every other part of GigFee normally.
Calendar (optional)
The gig importer reads the calendars already on your phone so you can pick events to bring in. It is read-only, so it never changes or adds an event, and the reading happens on your device. As with contacts, the gigs you choose to import become part of your GigFee data and are included in a backup.
Photos (optional)
Adding a logo, or photographing a bill, uses your device's photo picker or camera, which gives GigFee access only to the images you select or take. They are copied into the app's private storage, and are included in a cloud backup if you have one.
Address suggestions (optional)
This is the one feature where something you type leaves your phone. Everything else described on this page (contacts, the calendar, reading a bill) happens on the device. We are calling this one out rather than burying it.
When you type into an address field (a client's address, your own business address, or a gig's venue), GigFee sends what you have typed to Google Places to fetch matching suggestions, and shows you what comes back. It starts only after you have typed three characters, and only in an address field. Typing anywhere else in the app sends nothing.
A gig has two of these fields and they behave differently. The venue name looks through the venues you have played before first, and Google is asked only when your own history has nothing to offer, which is usually the first time you play somewhere new. The gig's address field asks Google directly, because a place you have never been is exactly the case it exists for.
Google receives the characters you typed. It does not receive your name, your email address, your GigFee account, your invoices or anything else about you. What Google does with the query is covered by Google's privacy policy. GigFee keeps nothing from the lookup except the address you actually choose, which is then part of your data like anything else you typed in.
You never have to use it. Ignore the suggestions and type the address out. Every address field is an ordinary text box and always works, with or without a connection.
Reading a bill
When you attach a bill somebody sent you, GigFee can read the text off it to fill in the form. That recognition runs entirely on your phone, using a model bundled with the app. The document is not sent to an online text-recognition service. Somebody else's invoice, with their name, ABN and bank details on it, never leaves your device for that purpose.
Purchases
Purchases are processed by Google Play. We never see or receive your payment card details, billing address or any other payment information. Google handles the transaction and tells GigFee only whether a purchase is active.
Your purchase is tied to your Google account, which is what lets it be restored if you reinstall the app or move to a new phone.
Notifications
GigFee can remind you when an invoice is due. Reminders are scheduled and shown by your device. Nothing is sent through a notification server, and no information leaves your phone to produce them.
Sharing and exporting
When you send an invoice, export a spreadsheet or share a backup file, your device's share sheet or email app sends it to the destination you choose. Once it leaves GigFee, it is handled by that app or service under their terms, not ours.
Analytics, advertising and tracking
There are none. GigFee contains no analytics SDK, no advertising, no crash-reporting service and no tracking of any kind. We do not know how many invoices you have made, which screens you visit, or whether you opened the app today.
Address suggestions are not an exception to this. That lookup sends the characters you typed into an address field, and GigFee attaches no name, account or profile to it. Like any internet request it does reach Google from your connection. It happens only while you are typing in that field, and is described in full under "Address suggestions" above.
Children
GigFee is a business tool intended for adults. It is not directed at children and we do not knowingly collect information from them.
Android's own backup
Separately from anything GigFee does, Android itself backs up app data to your Google account. It is a feature of the phone, not of this app, and it is on by default for most people. When your device is idle, charging and on wi-fi, Android copies GigFee's database to your Google Drive, and restores it automatically when you reinstall the app or set up a new phone.
We are calling it out because it is genuinely useful and because you should know it happens. For most people it is the only backup they will ever have, since it is the only one that asks nothing of them. It covers your invoices, clients, gigs and settings, and your logo.
It goes to your Google account, not to us. We cannot see it, we are not told it happened, and it is not the same thing as GigFee's cloud backup. It is subject to Google's privacy policy rather than this one.
To turn it off, open the phone's Settings, then Google, then Backup, and either switch backup off entirely or exclude GigFee from it. The exact wording moves around between Android versions and manufacturers. Turning it off does not affect anything inside GigFee.
Security
On your phone, your data sits in Android's app-private storage, which other apps cannot read. In the cloud, it is isolated per account by server-side rules, encrypted in transit and encrypted at rest.
We would encourage you to protect your phone with a screen lock, and to keep your own backups as well. GigFee's manual backup exists for exactly that reason.
Your rights
Australian privacy law, including the Privacy Act 1988 (Cth) and the Australian Privacy Principles, gives you rights to access and correct personal information an organisation holds about you. If you have used cloud backup, you can exercise those rights by contacting us at the address below; in practice your own copy in the app is the same data, kept current.
You remain responsible for the personal information you enter about your own clients, and for meeting any obligations you have to them.
Changes to this policy
This policy changed on 8 August 2026, when optional cloud backup was added. Before that release GigFee had no accounts and sent nothing off the device. If what we collect changes again, this page will say so and the app will tell you rather than relying on you re-reading it.
Who we are
GigFee is published by Anthony Collins trading as Tones AU, a sole trader in Australia. "We", "us" and "our" in this policy mean that business.
Contact
Questions about this policy, or a request to delete your data:
admin@tones-au.com