Legal
Data protection notes β Steadfast
Supplementary notes to the general Data protection for the Steadfast app (Organising Health & Accessibility) by Christian Tonke. One section per module: what is stored locally, which permissions are used and why, and whether data leaves the device.
Contents
Modules
Controller
Christian Tonke
Adelheider Str. 258
27755 Delmenhorst
Germany
Email: christian@tonke.de
Applies to all modules
- No user account. Steadfast does not require registration, an email address or signing in with me. I don't know who uses the app.
- Local only. All content lives in a local SQLite database inside your device's private app container; particularly sensitive fields are additionally encrypted with AES-256-GCM, with the key in the keychain (iOS Keychain or Android Keystore). Deleting the app removes this data.
- No server of mine. Steadfast has no server of its own. The only network connection is purchasing and verifying the subscription via StoreKit 2 (Apple) or Google Play Billing (
expo-iap) β Apple's/Google's own privacy terms apply there as well. - Sharing only by you. Exports, backups and reports (PDF/ZIP/CSV) are only ever shared through the system share sheet, when you trigger it yourself.
- Subscription. Steadfast is a subscription (β¬3.99/month, β¬29.99/year) with a free basic tier; purchase and management run entirely through Apple/Google β I never see any payment details.
1. Symptom History
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Symptom, severity, time, time of day, trigger, duration, body area, relief, note, "for appointment" flag, evidence.
Permissions: Camera, photos, files (evidence only).
2. Medication & Supply
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Name, form, own schedule, times, stock, dose per intake, reorder threshold, practice, intakes, stock movements.
Permissions: Notifications, camera, photos.
3. Preparing Doctor Visits
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Title, specialty, practice, questions/answers, things to bring, notes, aftercare.
Permissions: Notifications, files.
4. Food & Tolerance
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Meals, ingredients, reactions, own intolerances; menu photo + OCR with keyword highlighting.
Permissions: Camera, photos.
5. Barrier-Free Outings
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Places, address, criteria, rating, must-have criteria per profile, toilets, visits.
Permissions: Notifications, camera (QR), photos, files.
6. Low-Stimulation Planning
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Plans, stimulation level, rest periods, retreat spots, aids, schedule cards, review (0β10).
Permissions: Notifications.
7. Info & Communication Cards
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Card texts, emergency contacts, diagnoses/allergies/medication/aids only if entered.
Permissions: β.
8. Noise & Surroundings
Local only β data leaves the device only if you share or back it up yourself
What is stored locally: Time, location, relative average/peak level, per-second trace, duration, how it felt, surroundings, note.
Permissions: Microphone.
App stores
Steadfast is distributed through the Apple App Store and Google Play. The terms of service and privacy policy of Apple or Google apply to the payment process and billing.
Legal basis
Local processing on your device: Art. 6(1)(b) GDPR (performance of the contract/use of the app) or legitimate interest (Art. 6(1)(f) GDPR). Any voluntary sharing (export, share sheet) happens at your own initiative.
Your rights
Since all content lives exclusively on your device, you can view, change, export or delete it yourself at any time (app settings or uninstalling). For questions about this processing, reach me at christian@tonke.de.