Leaving, and what you take with you
A program’s relationship with TypVault can end: new leadership, a new vendor, a program that winds down. What a departing director takes with them is the same case-level export any authorized operator can already run — not a special feature built for the occasion.
What you can pull out
Section titled “What you can pull out”A program staff, program admin, or system admin account can request a case-level export as a CSV or a JSON file. Every export needs at least one filter — a start date, a status, a category, or a priority — so a single request can’t walk out with an entire history at once.
Each role carries its own ceiling, on both size and frequency: program staff up to 1,000 rows per request and five requests an hour; program admin up to 5,000 rows and ten an hour; system admin up to 10,000 rows and twenty an hour. A request past either limit is refused.
Each row is a case: a case reference, category, status and sub-status, priority, how the tip came in, when it opened and closed, and reward status and amount. That’s the shape of “what happened to each case” a program keeps for its own history. A tip a reporter never finished submitting isn’t part of that history and isn’t in scope.
What doesn’t come with it
Section titled “What doesn’t come with it”The export leaves out the narrative and the reporter’s tip code — the query behind it never reads either column, so there’s nothing there to include.
A separate, more tightly governed path exists for a full legal-discovery production of the same case-level fields: it needs a second, different supervisor’s approval before it can run. That path is covered in Insights, reports, and data export.
Every export, either path, is written to the audit trail first — who ran it, the filters used, and how many rows — before the data is read, so the record survives even a download that never finishes.
Your program’s own database
Section titled “Your program’s own database”None of this reaches into another program’s records, because there aren’t any within reach: your program’s cases, audit trail, and encryption keys live in a database built for your program alone, not shared with any other program on TypVault.
Leaving TypVault means taking your own case history with you, not untangling it from anyone else’s.
The honest limits
Section titled “The honest limits”This describes what the export does today, not a migration service. TypVault doesn’t promise a retention window, a conversion into another system’s format, or a timeline for when a departing program’s access ends — those stay decisions for your program and whoever operates your deployment.
Related
Section titled “Related”If you’re weighing a transition and need specifics beyond this page, talk to your system admin.