Exports only after written boundaries are agreed.

Fit-check without data transfer

The initial fit-check should contain only the customer’s business contact details, confirmation that OpenAI and Anthropic exports exist, the intended 31-day period, formats, approximate combined rows and size, the diagnostic question and a plain list of fields. Do not include sample values.

No export file is needed to decide whether the request matches a supported provider-native JSON shape or the published normalized template.

Written intake arrangement

After scope confirmation and purchase, VANTYX Labs and the customer agree in writing on:

• the exact files and source owners;
• the protected transfer channel;
• the processing location and who may access the files;
• the business purpose and permitted outputs;
• the exact retention and deletion arrangement;
• how deletion or return will be confirmed where applicable.

The default supported transfer uses one customer-controlled, expiring HTTPS URL per accepted file, with one structured transfer message per file and no more than four files for the engagement. Each URL must be self-contained and require no separately emailed password, bearer token or credential; its embedded access token is removed from Agent-visible messages and kept in the protected transfer boundary. The customer revokes each URL after VANTYX Labs confirms download. Another method is used only if it is agreed and verified in writing first. No universal retention deadline is claimed before that arrangement exists.

Accepted data

Only the minimum authorized OpenAI and Anthropic billing and usage exports required for the agreed diagnostic are eligible:

• documented provider-native usage/cost JSON responses supplied as complete pages, or the published normalized schema as CSV or a JSON array with the identical keys;
• one exact shared continuous period of up to 31 days;
• one undimensioned provider-total billing row per provider in normalized mode, or contiguous native cost intervals with only exact-overlap components;
• up to 50,000 rows combined;
• up to 50 MB combined;
• only source fields needed to understand provider, model, timestamp, usage, source-supplied cost and agreed allocation labels.

Provider-native usage data may not contain an explicit dollar cost. That is accepted as a visible capability limitation and marked NOT_COMPARABLE; VANTYX Labs does not silently reprice it. OpenAI and Anthropic names identify supported export types. No affiliation with either provider is implied.

Pre-acceptance checks

Files are checked for authorization, supported source and schema, complete native pagination where applicable, period, format, readability, size, row count and prohibited content. Material exclusions, unavailable fields and limitations are recorded.

Unsafe, unauthorized, unsupported, corrupted, partial or materially incomplete inputs are rejected. Rejection does not start substantive diagnostic work.

DATA ACCEPTED

The delivery clock starts only when VANTYX Labs sends a written message containing DATA ACCEPTED. That confirmation identifies the accepted sources and any recorded exclusions.

Checkout, upload, transfer notification, partial receipt or an automated acknowledgement is not DATA ACCEPTED.

Processing boundaries

• Original accepted files remain distinct from working copies.
• Source references, record references and SHA-256 integrity hashes support lineage.
• The mapping record names the source schema, endpoint, format, mapped fields, unavailable fields and limitations.
• Only fields needed for the agreed diagnostic are processed.
• Unknown values remain unknown rather than being invented.
• Source-supplied costs are used for exact arithmetic but are not independently repriced.
• Files are not used to obtain production-account access.
• The service does not request raw prompts or customer content.
• Outputs contain only the information required for the diagnostic and its limitations.

Retention and deletion

The exact retention period and deletion or return process are agreed in writing before transfer. VANTYX Labs does not publish an arbitrary universal deadline that has not been operationally implemented.

Where the written arrangement requires deletion confirmation, that confirmation is part of the engagement record. Necessary transaction, security or legal records may be retained separately from the diagnostic export files where applicable.

Incidents and questions

If either party suspects that prohibited or unintended data was transferred, processing should stop while the scope and appropriate response are reviewed. Data-handling questions should be sent to hello@vantyxlabs.pt without attaching exports or credentials.