Security at MigraInfo Pro

Describes the service as of October 9, 2026. We update this page when the service changes.

MigraInfo Pro is designed for immigration law firms, nonprofit organizations, consulates, and similar organizations that handle information about their clients' immigration cases. This page explains how we protect it, in enough detail for your own vendor review. Questions it doesn't answer go to security@migrainfo.com.

Where your data lives

MigraInfo Pro runs on Google Cloud (Firebase). Your organization's data is stored in Google's United States multi-region database and processed in the United States. Data is encrypted in transit with TLS and at rest by Google Cloud.

Who can see it

• Your organization only. Every case, client, note, key date and message log belongs to one organization. Organization-scoped data is readable only by authorized members of that organization under the database's security rules, checked on every request. The one public exception is your logo, which is served from storage for your sign-up page and emails.
• Roles. Owners, admins, staff and read-only members. Changes never go straight to the database: every change goes through our server, which checks the member's role first.
• Your clients see only what you send them and, if you invite them into the MigraInfo app, the status of that one case. They never see your notes, your team or your other cases.
• Our staff access production data only to operate, support or secure the service, through named accounts protected by multi-factor authentication and role-based permissions.

Signing in

Members sign in with their Google or Microsoft work accounts. Those providers manage the credentials, so MigraInfo does not receive or store users' passwords, and your organization's own policies, including multi-factor authentication, apply when your members sign in.

Client communications and consent

Texts and emails go only to clients with a recorded consent for that channel. STOP replies and email unsubscribes are honored automatically, and every message, including blocked ones and the reason, is logged on the case as your record of notice.

Built to keep less

• Invite links and client share links are stored only as one-way hashes.
• Email logs leave out each client's private unsubscribe link.
• Error reports from the web app strip tokens and query strings from page addresses.
• Card and bank-account details are entered with Stripe and do not pass through or stay on our servers; we keep billing metadata such as Stripe identifiers and invoice references.

Backups and recovery

The database keeps point-in-time recovery for 7 days and daily backups for 7 days, and is protected against deletion. Your organization's owners and admins can also export everything as one file at any time, from Settings.

Audit trail

Changes to membership, roles, settings, billing, client consent and messages are written to an audit log that your organization's owners and admins can read in the app and include in the export.

Where case data comes from

USCIS status comes from USCIS's case-status service. Immigration court information comes from EOIR's public automated case information, checked from your members' browsers. MigraInfo Pro never asks for or uses your credentials for any agency system.

Service providers and other third parties

These companies provide infrastructure, communications, authentication, billing and other services used by MigraInfo Pro:

• Google Cloud (Firebase). Hosting, database, server code, sign-in and logging.
• Microsoft. Sign-in identity for members who use a Microsoft account.
• Stripe. Billing and card processing.
• Twilio. Text messages to your clients.
• Resend. Email delivery.
• hCaptcha. Human verification for court lookups made from your browser.

Each one's legal role (subprocessor, or an independent provider such as a payment processor or identity provider), the data it receives and where it operates are set out in our Data Processing Addendum, which is the authoritative list. We'll tell your organization's owners before adding a subprocessor.

Incidents

If a security incident affects your organization's data, we will notify your organization's owners without undue delay and no later than 72 hours after we become aware of a security incident affecting your data (an unauthorized access to it, or its loss, alteration or disclosure, whether on our systems or a subprocessor's; not unsuccessful attempts or blocked attacks), or sooner where the law requires.

Report a vulnerability

If you find a security problem in MigraInfo, tell us at security@migrainfo.com. Include what you found, where, the steps to reproduce it and how to reach you. We acknowledge reports within two business days, keep you informed while we fix the problem, and tell you when it is resolved.

In scope: migrainfo.com, app.migrainfo.com, pro.migrainfo.com, the MigraInfo apps for iOS and Android, and the servers they talk to.

Please: test only against accounts and organizations you created; stop as soon as you can demonstrate the issue, without reading, changing or keeping data that isn't yours; and don't run denial-of-service tests, send spam, or try to social-engineer our staff or anyone's clients.

We treat research done in good faith within these rules as authorized and will not pursue legal action over it. We don't run a paid bug bounty, but we're glad to credit you here if you'd like. A machine-readable version of this policy is at /.well-known/security.txt.