Technology Department Pilot v1 — operating terms
This page states the Technology Department Pilot v1 operating terms version that governs your purchase. The version you accept at Checkout — recorded on your order and never altered afterward — is your controlling contract for this order, not any later edit to internal source material.
The offer: one quantity, $2,500 USD, charged once. It covers one U.S. business or legal entity, one accountable decision maker, three mapped workflows, one activated workflow, and one private tenant and repository. Third-party expenses (postage, paid advertising, premium licensed data, specialized third-party APIs, dedicated cloud or GPU infrastructure, domain registration, app-store fees, extraordinary third-party software) require your separate written approval before they're billed.
Eligibility: self-service purchase is limited to businesses in the 50 U.S. states and the District of Columbia. U.S. territories and non-U.S. buyers use the scope-conversation path instead of this checkout. You attest to business use and supply your legal business name, decision-maker name, and business street, city, state, ZIP, and country before Checkout. Your Stripe billing country and state must match that declaration; a missing, unrecognized, non-U.S., or mismatched location prevents fulfillment and enters the refund path if a charge was captured.
Capacity: at most three capacity keys may be owned at once by open reservations, paid orders awaiting kickoff, or in-progress Pilots. One account may have one active Pilot order. A Checkout reservation owns one key for 30 minutes. Only a provider-confirmed expiry or cancellation, a provider-confirmed refund, or contract-defined completion releases that key.
Kickoff: Solace contacts you by 5pm America/New_York the next business day after payment is confirmed. Kickoff is recorded only when the first working session occurs and both sides confirm scope and required access. Before kickoff, two unanswered reminders and 15 calendar days without the required prerequisites cancel the engagement and start a full refund.
Delivery: the target is a delivery notice covering all eight inclusions within 30 calendar days after kickoff. You supply access, data, and feedback within 5 calendar days of each written request; a recorded delay on your side pauses our delivery clock. After kickoff, 30 calendar days of recorded customer-caused delay lets Solace send a delay-closure notice with all completed artifacts, your repository/export, an evidence and dependency log, and a label for each inclusion (delivered or blocked, with the missing prerequisite named). Work blocked solely by that recorded delay is not automatically refundable — a material mismatch within Solace's own control still uses the remedy and refund rule below. A written extension supersedes the delay-closure date.
Review and remedy: every delivery notice — normal or delay-closure — starts a 5-weekday review window for you to report a material mismatch. Solace then has 10 weekdays to remedy it and send one replacement notice. You then have 5 more weekdays after that replacement notice to identify, with specifics, any material mismatch that still blocks acceptance of a listed inclusion. If Solace states it cannot remedy the mismatch, misses that deadline, or your timely, specific, substantiated report survives the replacement review, you receive a full refund instead of another replacement cycle. Completion is recorded only on your acceptance, an unanswered review window expiring, or the replacement review expiring — never before one of those events, and never by an administrator marking it directly.
Cancellation and refund: you may cancel for a full refund any time before kickoff is recorded. After kickoff the Pilot is nonrefundable except for the remedy-failure path above, a separate written agreement, or rights the law does not allow these terms to limit. “Full refund” means the entire captured charge, including collected tax, without deducting processor fees. Requesting it records refund_pending; only provider confirmation records refunded.
Data ownership and deletion: you own and keep the transferred repository and your customer-specific work. A never-paid reservation has no tenant, repository, or engagement working data. For other Solace-managed working data, deletion is due 30 calendar days after service closure (completion, cancellation, or remedy failure), scoped to your exact engagement, and refused if that engagement's data is owned by a newer active engagement. Firestore point-in-time recovery may retain deleted bytes for its separately observed configured window, used only for disaster recovery — this does not cover repositories, object versions, logs, or other backups. Payment, tax, fraud, security, and legal records are retained only for their required operational period, with restricted access.
Back to the Pilot →