Privacy Policy – LarasReport

Last updated: 28 September 2026

This policy covers the LarasReport Android app, package com.larasdesk.larasreport. It explains the local creation of service reports, photos, customer confirmations and PDF files, and the sharing actions you initiate.

1. Provider and privacy contact

LarasReport is provided by Lara Knuth, Dresden AI Insights. Contact address: Kurhausstraße 16, 01259 Dresden, Germany. Email: support@larasdesk.com; phone: +49 1567 8333414.

The provider is your contact for questions about the app and is responsible for personal data she processes herself, for example when handling a support request addressed to her. The app does not give her remote access to your reports. When you use LarasReport for customer work, you or your business decide which customer data to include, for what purpose and with whom to share it. You must inform the people concerned and establish an appropriate legal basis for these business activities. Buying the app does not provide that basis.

2. Data processed by the app and its purposes

LarasReport helps you document work and produce an A4 PDF. The app processes the details you enter: sender name and optional contact line, customer, work location, date, reference, work performed, total hours and up to 30 material entries. A report can include up to 25 photos with notes and a chosen order. Free text and images may contain information about you, your customers or other people.

An optional customer confirmation adds a name, drawn lines, device time and local time offset. The app uses the report revision and a local hash to associate the confirmation with a particular version of the contents. Subsequent changes to the contents remove the confirmation. There is no identity check, biometric recognition or independently verified time. This feature does not provide a qualified electronic signature or promise formal acceptance of work or evidentiary reliability.

For its operation, the app also stores report numbers and internal identifiers, creation and update times, revisions, photo metadata, hashes, your sender profile and the language setting. Information about an interrupted camera or selection operation helps associate its result with a report. Technical cleanup jobs contain file and report references, timestamps, error codes and retry counts. They help prevent outdated writes and remove files created by the app.

3. Storage and protection

Reports and technical records are stored in the app's local database. Processed photos and thumbnails are kept in private app storage. The language setting is stored in local WebView storage. To share a report, the app temporarily places a readable PDF copy in its own cache under report-exports/.

The app uses Android's separation of app storage. It does not add its own encryption to reports or PDF files. Protection therefore also depends on the condition of your device and its screen lock. This does not rule out access through a compromised operating system or an unlocked device.

4. Photos and permissions

You start the camera or photo picker yourself. The app does not declare its own camera, media, location or internet permission. Capture and selection use the relevant Android or camera interfaces.

LarasReport locally creates new JPEG files and thumbnails from the selected image pixels. Original EXIF and GPS metadata is not copied into these new images. Faces, addresses and other details visible in the picture remain visible. Selected original photos outside the app are neither edited nor deleted. A camera capture may initially exist as an app-owned temporary file that still contains original metadata; cleanup is attempted after processing and may be queued for another attempt if it fails.

5. Sharing and external services

LarasReport operates without its own network connection and does not automatically upload reports, photos or customer confirmations. The app has no user accounts, cloud synchronization, advertising, usage analytics or diagnostic uploads. A backup file, too, only reaches the location you choose in the Android save dialog (section 7).

Only your “Share PDF” action passes the specific readable PDF through the Android share sheet to an app you select. The file may contain report text, photos and the customer confirmation. The receiving app determines under its own rules whether to store the file locally or transmit it elsewhere, including to a cloud service. LarasReport cannot recall or delete copies held there. Returning from the share sheet does not confirm delivery.

Installation, purchase and updates through Google Play are separate store activities. Google processes data for these activities under its privacy policy. LarasReport has no payment processing or in-app purchase integration of its own. If you open this policy in a browser or contact the provider outside the app, the general LarasDesk privacy information also explains page access, hosting and support. These activities do not automatically send local report contents to the provider.

This public page is delivered through Google's Firebase Hosting. Google processes IP addresses; it describes abuse detection and hosting usage analysis as purposes and retains IP data for a few months. Processing outside the EU, in particular in the USA, is possible. For transfers to the USA, Google has joined the EU-US Data Privacy Framework, which is covered by an adequacy decision of the European Commission; for transfers outside that framework, Google states that it relies on standard contractual clauses. Details, including international transfers, are explained in the Firebase privacy information. Providing and securing the requested information page serves a legitimate interest under Article 6(1)(f) GDPR. This browser request is separate from creating reports locally.

6. Retention and deletion

A report stays in this installation until you delete it, clear the app's data through Android or uninstall the app. Deleting a report clears its text, sender snapshot and customer confirmation and removes its photo records. A technical deletion record remains with the identifier, report number, work date, revision and creation, update and deletion times. It prevents an outdated save operation from recreating the report or reusing the report number. This record and the separately stored sender profile have no automatic expiry period.

App-owned photo files and temporary camera originals are removed through stored cleanup jobs. If cleanup fails, it may be retried during a later app operation. Removal of a PDF cache copy is scheduled approximately five minutes after the share sheet returns. After the process ends, known old cache copies may be removed during later cleanup once they are at least 24 hours old. Files not yet handed to a receiving app are removed immediately where possible. Active sharing, a terminated process or errors may delay actual deletion; these times are not guaranteed maximum periods.

Clearing app data or uninstalling the app also removes the remaining local technical records. Previously shared PDFs and original photos outside the app are unaffected. Secure physical overwriting of device storage is not promised. The provider cannot remotely delete local data from your device.

7. Manual backup and restore

From version 0.1.5, you can create a backup file yourself under “Data & backup” in the menu. The app creates it only when you tap the action, never on a schedule or at app start. In the Android save dialog you choose the location and file name; the app does not remember that location and keeps no access to it afterwards. The ZIP file contains all existing reports, including drafts, with their sender snapshot, texts, materials, photos with thumbnails and notes, and customer confirmations, as well as your sender profile. For deleted reports it contains only the identifier, report number, work date, revision and timestamps. It does not contain PDF cache copies, temporary camera files, cleanup jobs, interrupted camera operations or the language setting.

The backup file is not encrypted. Anyone who can open it can read reports, photos and customer confirmations. If you choose a cloud storage service, its app uploads the file under its own responsibility; LarasReport opens no connection for this and cannot recall or delete copies held there. Before saving, the app writes the file temporarily to its private cache under larasreport-backup/ and attempts to remove this copy after completion or cancellation. Removal of remaining copies is retried at the next app start; file-system errors may delay deletion.

To restore, you choose a backup file yourself. The app copies it temporarily to the same private cache, checks its structure and checksums and shows what will be added before anything changes. Missing reports are added only after you confirm; if no sender is set up yet, the backed-up sender is used. Existing reports are never overwritten or deleted, and reports deleted on this device are not restored. A customer confirmation that no longer matches the backed-up content is not carried over. The checksums detect damaged files; they are not a signature and prove neither origin nor integrity against deliberate editing.

Android system backup and automatic device transfer remain disabled. Without a current backup that you created, device loss or failure, clearing app data or uninstalling the app can cause loss of reports. Versions up to 0.1.4 offer no backup. An exported PDF remains a readable document; it cannot be imported as an editable report.

8. Requests, legal bases and your rights

If you contact the provider, the contact details and request contents you supply are used to handle your request. For matters concerning your app contract or a related pre-contractual request, the basis is Article 6(1)(b) GDPR; for other requests it is Article 6(1)(f) GDPR and the interest in responding. You are under no statutory or contractual obligation to contact the provider; without contact details, however, your request cannot be answered. Send only the information needed for that purpose. Reports or photos are not automatically required for a general support question or retrieved from the app. Request data is deleted when no longer needed to handle it, unless a statutory retention requirement applies. The general privacy information explains the related external activities.

Subject to the conditions in the GDPR, you may request access, correction, deletion or restriction and may have a right to data portability. You may object to processing based on legitimate interests for reasons relating to your particular situation. Where processing is based on your consent, you may withdraw it for the future. Whether or not you create a backup does not affect these rights.

For questions about processing by the provider, use the contact in section 1. For customer data in a business service report, the responsible business is the appropriate contact; the provider cannot access those local contents. You may also complain to a data protection authority, particularly in the country where you live, work or believe a violation occurred. The Saxon Data Protection and Transparency Commissioner is one contact for the provider's location. LarasReport does not create user profiles or make automated decisions about people that have legal or similarly significant effects.