SoloCustody Privacy Policy

1. Why this app has its own policy

ClearStack Apps ("we", "us", "our") operates SoloCustody, sold on Google Play as Custody Log: Parenting Time. It is a record of custody handovers and child costs kept by one parent during a family law matter. That record can contain a child's medical receipts, the times a parent came and went, and notes written on bad days, so this policy is deliberately specific rather than pointing at our general one.

Short version: everything you enter stays on your phone, in a database encrypted with AES-256. There is no account, no sync and no server holding your record. The app requests no location permission of any kind and records no audio or video. The only things that leave the device are anonymous crash and diagnostic reports sent to Google, and a backup file you choose to share.

2. What the app does not do, and cannot do

These are properties of the build, not promises about our intentions:

• No location. The app declares no location permission. All three Android location permissions are explicitly removed from the manifest at build time so that no library can reintroduce one, and this is checked against the merged manifest of the release build rather than the source.
• No audio or video recording. RECORD_AUDIO is removed the same way. The app never offers to record anybody.
• No advertising. There is no advertising SDK in the app. Both advertising-ID permissions are stripped and advertising-ID collection is switched off in analytics, so Advertising ID is declared "No" on the Play data safety form.
• The other parent is never contacted. There is no invitation, no shared account and no notification to anyone else. They do not need to install anything and are never told the app exists.

3. What you enter, and where it stays

All of the following is created by you and kept on your device. None of it is sent to us:

• Case details — your name, how you refer to the other parent, an optional case reference, court note, and your lawyer's name and email
• Children — first name, optional date of birth, optional photo
• Your parenting plan — the pattern, handover time and usual place
• Handovers — the scheduled time, the times you record for your own arrival and departure, the outcome you state, your note, and an optional photo of the location
• Amendments — when you change a logged entry later, the previous value and the reason you gave
• Child costs — amount, currency, category, split percentage, the dates sent and repaid, an optional receipt photo, and your note
• Dated notes — anything you write, with the timestamp you set

4. Encryption on the device

Every database in SoloCustody is stored in Hive boxes encrypted with AES-256. The 256-bit key is generated on first launch by a cryptographically secure generator and held in flutter_secure_storage, which on Android is backed by the Android Keystore (AES-GCM with RSA-OAEP key wrapping). The key never leaves the device and is not bundled in the app.

An optional app lock uses your device's own unlock (fingerprint, face, PIN or pattern). A fingerprint that stops being recognised is not a lock-out: the app does not require biometrics, so your device PIN or pattern gets you in. The lock is offered on first run and never forced, because a device with no enrolled biometric and no device credential cannot use it at all.

Photos and receipts are stored as files in the app's private storage directory. Those files are protected by Android's own file-based encryption rather than by the database key.

This is strong, practical protection for a mobile device against someone picking your phone up. It is not a claim of certified or tamper-proof security.

5. What leaves your device

Crash and diagnostic reports (Google Firebase). If the app crashes or misbehaves we receive a technical report: the device model, the Android version, the app version, and a stack trace. These contain no part of your record — no names, no dates, no handovers, no costs, no photos. We use them only to find and fix faults.

Anonymous usage events (Google Analytics for Firebase). Counts of which screens are opened, so we can tell which parts of the app are used. No content and no advertising identifier.

Purchases (Google Play Billing). If you buy a subscription or the one-time purchase, Google processes the payment. We never see your card details. We receive only the fact that a purchase for this app occurred.

Backup files you share. The app can write a .scbak file containing your whole record, receipts included, so you can move it to a new phone. That file is created on your device and goes wherever you send it. It is not encrypted, so treat it like the document it is and do not send it anywhere you would not send the PDF.

The PDF record, when you export it. Generated on your device and shared only where you choose to send it.

6. Camera and photos

The app asks for camera access only when you choose to photograph a receipt or a handover location. Photos are compressed and stored on the device. The app never photographs or records another person, and the screen where you attach a location photo says so.

The app holds no permission to read your photo library. The Android media permissions are removed from the manifest at build time, so when you attach a photo the system hands the app only the single file you picked and nothing else.

7. Children's data

Children are the subject of this record, not its users. The app is rated for adults and is intended for a parent. The only information about a child the app holds is what you choose to enter: a first name, an optional date of birth, an optional photo, and the costs and handovers you record. None of it is transmitted to us or to anyone else.

8. What the record is, and is not

SoloCustody keeps your own contemporaneous record. It is not legal advice and it is not a determination about anyone. Whether a court accepts this record, and what weight it carries, is for your lawyer and the court to decide. The app works out outcomes only from the times you enter yourself; it observes nothing and never states why a handover did not happen.

9. Retention and deletion

Because there is no server, there is nothing for us to delete. Deleting an entry removes it and its photo from the device. Uninstalling the app removes the whole record, including the encryption key, and it cannot be recovered afterwards from us or from anyone else. Keep a backup file if that matters to you.

Crash and analytics data held by Google is retained under Google's own retention periods and is not linked to you.

10. Your rights

Since your record never reaches us, we hold nothing about you to disclose, correct or erase. For the crash and analytics data described in section 5, or for any question about this policy, write to support@clearstackapps.com.

11. Changes

If this policy changes we will update the date at the top of this page. Material changes to what the app collects will also be described in the release notes on Google Play.