SpecCalc Hub
Refund / Digital Content Policy
Last updated: June 20, 2026. Legal version: v1.5.0. Read this version together with the current public product behavior, calculator limitations, digital-delivery wording, and any active payment or analytics controls visible on the site.
SpecCalc Hub currently combines launch-stage free access with a future paid digital-content model. Some pages may display a regular reference value, such as a regular USD 9 Premium PDF price, while the launch offer still allows certain public downloads without payment.
Where a page states that a launch offer is free, no payment should be assumed merely because a regular future price is visible nearby. The purpose of the launch state is product validation and content testing, not immediate automatic monetization on every flow.
If pricing, access or delivery status changes materially, the visible product copy and this policy should be updated together so that users are not left comparing an old legal page with a newer runtime flow.
Uzbekistan payment demand-test and non-automatic confirmation
Where a static Paynet link or QR is shown for Uzbekistan, it must be treated as a payment-demand test or local interest signal until a verified dynamic checkout and callback flow is fully implemented. A static payment link by itself does not automatically prove that a specific order has been received, reconciled or fulfilled.
Users should not assume that scanning a static QR, opening an external payment page or seeing a local payment label guarantees instant activation of a digital product. Real paid fulfillment requires a verified payment status and an operational delivery path.
Before real paid Uzbekistan sales are considered production-ready, the owner must separately validate the Paynet recipient, settlement path, business accounting treatment and the exact support workflow for failed or ambiguous payments.
Digital content access, refunds and delivery boundaries
Premium PDFs and similar downloadable materials are informational digital products. They are not certified engineering documents, permit packs, official project submissions or safety approvals, and they must not be purchased with that expectation.
If a digital product is provided immediately after payment and the user has already begun accessing or downloading it, refund rights may be limited where applicable law permits that limitation for immediately delivered digital content.
If the product was not delivered because of a technical failure on the service side, the user should contact legal@speccalchub.com or contact@speccalchub.com with the order context, timestamp and payment reference so the delivery failure can be investigated.
Misuse, edited reports and support handling
Refunds are not intended for cases where a report was edited, stripped of disclaimers, redistributed outside the original context, presented as certified engineering work or misused in a way that changes the nature of what was originally delivered.
A calculation disagreement, by itself, is not always proof of a defective digital product. Many pages are intentionally simplified and already explain assumptions and limitations, so support review may first ask whether the inputs, units, local rules and equipment context were interpreted correctly.
Where a chargeback, duplicate payment or ambiguous transaction appears, the support process may require enough non-sensitive transaction context to trace the event and prevent double fulfillment, but not more personal data than the situation operationally requires.
Contact and policy scope
This page should be read together with the Terms of Use, Privacy Policy and Calculator Disclaimer, because access, digital delivery, privacy limits and professional-boundary language all operate together.
Refund and delivery questions: legal@speccalchub.com. General product questions: contact@speccalchub.com. Public business country disclosure: Uzbekistan.
If the product later moves from launch-free access into a fully paid flow, the revised delivery and refund mechanics should be documented before that new monetization state is presented as normal public operation.
That documentation should identify what triggers delivery, how failed payment states are handled, which support channel owns disputed transactions, and how corrected policy text will be published so users are not comparing an outdated legal page with a newer checkout flow.