close
Privacy and data handling

Keep the useful signal; minimize the personal data.

The reference implementation stores operational request records to provide resolution and revision status. It also records privacy-minimized demand telemetry so the project can tell whether agents are actually using the protocol.

Telemetry

Demand telemetry records coarse capability use, readiness grade, process/material categories, and a salted truncated caller hash. It does not store raw IP addresses, contact details, or requirement text in the telemetry table.

After the predeclared public-entry cohort reaches a terminal review boundary, the Invention Commons Protocol may preserve one digest-bound settlement containing only aggregate cohort, completed-window, and first-review counts plus the frozen decision. The settlement contains no caller fingerprint, IP address, user agent, request content, file reference, contact detail, or event row. It survives later telemetry retention changes, but it does not establish causal attribution, human demand, purchase intent, a quote, an order, or a physical outcome.

The operator screening log records only the decision time, verdict, stage, closed categories, match count, policy version, closed source class, and—when available—a bounded request ID. New records retain no purpose, request excerpt, or exact matched text and expire after 30 days. Each write is an independent prefix-discoverable entry rather than an update to one shared mutable index, so concurrent successful writes cannot silently overwrite one index reference. Prefix reads are eventually consistent and the operator response says so. Reads are capped at 200 entries and disclose the limit, returned count, lower-bound discovered-key count, completeness, truncation, and that category and verdict counts cover only the returned window. The operator API suppresses content fields from any legacy record in that window and never presents a truncated legacy-content count as exhaustive; legacy storage is not silently rewritten or deleted without a separately authorized cleanup.

The screening log has a separate content-free integrity marker. If an audit write is lost, the marker records only a lower-bound count, closed failure classifications, and the last-failure time; it contains no request, purpose, excerpt, category, match, request ID, identity, or error text. Screening outcomes remain independent of audit-storage availability, but the operator view must report the trail as incomplete rather than silently presenting partial evidence as complete.

Deferred quote jobs retain the submitted requirement, temporary design-file reference, salted caller fingerprint, and job state in bounded operational storage for up to 24 hours so the accepted job can be settled and polled. A separate transactional execution-claim record retains only a random quote-job identifier, random claim token, closed execution state and reason, and timestamps for up to 48 hours. That claim record contains no request content, file, caller fingerprint, provider response, price, contact detail, credential, order, or payment. It exists only to prevent concurrent or interrupted executors from repeating external work; provider contact remains inactive in this release.

Supplier-package rejections add only a closed reason suffix to that existing event. For missing-purpose rejections observed after the v1.83.0 boundary, one closed input-shape label distinguishes empty arguments, a malformed purpose, a common wrapper, or other structure without retaining field names or values. Rejected events clear process, material, quantity, geometry, and CAD dimensions before storage; no requirement, package, gap text, file, delivery route, or accountable principal enters the event. Earlier pre-contract rejection shapes are not reconstructed or guessed.

Resolution-report delivery telemetry records only the transport and one closed outcome: pending machine draft, expired generation, machine draft returned, operator-published report returned, invalid request ID, or unknown request. Marked probes are excluded. The aggregate exposes no request ID, report, purpose, specification, caller identifier, contact field, supplier, quote, order, payment, or physical outcome. A returned state does not prove a person read the report, found it useful or correct, or took any downstream action.

Supplier-email artifact telemetry records only whether the local draft rendered or a closed rejection reason, its channel, the existing salted caller hash, coarse client family, and any screening verdict. It does not retain the requirement, envelope, recipient, subject, message, digest, design file, or accountable principal. Marked conformance probes are excluded, and a rendered result still means only an unsent local draft.

The operator-only first-supplier-pilot ledger is separate from public demand telemetry. It stores only a closed supplier alias, closed lifecycle event, timestamps, and—when applicable—an integer price, currency, price basis and scope, closed delivery-inclusion status, bounded lead-time range/day basis/start trigger, or closed correction category. It is append-only operator-attested evidence. At read time, the server associates those rows with code-owned SHA-256 hashes of the exact canonical package and STL bytes; those hashes contain no address or identity and grant no authority. The ledger stores no supplier identity, mailbox, message, reply, file, requirement content, free text, credential, order token, payment data, or personal data; recording a boundary does not cause it or grant physical authority.

The active physical-exchange ledger is also separate from public demand telemetry. It stores a registered exchange ID, closed supplier alias, closed lifecycle event, timestamps, exact artifact-binding hash, and only the structured facts needed for cart totals, captured payment totals, expected arrival, inspection counts, and a privacy-safe evidence-file hash. It stores no supplier identity, contact details, delivery address, order identifier, payment credential, message, file bytes, requirement content, or free text. Recording an observation cannot contact a supplier, submit or accept an order, charge money, start fabrication, or claim usefulness.

Request data

The first specification-exchange cohort stores each complete outside submission and return channel in a private operator database. The public response and any public aggregate contain only an opaque receipt, cohort position, closed qualification outcome, and rule—not the organization, contact route, component facts, dimensions, files, budget, or request text. Exact duplicate content reuses its original slot. Incomplete requests, submissions without permission, internal submissions, and marked probes are not stored or counted. Private content is automatically redacted after 180 days; its content-free receipt remains so an expired record cannot reopen the fixed ten-submission cohort. The submission is used only to evaluate and follow up on this exact qualification path, not sold or used to train a model without explicit permission.

Prelaunch requester-pilot research is restricted to public organization facts and published role-based contact routes. The private operator store keeps a project alias, organization domain, closed qualification signals, dated source URL, campaign state, and a keyed one-way contact digest used for duplicate and permanent-suppression checks. Research, lifecycle-event, authenticated provider-feedback, and transport-free contact-claim rows expire after 180 days; keyed opt-out, bounce, complaint, incorrect-fit, policy, and operator suppressions are permanent so an expired campaign record cannot cause repeated contact later. Provider feedback accepts only signed, campaign-bound single-recipient bounce and complaint metadata; it retains a keyed event digest, target alias, closed event type, timestamps, and campaign version, and never retrieves provider message content. Contact claims retain only a keyed operation digest, target alias, touch number, closed pre-contact or contact-intent state, timestamps, and campaign version. A contact-intent receipt is non-reclaimable but does not mean a message was sent or authorize transport. The store does not retain a recipient mailbox, personal name, subject, message body, attachment, credential, invoice, payment record, supplier, order, or design as a queryable campaign field. Draft rendering and authenticated feedback receive a published role mailbox only transiently. A reply to the dedicated pilot role mailbox may be accepted only when it is bound to an existing contact-intent claim and the sender matches that claim's keyed contact digest. The complete raw reply is encrypted before storage with a separate operator key, retained for at most 30 days, and available only through the private operator API; no reply content is stored in a queryable plaintext field. Authentication status and content-minimized receipt metadata are stored separately. Reply content is untrusted data: it cannot automatically qualify a target, infer consent, send a response, or grant commercial, transport, payment, supplier, or physical authority. Campaign transport remains absent and external contact remains unauthorized until a separately reviewed activation.

The former Manufacturing Readiness Packet pilot is retired. Any historical pilot correspondence remains an operational service record, is not entered into public demand telemetry, is not sold, and may be deleted on request subject to legal or accounting retention duties. Do not send confidential CAD or proprietary files by email.

Temporary uploaded manufacturing files are validated before storage, retained for one hour, and served with private no-store caching. Upload telemetry records only a closed result, format, and coarse size bucket—not bytes, filenames, extracted metadata, or requirement text.

prepare_domain_solutioning_case is a stateless response transformation. It includes intent, specification fields, and deterministic review evidence, but removes design-file URLs, filenames, bytes, contact fields, callback routes, and private business-context fields. The public operation does not transmit the case to deb8stack or any model. Its privacy-minimized demand event contains no requirement text or returned case.

validate_domain_solutioning_result is also stateless. It receives a caller-held case and candidate result, retains neither, and records only the closed capability outcome in ordinary privacy-minimized demand telemetry. It rejects model-created design-file references, re-screens reconstructed candidates, and returns no requirement mutation or physical authority. The operator aggregate counts only attempts, privacy-separated callers, completed local transformations, and closed rejection reasons for these two operations. It exposes no intent, specification, case digest, framework, model, candidate, dissent, evidence reference, validation plan, design file, caller identifier, or authority-bearing field.

Provider-estimate lifecycle evidence may be published under CC0 only after a fixed minimum of five unmarked admitted jobs. The public evidence contains aggregate execution counts and closed failure reasons—not caller fingerprints, job or request IDs, files, prices, prompts, or requirement content. Counts below that threshold are suppressed.

Submitted requirements and design-file references are stored in project operations infrastructure to provide the requested service. The Invention Commons Protocol does not sell that content or intentionally use identifiable request content to train models without explicit permission. Probe records expire automatically; automated retention for ordinary requests is not yet implemented.

Concierge messages may be processed by Nebius Token Factory using the selected open-weight conversational model. The request asks the provider not to store the completion (store=false), but this is not a claim that the provider retains no operational data. If that path fails, the concierge may fall back to Cloudflare Workers AI. Resolution-report drafts continue to use Cloudflare Workers AI. Attachment bytes are not included in either concierge prompt, and attachment-only chat does not send filenames. Generated text cannot mutate requirement facts; deterministic validation, review, and screening remain authoritative.

No public supplier sharing today

There is no active public provider or supplier-release path in this reference implementation. Controlled evidence paths use only the published harmless sample part. A protected draft-only step may send operator-entered delivery details directly to Slant; the Invention Commons Protocol retains only the destination region/country and redacted outcome evidence, not the delivery name, street, city, postal code, or receipt email. User requirements are not sent to suppliers through a2a2p.com today.

Who controls this data

Physical Membrane LLC (Wyoming, USA, formed 2026-08-06) is the data controller. Business address: 30 N Gould St Ste N, Sheridan, WY 82801, USA.

Deletion requests

You may ask for deletion of an operational request record by emailing hello@a2a2p.com with its request ID. Deidentified aggregate telemetry may remain because it cannot reasonably be linked back to the request.