Privacy Policy

1. Introduction

This Privacy Policy applies to the FixLog Android application provided by Mikael Tenshio.

FixLog is designed as a local-first repair and maintenance tracker. It does not require an account, developer-operated cloud database, analytics SDK, advertising SDK, or tracking service for its core features.

FixLog supports:

• Tracked items such as motorcycles, cars, appliances, gadgets, tools, and home items
• Repair and maintenance logs with dates, costs, notes, technicians, shops, parts, receipts, and photos
• Maintenance reminders, spending summaries, categories, and local app preferences
• User-created portable backups and optional exact shop locations selected on a map

Your maintenance records are kept in private app storage on your device unless you explicitly choose to export, back up, share, or open information in another app.

2. Data Stored Locally

Depending on the features you use, locally stored data may include:

• Item names, categories, brands, models, serial numbers or plate identifiers, purchase dates, notes, and item photos
• Repair titles, dates, costs, notes, receipt or repair photos, and related item information
• Technician or shop names, phone numbers, addresses, specialties, notes, and manually selected latitude/longitude coordinates
• Reminder schedules, notification preferences, spending summaries, currency, theme, category choices, and other app settings

These records are not automatically uploaded to a developer-operated server. Spending totals, reminder lists, and insights are calculated from the records stored on your device.

3. Photos, Receipts, and Media

FixLog lets you optionally add item photos and repair or receipt images. Selected images are copied into FixLog's private app storage so the app can keep them with the relevant records.

For gallery selection, FixLog uses the Android system Photo Picker where available and does not request broad photo-library or storage access. For capture, FixLog can open an installed camera app and grants that camera app temporary access only to the destination image file; FixLog does not request the Android CAMERA runtime permission.

Images remain local unless you explicitly create a backup, export information, share content, or otherwise send a file to another app or storage provider.

4. Maintenance Reminders and Notifications

FixLog can schedule local maintenance reminders for dates and repeating maintenance tasks. Reminder scheduling is performed on the device using Android system scheduling components.

On Android versions that require notification permission, FixLog may ask for notification access when you enable or create a reminder. If permission is denied or app notifications are disabled, the reminder record can still be saved but Android may not display its notification.

Reminder titles, dates, item names, and maintenance information are not sent to the developer in order to schedule these local notifications.

5. No Analytics, Advertising, or Tracking

The current FixLog Android release does not include Firebase Analytics, Firebase Crashlytics, Google AdMob, an advertising SDK, a developer analytics SDK, user-tracking SDK, or the Android Advertising ID permission.

FixLog does not send app-open events, screen-view events, repair records, item names, costs, photos, reminders, device identifiers, or advertising identifiers to the developer for analytics, advertising, or profiling.

Google Play and the Android operating system may process technical information about app installation, delivery, purchases, security, or device operation under their own terms and privacy policies. That platform processing is separate from FixLog's own data handling.

6. Optional Shop Map and Location Data

FixLog can optionally show an OpenStreetMap-based map when you choose an exact location for a saved repair shop. The app does not request device GPS or precise-location permission for this feature; you choose the point manually by tapping or dragging the map pin.

When you open the exact-location picker, FixLog uses Internet access to load map tiles from OpenStreetMap infrastructure. The map provider may receive ordinary network information such as your IP address and requests for the map area being displayed. FixLog does not use this connection for analytics or advertising.

The coordinates you select are saved locally with the shop record. If you tap the Map action, FixLog passes the saved coordinates or address to the mapping app or service that you choose, and that third party handles the information under its own privacy policy.

OpenStreetMap Foundation privacy information is available at https://osmfoundation.org/wiki/Privacy_Policy.

7. Permissions and Device Features

The current Android release may use the following permissions or platform features:

• Notification permission for maintenance alerts on Android versions that require runtime approval
• Internet and network-state access only for loading the optional OpenStreetMap tiles used by the exact shop-location picker
• Wake lock and boot-completed access through Android scheduling components so saved reminders can be handled reliably and re-established after a reboot
• System Photo Picker, file picker, and sharing interfaces when you choose images, backups, exports, or destinations
• External camera app for optional photo capture using temporary file access; no FixLog CAMERA runtime permission is requested

FixLog does not request contacts, microphone, SMS, call-log, or device precise-location permission for its current features, and it does not request broad all-files or broad photo-library access.

8. Backup, Restore, Export, and Retention

FixLog keeps its native records and imported image copies in private app storage. Android system cloud backup for FixLog is disabled in the current release.

When you choose to create a portable backup, FixLog can package app records and referenced images into a backup file and lets you choose the destination through Android's file picker. Once saved outside FixLog, that file is controlled by the destination app, file provider, local storage, or cloud provider you selected.

Restoring a backup reads the backup you select and imports its records and included images back into FixLog's private storage. FixLog may display a progress state while a large backup is being created or restored.

Local data remains on the device until you delete it, clear FixLog's app data, restore different data over it, or uninstall the app. Exported or backed-up files remain wherever you saved them until you remove them there.

9. Migration from Older FixLog Versions

When updating from certain older FixLog versions built with the previous web-based framework, the current native Android app may perform a one-time local migration of existing repair records, reminders, shops, settings, and embedded images into the new native storage format.

This migration happens within the app's device storage. The migration process does not upload the old FixLog data to the developer or to an analytics service. A local safety copy of the legacy state may be retained inside private app storage as part of the migration process.

FixLog can also recognize supported older backup formats when you manually choose them for restore.

10. Children's Privacy

FixLog is not directed to children under 13. The app does not provide a developer-managed account system or knowingly collect personal information from children through analytics or advertising services.

11. Changes to This Privacy Policy

This Privacy Policy may be updated when FixLog changes its features, permissions, third-party services, or data-handling practices. The effective date on this page will be updated when material revisions are published.

12. Contact Us

Email: help.tenshioapps@gmail.com

Effective date: August 7, 2026