Law-enforcement preservation holds — what we keep, what we surface

If your org or one of your users is the subject of a law-enforcement preservation request (subpoena, court order, agency request), Turtini supports formal preservation holds at both the org and user level.

What a preservation hold does:
• Suspends the standard purge clocks (cancellation 365-day window, soft-delete TTLs, ephemeral data trims).
• Pins all current data — Firestore documents, Storage files, integration audit logs — at the moment the hold is placed.
• Records the requesting agency, the case reference, the issuing officer, and the hold start date in the org's lawEnforcementHold field (or the user's equivalent).

What we surface to the held org / user:
• The fact that a hold is in place, but not the agency name, case reference, or scope. The hold-acknowledgement screen says: "A legal preservation hold has been placed on this account. Contact support if you need information about your account."
• If the requesting agency requires non-disclosure (a 2703(d) gag, an NSL, etc.) we follow that order — the held party may see no notification at all until the order is lifted.

What we surface to law enforcement:
• On receipt of a properly-served preservation request, our legal team confirms the scope and applies the hold.
• Subsequent compulsion (search warrant, court order) is handled by our legal team in line with the request and applicable law. We do not voluntarily produce data without a court order or equivalent legal process.
• Our standard reference — including how to serve process — is at turtini.com/legal/le-guide (or the linked Law Enforcement page). The page lists the registered agent, the production format, and the cost-recovery schedule for non-trivial productions.

If you believe an account is being unlawfully held:
Contact our legal team via [email protected] with "Hold dispute" in the subject. We forward to outside counsel and work the dispute through the issuing agency or court.

This article is visible to government and law-enforcement orgs and to Turtini platform admins. It is intentionally not visible to commercial orgs — it's not the kind of thing they need to see day-to-day.