Authenticated access
Accounts use authenticated sessions, server-side authorization checks, and role-aware access for protected records.
Security
MiCaso and PetitionPro handle sensitive immigration information, so access control, private storage, and careful operational practices are core requirements.
Accounts use authenticated sessions, server-side authorization checks, and role-aware access for protected records.
Production deployments use HTTPS so information moves between the app, browser, and backend through encrypted connections.
Mobile builds should contain only public client configuration. Server-only keys for AI, payments, messaging, and admin database access stay on the backend.
Uploaded notices and documents are stored through controlled backend paths and signed or authenticated access patterns where supported.
Signed-in MiCaso users can start account deletion in the app from Profile, and support can help with privacy or deletion requests.
Users should protect their device, use strong passwords, avoid sharing login credentials, and upload only documents needed for the feature they are using.