The essentials, clearly.

.mdSiren is a document security checkpoint for AI systems. It checks each supported incoming version, gives it an Approved, Needs review or Quarantine decision, and keeps eligible Approved copies available for people and authorised Pro integrations.

Yes. Free and Pro access are available now. Start with five Standard Scans, once per account, with no payment card required.

Approved means required supported checks completed for the exact version without a finding that blocks approval or needs review. Needs review means a finding needs attention or required coverage is missing. Quarantine keeps a version with a blocking finding out of normal reuse. Manual approval override is not available.

The scan could not complete, so no security decision was made. Retry is available and no new scan credit is consumed. A reserved credit is released on terminal failure. A failed recheck adds no new charge, but it does not refund the original completed scan. Technical failure is separate from the three document destinations.

PDF and DOCX up to 4 MiB; TXT and Markdown up to 1 MiB, subject to supported structure and complexity limits. Pro does not currently unlock larger files.

No. Documents are uploaded to your private account workspace for processing and storage. The website does not collect documents; uploads happen inside the .mdSiren application.

Projects and Collections organise document records for a client or workflow. You choose them explicitly; .mdSiren does not classify projects automatically. Pending, Approved, Needs review and Quarantine records can share a Collection, and corrected replacements inherit the document’s memberships.

No. Collection membership only organises a record. It never grants approval or retrieval. Only the current exact version can be retrieved, and only while every Approved release check still passes.

The private Library keeps eligible current Approved versions, scan records and reports available for reuse. It is separate from Projects and Collections, which can contain records in every status. Eligibility is checked again when a file is retrieved.

The corrected file becomes a replacement version and inherits the document’s Collection memberships. The earlier version stops being eligible for retrieval as soon as the replacement is accepted. The new version needs its own decision, and there is no fallback to the earlier version while it is pending or held. Both remain in version history while retained.

Approval remains bound to the inspected bytes and scan policy. A policy change can make an earlier approval stale and hold the version for a supported recheck before it is released again.

Free includes 32 MiB of retained originals and reports plus 50 retained version records. Pro includes 10 GiB and 10,000 version records. Held, historical and deletion-pending records count where applicable. Confirmed deletion releases stored bytes; version-record cleanup can take longer. .mdSiren does not promise permanent or unlimited retention.

Download the eligible current Approved exact version and add that checked file to your chosen AI workflow. The report is available separately. If the source changes, submit the replacement and wait for its own decision before using it.

A completed Standard Scan ending in Approved, Needs review or Quarantine uses one scan. A new or corrected version uses another. Rejected intake and unsuccessful new scans do not spend a completed scan credit. Eligible supported rechecks of an already charged version do not spend another credit.

No. Free and Pro use the same Standard Scan checks and decision rules. Pro buys recurring capacity and machine access, not a more favourable verdict.

Free includes five Standard Scans, once per account, the complete decision and evidence for every completed scan, a private Library, Projects, reports and eligible downloads. It includes 32 MiB of retained originals and reports and 50 retained version records. No payment card is required.

Pro is £19 per month in GBP. It includes 100 Standard Scans each paid billing month, shared by the app and API with no rollover; 10 GiB of retained originals and reports; 10,000 retained version records; and scoped API submission, status, reports, Collection manifests and eligible exact-version retrieval.

Reports and eligible retrieval do not use scan credits, but request and transfer limits still apply. Original downloads reserve their exact byte size; report reads reserve 256 KiB, and failed attempts can consume transfer allowance. Pro includes 10 GiB of paid-period download reservations shared by web and API retrieval. Reservations are not guaranteed delivered bytes.

Scan exhaustion does not by itself remove eligible retained web reports, downloads or Library organisation. Active Pro API retrieval can continue when no scan credits remain, subject to its other limits. New scans require available allowance.

Cancelling renewal normally keeps paid access active until the current entitlement ends; refunds or disputes can end it earlier. After downgrade, eligible retained web reports, downloads and Library organisation remain available within the plan limits, but API access requires active Pro.

Deep Scan is planned. Deep Scan is intended to add bounded contextual analysis to eligible findings that need closer review. It will not override a registered hard stop.

The Pro API lets authorised agents submit documents to the account Library or an authorised Project Collection, check status, read reports and retrieve eligible Approved exact versions. Access requires active Pro, a valid scoped key and the relevant permissions. Retrieval eligibility is checked again for every file request.

No. These retrieval controls apply to files supplied through .mdSiren. They cannot revoke previously downloaded copies or control files an agent obtains elsewhere. Permissions and security controls in the consuming AI system remain necessary.

Eligible retrieval returns the original Approved exact-version file bytes. It does not return extracted text or a rewritten document. Status, Collection manifests and machine-readable reports are separate API responses, and each action requires its corresponding scope.