Privacy and retention
Last reviewed September 15, 2026.
New conversions are processed in memory. Your serialized input is transmitted to the Unserialize server, converted, returned to your browser, and not stored in the outputs database.
Request bodies are not recorded in application logs or Nightwatch. Operational telemetry uses only the interface, outcome category, a diagnostic category, latency, and an input-size bucket—not submitted serialized values, byte offsets, or converted content.
Technical usage metadata
Separately from conversion content, Unserialize records technical metadata about how it is used: the browser or client User-Agent string, the request URL, and the referring URL, along with the interface, outcome, and timing described above. This is not anonymous data. A User-Agent, a URL, and a timestamp can describe a particular visit, and a URL you arrive from may itself carry information about you.
This metadata is stored only in Unserialize's own database. It is never sent to Google Analytics or any other third-party analytics provider, it is never exposed through a public endpoint, and it is not used to build a profile, a fingerprint, or a unique-visitor count. Credentials embedded in a URL are removed and the values of sensitive query keys such as token, api_key, and password are replaced before anything is written.
Usage metadata is deleted automatically after 30 days by a scheduled daily purge. The database is not backed up, so 30 days is the complete retention period and there is no copy that outlives it. Long-lived conversion counts are kept, but they hold only a date, an interface, an outcome, and a total.
Limits and unsupported data
Inputs are limited to 262,144 bytes. PHP objects are rejected and classes are disabled during decoding. Invalid data and values that cannot be represented as JSON return an error.
Legacy output links
Legacy output links created by an earlier version may remain available so existing links continue to work. They are excluded from search indexing and are not linked from public navigation or discovery files. Contact [email protected] about a legacy value or privacy concern.