How KNOQ handles information in website account signup and its app trial, and where to turn with a privacy question.
Version 8 · 25 September 2026 · Account signup and current app services
Who looks after your information?
KNOQ is a registered business name operated by Steve Harley, ABN 40 673 535 778. Steve is the privacy contact: steve@knoq.au.
This notice covers KNOQ website account creation, the mobile apps and their connected account service. Browsing and information you send through optional interest, research and support forms are covered by the separate website privacy notice. An app account and a website expression of interest are separate.
What the account and app use
Your account
You can create an account with an email address and password through Firebase Authentication. The apps also support Google or Apple sign-in where available. Firebase handles the password-based sign-in and recovery process; do not send your password to KNOQ support. KNOQ uses account identifiers and the name, email and profile information supplied through that sign-in or your profile to recognise your account and synchronise it.
Signing in is needed for the protected account workspace. KNOQ does not ask for your Google or Apple password.
App integrity and diagnostics
Firebase App Check helps check requests from the apps and website account pages. The website account pages use Firebase authentication and an App Check provider to protect signup and sign-in. Crashlytics processes installation identifiers, device/app information and crash diagnostics to help investigate failures.
KNOQ’s Android failure reports use the operation, failure type, HTTP status and attempt count; they do not include the contents of request forms. Diagnostic records should not be assumed anonymous.
Choosing a service
The app reads KNOQ’s service catalogue. When a household with current access sends a request, KNOQ receives the service, description, timing and address details they provide. Eligible professionals can receive a privacy-protected offer; the professional receives the job address after accepting.
Norb’s service suggestions in the app use local catalogue rules. This is separate from the website’s Ask Norb service.
Professional applications
Professionals supply profile and service details and the evidence needed for the services they offer. Steve reviews these details through a restricted, authenticated approval page. Decisions, review notes and relevant expiry dates are recorded. Account creation alone does not approve a professional. Do not send evidence or credentials through public website forms or Ask Norb.
Jobs, location, notifications and payments
For approved trial jobs, KNOQ receives job details, addresses, status updates and messages that participants send through the app. It may also receive professional verification details, reviews and support reports when those features are used. Relevant job information is shown to the authorised household and professional.
Before a professional accepts, location is approximate. After acceptance the professional receives the job address. When the professional starts travelling, precise live-trip updates can be shown to the household. Sharing stops at arrival, and the server’s current live-trip point is deleted. You can review or turn off app permissions in your device settings.
The app includes Firebase Messaging for notifications. With your notification permission and applicable account access, notifications can alert you to relevant account or job activity. Firebase Messaging processes push tokens and installation information. Delivery also depends on device settings and connectivity; a notification is not confirmation of a booking. Payments in KNOQ remain unavailable. Do not enter payment-card details into a request, message, support form or privacy email.
Who helps run the app?
Maps on Android, iPhone and iPad. KNOQ uses Mapbox to display the professional’s authorised location on the journey map and provide route and estimated-arrival information where available. Mapbox may process map requests, location information, identifiers, map interactions, usage, performance and diagnostic information to provide and improve its services. Location telemetry depends on device permissions and SDK settings; KNOQ currently uses the SDK’s default telemetry settings. This provider processing is separate from KNOQ’s live-trip sharing with the household, which stops at arrival. See Mapbox’s privacy policy and telemetry information.
Google sign-in on iPhone and iPad. Google may process your user identifier to record sign-in permissions you grant, and your IP address to estimate a general location for fraud prevention. KNOQ does not request additional Google account scopes for phone information. See Google’s sign-in data disclosure.
KNOQ uses Google Cloud for its connected service, Firebase for authentication, app integrity and diagnostics, and Google and Apple for sign-in. Firebase Messaging supports account and job notifications when authorised and permitted by the device. Service providers process information needed for their respective functions.
The KNOQ API is hosted in Google Cloud’s Sydney region. That does not mean all app information stays in Australia: Firebase Authentication processes data in the United States, and other Firebase services may process it on global infrastructure. See Firebase’s privacy information, Google’s privacy policy and Apple’s privacy policy.
The detailed provider and processing-location inventory remains under review. No Firebase Analytics integration is active in the reviewed native app configuration, and the reviewed SDK privacy declarations do not declare tracking.
Signing in is separate from confirming deletion. The secure progress screen shows whether a confirmed request is processing, needs action or is complete. A receipt is not confirmation of deletion. If you already confirmed a request, return to saved progress instead of submitting another.
Information kept after online account deletion
When online account deletion completes, your personal profile information and closed-job descriptions are removed from both parties’ KNOQ history. Exact wording is retained only where specifically needed for a dispute or legal requirement, and only until that need ends.
Only the minimum necessary closed-job and support records may be kept for up to 90 days from the original closure of the job or support case, and removed earlier when no longer needed. Requesting account deletion does not restart that period.
Specific justified legal, dispute or security exceptions apply only to the records needed for that purpose and only while necessary. Minimal deletion references may remain to prevent deleted accounts or data from being restored. The 90-day limit applies to the routine closed records above; it is not a promise that a deletion request takes 90 days or that every retained record has the same lifetime.
Keeping and protecting information
Account information supports sign-in and profile continuity; integrity and diagnostic records support security and fault investigation. Access to the account service requires authentication, and it uses HTTPS.
KNOQ aims to complete account-deletion requests within 30 days. Limited records may be retained for security, fraud prevention, legal or regulatory reasons, and recovery backups may remain until they expire. KNOQ will explain any retention that applies to your request.
For its own service, Firebase says Crashlytics keeps crash data and associated identifiers for 90 days before beginning removal from live and backup systems. This is a provider-specific practice. The Firebase notice explains its service-specific handling.
Your questions and choices
You can contact Steve about access to your information, corrections, privacy concerns or an account-deletion request. The information to include and what happens next are explained on the next page.
Please do not send passwords, identity documents or payment-card information.
When this notice changes
The version and date above identify this notice. It will need updating as the account service, apps and their data handling change. A published notice does not replace the operational work needed to protect information or fulfil deletion requests.
About this update
This update covers email/password account creation on the website, professional application review, maps on both mobile platforms and consent-based notifications. It retains the online and email deletion routes and the existing retention explanation. It does not announce public app-store availability or change device permissions.
