← All help topics Understand your data

What local-first means in OptiFit

Where tracking data lives by default and when files can leave app storage.

A local app for your everyday

OptiFit processes nutrition, fasting, training and progress directly on your device. You create a local profile without an online account. The installed app supports this tracking offline and sends no in-app usage analytics to us.

Your entries are personal information: they may include profile details, body measurements and nutrition or training history. You keep them on your device. We receive no automatic copies of your entries.

What encryption protects

The local tracking database is encrypted using SQLCipher and AES-256. Permanently saved progress photos and their thumbnails are also stored in this database. At database startup, the app checks that it is not using an unencrypted SQLite database.

A random database key is managed through protected device storage. Encryption at rest is one protective measure; it is not a guarantee against every form of access to an unlocked or compromised smartphone.

Your data stays with you

Your meals, body measurements and training entries are stored and processed locally. This approach keeps personal information in your hands and avoids automatically transmitting your entries to us.

This statement concerns app data storage. Website visits, app-store use, support enquiries and external services you select have their own processes and privacy information.

Local access over time

An installed, working version processes your tracking locally. You can use these features and access your saved entries without an internet connection.

A working installation on a compatible device is still required. This is not a promise that every future operating system version, update or device change will work without limitations. Keep important backups deliberately.

Backups and portable exports are different

A full snapshot contains the encrypted database and depends on the key of that installation. A portable export is a different format: it contains readable data inside a ZIP file and is not automatically protected by database encryption.

You initiate exports and sharing yourself. Check where you save files and who receives them. Other apps and storage destinations have their own storage, transfer and privacy rules.

The precise boundary of encryption

Not every local file is covered by SQLCipher. Ordinary settings, local diagnostic logs and temporary photo drafts before saving sit outside the encrypted tracking database. App-private storage and database encryption are separate layers of protection.

The precise promise is therefore that saved tracking data and permanently saved progress photos in the local database are encrypted. A blanket promise covering every file, export or device would go further.