Pixel Mill · Cancellation Policy · v1.0 · Effective 21 July 2026
| Field | Value |
| Operator | MANAGEMENT RESILIENCE LTD |
| Company number | 15587224 |
| Registered office | 20 Wenlock Road, London, England, N1 7GU |
| Trading name / brand | Pixel Mill |
| Website | https://pixel-mill.com |
| Contact email | info@pixel-mill.com |
| Support / complaints | info@pixel-mill.com; written correspondence may also be sent to the registered office |
| Governing law | England and Wales |
| Document version | v1.0 |
| Effective date | 21 July 2026 |
| Important: Pixel Mill has no subscription or automatic renewal. Account closure is separate from order cancellation and normally extinguishes unused Tokens without creating cash value. |
1. Scope and relationship to other documents
1.1 This Cancellation Policy explains how a user may stop an uncompleted order, withdraw from an eligible distance contract, close an Account or discontinue future use of Pixel Mill.
1.2 It also explains the separate consequences for ready-made content, Generated Outputs, Token balances, licences, payment disputes and retained records. In practice, scope and relationship to other documents is assessed through the request, Account authority, payment, fulfilment, Token balance and legal right, with the result reflected in the effective closure or cancellation status and any retained obligation.
1.3 The Terms, Refund Policy, Payment Policy, Digital Product Fulfilment Policy and Privacy Policy continue to govern their respective subjects.
1.4 When applying scope and relationship to other documents, those indicators are considered together rather than relying on a single unverified assertion.
2. No subscription or automatic renewal
2.1 Pixel Mill currently sells one-off Digital Products and prepaid Token Packs and does not operate a subscription or automatic-renewal plan. The operational checkpoint for no subscription or automatic renewal is the request, Account authority, payment, fulfilment, Token balance and legal right; completion is shown by the effective closure or cancellation status and any retained obligation.
2.2 Closing an Account is therefore not required to stop a future recurring Pixel Mill charge, because no recurring instruction is created by a purchase under the current model. This treatment of no subscription or automatic renewal is traceable without expanding collection or restriction beyond what the situation requires. A future subscription feature would require separate advance disclosure and affirmative consent before any recurring billing could begin.
3. Definitions and cancellation routes
3.1 Order cancellation means stopping an order before fulfilment; statutory withdrawal means exercising an applicable cooling-off right; Account closure means ending access to the user profile and Token ledger. For definitions and cancellation routes, relevant indicators include request time, payment and fulfilment status, Account control, Token use and closure reason, and the resulting action is documented through the closure confirmation, access status, retained-entitlement decision and any refund action.
3.2 A service-retirement cancellation occurs where Pixel Mill permanently withdraws a material Service component, while termination is an enforcement action for breach or risk.
3.3 Each route has different effects and must be identified from the user request and transaction status. The definitions and cancellation routes approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy.
4. Cancelling before payment completion
4.1 A user may leave the checkout before payment submission or before authentication completes, and no Pixel Mill contract is completed unless successful status is received.
4.2 A pending authorisation may nevertheless remain visible temporarily and is ordinarily released by the issuer where capture did not occur. Implementation of cancelling before payment completion links checkout disclosure, provider status, issuer response, amount, currency and authentication result to the reconciled order, provider reference and financial-status record, so the practical consequence can be explained and reviewed.
4.3 The user should check the Account, confirmation email and issuer status before making a duplicate purchase.
4.4 No cancelling before payment completion outcome is based solely on a technical label where reliable contrary evidence is available.
5. Cancelling an unfulfilled paid order
5.1 A user should contact info@pixel-mill.com immediately where payment succeeded but the ready-made content, Token Pack or generation request has not been fulfilled. Pixel Mill verifies cancelling an unfulfilled paid order against request time, payment and fulfilment status, Account control, Token use and closure reason and records the action in the closure confirmation, access status, retained-entitlement decision and any refund action.
5.2 Pixel Mill will determine whether the order can be voided, whether fulfilment has already started and whether a correction, cancellation or refund is appropriate. The cancelling an unfulfilled paid order record supports user communication, internal control and any provider, authority or court process that lawfully follows. A captured but undelivered order will not be retained without the purchased entitlement or an appropriate reversal.
6. Consumer cooling-off rights
6.1 A Consumer may have a 14-day cancellation right for a distance contract, subject to the rules for digital content and services and any valid request for immediate performance. The practical standard for consumer cooling-off rights is tested using applicable status, user location, request details, correspondence and mandatory legal conditions; the reasoned response, escalation route and preserved statutory option then evidences the action taken.
6.2 Where the Consumer expressly requests immediate digital supply and acknowledges the resulting loss of the cancellation right, that right may end when download, access, Token crediting or generation begins.
6.3 The waiver does not remove remedies for non-supply, defects, material misdescription or other non-excludable rights. Timing, scope and any exception under consumer cooling-off rights are determined from the actual Service stage rather than a generic classification.
7. Ready-made digital content
7.1 A ready-made content order may be cancellable before access begins where the applicable cooling-off right remains available.
7.2 Once access or download begins following the required immediate-supply consent and acknowledgement, the ordinary change-of-mind right may be lost. Operational review of ready-made digital content focuses on product disclosure, source material, rights information, intended use and distribution context, after which the licence position, restriction, removal or rights-holder response confirms the result.
7.3 The content licence remains subject to the Terms and ends if the transaction is validly cancelled or refunded.
7.4 The ready-made digital content distinction prevents an Account, payment, content or rights issue from being treated as if every consequence were identical.
8. Token Packs and generation
8.1 Unused Tokens may be eligible for cancellation where performance has not begun or the statutory right has not been validly waived. For token packs and generation, Pixel Mill considers purchase record, Account identifier, Token ledger, generation deductions and reversals and uses the corrected balance, entitlement status and linked transaction history to close or escalate the matter.
8.2 Using a Token to submit a generation request constitutes performance for that Token, and completed generation ordinarily makes the consumed amount non-refundable absent failure, defect or another mandatory remedy. The token packs and generation outcome remains proportionate to severity, recurrence, user impact and the legal or contractual duty involved. A partial statutory or contractual remedy may take account of Tokens already consumed and value already supplied where law permits.
9. Voluntary Account closure
9.1 An Account holder may request closure from the registered email address and may be asked to verify control of the Account. In practice, voluntary account closure is assessed through request time, payment and fulfilment status, Account control, Token use and closure reason, with the result reflected in the closure confirmation, access status, retained-entitlement decision and any refund action.
9.2 Closure disables access to order history, generation tools, downloads and remaining Tokens after the request is completed.
9.3 The user should download lawfully retained files and resolve open support, refund or dispute matters before closure. When applying voluntary account closure, those indicators are considered together rather than relying on a single unverified assertion.
10. Effect on unused Tokens
10.1 Voluntary Account closure does not itself create a cash value or automatic refund for unused Tokens.
10.2 Remaining Tokens are extinguished when closure is completed unless a mandatory legal right or an approved refund requires a different outcome. The operational checkpoint for effect on unused tokens is purchase record, Account identifier, Token ledger, generation deductions and reversals; completion is shown by the corrected balance, entitlement status and linked transaction history.
10.3 Tokens cannot be transferred to another user, sold, redeemed or converted into a payout before closure.
10.4 This treatment of effect on unused tokens is traceable without expanding collection or restriction beyond what the situation requires.
11. Effect on licences and downloaded files
11.1 A valid licence for fully paid downloaded content may continue after ordinary Account closure where the Terms do not require ongoing access and the transaction was not reversed. For effect on licences and downloaded files, relevant indicators include product disclosure, source material, rights information, intended use and distribution context, and the resulting action is documented through the licence position, restriction, removal or rights-holder response.
11.2 Online redownload access, Token functionality and generation tools end with the Account, so the user must retain lawful local copies. The effect on licences and downloaded files approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy. A licence ends where payment is refunded, reversed or charged back, or where the content was obtained through fraud or material breach.
12. Pixel Mill suspension or termination
12.1 Pixel Mill may suspend or terminate access for payment fraud, chargeback abuse, account compromise, illegal content, intellectual-property infringement, security attacks or material repeated breach. Implementation of pixel mill suspension or termination links request time, payment and fulfilment status, Account control, Token use and closure reason to the closure confirmation, access status, retained-entitlement decision and any refund action, so the practical consequence can be explained and reviewed.
12.2 Where risk permits, Pixel Mill may give notice, request remediation or limit only the affected feature before full termination.
12.3 Immediate action may be taken where delay would expose users, rights holders, payment systems, infrastructure or legal compliance to material harm. No pixel mill suspension or termination outcome is based solely on a technical label where reliable contrary evidence is available.
13. Consequences of termination for breach
13.1 Termination for breach can disable the Account, cancel pending generation, remove access and extinguish remaining Tokens without a cash refund to the extent permitted by law.
13.2 Completed lawful purchases are assessed separately from abusive or disputed transactions, and evidence is preserved for providers, issuers, schemes, authorities or proceedings. Pixel Mill verifies consequences of termination for breach against request time, payment and fulfilment status, Account control, Token use and closure reason and records the action in the closure confirmation, access status, retained-entitlement decision and any refund action.
13.3 A termination decision does not eliminate a genuine statutory refund, privacy request or right to contest the action.
13.4 The consequences of termination for breach record supports user communication, internal control and any provider, authority or court process that lawfully follows.
14. Dormancy and inaccessible Accounts
14.1 Pixel Mill may protect a long-unused or compromised Account by requiring fresh authentication, password reset or ownership verification. The practical standard for dormancy and inaccessible accounts is tested using request time, payment and fulfilment status, Account control, Token use and closure reason; the closure confirmation, access status, retained-entitlement decision and any refund action then evidences the action taken.
14.2 Dormancy does not create recurring fees, and Tokens do not expire merely because the Account has been inactive while the Service and Account remain available. Timing, scope and any exception under dormancy and inaccessible accounts are determined from the actual Service stage rather than a generic classification. If the Service is permanently retired, the service-retirement process below applies instead of silent forfeiture.
15. Service retirement or material discontinuation
15.1 Pixel Mill may discontinue a feature for legal, security, supplier, technical or commercial reasons and will use reasonable notice where practical. Operational review of service retirement or material discontinuation focuses on request time, payment and fulfilment status, Account control, Token use and closure reason, after which the closure confirmation, access status, retained-entitlement decision and any refund action confirms the result.
15.2 For a permanent Token-generation shutdown, Pixel Mill will assess a reasonable use period, equivalent fulfilment, Token conversion into eligible Service value or a proportionate refund where required.
15.3 The treatment will consider remaining balance, purchase date, use history, legal rights and the feasibility of continued secure access. The service retirement or material discontinuation distinction prevents an Account, payment, content or rights issue from being treated as if every consequence were identical.
16. Data after closure
16.1 Account closure is not identical to immediate deletion of all personal data.
16.2 Pixel Mill may retain transaction, tax, fraud, consent, fulfilment, dispute and legal records for the periods and purposes stated in the Privacy Policy, while deleting or anonymising data no longer required. For data after closure, Pixel Mill considers request time, payment and fulfilment status, Account control, Token use and closure reason and uses the closure confirmation, access status, retained-entitlement decision and any refund action to close or escalate the matter.
16.3 A separate erasure request may be made and will be assessed under applicable data-protection law.
16.4 The data after closure outcome remains proportionate to severity, recurrence, user impact and the legal or contractual duty involved.
17. How to request cancellation or closure
17.1 The user should email info@pixel-mill.com from the Account address and state whether the request concerns an order, statutory withdrawal, Token balance or Account closure. In practice, how to request cancellation or closure is assessed through request time, payment and fulfilment status, Account control, Token use and closure reason, with the result reflected in the closure confirmation, access status, retained-entitlement decision and any refund action.
17.2 The request should include the order reference, date, amount, Account email, current fulfilment status and the requested outcome without sending full card details. When applying how to request cancellation or closure, those indicators are considered together rather than relying on a single unverified assertion. Pixel Mill may ask proportionate questions needed to prevent unauthorised closure or misdirected refunds.
18. Processing and communications
18.1 Pixel Mill aims to acknowledge a cancellation or closure request within two business days and normally provide a substantive outcome within ten business days. The operational checkpoint for processing and communications is the request, Account authority, payment, fulfilment, Token balance and legal right; completion is shown by the effective closure or cancellation status and any retained obligation.
18.2 Urgent pre-fulfilment requests are prioritised, but delivery may complete before a message is read where automated supply was requested.
18.3 The decision confirms the effective time, Account status, Token treatment, refund position, data consequences and any remaining action. This treatment of processing and communications is traceable without expanding collection or restriction beyond what the situation requires.
19. Age and authorised requests
19.1 Only users aged 18 or over may hold and close an Account, and an organisational request must come from an authorised representative.
19.2 A parent or payment-card holder reporting unauthorised use should secure the credentials and provide enough information to locate the transaction. For age and authorised requests, relevant indicators include age requirement, Account control, payment authority and any credible safeguarding information, and the resulting action is documented through the eligibility decision, protective restriction and limited disclosure record.
19.3 Pixel Mill will avoid disclosing Account information to an unverified third party while investigating the authority and payment position.
19.4 The age and authorised requests approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy.
20. Changes and governing law
20.1 Pixel Mill may update this Policy for Service, legal, provider or operational changes, but an update will not retrospectively create recurring billing or remove an accrued mandatory right. Implementation of changes and governing law links applicable status, user location, request details, correspondence and mandatory legal conditions to the reasoned response, escalation route and preserved statutory option, so the practical consequence can be explained and reviewed.
20.2 This Policy is governed by the laws of England and Wales, subject to mandatory consumer law and forum rights in the user’s country of residence. No changes and governing law outcome is based solely on a technical label where reliable contrary evidence is available. Questions or complaints may be sent to info@pixel-mill.com or in writing to the registered office.
21. Practical cancellation outcomes
21.1 A cancellation request is classified by payment status, fulfilment status, digital-supply consent, Token use, Account status and reason for termination. Pixel Mill verifies practical cancellation outcomes against request time, payment and fulfilment status, Account control, Token use and closure reason and records the action in the closure confirmation, access status, retained-entitlement decision and any refund action.
21.2 The practical outcome can be no completed order, void, refund, Token reversal, closure with extinguishment, continued licence, suspension or service-retirement remedy.
21.3 Users should retain the confirmation because the effective date determines later access and dispute evidence. The practical cancellation outcomes record supports user communication, internal control and any provider, authority or court process that lawfully follows.
Cancellation and closure outcomes matrix
| Scenario | Effect on Account | Refund position | Operational note |
| Checkout abandoned before completion | No change | No Pixel Mill refund if no capture; issuer may release a hold | Check email, Account and issuer before retrying |
| Paid order stopped before fulfilment | Account remains open unless requested otherwise | Void or refund where cancellation is available | Contact support immediately with the order reference |
| Voluntary closure with unused Tokens | Account access ends and remaining Tokens are extinguished | No automatic cash refund; mandatory rights remain | Download eligible files and resolve open cases first |
| Termination for material breach | Access may be suspended or ended | No refund for abusive use to the extent lawful | Completed lawful transactions and statutory claims are assessed separately |
| Dormant Account reactivated | Authentication or verification may be required | No refund merely due to inactivity | Tokens do not expire while Account and Service remain active |
| Permanent generation-service retirement | Generation access ends after the announced process | Use period, equivalent value or proportionate refund as required | Treatment depends on balance, purchase date and legal rights |
| Refund followed by closure | Account may close after case completion | Approved amount returns to original method | Related Tokens and licences are reversed |