Security and compliance

Last updated: October 2026

What this page is

The facts a client's security review asks for, in one place: where the data lives, how it is protected, who can reach it, how long it is kept, and how the platform behaves when something goes wrong. It describes the platform as it runs today and is updated when that changes. Supporting documents (data processing agreements with our providers, the list of sub-processors, our incident process) are available on request at privacy@migbirds.com.

Hosting and data residency

The application runs in Vercel's Dublin region (Ireland, EU), pinned to that one region so a request is never served from elsewhere. The database and the stored files are hosted by Supabase in Ireland (EU). Request rate limiting runs on Upstash in the EU (eu-west-1). Two kinds of processing leave the EU: AI processing by Anthropic in the United States, which a company can switch off for its own data (see AI processing), and audience measurement by Google, only for visitors who accepted analytics cookies.

Encryption and transport

Every connection to the platform uses HTTPS; plain HTTP is not served. Data is encrypted at rest by the hosting providers. Uploaded documents sit in private storage buckets and are served only through authenticated routes that re-check the viewer's rights on every download. A Content Security Policy limits where scripts, frames and images may come from, and state-changing requests are refused without a matching origin.

Authentication

Sign-in is handled by WorkOS AuthKit; Migbirds never stores a password. Two-factor authentication is available to every account and can be made mandatory for a client's users. Single sign-on with a client's own identity provider (SAML or OpenID Connect) is set up per client on request, so a client's users sign in with their corporate accounts and follow the client's own password and access policies. Sessions are cookie-bound and expire; signing out ends them. When a Migbirds administrator views the platform as another user, a banner says so and every such session is recorded in the audit trail.

Access control and traceability

Access follows two role hierarchies: platform roles for the Migbirds team and company roles (owner, admin, recruiter, viewer, internal talent) that a company's own administrators manage, including removing members and blocking a talent from the company's space. Candidates stay anonymized to a company until it accepts the marketplace agreement and the candidate advances in its process; contact details open only at the shortlist stage. The browser never talks to the database: every read and write goes through an authenticated API route, and the database refuses direct access to every table holding personal data. Sensitive actions (role changes, impersonation, exports, deletions, settings, statements, blocks) are written to an audit trail with the actor, the time and the IP address.

Data retention

Account data is kept for the life of the account. When a person asks to delete their account it is switched off at once and erased fourteen days later, or immediately on request; the reason they give, if any, is kept without their name. Operational records are deleted automatically by a daily job: email delivery events after 12 months, the email log after 24 months, AI usage records after 24 months, the audit trail after 36 months. The database provider keeps automated backups of the data. A client's postings, applications and missions are kept while the client's account exists, so the client can report on them.

Selective deletion for a client

A company's administrators can remove members from the team, delete draft postings, close and archive published ones, and block a talent from the company's space. A person's own account is erased at their request, as described above. A client can also ask Migbirds to erase the data of its former users under a rule of its own, for example the exit date plus five years; such requests are handled within thirty days and confirmed in writing.

Service levels and incidents

The platform targets a monthly availability of 99.00%, planned maintenance excepted and announced at least 48 hours ahead. Support requests reach the team through the Help Center and the chat with the Migbirds team; a request is acknowledged within one business day. A security incident affecting a client's personal data is notified to the client within 72 hours of its discovery, with what happened, what data is concerned and what was done. Access to production systems is limited to the Migbirds team and traced. Availability is measured every minute from outside the platform by an independent monitor; the live status and the uptime of the last 30 and 90 days are public on the status page.

See the live status page

AI processing

Some features call an AI model (Anthropic Claude): reading a resume into a profile, importing or improving a job description, translating it, the written match insight on an application, the ranking of a pipeline, interview kits, rejection drafts and the anonymized dossiers the Migbirds team prepares. The processing runs on Anthropic's servers in the United States; Anthropic does not use data received through its API to train its models. No decision about a person is made by the AI alone: it proposes, a person decides. A company's administrators can turn AI processing off for the company's data in Company settings; from then on none of these features runs on the company's postings or applicants, whoever asks.

Sub-processors

Vercel (application hosting, Ireland), Supabase (database and file storage, Ireland), Upstash (rate limiting, EU), WorkOS (authentication and identity), Resend (transactional email), Anthropic (AI processing, United States), 8x8 (video rooms for interviews), Slack (an internal mirror of support requests for the Migbirds team), and, only with the visitor's consent, Google (audience measurement, United States). Data processing agreements are in place with each of them.

Keeping the freelancer base current

Profiles belong to the talent who maintain them. The platform asks for what is missing or stale: reminders to import a CV, declare skills and take the behavioral assessment in the first weeks; an availability review every 45 days and at the end of each mission; a confirmation of skill levels after each check against the CV; a request for the administrative documents a client needs before a mission starts, and a reminder before each one expires. Imported profiles are checked against their own text before they appear, and the sourcing imports are enriched the same way.

Contact

For a security questionnaire, a document, or to report a vulnerability, write to privacy@migbirds.com. Vulnerabilities reported in good faith are acknowledged and handled in confidence.