Local by default
Opening the App does not upload the Garage.
DRILOREPrivacy by design
Your vehicle data serves you — not an advertising profile.
The important answer appears first. Expand the exact data map, owner controls or future requirements when you need the complete policy boundary.
No ad business
No behavioural advertising profile or sale of Garage records.
Purpose before collection
Online requests use only the practical fields for that result.
Owner-controlled sharing
Backup, export and sharing remain deliberate actions.
The honest wording
We do not require a personal profile. Vehicle information can still be personal.
A Rego, VIN, vehicle photo, receipt, IP address or location can identify or relate to a person in context. Drilore therefore treats linkable vehicle data with personal-information care even when the core Garage does not ask for the owner’s name, birth date or contacts.
01 · CURRENT PRODUCTWhat exists, where it goes and how long it mattersOpen data map +
InformationWhere it goesControl or retention
Vehicle profile: make, model, Rego, VIN, photo, mileage and due datesApp-private storage on your deviceUntil you edit it, delete the App data or replace it with a restored Garage
Expenses, work items, receipts and service historyApp-private storage on your deviceUntil you delete the record or App data; included only in an export you choose
Encrypted Garage backupA file destination you chooseControlled by you and that storage provider; Drilore 1.1 cannot recover a lost password
Fuel or charging nearby requestDrilore API, then FuelCheck or Open Charge Map as requiredUsed to return results; not automatically converted into a Garage record
Current weather requestOpen-Meteo after location permissionCurrent condition cached on device; no Drilore location history
Car-wash searchApple Maps when opened on iPhoneHandled under Apple Maps terms; no Drilore wash-directory profile
Website calculator valuesThis browser pageUsed for the on-page result and not saved to a Drilore account
Network and security metadataHosting and API infrastructureMay be processed for delivery, abuse prevention and temporary rate limiting; not for an advertising profile
Infrastructure providers can process technical logs needed to deliver and protect a service. Exact provider, region and retention disclosures must be finalised before general public release.
02 · OWNER CONTROLSAccess, correct, export, restore and deleteOpen controls +
Access and correction
Current Garage data is visible and editable inside the App because it is stored on the device.
Portable backup
Export My Garage creates an encrypted file. You choose where to store it and keep the password separately. CSV is for review, not full restoration.
Deletion
Delete individual records or App data on the device. Copies you exported remain wherever you placed them and must be deleted there separately.
Permissions
Location is requested for a current nearby or weather action. Turning it off disables those results without deleting the local Garage.
03 · SEPARATE PURPOSESAnalytics and commerce cannot copy the GarageOpen boundaries +
Minimal product measurement
Future measurement should answer coarse product questions without sending Rego, VIN, receipts, notes or exact coordinates as analytics fields.
On-device insight first
Vehicle cost trends should be calculated on-device where practical. Optional cloud analysis must disclose purpose, fields, region, retention and deletion before consent.
Separate transaction purpose
Future checkout needs the customer details required for payment, delivery, support and legal obligations. Those belong to the order, not the local Garage.
Owner-approved crossing
An order may propose a receipt, warranty or replacement reminder. Nothing enters a Garage until the owner approves it.
04 · BEFORE LAUNCHCloud, forum, analytics and marketplace gatesOpen requirements +
Cloud Garage
Separate opt-in, disclosed data region, encrypted transport and storage, tested restore, export, deletion, backup-expiry and recovery design.
Product analytics
A separate choice using minimal event names and coarse counts. Raw VIN, Rego, receipts, notes and exact location must not be analytics properties.
Owner forum
Community identity and public posts remain separate from the private Garage. Sharing requires an explicit action and preview.
Marketplace
Payment and delivery data require their own purpose, retention and disclosure and must not be combined with private Garage history for advertising.
Privacy standard
Collect less. Explain it. Delete it when it no longer has a purpose.
OAIC guidance supports relevant, minimal collection and destruction or de-identification when information is no longer needed.
Release status and accountability
This is the accurate Drilore 1.1 product boundary, not the final legal privacy policy. Before general release Drilore must publish the operating entity, privacy contact, providers, data regions, retention periods, complaint path and market-specific rights.
Last product-boundary review: 25 August 2026.