How basmate protects business records.

A practical overview of how basmate handles account details, receipts, warranties, AI processing, subscriptions and backup data.

Effective date: 10 July 2026

Quick summary

The practical version.

basmate stores and processes business records so users can manage receipts, warranties and reports.

AI-extracted receipt details should be reviewed before they are used for reporting or business decisions.

App store subscriptions, cloud backup and third-party services follow their respective provider terms.

01

Information we collect

We may collect account details, business profile information, contact details, support messages, subscription status, device information, app usage records and form submissions.

If you use basmate, the app may process receipt images, supplier names, dates, totals, GST information, categories, warranty records, uploaded documents, notes, exports and backup metadata.

We may collect technical and security information such as IP address, browser and device details, timestamps, crash logs, analytics events and signals used to protect forms and accounts from misuse.

02

How we use information

We use information to provide basmate, manage accounts, process support requests, improve receipt scanning, organise records, maintain backups, send service notices and protect the product from abuse.

Where permitted, we may send product updates, launch notices and relevant business communications. You can opt out of marketing messages at any time.

We may use aggregated or de-identified data to understand product performance, improve features and plan future development without identifying individual users.

03

Receipts, AI and business records

Receipt images and uploaded documents may be processed to extract supplier, date, amount, GST and category information. AI-extracted information may require user review before relying on saved records.

basmate helps organise business records. It does not provide tax, accounting or financial advice, and users remain responsible for reviewing records before using them for reporting or business decisions.

We do not intentionally use user receipt images or private business documents for public marketing or unrelated purposes.

04

Subscriptions and payments

Subscriptions purchased through Apple or Google are managed through the relevant app store account. Payment information is handled by the relevant platform or payment provider under their own terms.

basmate does not need users to send payment card numbers through contact forms, support messages or uploaded documents.

05

Cloud backup and storage

Cloud backup availability depends on the selected plan, account status, connectivity and supported services.

Backed-up records may include receipt images, warranty documents, app data, business profile data and related metadata required to restore or sync records.

No storage or backup system can guarantee absolute protection from loss, interruption or security incidents.

06

Sharing information

We may share information with service providers that help us operate basmate, including hosting, storage, analytics, email, support, security, AI processing, app distribution and payment providers.

We may disclose information where required by law, to protect users or the service, to enforce terms, or as part of a business transfer subject to reasonable safeguards.

07

Retention and deletion

We keep information for as long as reasonably needed to provide the service, maintain records, comply with legal obligations, resolve disputes, prevent abuse and support account recovery.

Users may request export, correction or deletion where available and legally required. Some information may be retained where permitted by law, backup cycles, accounting requirements or security needs.

08

Contact

For privacy questions or requests, contact hello@basmate.app with enough detail for us to identify the account, information and request involved.

We may update this policy as basmate features, service providers and legal requirements change. The current version applies from the effective date shown on this page.