Who Owns Your Data? Export and Exit Questions for Traffic Control Software

Software conversations in this trade are about features: does it dispatch, does it track devices, does it bill. Almost nobody asks the question that matters most three years later, which is what happens to everything you put in it.

For a traffic control company that question is not academic. Your daily tickets are the evidence that the setup existed, that the customer signed for it, that a crew was on site at a given hour. If an agency audits a job, a prime disputes an invoice, or an attorney asks what was on the road the night of a crash, the answer lives in that system — and it may need to live there long after you have stopped using it.

This is a practical checklist for the contract conversation, not legal advice.

Start with the clause, not the salesperson

Vendor agreements usually address ownership explicitly. Look for three things:

A statement that you own your data. Most reasonable agreements say the customer retains ownership of customer data and grants the vendor a licence to host and process it in order to provide the service. If an agreement is silent on ownership, that silence is the finding.

What the vendor may do with it. Delivering the service is uncontroversial. Aggregated or de-identified analytics may be fine. What you want to know is whether customer names, job sites, rates or pricing are inside that permission.

What happens at the end. Termination clauses are where the money is. How long can you access the account after you stop paying? How long is export available? What notice do you get before deletion? What happens if the vendor terminates you rather than the other way round?

Export is the whole ballgame

A vendor can be scrupulous about ownership and still leave you stranded if the export is unusable. "You own your data" and "you can get your data in a form you can use" are different promises.

Ask for a sample export during evaluation — not a description of one. Look for:

• Jobs and tickets, with the fields you rely on, as CSV or similar.
• Signatures — as part of a PDF ticket, not as a database ID pointing at an image you cannot retrieve.
• Photos, as original files with the job and date identifiable from the filename or an accompanying index.
• Time records — who clocked in where and when.
• Customers and rate sheets, because rebuilding those by hand is weeks of work.
• Invoices, ideally as both data and rendered PDFs.
• Device history — what was deployed where, and when it came back.

Then open the sample. A CSV that loses the link between a ticket and its photos has technically exported everything and practically exported nothing.

Why the retention period is longer than you think

Records in this trade have three separate clocks on them.

Tax and accounting. The IRS's guidance on how long to keep records is the baseline for the financial side, and it varies by the type of record.

Employment and safety. OSHA's recordkeeping requirements set their own retention for injury and illness records, and certified payroll on public work brings its own obligations — certified payroll for traffic control contractors covers that.

Contract and claims. Contracts routinely require records to be retained and available for audit for a stated number of years, and the limitation period for a claim arising from a job can be longer than your software subscription.

If your ticket evidence is held only in a platform whose grace period is thirty days after non-payment, then a lapsed card and a missed email could remove your ability to answer a claim about a job from three years ago. That is the risk in one sentence.

Keep your own copies

The cheapest fix is a routine: export quarterly, store it somewhere you control, and check once a year that you can still open last year's export. It is not glamorous and it takes an hour.

Practical guidance:

• Export after each quarter closes, so the export matches a closed accounting period.
• Store it where more than one person in the company can reach it.
• Keep the rendered documents — signed ticket PDFs and photos — not just the data rows.
• Note the export date and what it contains in the folder, so a future reader knows what they have.

The same routine protects you against a less dramatic scenario than a vendor failure: your own migration to a different platform two years from now.

Access control is part of ownership

Who inside your company can see and export what is a related question that gets ignored until there is a reason to care. Worth settling early:

• Can a crew member see customer pricing? Usually they should not.
• Can a dispatcher delete a ticket, or only amend it with a trail?
• Is there an audit trail on edits to tickets and time records? An after-the-fact change with no record is a problem in a dispute.
• What happens to an account when someone leaves?

The National Institute of Standards and Technology's Cybersecurity Framework is a reasonable structure for thinking about this if you want one, but the traffic control version is simpler: the ticket record is evidence, so it should behave like evidence — amendable with a trail, not silently rewritable.

Questions to ask before signing

1. Who owns customer data under this agreement, and which clause says so?
2. What rights does the vendor have to use it, including aggregated or de-identified use?
3. Can I export jobs, tickets, signatures, photos, time records, customers, rate sheets, invoices and device history — and may I see a sample export now?
4. What formats, and are documents included as files?
5. After termination or non-payment, how long is the account readable, how long is export available, and when is data deleted?
6. What notice is given before deletion, and to which contact?
7. Is there an API or scheduled export so backups can be automated?
8. What is the data retention policy for photos specifically — are they stored at full resolution, and for how long?
9. Where is the data hosted, and who else can access it?
10. If the vendor is acquired or ceases operating, what happens?

A vendor who answers these quickly and in writing is telling you something useful about how they operate. So is one who does not.

The cost side

Two commercial points worth folding into the same conversation, because they affect whether you can keep the system in every truck where the records get created:

Per-user pricing. Charging by seat makes it expensive to put the app in the hands of every crew member — which is where tickets, photos and time records are captured. Per-user vs flat-tier pricing covers the arithmetic, and traffic control software total cost of ownership covers what else shows up on the bill.

Migration cost. The practical cost of leaving a platform is rebuilding rate sheets and customers, not exporting rows. Good exports lower it; nothing eliminates it. Migrating off spreadsheets covers the same work in the other direction.

Traffic OS charges flat monthly tiers — $499, $949 and $1,499 as of September 2026, with no per-user charge, so the app belongs in every truck — and keeps tickets, signatures, photos and device history against the job where they can be exported. The pricing page and features page have the detail; a walkthrough is the place to ask the export questions above and see the answers on screen.

Nothing in this post is legal advice. Ownership, retention and audit obligations vary by contract, state and the type of record — have your own agreement and your record retention schedule reviewed by a qualified adviser.