Authenticated access
Accounts use authenticated sessions, server-side authorization checks, and role-aware access for protected records.
Security
Security and data handling.
MiCaso and PetitionPro handle sensitive immigration information, so access control, private storage, and careful operational practices are core requirements.
Encrypted connections
Production deployments use HTTPS so information moves between the app, browser, and backend through encrypted connections.
No server secrets in mobile apps
Mobile builds should contain only public client configuration. Server-only keys for AI, payments, messaging, and admin database access stay on the backend.
Private document handling
Uploaded notices and documents are stored through controlled backend paths and signed or authenticated access patterns where supported.
Notifications and device records
Push tokens, platform, app build, timezone, and approximate device location signals are handled through backend controls and used for notifications, reliability, support, and owner analytics.
Store builds and update controls
MiCaso may use Apple, Google, Expo, and Vercel controls to publish app updates, manage production builds, and require minimum app versions when needed for security or reliability.
Account deletion
Signed-in MiCaso users can start account deletion in the app from Profile, and support can help with privacy or deletion requests.
User responsibility
Users should protect their device, use strong passwords, avoid sharing login credentials, and upload only documents needed for the feature they are using.