Refund and Cancellation Policy
Rules for subscription cancellation, refunds of plan payments and already completed one-off charges, and handling incorrect charges at SacredGPT.
1. Scope
This policy applies to Chat and Hermes plan payments. Standalone window-restoration purchases and one-off balance top-ups are no longer sold; already completed payments of that kind can still be refunded under the rules below. Current prices are published on the pricing page. Payments are processed through Platega; SacredGPT does not receive the user’s bank card details.
This policy supplements the Terms of Service and does not limit rights granted to the user by applicable law.
2. Request Reservations Are Not Payment Refunds
Before a model request, window volume may be reserved. After completion, actual usage is counted and unused reservation returns to the window automatically. If a request fails without countable usage, the full reservation is released. No payment refund request is required.
If a reservation is not released or a charge appears incorrect, the user may contact support for a review of the usage ledger.
3. Subscription Cancellation
Auto-renewal may be cancelled at any time from the billing page in the account dashboard or through support. After cancellation, no new payment is created, while the paid plan and its windows stay active until the current period ends. Unused window volume does not roll over.
Cancelling auto-renewal does not itself create a refund request for a completed payment.
4. Plan Payment Refunds
A user may request cancellation of a paid service and a refund as provided by applicable law. If the plan windows from that payment remain entirely unused and Platega supports transaction cancellation, SacredGPT may process a full refund after verification.
If any of the windows have been used, an automatic pro-rata refund is not technically available. Support reviews the request individually and determines the amount with regard to services actually supplied, documented expenses, and mandatory legal requirements.
5. Window Restoration and Legacy One-Off Payments
The same process applies to Heretic window-restoration purchases. A full automated refund is possible when the restoration has not yet been applied to usage and the payment provider supports cancellation. Requests involving partial application are reviewed manually.
One-off balance top-ups are no longer sold. Requests about older one-off payments and unused leftovers are reviewed individually; converting those funds into a subscription does not create a separate on-site wallet.
6. Incorrect Charges and Service Defects
If a duplicate payment, charge without confirmed usage, pricing error, or technical service defect occurs, the user may request a review and correction. SacredGPT checks the payment status, quota ledger, and model provider records; a confirmed error is corrected by restoring window volume, releasing a reservation, or refunding the payment as appropriate.
7. How to Submit a Request
Open a request through the ticket system or email support@sacredgpt.pro. Include the account email, payment date, amount, method, transaction identifier, and reason for the request. Do not send a full card number, CVC/CVV, API keys, backup codes, or 2FA codes.
8. Refund Method and Timing
An approved refund is sent through Platega to the original payment method when technically available. Settlement timing depends on the payment provider and the user’s bank; SacredGPT reports the status after receiving confirmation from Platega. If automated cancellation is unavailable, support will offer a resolution permitted by law.
9. Disputes and Chargebacks
Before disputing a payment through a bank, users are encouraged to contact support so that a delayed status or technical error can be ruled out. When a chargeback is received, SacredGPT may temporarily restrict associated paid features until review is complete, without limiting mandatory user rights.
10. Changes to This Policy
A new version is published on this permanent page with its revision date and applies to requests submitted after publication unless the law or the policy itself requires otherwise.
Found a bug? Show us.
Tell us what happened and what you expected. The page address and browser details help us reproduce it faster.
