Neon
Releases
Security & compliance
PII or large seed data inside migration file
Part of the Branching & migrations check · fix arrives as a guide
What it is
A migration file contains personal data or a large volume of seed rows inline.
Why it matters
Migrations are committed, so the data is in git history and readable by everyone with repository access — a problem under GDPR if it is personal data. Large inline seeds also make migrations slow and hard to review.
How to fix it
Move seed data to a separate script that runs outside the migration path, and generate synthetic data rather than copying production rows. Purge any personal data already in migration history.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.