Useful Llama

Road Camera by Useful Llama - Privacy Policy

Version 1.13 Effective date: 19 November 2026 Changes in 1.13: added private feedback through Google Forms and its one-time thank-you of extra recording time. Changes in 1.12: added optional Claude with your own Anthropic API key, and what account summaries, AI video descriptions and document reading send to Anthropic when a key is added. Changes in 1.11: added optional gift codes and corrected how Android backup applies to settings and gift-code information. Changes in 1.10: explained how playing or exporting clips can send positions along a recorded route for suburb lookup, how place names are stored, and where they appear. Changes in 1.9: added notes kept with clips when a photo camera is opened during recording. Changes in 1.8: added experimental traffic-light analysis and local review of saved speed-camera locations. Changes in 1.7: explained optional sound and front-camera controls, call and microphone-use detection limits, and interrupted document-photo cleanup. Changes in 1.6: added document-photo reading, optional photo retention and source labels for imported report details. Changes in 1.5: added optional government vehicle checks and reading vehicle details from a screenshot. Changes in 1.4: added automatic Gallery copies. Changes in 1.3: added journeys, location-only logging, journey exports, and sending journeys to Time Card and Invoice Maker. Changes in 1.2: added how quick-report photos are read for details. Changes in 1.1: added how recorded clip audio is transcribed and stored.

Who provides the app

Road Camera is provided by the independent developer trading as Useful Llama. Privacy and support contact: useful.llama@gmail.com. This policy is available at https://useful-llama.github.io/road-camera/privacy/.

Camera, microphone and recordings

The app uses camera access to record video and to provide previews and selected-frame analysis. Video may contain faces, vehicles, number plates and other identifying details. Sound recording starts off. If you enable it and grant microphone access, sound is recorded with the video. Speech typing is a separate microphone use described below.

Sound and the front camera are off by default. Enabling either shows a reminder to inform people being recorded and obtain any required permission. The camera screen also has a sound control. These reminders do not obtain consent from other people. While video sound is enabled, Road Camera uses Android's audio-mode and active-recording information on the device to try to detect calls and other microphone use and mute the clip's sound. This check does not read phone numbers, contacts, call contents or the identity of the other caller, and this detection information is not sent to Useful Llama. Detection depends on the phone, Android version and other app, and may be delayed or miss a case. It is not a guarantee that a conversation will be excluded. When the detected interruption clears, sound is enabled again if your recording and sound settings still allow it. Muting a clip does not necessarily release the microphone immediately, so Android's microphone indicator may remain visible. Keep sound off when a conversation must not be recorded.

Recording can continue through a foreground service while the app is not visible or the screen is off. A recording notification provides status and controls. Recording permissions and device restrictions still apply. Turning off video sound does not disable speech input that you separately choose.

Road Camera can store a note when you open a photo camera during recording, including the camera-use times and when recording is confirmed again. These are app observations, not a measurement of missing footage. The notes can appear with affected clips and in reports that include them.

Location, motion and events

With location permission, the app obtains position, speed, accuracy and related readings during recording, including while the screen is off. These can be stored with clips, used for stamps, event detection and speed-camera proximity, and included in reports. Motion sensors support impact and movement detection. The app stores event times, types and associated readings and clip references.

Smart event detection uses estimated speed and movement to flag clips for review. Optional AI-enhanced detection analyses reduced video frames on the phone to flag possible close calls. It does not independently confirm an accident. Detection settings can be changed in Settings.

The optional experimental traffic light guide analyses camera frames on your phone while recording to estimate traffic-light colours and arrow shapes. It is off by default. The guide does not upload frames for this analysis or save a separate history of its estimates. Its graphics are shown in the app and are not added to recorded video. Normal video recording and retention still apply. Estimates can be wrong or delayed and do not identify which signal applies to your lane. The detection software's service usage and diagnostic information is described separately in this policy.

Journeys and location-only logging

Road Camera stores journey start and end times, GPS route points and related readings, estimated distances and speeds, available start and end addresses, your purpose label and notes, and whether video was being recorded. Journeys can be logged alongside video or through location-only logging, which uses a location foreground service and can continue while the app is not visible or the screen is off. Location-only mode does not record video or sound. Only journeys meeting the app's duration and distance thresholds are retained as journey records.

When maps and address lookups are enabled, start and end coordinates may be sent through the phone's geocoding service to look up addresses. Loading a route map sends requests for its area to Google; the existing map and service-data disclosures apply. You can turn maps and address lookups off without deleting previously saved journey information.

When the GPS position overlay and “Maps and address lookup” are on, playing a clip or preparing a copy for the Gallery or sharing may send selected GPS coordinates from along the recorded route to the provider of your phone’s geocoding service. The service uses those positions to look up a suburb or locality. Road Camera stores returned place names with approximate area coordinates on your phone so it can reuse them. A place name can appear below the GPS position during playback and in exported copies. Anyone with a copy can see the location shown in it. Turning off “Maps and address lookup” stops new lookups. Copies already saved or shared keep their location stamps.

Excel exports contain journey details, including coordinates, addresses and notes. Saving or sharing them creates copies outside the journey record. A temporary copy of the latest Excel file is kept in the app's cache for sharing; it is replaced when you create another file and removed when you delete a journey. When you choose Add to a time card, Road Camera sends selected journey dates, times, addresses and a description containing estimated distance, purpose and notes to Time Card by Useful Llama on your device. It does not send video files or the full GPS route through that action. Time Card asks before adding the activities to a draft. If Time Card is not installed, the app opens its store page; you must return and send again after installing.

When you choose to send travel to Invoice Maker by Useful Llama, Road Camera sends the journey date, a description containing start and end address summaries and any notes, estimated kilometres rounded to one decimal place, and whole-minute duration. It does not send video files or the full GPS route through this action. Invoice Maker asks you to review the lines, select an invoice type and optionally enter a rate before adding them to a draft. If Invoice Maker is not installed, its store page opens; return to Road Camera and send again after installation. Copies added to Invoice Maker are managed separately from Road Camera's journey records.

Deleting a journey removes its Road Camera record, not separate clips, exported copies or Time Card activities. Those copies have their own deletion controls and may be retained or shared separately. Uninstalling or clearing Road Camera's data removes app-held journey records; exported and transferred copies remain subject to their destinations' settings.

Car connection and driving reminders

If you enable car auto-start, Bluetooth access is used to identify the selected car connection and react to connection changes. The app stores your selected car and related settings.

The optional Driving reminder starts off. With Physical activity permission, Google Play services supplies activity transitions, such as travelling in a vehicle, so the app can offer a recording reminder when appropriate. This reminder uses activity recognition rather than continuous GPS tracking for its trigger. Google Play services and device services operate under their own privacy practices.

Reports and remembered details

Reports may contain your account, driver and witness contact details, licence and policy numbers, vehicle details, injury descriptions, locations, estimated speed and impact readings, photos, selected clips and AI suggestions. Your own driver details are remembered for future reports. Deleting an individual report does not necessarily clear those separately remembered details.

You choose which report sections and photos appear in the PDF. Unticking a section excludes it from that export; it does not delete it from the stored report. Only share information you are authorised to disclose.

On-device analysis and AI summaries

Selected clips can be analysed on the phone using object detection and text recognition to suggest vehicle descriptions, possible number plates and lighting conditions, and to select frames for report photos. Suggestions can be wrong. Accepted values and selected photos become part of the report. Video analysis is distinct from address lookup and map loading, which may communicate with external providers.

Quick report can read text from photos you take, using on-device text recognition to suggest names, phone numbers, licence numbers, vehicle plates and insurance details. It fills only empty fields; review every suggested value. The original photos are retained with the report, along with recognised field values and markers showing which values came from photos. Changing a field does not change the photo. Report deletion and exported-copy rules apply as described below. Google's text-recognition service may collect usage and diagnostic information as described in this policy.

On supported devices and languages, you can request an on-device AI summary of your account. The supplied text and generated summary are processed locally, unless you have added a Claude key (see Optional Claude below). Saved summaries are report content and may appear in the PDF if included. Model preparation or downloads can require a connection.

These analysis features do not upload your footage or account to Useful Llama. MediaPipe sends performance and usage metrics to Google. Google's ML Kit and on-device AI services also collect usage and diagnostic information, such as device and app details, identifiers, performance information and feature events, under Google's policies. Local content processing does not mean that no service data leaves the phone.

Government vehicle checks

Government vehicle checks are optional. If you choose Check this plate, Road Camera copies the plate number to your device clipboard and opens the selected government website in your browser. Road Camera does not automatically submit the plate or retrieve the result. Information you enter or submit on that website is handled under its own privacy policy. You can return to Road Camera and choose a screenshot to read vehicle details on your phone. Road Camera does not save a copy of that screenshot or attach it to the report through this action. Details you choose to use are saved in the report and can appear in a PDF you create and share. The original screenshot remains wherever you saved it; choosing it here does not delete it. Your photo picker may download an image stored with a cloud provider.

Optional Claude (your own Anthropic account)

You can connect Claude, an AI made by Anthropic, by adding your own Anthropic API key in Settings. The key is stored only on your phone and is not backed up. You choose which Claude answers and pay Anthropic directly for what you use. Only while a key is added, and only when you use one of these features, the app sends Anthropic what that feature needs: to summarise your account, the account text you supplied; for the AI video summary in Quick report, up to four still frames from the clips you ticked, with their times and what the phone's own analysis found (such as suggested vehicle descriptions or number plates); and to fill in from a document, the document photo you chose, which can show names, addresses, dates of birth, licence, registration and policy numbers. Frames and photos can show people, vehicles and number plates. Claude's results are labelled as AI and are suggestions: you review them before they are saved or included in a report. If Claude cannot help, the app falls back to the on-device features described above. Anthropic handles what it receives under its own terms and privacy policy (https://www.anthropic.com/legal/privacy). Without a key, nothing is sent to Anthropic. You can remove the key in Settings at any time.

Document photos in reports

Fill in from a document lets you photograph or choose a document and read its text on your phone. Without a Claude key, the document image and recognised text are not uploaded for this reading step; with a key, the photo is sent to Anthropic to read it (see Optional Claude below). Road Camera creates a local working copy while you review it. You choose which details to save, where they belong and whether to append other recognised text to Other information. A copy of the photo is retained with the report only if you select that option. Otherwise the app attempts to delete the working copy when you finish or cancel. It also attempts to remove abandoned working copies when an app screen is created. A pending camera photo is protected from this cleanup for up to an hour, and may remain until a later app start after that period. Interrupted imports or failed deletions may leave temporary copies in the app's cache. Details saved from a photo are marked with their source, including in the report PDF. Selected details and included photos may be shared when you export or share the report. Removing a photo does not remove details already copied into the report, or PDFs already shared. Choosing an existing photo does not delete its original, and your photo picker may download a cloud-stored image. Only record and share other people's identity documents or details when you are authorised to do so, and keep only what is needed. The text-recognition software's usage and diagnostic data are described separately in this policy.

Speech input and guided questions

If you use speech typing or Talk me through it, microphone audio is passed to the phone's speech-recognition service. On-device recognition is used when supported; otherwise the installed service may send audio to its provider's servers. The provider controls its handling and retention. The app receives recognised text for your report rather than saving the dictation audio as a report audio file. This is separate from any sound recorded with video.

The guided flow presents questions one at a time and accepts spoken answers and navigation commands. You can pause listening and type instead. Recognised words and accepted suggestions are saved into the report for review.

Transcribing recorded clip audio

On compatible phones running Android 13 or later, you can transcribe sound already recorded in clips using the phone's on-device speech recogniser. The app supplies the clip's audio for local transcription; this feature does not use cloud speech recognition. It is separate from speech typing, which may use a provider's servers as described above. A speech-language pack may need downloading through the phone's service. Generated text, approximate audio-section times, clip references and your selections are stored with the report, including unselected lines. Some strong language is masked in the text; the original audio is not changed. Selected lines can appear in exported PDFs and be supplied to an on-device AI summary. Unticking a line does not delete it, remove it from an existing summary or recall exported copies. Delete the report to remove its app-held transcript; original clips and shared copies have their own deletion controls and retention.

Address lookup and maps

Looking up an address sends the relevant coordinates through the device's geocoding service to its provider. The guided report flow can also perform this lookup while preparing suggestions. A returned address may be saved in your report.

Loading the report's embedded Google map sends requests for the selected location to Google, even if you do not share the report. The Maps SDK also collects service information such as device metadata, IP address, SDK identifiers and diagnostic information. Opening an external map link gives its destination the selected location. You can move the report pin by tapping the map or dragging it. The report retains the position you choose separately from the original GPS position. In the guided report flow, moving the pin can trigger another address lookup. The map and address are suggestions to check, not verified incident locations.

Google's handling is explained in Google's Privacy Policy (https://policies.google.com/privacy).

Speed-camera data

Built-in Australian camera locations come from OpenStreetMap and are checked against the phone's location locally. You can also save your own camera spots on the device. Looking up or opening a map for a spot can involve the external services described above.

For speed-camera locations you save, Road Camera also keeps local review status and whether a location was passed during a drive, so you can review the saved spots later. Removing a saved spot does not remove existing events or recordings. Opening a spot in an external map sends its location to the map destination under that service's practices.

Camera-location data: © OpenStreetMap contributors, available under the Open Database Licence. See OpenStreetMap copyright and licence information (https://www.openstreetmap.org/copyright) and Road Camera's published camera dataset (https://useful-llama.github.io/road-camera/speed-cameras/). Viewing these web pages involves the hosting provider. The built-in dataset is not a record of your journeys.

Purchases and local settings

There are no ads and no Useful Llama account or recording-upload server. Google Play handles subscriptions, purchases and payment information. The app queries purchase information and acknowledges purchases to check Unlimited access; it does not receive payment-card details. It keeps local access status and the time of a missing-purchase check, together with recording-use counters, pause timing, report counts, preferences and Terms acceptance. Google holds its purchase records under its own practices.

Optional gift codes

If you choose to redeem a gift code, the app sends the code, the app identifier and a randomly generated installation identifier to Useful Llama's code service on Google Apps Script. No Useful Llama account is required. The installation identifier lets the service recognise a repeated request and manage the redemption limit; it is not your name, but it can link requests from this installation. Checking an existing gift sends its grant reference and the same installation identifier instead of the code.

Useful Llama keeps redemption records in a private Google spreadsheet, including the app, installation identifier, grant reference, receipt, redemption time, code version, allocated place, grant status and notification status. The service's code list stores salted hashes rather than readable codes. Redemption notifications sent to the Useful Llama owner include the app, reward, receipt, time and redemption counts. They do not include the code or installation identifier. Google processes service and connection information under its own policies.

These records provide and check the gift, prevent repeated requests from consuming another place, enforce the redemption limit and manage owner notifications. Uninstalling the app does not delete the service's redemption records or emails. To ask for access to your redemption record or for its removal, write to useful.llama@gmail.com with the app name and the receipt or approximate redemption time. Do not send the gift code, private recovery reference or passwords. When a record is removed, its installation identifier is deleted; the redemption still counts towards the code's limit, and the gift can no longer be checked or restored from the service (a later check on the phone removes it). We may need further information to locate the record. Google controls its own service records.

Storage, retention and deletion

Clips, associated tracks, events, report drafts, photos and PDFs are stored in the app's device storage. Original clips are retained without the free-version overlay; the free plan displays or exports the applicable watermark. Loop recording can replace older unsaved clips. Saved clips are excluded from normal loop replacement. Dismissing an event may return its clips to loop storage.

Use the available delete controls to remove local clips or reports you no longer need. Deleting one record does not remove copies in other reports, remembered details, exported files or someone else's storage. Clearing app data or uninstalling removes local app records. Android backup and supported device transfers may preserve selected settings and gift-code information, including the installation identifier, grant reference and receipt. Road Camera excludes its clips, journeys, reports, remembered personal details and local usage/purchase records from that app backup. Google Play restores purchases separately. Backup availability depends on your device and backup settings; it is not guaranteed. The app does not provide cloud recovery of recordings or reports. Manage Gallery copies and other exports separately, and keep needed copies before removal or reset.

Automatic Gallery copies

Automatic Gallery copies are off by default. If enabled, Road Camera queues new eligible clips for copying to Movies › Road Camera in shared device storage. You can choose highlights or all completed clips and optionally reduce the copies' resolution. Copies can include recorded sound, selected video overlays such as time or location, and the applicable free-version watermark. The app keeps local queue and completion records to manage copying. A queued clip may fail to copy or become unavailable before copying; this is not a guarantee of backup. Turning automatic copies off cancels clips still waiting to be copied.

Apps with permission to access this media, and backup services configured for the folder, may read or upload these copies under their own settings and policies. Road Camera does not itself upload these video copies or verify cloud-backup completion. Deleting an original clip, clearing Road Camera's data or uninstalling Road Camera does not remove Gallery copies or copies held by backup services. Manage those copies through the relevant Gallery or backup service. Changing overlay or compression settings does not change copies already made.

Sharing, Gallery and support

When you save to the Gallery, export a file or share through another app, that destination receives the copy you select. Gallery or storage services may sync files to a cloud account under your settings. Recipients may retain or forward copies. Deleting the app's original does not remove those copies.

Send feedback lets you send private feedback, described below, or email us. Choosing email opens your email app with our address and the app name and version in the subject; it does not automatically attach device details, recordings or reports. If no email app is available, it copies our address for you to use.

If you email support, we receive your email address, message and any attachments through our email provider. Send only what is needed and remove other people's private details where possible. We use correspondence to handle your request and delete it from our mailbox when the issue is resolved; provider retention and backups follow the provider's practices.

Private feedback

Private feedback is optional and is separate from a Google Play review. When you press Send, the app sends your rating from 1 to 5, any note you enter (up to 1,000 characters), and the app's name and version to Useful Llama's Google Form over an encrypted connection. The response is stored in Google Forms and its linked response spreadsheet for us to read and use to understand problems and improve the app. Google also records the submission time.

The app does not attach your name, email address, account or device identifier, location, recordings or reports to this request. Your note can identify you if you include personal information, so please leave out names, contact details, vehicle registrations, passwords and payment information. Google receives connection information when handling the request and processes it under its own privacy policy. This feedback is not a public review and is not published by Useful Llama.

Only Useful Llama's authorised administrators can view the private responses. If monthly reporting is enabled, responses and summary statistics may also be included in a private report emailed to useful.llama@gmail.com. This does not subscribe you to email. Monthly reporting is not required to send feedback.

We retain feedback while using it to investigate issues and plan improvements. There is no automatic deletion schedule for these responses. To ask us to find, correct or delete a response, email useful.llama@gmail.com with the app name, the approximate date and time you sent it, and a short exact excerpt from your note, if you wrote one. Our copies in the Form, linked spreadsheet and any retained reports are handled separately from Google's own service records. Deleting the app or its local data does not delete feedback already sent.

On the free version, the first private feedback the form confirms adds a one-time thank-you of 2 hours of watermarked recording, whatever rating you give. The app records on this phone that the thank-you was given and how much of that time is left; these records stay with the app's other local usage records and are not sent to Useful Llama. Nothing is given for Google Play ratings or reviews.

Your choices and updates

You can change feature settings and Android permissions. Disabling access can prevent related features from working and does not erase previously saved records or provider-held information. The app is not directed at children. We will update this policy when relevant practices change; the current version and date appear above. Contact useful.llama@gmail.com with privacy questions.