Know what the purchase includes. Know where the obligation stops.
The three current paid tools are private-delivery, source-available software: Replay Input Preflight 1.0.0, Target-Blind Feature Freezer 1.0.0, and Temporal Boundary Auditor 1.1.0. This guide consolidates when delivery begins, what exact materials arrive, how the buyer verifies and retains them, which support and replacement duties apply, and which future versions or compatibility work are not included.
The product-specific clock starts only after four conditions are true.
01 / Request
Send bounded intake.
Name the purchasing individual or legal entity, billing email, intended Python version, and only the additional non-sensitive detail the selected product requests. Do not send files, data, targets, schemas, code, credentials, customer material, regulated data, or unauthorized material.
02 / Accept
Receive written acceptance.
A request is not an order. Availability is not guaranteed until KaldenFrame accepts the exact product and purchaser in writing.
03 / Complete
Resolve billing and runtime intake.
The non-sensitive billing and compatibility information required by the accepted order must be complete before the clock begins.
04 / Pay
Confirm payment.
Delivery is due within the product's stated two- or three-business-day window only after written acceptance, complete non-sensitive intake, and payment confirmation are all present.
No active web checkout or automatic order acceptance is claimed. A written order or signed agreement controls where it expressly differs from the standard public terms.
02 / Exact delivery
One commercial archive, one exact licensed version.
Each order licenses the exact product version named in the accepted order and delivered archive. Public schemas and synthetic evaluation packs do not contain the executable implementation and grant no software license.
Consolidate installation or contract-format questions.
Each standard order includes one consolidated installation or contract-format support email received within thirty calendar days after delivery. Include the exact product, version, runtime, command or interface, observed result, expected result, and a minimal non-sensitive reproduction.
Custom features, dataset review, pipeline implementation or repair, managed operation, model analysis, security audit, consulting, multiple support rounds, and an SLA are not included.
Before delivery
Written cancellation is refundable.
A buyer may cancel in writing for a full refund before delivery. If KaldenFrame cancels an accepted order before delivery, amounts paid for that canceled order are refunded.
After delivery
Corrupt or materially incomplete files have a replacement path.
Promptly provide non-sensitive order context and describe the missing or corrupt material. Feature Freezer uses a ten-business-day conforming-replacement window after prompt notice; Temporal Auditor uses a reasonable replacement time. Other post-delivery refunds are not promised by the standard terms.
05 / Future boundary
Perpetual use of delivered bytes is not perpetual update work.
Version
The delivered version is the standard entitlement.
Future versions, upgrades, maintenance releases, or subscriptions are excluded unless the accepted written order expressly adds them.
Compatibility
Current runtime statements are version-specific.
Python 3.11+ support describes each current product at its validated release boundary. Future Python, operating-system, packaging, or policy changes are not guaranteed.
Network
No updater or license-server call.
None of the three current local runtimes makes network, activation, updater, license-server, telemetry, or credential requests.
Assurance
No universal outcome follows.
Delivery, verification, and support do not establish correctness, complete leakage detection, lineage, compliance, safety, security, production readiness, or fitness.
Buyer FAQ
Six answers to settle before the order.
The visible answers exactly match the structured FAQ above. Product terms or an accepted written order control if they expressly differ.
01Does a paid software purchase include future versions?
No. The standard purchase licenses the exact product version delivered for perpetual internal use by the buyer stated in that product's terms. Future versions, upgrades, maintenance releases, compatibility work, or update subscriptions are not included unless an accepted written order says otherwise.
02Does the delivered software call an updater or license server?
No. All three current runtimes make no network requests, including updater, license-server, telemetry, or credential calls. Delivery and support use the separately disclosed email channel; the local runtime does not require an online activation check.
03How should a buyer verify the delivery?
Compare the received archive and wheel against the delivered SHA-256 checksum record before installation, then retain the archive, checksum record, license, and accepted order together. A matching hash identifies exact bytes; it is not a signature, provenance attestation, trusted timestamp, vulnerability report, or safety guarantee.
04What support is included?
Each standard software purchase includes one consolidated installation or contract-format support email received within thirty calendar days after delivery. It does not include implementation consulting, dataset review, custom features, pipeline repair, managed operation, an SLA, or indefinite maintenance.
05What if the delivered files are corrupt or materially incomplete?
Promptly notify billing with the order context and a non-sensitive description. The product terms state the applicable conforming-replacement boundary. Before delivery, written cancellation receives a full refund, and a seller cancellation before delivery is refunded. The product terms or an accepted written order control.
06What is the buyer responsible for retaining?
Keep controlled backups of the accepted order, commercial license, original delivery archive, wheel, checksum record, schemas, synthetic cases, and any replacement notice. The license permits protected backups for the named buyer, but KaldenFrame does not promise indefinite redelivery, hosted storage, public package availability, or future-runtime compatibility.
Choose the next inspection
Evaluate the product, then build a bounded request.