CIRCUITPATH / PRE-LAUNCH RESERVATION
Pre-launch reservation terms
Payment status: CircuitPath currently accepts USD reservations paid via Wise and INR reservations paid via PayU, with all payments verified manually against the invoice number before confirmation. These terms describe the reservation model and the controls that apply. Live proxy access remains pre-launch. They are not a receipt, payment confirmation, refund promise, or grant of live proxy access.
1. What a reservation is
A pre-launch reservation is intended to record a customer's request for future CircuitPath bandwidth, subject to the final published terms and a server-confirmed payment. It is not a bank account, investment, security, deposit, loan, stored-value product, or guaranteed return. A reservation does not create proxy credentials, access to a provider, a fixed launch date, or a permanent individual price lock.
2. Planned pricing
The current product direction displays a pre-launch rate of $0.70 per GB and a planned post-launch standard rate of $1.40 per GB for everyone. Buying before launch does not permanently lock the $0.70 rate after launch. The authoritative source currency is USD.
The current backend is configured with a planned minimum reservation amount of $5.00. The exact minimum, maximum, fractional-GB behavior, rounding, taxes, currency conversion, and payment fees must be confirmed in the final checkout terms before a full commercial launch. The amount and GB shown to you immediately before payment must be treated as the authoritative offer for that transaction.
3. Eligibility and information
Before a payment flow is opened, CircuitPath may require verified Google Sign-In, a matching verified email, company and role information, an authorized-use description, and acceptance of the version of these terms shown at checkout. We may refuse or manually review a reservation when identity, use, amount, or payment information cannot be verified.
4. Payment confirmation
For USD reservations, the payment page is hosted by Wise; for INR reservations, it is hosted by PayU. CircuitPath does not collect card details in its own form. A browser redirect, screenshot, email, or user statement is not proof that money arrived. CircuitPath will treat a reservation as paid only after the operator verifies the payment against the invoice number on the provider (Wise or PayU) and confirms it server-side, matching the exact reservation, amount, and currency. Mismatches, duplicates, pending events, reversals, refunds, and ambiguous payments may be held for manual review. After verification, CircuitPath sends a confirmation.
5. Launch and activation
CircuitPath has no fixed launch date. If a payment is ever confirmed, any future bandwidth entitlement will become redeemable only when the service is actually available and the final service terms say it is redeemable. India egress, protocol support, residential coverage, rotation behavior, connection limits, and availability will depend on the network that is approved and launched. No access is available before launch unless CircuitPath announces a separate controlled beta.
6. Refunds, delay, and failed payments
If CircuitPath does not launch the proxy service, all paid customers are refunded automatically — no refund request is required. The final refund policy must state the launch-delay trigger, eligibility, deadlines, treatment of consumed or suspended bandwidth, taxes and payment fees, payment method, and timing. Until that final policy is published, CircuitPath must not represent that every reservation is unconditionally refundable or promise a specific refund time.
Failed, reversed, disputed, or chargebacked payments may be investigated and reconciled before any entitlement or refund status is final.
7. Entitlements, expiry, and use
Whether unused bandwidth expires, whether it can be transferred, how it is measured, how rounding works, and how suspension affects it are not finalized. A confirmed payment may create a server-side entitlement only after reconciliation; an entitlement is not live proxy access. Usage, if a proxy service launches, will be measured from server-side provider records and an immutable usage ledger rather than from a browser display.
8. Acceptable use and suspension
Any future reservation and entitlement remain subject to the Acceptable-use policy and Terms of service. CircuitPath may suspend or revoke future access for abuse, fraud, security risk, unlawful activity, or non-payment. The final terms must explain how suspension, unused entitlements, and any eligible refund are handled.
9. Records and version
CircuitPath records the reservation, consent, terms version, payment evidence, reconciliation decisions, and relevant audit events needed to operate and defend the transaction. The version displayed before a future payment must be stored with that reservation. See the Privacy notice for the categories of information and provider disclosures.
10. Release gate
Before a full commercial launch, CircuitPath must publish the legal operator and contact, final price and tax treatment, refund and chargeback process, expiry and activation rules, applicable countries and restrictions, support commitments, and a legally reviewed paid-service agreement. It must also test the Wise hosted link, signed event schema, duplicate and retry behavior, reconciliation, refunds, and customer-facing status handling. Until those gates pass, the product remains pre-launch and live proxy access remains unavailable.