Sogliva privacy policy

Last updated: 2026-10-30

Data controller: Enea Studio — contact: developer.eneagames@gmail.com


1. In short

Sogliva is an app for keeping track of the money available between one salary credit and the next. It is built to work entirely on the device:

The following sections describe how this works in detail.

2. Data processed, and where it lives

The data you enter in Sogliva — accounts, transactions, balances, income, commitments, funds, loans, due dates and settings — is saved in a database encrypted with SQLCipher in the device's internal storage. The encryption key is generated randomly on the device and protected by the Android Keystore on Android and by the iOS Keychain on iPhone, where it stays bound to that device and is available only while a device passcode is set; it is not stored in the database nor anywhere else in clear text.

The controller has no access to this data: there is no account, there is no server, there is no channel through which the data could reach the controller.

Imported files

You can import bank statements from .xls, .xlsx, .csv and .pdf files chosen through the system file picker. Imported files are copied into the app's encrypted store and deleted automatically after 30 days. You can delete them earlier.

Attachments

You can attach a photo of a receipt or a document to a transaction, taken with the camera or chosen through the system picker. The copy stays in the encrypted store on the phone, travels only inside the encrypted backup and is erased when you remove the attachment or erase the app's data. It is not sent to anyone.

Widget (Android)

On Android you can add Sogliva's widget to the Home screen. It shows what you can spend and when it was last updated even while the app is locked: to do so, Sogliva leaves those lines in clear text in the app's private storage, outside the encrypted store. They hold no transactions, accounts or descriptions, never leave the phone and are erased when you remove the last widget. Without a widget nothing is written.

Notifications

Sogliva's notifications are local: they are scheduled by the operating system on the device, without passing through external servers. They are off by default and are turned on only by your choice. Their text never contains amounts, accounts or counterparties. They can be turned off at any time from the app or from the system settings.

Backup

A Sogliva backup is:

The backup file is saved where you choose (device storage, other apps, your own cloud services). From that moment its safekeeping is your responsibility and that of the services you choose.

Plain-text export

On your explicit request, from Settings → "Export the transactions", Sogliva writes an unencrypted CSV file with the transactions in the vault (date, description, amount, currency, account, category). The file is saved only in the folder you choose at that moment, does not leave the device and is not transmitted to anyone; whoever can open that folder can read it. The screen says so before you tap. It is a separate action from the backup, which stays encrypted.

Deletion

You can delete all data from the app at any time: deletion closes the database, destroys the encryption key (crypto-shredding) and removes files, caches and notifications managed by the app. Uninstalling the app also removes the data from the device. Without a Sogliva backup and its recovery code, deleted data cannot be recovered — neither by you nor by the controller.

3. Permissions used

Android

The list below matches the manifest of the release build; permissions that require explicit consent are requested only when needed. The "display over other apps" permission (SYSTEM_ALERT_WINDOW), which the development template declares for debug windows, is removed from the release build because no feature uses it; so is access to photos and storage (READ_MEDIA_IMAGES, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE), because the files you choose go through the system picker.

PermissionWhy
Notifications (POST_NOTIFICATIONS)Optional local alerts about due dates and critical days. Off by default.
Biometrics (USE_BIOMETRIC, USE_FINGERPRINT)Locking the app with a fingerprint or the device credential.
Boot completed (RECEIVE_BOOT_COMPLETED)Re-scheduling local notifications after the phone restarts.
Vibration (VIBRATE), wake lock (WAKE_LOCK), badge (READ_APP_BADGE and the equivalent permissions of the Samsung, Huawei, Oppo, HTC, Sony and other launchers)Operation of local notifications.
Push notifications (com.google.android.c2dm.permission.RECEIVE)Declared by Firebase Messaging, which the notifications library brings along. Sogliva receives no push notifications: there is no server to send them, and its notifications are all local.
Install referrer (BIND_GET_INSTALL_REFERRER_SERVICE)Declared by a framework library (Expo) that could ask Google Play which link the app was installed from. Sogliva does not ask.
Internal permission (DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION)Generated by AndroidX so that the app's internal messages cannot be received by other apps. It grants access to nothing.
Licence check (com.android.vending.CHECK_LICENSE)Not requested by the app: Google Play adds it to the copy it distributes, as part of automatic protection, to check that the app was installed from the store. Sogliva's own code does not use it.
Screenshot detection (DETECT_SCREEN_CAPTURE)Applying the optional protection against screenshots and recordings. On Android 13 and later, the recent-apps preview is hidden even when optional capture protection is off.
Network (INTERNET, ACCESS_NETWORK_STATE)Declared by the app framework (React Native/Expo). By design Sogliva makes no network connections: there is no server to send data to. Measured on the release produced from the App Bundle on 11 September 2026: zero bytes received and zero sent while unlocking, completing onboarding and opening the home screen.
Camera (CAMERA)Photographing a receipt or a document to attach to a transaction or an administrative task. Requested at the first shot, never at start-up. The attached photo stays in the encrypted store on the phone, and nothing leaves the phone.

iPhone

On iPhone every permission is requested by the system the first time it is needed, never at start-up. The iOS build asks neither for push notifications nor for cross-app tracking (App Tracking Transparency), nor for access to the photo library: a file already on the phone is chosen through the system picker.

PermissionWhy
NotificationsOptional local alerts about due dates and critical days. Off by default: iOS asks for permission only when you turn them on.
Face ID (NSFaceIDUsageDescription)Unlocking the app with Face ID or the device passcode.
Camera (NSCameraUsageDescription)Photographing a receipt or a document to attach to a transaction or an administrative task. The attached photo stays in the encrypted store on the phone, and nothing leaves the phone.

4. Legal basis and rights (GDPR)

Since no personal data leaves the device and the controller does not collect, receive or keep any user data, there is no processing of personal data by the controller within the meaning of Regulation (EU) 2016/679.

The rights provided by the GDPR — access, rectification, erasure, portability — are exercised by you directly and on your own:

Note on platform services

Distribution through Google Play or the App Store may mean that Google or Apple collects technical device data (for instance crash and performance statistics from Android vitals, or iOS crash reports, if you have enabled diagnostics or sharing with app developers in the system settings). This data is collected and processed by Google or Apple under their own policies; Sogliva includes no crash-reporting or analytics SDK of its own and does not receive such data on your device.

5. Children

Sogliva is a personal finance tool and is not aimed at children. As it collects no data, the app does not knowingly collect data from children.

6. Changes to this policy

Should future versions of Sogliva introduce features that involve collecting or transmitting data (for instance synchronisation or optional services), this policy will be updated before that feature is released, with the date shown.

7. Contact

For any question about this policy: developer.eneagames@gmail.com

Data controller: Enea Studio