Court and citation data in integrations: handle with care
Citations, court dates and case records are useful to share, and easy to share wrongly. Cautions for integrations that touch them: sealed records, juveniles, identifiers, open data and what to log.
Citation and court data travels further than most people expect. A parking citation might move from a handheld device to the citation system, then to a payment portal, a collections vendor, the court, and an open data dashboard. A code enforcement case can end up in an administrative hearing system and then the county court.
Each of those moves is reasonable. Each is also a place where data can go somewhere it shouldn't. This post lists the cautions worth building into any integration that touches citations or court records. It is general guidance; your city attorney, court clerk and state law decide the specifics.
Know what kind of data it is
Not all citation data is equally sensitive.
| Data | Typical sensitivity |
|---|---|
| Parking citations | Low to moderate; plate numbers can still identify people |
| Code enforcement cases | Moderate; addresses and complainant details |
| Traffic and criminal citations | Higher; names, birth dates, license numbers |
| Court case records | Varies; some are sealed, confidential or restricted |
Some of this may also be criminal justice information, which brings its own security rules. Ask your CJIS contact if you're unsure.
Sealed, expunged and confidential records
Courts seal or expunge records, and certain case types are confidential by law. The integration doesn't know that unless it is told.
- Find out which fields mark a record as sealed, confidential or restricted in the source system.
- Filter those records out of any flow that doesn't need them, before any other step.
- Make sure that when a record becomes sealed later, downstream copies are updated or removed according to your rules.
The last point is the hardest. A sealed record that still sits in a dashboard or a vendor's system is a real problem.
Juveniles
Records involving minors usually have stricter rules. Filter them out of anything public, and think carefully before sending them to any outside vendor at all.
Identifiers
Driver's license numbers, birth dates and Social Security numbers turn up in citation records more often than they should.
- Send only what the destination needs. A payment portal needs a citation number and amount, not a birth date.
- Mask or remove sensitive identifiers before delivery.
- Tokenize when two systems need to match records without seeing the real value.
Open data and dashboards
Citation counts by area or type can be valuable public information. Publishing individual records needs much more care.
- Prefer counts and summaries to row-level data.
- Remove names, plates, license numbers and exact addresses from anything public.
- Watch for small numbers that make individuals identifiable, such as one citation of a rare type on one street.
- Review the dataset with your attorney before the first publication.
Collections and outside vendors
When unpaid citations go to a collections agency or another vendor:
- Check the contract covers how they protect, use and destroy the data.
- Send the minimum fields the contract requires.
- Make sure records that are paid, dismissed or sealed are recalled or updated promptly.
Logging
Integration logs are another place court data can collect without anyone noticing. Keep record contents out of them. Log citation or case IDs, counts and outcomes, and mask personal details in error messages. That keeps logs useful for tracing problems without creating a second set of records to protect.
Questions to ask before building
- Which records in this flow could be sealed, confidential or involve minors? How are they marked?
- Does the destination need each field we are sending?
- What happens downstream when a record is sealed, dismissed or paid?
- Who else receives this data after the destination, and under what agreement?
- What does the integration log, and for how long?
In SentraBridge
In SentraBridge, filters and rules can drop sealed, confidential or juvenile records before any other step, and the Protect fields step masks, removes, tokenizes or encrypts identifiers inside the flow. Only mapped fields reach the destination. Records pass through in memory, and run history keeps IDs and counts with personal details masked. See security and rules.