RepairGo App Privacy Policy
Information about RepairGo app variants, limited iOS repair requests and authenticator setup, and the separate DEMO mode.
Who is responsible
REPAIRGO PTY LTD (ABN 89 701 552 052, ACN 701 552 052) is responsible for the RepairGo mobile app. This policy covers customers, technicians and repair-shop participants. Last updated: 19 November 2026.
The earlier Android internal customer release labelled STAGING / LIVE OFF is limited to an approved synthetic test account and reading that account's own information. It does not provide account registration, bookings, live payments, geocoding or technician availability. The other features described below are not all available in that release. Privacy and account-deletion instructions are accessible without signing in.
The app offers a normal RepairGo environment and a separately labelled DEMO environment. Choosing Try the demo connects to STAGING and Stripe TEST using dedicated demonstration accounts. DEMO bookings do not arrange a real repair or charge real money. Use only the supplied fictional details in DEMO, including for payment and document-upload trials. Account and technical information can still be processed by our service providers during testing.
Choosing Continue to RepairGo uses the normal environment, where account registration and technician or shop verification can process real information. During the current pre-launch period, new technician discovery and assignment and live repair-payment operations remain closed. An internal-test distribution label does not itself mean that every screen uses STAGING.
Limited iOS repair requests and authenticator setup
The limited iOS repair-request app is separate from the Android customer-enquiry flow and the DEMO variants described below. The Android customer-enquiry flow remains restricted to approved accounts and their own enquiries. Availability depends on the release and service gates; completing account security setup does not open repair requests.
For the limited iOS app, Firebase Authentication processes your account email, password credentials and enrolled phone or authenticator (TOTP) verification information. Creating an account sends a verification email only after you choose Create. Authenticator setup displays a private setup key for your authenticator app. TOTP verification uses the authenticator app rather than an SMS code; existing verification methods stay unchanged. Keep passwords, setup keys and verification codes private.
The limited iOS app uses Google Firebase App Check with Apple App Attest for app and device integrity verification. Advertising, Analytics, Crashlytics and Performance collection are not enabled by this iOS app. Google Firebase and Google Cloud still process authentication, integrity and infrastructure security information, including provider telemetry; this is not a promise of zero logging. Relevant processing by providers and their subprocessors may occur outside Australia.
When its repair-request service is enabled, the limited iOS app processes the device and fault description, contact details, manually entered repair address, private request reference, quotes, appointment preferences and private messages you submit. Access is restricted to your account and authorised RepairGo operations. Payments, automatic address lookup, live technician availability and location tracking are not enabled in this release. An appointment request is not a confirmed booking; appointments are confirmed manually.
Image attachments are not an advertised or operational feature of this limited iOS release. Where an attachment service is later enabled for your account, you select the file yourself in the device file picker. The limited iOS app does not request photo-library, camera or location permission. Submitted images are private collection and remain restricted in quarantine until the required safety scan and manual review are completed.
For these limited iOS account and repair-request records, retention depends on service operations, security, disputes and applicable legal obligations. Ask RepairGo about the records and retention that apply to your request. The existing schedules for other app workflows are described below; no new fixed retention period is set here for the limited iOS flow.
If every registered verification method is unavailable, contact RepairGo for an identity review. Email verification or a password reset does not replace MFA, and a recovery request does not automatically remove a factor or grant account access. Privacy and account-deletion instructions remain available without signing in.
Information in other RepairGo app variants
Account information includes your name, email address, phone number, account identifier, role, profile information and authentication records. Passwords and phone verification are handled through Firebase Authentication.
Service records include the device and fault you select, service address, appointment details, technician assignment, estimates and approvals, journey and repair status, repair reports, uploaded device photos, customer acknowledgement and signature, and invoice and transaction references. Private job messages and attachments are processed when you use those features.
Technicians and repair-shop participants may provide business, identity, qualification, insurance or other verification documents and payment-onboarding information needed for their role. Do not upload information about another person without authority.
For the other app variants described in this section, Firebase and related app services process installation identifiers, notification tokens, device and app metadata, IP addresses, integrity or authentication signals, performance measurements and diagnostics. The app uses Firebase Performance Monitoring; this is distinct from advertising tracking.
Service addresses and availability
We collect a service address to identify the requested repair location and assess service coverage. Address and appointment information is kept in access-controlled booking records. Technicians who need access for an assigned repair and authorised staff may receive the relevant information; a service address is not a public profile entry.
At this pre-launch stage, the closed production matching service does not send customer addresses to an external address-verification provider. DEMO matching trials use synthetic locations or identified public-place test addresses. Going Online in DEMO does not make a real technician available for customer bookings.
Before enabling a new external address-verification provider for customer matching, we will identify that provider, explain the address fields shared and relevant retention and overseas-processing arrangements, and update the notice shown when the address is collected. We do not treat a general privacy-policy acknowledgement as permission to share unrelated contact details or access instructions with a geocoding provider.
If an address cannot be verified for a service-area check, we may be unable to confirm technician availability. You can request correction of an address through the app or support. A technician's current Online status does not by itself reserve a future appointment or guarantee round-the-clock attendance.
Location and device permissions
In app variants with these location features enabled, location is used for service-area matching, addresses, maps, navigation and technician journey tracking. A technician's precise current location can be shown to the customer assigned to that job when the relevant tracking feature is active. Service addresses are shared with participants who need them to perform the requested repair.
Android location access is subject to device permissions. The current Android release does not request background-location permission. Service providers can also derive an approximate location from an IP address for security or performance reporting. Camera, photo or file selection and notification permissions support the corresponding features; declining a permission can limit that feature.
Why information is used and who receives it
Information is used to operate accounts, verify participants, coordinate bookings, communicate about services, show repair progress, process payments, issue reports and invoices, provide support, maintain security, investigate disputes and improve app reliability.
Customers and their assigned technicians or shops receive information needed for their booking. Authorised RepairGo staff may access records for support, safety, verification, administration, fraud prevention or dispute handling. Job communications are not a public social feed.
For the other app variants described above, Google Firebase and Google Cloud provide authentication, databases, functions, file storage, notifications, integrity checks and performance monitoring. Google Maps supports map features. Stripe processes payments and technician payment onboarding. Resend is used where service emails are enabled; the current STAGING completion test does not send completion emails.
Payment card details are entered into Stripe's payment components. RepairGo does not store full card numbers or CVC/CVV values in its booking records. RepairGo retains transaction status, amounts, references and invoices needed for the service. Stripe may process payment, identity and security information under its own privacy terms.
Information may be processed outside Australia by these providers and their subprocessors. RepairGo does not sell personal information or provide it to advertisers for independent advertising. The current app does not display third-party advertising.
Retention, deletion and your choices
For the existing job workflows described above, RepairGo's approved retention schedule is three months for job chat, thirty days after a job for technician location history, twelve months after completion for repair photos, and five years for booking and repair history. Financial, invoice, verification and security records may need to be kept for applicable accounting, legal, fraud-prevention, warranty or dispute purposes. These periods are subject to a relevant legal obligation or unresolved matter.
Account and associated-data deletion requests require review of the records involved. The Android customer-enquiry release provides Privacy and account deletion on the sign-in screen and in the account workspace. Its email-draft option prepares a request for you to review and send; opening or copying a draft does not submit a request, disable your account or delete information. We may need to verify account ownership before processing. We will explain any records that must be retained and why, and confirm the outcome. A request or account deactivation is not confirmation that deletion is complete.
You can request account and associated-data deletion even after uninstalling the app. Use the account-deletion instructions linked below or contact naouras@drrepairgoau.com. Send the request from your account email where possible. Do not send passwords, verification codes, full card details or identity documents in an initial request. We may need to verify that you control the account.
You can manage device permissions in Android settings. RepairGo targets users aged thirteen and above, rather than children under thirteen. Contact us if you believe a child under thirteen has provided information through the app.
Security, contact and changes
The app's Firebase, Google and Stripe connections use encrypted transport. Access controls and authentication restrict service records to authorised participants and staff. No system can guarantee absolute security; do not share account passwords or verification codes.
For privacy questions, access, correction or deletion requests, email naouras@drrepairgoau.com. General app support is available at support@repairgo.com.au and through the contact page. We review this policy when the app's data practices change and publish the updated date here.
Accessory purchases in the separate Shopify store are covered by that store's privacy information. Opening that store does not turn a STAGING repair test into a real repair or payment.
