Cancel contract
Submit a cancellation declaration.
This public function works without signing in. It accepts ordinary cancellation and provides an optional reason field for extraordinary cancellation, then creates a timestamped record and receipt.
What happens
- 01
Identify the contract
Enter your name, receipt email, and the contract or PayPal subscription reference.
- 02
Choose the timing
Give an end date or leave it empty for the earliest contractually permitted date.
- 03
Review and confirm
The form shows the declaration before the final confirmation action.
- 04
Keep the receipt
The service records receipt time and reference and sends the declaration by email.
What happens to the declaration data
Production stores the name, email, contract reference, requested date, optional extraordinary-cancellation reason, receipt and delivery state, and timestamps in PostgreSQL. A configured email provider receives the receipt contents for attempted delivery to you and the Syntax Studios operator. No staff decision, operator identity, notes, or decision history are currently attached to this cancellation record.
For rate limiting, the form uses the raw IP string supplied by a trusted proxy in a process-memory bucket for up to one hour; without a trusted proxy header it uses “unknown”. An exact automated deletion period for legal-request records is not yet implemented. See the privacy policy.
What happens to service and data
Submitting this public form does not itself stop renewal, stop the runtime, or change the paid-through date. The authenticated billing flow separately verifies cancellation with PayPal. Under the normal lifecycle, a final archive expires exactly 30 days after paid-through; at expiry, its data becomes due for deletion and a purge is attempted. Failures are recorded and retried, so completion can occur later.
An extraordinary cancellation can require a different service or payment outcome, but no operator review workflow is currently connected to this form. Billing, consumer-declaration, audit, and claim records can remain under separately approved legal retention rules.
Official reference
Function designed with reference to Section 312k BGB. Before launch, qualified counsel must verify constant availability and direct accessibility, labels, required fields, durable-medium storage, immediate confirmation delivery, effective-date rules, accessibility, and the full provider execution path. The current form stores a request and attempts email delivery but has no connected operator decision queue or provider execution path, so legal compliance cannot be inferred from the UI alone.