Civistara app · Member mobile app
Where members see where they stand.
The Civistara app is the member app of Civistara Compliance. Members see their status, log work or volunteer hours, report an exclusion, answer notices, and follow an appeal, on their own phone and in their own language. What they submit reaches state staff as structured evidence; the state agency decides.
What follows describes what the app does, for state agencies, health plans, and the providers who help members keep coverage. Items still in development are labeled.
- Languages
- 15UI languages · every translation file at key parity with English
- Accessibility
- 22screens reviewed against WCAG 2.1 AA · on-device testing of 5 in progress
- Platforms
- 2iOS and Android
- Encryption depth
- 3layers at rest · device-only keys · zero analytics vendors
Updated
Hours checked where they happen, when the member chooses.
Location check-in is optional proof for the member. A member who chooses it can check in at a registered work or volunteer site; the app sends adaptive-cadence heartbeats during the session, more often near the site boundary. Each heartbeat consumes a server-issued, single-use token, so a replayed packet is rejected. Treatment sites are never geofenced.
Mock-location and impossible-accuracy signals raise anomaly flags for staff review. Native device attestation is on the roadmap: Android Play Integrity verification is implemented, with production enforcement planned for general availability; Apple App Attest on iOS is planned.
- Verification
- Adaptive-cadence heartbeat · single-use token rotation · server-side validation
- Provenance
- On-device geofence + server-side distance check · mock-location and impossible-accuracy anomaly flagging
- Device attestation
- Roadmap · Android Play Integrity verification implemented, production enforcement planned for general availability · Apple App Attest planned
- Standard
- IETF RFC 4122 unique tokens · TLS pinned to the issuing certificate authority
Multi-language at production depth.
The Civistara app is available in 15 languages: English, Spanish, Vietnamese, Haitian Creole, Arabic, Chinese, Portuguese, Hindi, Korean, Tagalog, Russian, French, Urdu, Persian, and Japanese. Three of those languages render right-to-left, meaning the entire interface flips horizontally so menu drawers, navigation, and form fields appear in the natural reading direction. The right-to-left languages are Arabic, Urdu, and Persian.
Every translation file carries the same keys as the English source, and a test checks parity. Onboarding, status, exclusion requests, and in-app guidance are covered in all 15 languages. Spanish and Vietnamese are New Orleans’ priority languages for residents with limited English.
- Locales
- 15 · English, Spanish, Vietnamese, Haitian Creole, Arabic, Chinese, Portuguese, Hindi, Korean, Tagalog, Russian, French, Urdu, Persian, Japanese
- Right-to-left
- Arabic, Urdu, Persian · the interface flips horizontally for natural reading direction
- Coverage
- Every locale at key parity with English · parity-tested
- Reach
- Onboarding, status, exclusion requests, in-app guidance
Always on, always visible.
The member sees their status at a glance. Every check-in updates the dashboard. The cure-period countdown shows on screen, and in-app notices carry a timestamped delivery receipt. The member can read who accessed which media asset, when, and with what role, directly from the mobile app.
The Civistara app is offline-first: an encrypted read cache, queued changes, and automatic sync on reconnect. A member can see recent status and record hours or an exclusion request without a signal, and the app sends them when service returns. Compliance-critical screens carry a non-dismissible banner when the data on screen may be out of date.
- Real-time
- Live compliance dashboard · cure-period countdown · notice delivery receipts · in-app access log
- Offline
- Offline-first · encrypted read cache · queued changes · automatic sync on reconnect
- Resilience
- Form draft auto-save with 24-hour restore window on hour logs, exemption requests, and appeals
- Honesty
- Non-dismissible stale-data banner on compliance-critical screens when offline
Privacy by design.
Beneficiary data is encrypted at rest in three independent layers. The device keychain holds session credentials. A full-disk encrypted store holds cached records using AES-256-CBC with HMAC-SHA256 integrity verification. Media uploads are encrypted in 1-megabyte chunks before they leave the device. The encryption keys are device-only. They never leave the phone, and they are destroyed when the beneficiary signs out.
Screen-capture and app-switcher previews are blocked on every screen that displays protected health information. Push notifications carry generic content for sensitive event types so a lock-screen reader cannot see a denied exemption. The app collects no behavioral analytics. There is no third-party analytics vendor. No Firebase. No Amplitude. No Segment. A first-launch consent gate captures the beneficiary's acceptance of the privacy policy and terms of service, timestamped to the device keychain and re-prompted on policy amendments.
- Encryption
- Three layers at rest · device keychain + full-disk AES-256-CBC + chunked file encryption · device-only keys
- Exfiltration block
- Screen-capture and app-switcher protections · audit event emitted on every attempt
- Notifications
- Generic payloads for 22 sensitive event categories · lock-screen safe by default · user-toggleable
- Analytics posture
- No analytics vendor · no Firebase, no Amplitude, no Segment · zero third-party trackers
A source of clean data for everyone.
Submissions from the Civistara app are structured. An hour entry carries activity type, employer or organization, location provenance when the member chose location check-in, and timestamp. An exclusion request lands in a typed category. A status-change report (pregnancy, disability onset, treatment enrollment) creates the matching exclusion record on the platform side after staff review.
State staff receive typed, validated, attestation-tagged evidence rather than free-form text to re-key, with an audit trail from the member’s submission to the state’s record. See /safeguards for the protections enforced on top of that data, and /platform for the architectural guarantees that hold the audit chain together.
- Structure
- Typed activity records · typed exclusion categories · attestation-tagged hours · timestamped at submission
- Coordination
- Status-change reports create exclusion records on staff approval
- Traceability
- Two-tier audit emission · device-to-ledger chain · 37 action types across 12 resource categories
- Intended effect
- Less re-keying by staff · evidence ready for fair-hearing review