Data retention and deletion
This page describes what actually happens to what you paste.
It is written to match the implementation, and when either changes, both change together, versioned and dated.
Two kinds of records, different rules on purpose
Imbas keeps two fundamentally different kinds of data. The public measurement record, published cases and protocol captures, is built to persist: that permanence is the point of the instrument, and it is governed by the continuity pledge, not this page. Reader product data, the questions and answers you paste into the Reader, is telemetry. It is not the public record, and it does not inherit the record’s permanence doctrine. This page governs the second kind.
Reader runs
When you run an inspection, Imbas stores the question, the pasted answer verbatim, the inspection output, content hashes, and version metadata. Run content is retained while the Reader program operates under this v1 policy, and deleted on request. This is stated as v1 operational doctrine, not permanence: as institutional use grows, tiered retention of raw text is the expected evolution of this policy, and that change will arrive as a dated version of this page, never silently.
Retention is not consent. Calibration use, candidate-case retention, and any publication each require your own explicit action, recorded as per-record state; nothing is implied by running an inspection. Where a feature offering that action has not shipped yet, the use simply does not happen.
Shares
Share pages are unlisted, excluded from search indexing, and permanent by design: a receipt that rots undercuts the reason receipts exist. Anyone holding the link can view it; the link preview never includes answer text. If you created a share and want it gone, that is a deletion request and it is honored. If you are a third party asking that a published record be removed or altered because it concerns you, that is a different thing: it routes through the alteration-request rule on the independence page and is logged there.
What deletion means
A deletion request removes, from Imbas-controlled storage: the run row, any paired analysis derived from it, any share record you created from it, the stored raw text, derived inspection content, and any candidate-lead copy that retained your text. Deleting the obvious row while copies persist elsewhere would be deletion in name only, so the closure set is defined and the internal procedure walks it.
One honest boundary: receipts you downloaded and copies on other people’s machines are yours and theirs; Imbas can delete what Imbas holds, not what has already traveled.
How to request deletion
Email brendan@imbaslabs.com with enough to identify the record: the share ID, or the approximate time and question of the run. Requests are fulfilled manually, by a person, within 7 days. There is no self-serve deletion today; when that changes, this page changes.