What database does Lova use?

Lova uses SQLite, an embedded database that runs entirely on your device. Your data is stored in an encrypted database file that only the Lova app can access.

How is my data encrypted?

Your data is encrypted using AES-256, the same encryption standard used by banks and governments. The encryption key is stored in your device's secure enclave (iOS Keychain or Android Keystore).

What about syncing between devices?

Lova supports local sync via your home network or direct device-to-device transfer. Data never passes through our servers. You control exactly when and how sync happens.

Can I export my data?

Yes! You can export your data in FHIR (healthcare standard), CSV, or JSON formats. This is your data - you should be able to take it anywhere.

What happens if I lose my phone?

Your data is protected by your device's security (Face ID, fingerprint, PIN). Without your device unlocked, the data is encrypted and inaccessible. We recommend regular local backups.

How Lova Protects Your Privacy - Technical Deep Dive

The Architecture

Lova uses a zero-server architecture. Unlike most apps that sync your data to cloud servers, Lova stores everything locally on your device. There are no Lova servers that store user data - because there's no user data to store.

Local Storage

All your health data is stored in a SQLite database on your device. SQLite is a proven, reliable database engine used by iOS, Android, and billions of apps worldwide. It's embedded directly in Lova - no network connection required.

ℹ️

Database Location

iOS: App sandbox, protected by Data Protection
Android: Private app storage, encrypted at rest

Encryption

Your database is encrypted using AES-256 encryption. The encryption key is generated on first launch and stored in your device's secure enclave:

iOS: Keychain Services with kSecAttrAccessibleWhenUnlocked
Android: Android Keystore with hardware-backed keys

Network Isolation

Lova's core functionality requires zero network access. The app works completely offline. When you do connect to the internet, Lova only makes network requests for:

Checking for app updates (optional)
Loading this website (when you tap "Help")

Health data is never included in any network request. This is enforced at the architecture level - there's simply no code path that sends health data over the network.

Data Export & Portability

Your data belongs to you. Lova supports exporting your complete health history in multiple formats:

FHIR (Healthcare Standard)

Fast Healthcare Interoperability Resources is the modern standard for health data exchange. Export your data as FHIR resources to share with healthcare providers or import into other health apps.

CSV & JSON

For analysis in spreadsheet apps or custom tools, export as CSV or JSON. All fields are clearly labeled with documentation.

💡

Regular Backups

Since your data lives only on your device, we recommend regular exports as backups. Store them securely - they contain sensitive health information.

Local Sync (Optional)

If you use Lova on multiple devices, you can sync between them without any cloud service:

Local Network Sync: Devices on the same WiFi network can sync directly
Direct Transfer: Use QR code or NFC to sync device-to-device
File Export/Import: Manually transfer encrypted backup files

At no point does your data pass through Lova servers or any third-party cloud service.

Verify It Yourself

Every claim on this page can be verified. Use network monitoring tools to confirm no health data is transmitted. Try the app in airplane mode—everything works because everything stays on your device.

How It Works