A refund request is reviewed, recorded, and reconciled.

Provide your full name, an email address for the receipt, the contract or PayPal subscription reference, and the circumstances you want reviewed. A reason helps staff identify the payment but does not waive any right that can legally be exercised without one.

Do not submit a password, card number, PayPal login, recovery code, private key, Telegram bot token, medical information, or unrelated personal data. If a transaction reference is needed, use the non-secret identifier shown by PayPal or in the portal billing view.

After confirmation, the production service stores the request in PostgreSQL. It sends an email receipt to the supplied address and an operator notice to Syntax Studios. Those messages contain the request reference, name, contract reference, receipt time, and submitted reason.

If delivery to your address fails, the request remains stored and is marked confirmation pending for staff review. Delivery failure does not erase the declaration. Application error logs are designed to record the request identifier and error type rather than repeat the submitted message.

The submitted identity and request remain fixed. Staff can move the request through received, under review, approved or declined, and resolved states. The operator identity, note, timestamps, correlation identifier, and decision history are recorded so the outcome can be traced.

The request form itself does not evaluate eligibility and does not make a solely automated refund decision. An exact automated deletion period for refund and other legal-request records is not yet implemented; the approved retention schedule is a launch blocker described in the privacy policy.

An operator approval stored in the portal does not itself move money. Until the PayPal integration exposes a reliable automated subscription-sale or capture refund primitive, authorized staff executes the approved provider refund in PayPal.

The platform then tracks the resulting PayPal state from verified, deduplicated provider events. PayPal processes the payment account and refund; Syntax Studios records provider identifiers, amount, status, and timestamps but does not receive payment credentials.

A refund does not silently become an ordinary cancellation, withdrawal, account deletion, or immediate instance purge. The refund review record is separate and does not record or apply a service-end time, paid-through change, or lifecycle action. Any such action must be performed and evidenced separately.

Where service ends through the normal paid-through lifecycle, the runtime is stopped at paid-through and a validated final archive expires exactly 30 days later. At expiry, the data becomes due for deletion and the system attempts the purge. Failures are recorded and retried, so completion can occur later. Billing and legal records can remain under separately approved statutory or claims-retention rules.

Cancellation stops future renewal. Withdrawal exercises a statutory right where its requirements apply. Refund returns a payment. Reversal or chargeback is a provider-side payment event or dispute.

One event can require another action, but the service records each separately to avoid losing access, money, or data because of an ambiguous status. Use the cancellation function or withdrawal function when that is the declaration you intend.

Nothing on this page limits statutory defect remedies, repayment duties, withdrawal rights, fraud protections, payment-provider dispute rights, or other mandatory consumer law. A customer does not lose those rights by using or not using this form.

Before launch, qualified counsel must approve the commercial refund policy, statutory repayment timing, consequences of partial service performance, tax and invoice corrections, dispute handling, evidence requirements, customer communications, and the relationship between refund, cancellation, withdrawal, and data retention.