Privacy policy.

1. What this policy covers

This policy explains how Vroki (“we”, “us”) handles information through vroki.com. It also describes the current development build of the Vroki iPhone app, which has not yet launched. We will update the app-specific information before release if its practices change.

The website does not require an account, collect payment-card details or provide a place to upload trips, vehicle records or odometer photos. Screens shown here are captures of the actual development app with fictional demo data.

2. Website analytics

We use Stactics to understand which pages people visit and whether useful links are being used. When enabled on the public Vroki website, our analytics code sends a website-open event, page-view events and selected actions such as opening pricing, the FAQ or the privacy contact link.

Each event contains a randomly generated browser identifier used as both the user and device identifier, an event identifier, a timestamp, the web platform and release channel, and a recognised page path or predefined action name. Visits from the same browser identifier can be linked together. This is pseudonymous information, not anonymous information.

Our event payloads do not include URL query strings, fragment identifiers, referring URLs, link destinations, typed text, names or email addresses. Unrecognised page paths are recorded as “/404”. Website analytics do not receive your iPhone’s GPS, trip routes, vehicle details, odometer readings or photos.

Separately from the event payload, Stactics receives and stores the request IP address and browser user-agent information. Its service can derive approximate location and network-provider information from IP addresses when its lookup data is available. This does not access your device’s GPS.

We use these events to understand and improve the website. The site does not include advertising trackers or a separate third-party crash-reporting SDK. Analytics failures do not prevent you from using the site.

3. Your analytics choice

You can turn off Stactics analytics for this browser. This stops new events from this website, removes its stored analytics identifier and clears events waiting in memory. It cannot recall requests already received by Stactics or delete existing server records.

We also honour the Global Privacy Control and Do Not Track signals available to the website. A browser privacy signal keeps analytics off even if the button above is set to allow them.

Your off preference is saved in this browser’s local storage. If storage is blocked, the choice lasts only for the current page session. Clearing site data removes the identifier and saved preference; a later visit can create a new identifier unless analytics are turned off again or a browser privacy signal is present. A different browser or device has a separate choice.

4. Browser storage and hosting

The analytics code uses local storage rather than cookies. It stores a random identifier under vroki.stactics.browser, with a 90-day expiry checked on a subsequent visit. The on/off preference is stored under vroki.stactics.disabled until you change it or clear site data. If local storage is unavailable, an identifier can be held in memory for the current page session.

Up to 100 unsent events can be queued in memory while the page is open. Accepted events are removed. Failed batches are retried a limited number of times and then dropped; closing or reloading the page clears the in-memory queue. The website does not write that queue to browser storage.

The infrastructure serving the website and Stactics API processes ordinary request information, such as IP address, browser details, requested resource and time, to deliver, operate and secure the services. These operational records are separate from the event payloads described above. Site fonts and preview artwork are served with the website’s own assets. Your light or dark appearance preference is saved locally under vroki.theme until you change it or clear site data. Choosing “System” removes that saved override. This preference is not sent to Stactics.

5. The iPhone app

The current development build stores vehicle details, trips, recorded GPS routes and odometer readings on your device. It does not require a Vroki account. Location is used for a trip you start. Camera odometer reading and automatic background start are planned features; their final permissions and practices will be described before release.

Optional app usage analytics

The app uses Stactics to understand use of features such as opening the app, selecting a tab, saving a trip or odometer reading, starting and ending a recording, previewing a report and preparing a backup. Analytics are on by default in the current build. You can turn off “Share usage analytics” under Settings → Privacy & data.

Events contain a random installation identifier, event identifier, timestamp, iOS platform, app version and build, device type, release channel and predefined action names. They do not include trip or vehicle identifiers, registration numbers, coordinates, routes, odometer values, trip purposes or other text you enter. Events linked to an installation are pseudonymous, not anonymous. Stactics also receives request IP and user-agent details and may derive approximate location and network-provider information, as described above.

Turning app analytics off stops new events, cancels retries and removes the local analytics identifier and queued events. It cannot recall requests already received or delete server records. Turning it back on creates a new identifier. This choice is separate from the website control above. Demo and UI-test sessions do not send analytics.

The app can retain up to 2,000 unsent analytics events in local application storage, excluded from device backups, and retry failed batches. Accepted events are removed. Disabling analytics clears this queue and its identifier.

Exports and other services

You choose whether to export or share a data copy. Files you share, save to a synced location or include in a device backup are handled by the selected recipient or storage provider, with their own retention and deletion arrangements. Apple’s mapping and purchase services may process information needed to provide their features under Apple’s own terms and privacy policy. We will update this page if release practices change.

6. Contact and support information

You can send a question, technical issue, suggestion or privacy request through our support form. The form collects your name, email address, enquiry topic, device category, message and permission to use those details to respond.

When you choose to send it, this information is submitted to Stactics for the Vroki team to review and reply. Stactics also stores the submission time, website source, form version, IP address and browser user-agent. Our form requests omit the referring URL and do not attach the website analytics identifier. Sending a support request is separate from analytics and still works when analytics are turned off.

We do not store your draft in browser storage or send it while you type. Successful submissions clear the form; if receipt cannot be confirmed, the message remains on the page so you can retry. Leaving or reloading the page can discard an unsent draft. Do not include passwords, payment-card details, full logbooks or location histories.

If the form is unavailable, you can use Ocintra’s contact page and mention Vroki. That separate service handles the details you choose to provide under its own privacy policy.

7. Retention and service providers

Stactics and the infrastructure serving the website and API process the website and app analytics data described above. Server event retention follows the Stactics account and service settings. Aggregated statistics, browser-identity records, security logs and contact enquiries have separate lifecycles. Clearing browser storage does not remove those server records.

We do not state a fixed server retention period or promise that all service processing occurs in Australia. Provider locations and retention can depend on the services and account configuration. Contact us for information relevant to your request, including overseas processing, access, correction or deletion.

8. Privacy enquiries, requests and complaints

Use our support form, choose “Privacy request” and describe your question or concern. You can ask about information held by the services, request access or correction, ask for deletion, or make a privacy complaint.

Include enough context to locate the relevant information, such as the approximate date of a visit or enquiry. Linking pseudonymous analytics to a request may require the browser identifier; do not send unrelated personal records. We may need to confirm that a request relates to you before responding or changing records. We will review the request, explain the outcome and any applicable limitations, and respond through the contact details you provide.

If your concern is not resolved, you can contact the Office of the Australian Information Commissioner about the complaint options available to you.

9. Changes to this policy

We will update this page when these practices change, including before a material new collection practice is introduced. The date above identifies the current version. Check this page again when the iPhone app launches for its final release-specific privacy details.