Pixel Mill · Digital Product Fulfilment 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 supplies digital files and Account-based Tokens only. Successful orders are normally delivered immediately or within several minutes; a payment, fraud or technical review may extend fulfilment up to 24 hours. |
1. Scope and purpose
1.1 This Digital Product Fulfilment Policy explains how Pixel Mill delivers ready-made image files, credits Token Packs and makes Generated Outputs available after a successful one-off payment.
1.2 It covers normal timing, completion points, user-side prerequisites, manual review, evidence, failed delivery and support. In practice, scope and purpose is assessed through the payment, order, entitlement, Token ledger, output and access records, with the result reflected in the confirmed delivery state and corrective action.
1.3 No physical goods are shipped and no postal delivery or tracking number applies.
1.4 When applying scope and purpose, those indicators are considered together rather than relying on a single unverified assertion.
2. Digital Products covered
2.1 Ready-made content consists of downloadable artificial-intelligence-generated photographs or visual bundles selected from the catalogue. The operational checkpoint for digital products covered is the payment, order, entitlement, Token ledger, output and access records; completion is shown by the confirmed delivery state and corrective action.
2.2 A Token Pack is a prepaid contractual balance used only for eligible generation requests, while a Generated Output is the digital file produced after a valid prompt and Token deduction. This treatment of digital products covered is traceable without expanding collection or restriction beyond what the situation requires. The order confirmation identifies the purchased product, quantity, licence, amount, currency and applicable supply route.
3. Payment prerequisite
3.1 Fulfilment begins after Pixel Mill receives successful payment status from the secure checkout provider. For payment prerequisite, relevant indicators include checkout disclosure, provider status, issuer response, amount, currency and authentication result, and the resulting action is documented through the reconciled order, provider reference and financial-status record.
3.2 An authorisation, challenge or pending bank entry does not by itself establish that Pixel Mill captured payment or created an entitlement.
3.3 Where payment later reverses, the related access, Tokens and licences may be suspended or withdrawn. The payment prerequisite approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy.
4. When fulfilment is complete
4.1 Ready-made content is fulfilled when the paid download entitlement or file link is made available in the Account or valid order email.
4.2 A Token Pack is fulfilled when the purchased Token quantity is posted to the correct Account ledger and visible or usable. Implementation of when fulfilment is complete links payment status, entitlement creation, file or output availability, email events and user troubleshooting to the release, redelivery, restoration, service notice or refund outcome, so the practical consequence can be explained and reviewed.
4.3 A Generated Output is fulfilled when processing completes and the output is available through the Account or download interface.
4.4 No when fulfilment is complete outcome is based solely on a technical label where reliable contrary evidence is available.
Fulfilment scenarios and evidence matrix
| Scenario | Typical treatment | Likely evidence | Next step |
| Ready-made file delivered | Entitlement or link created immediately after successful payment | Order confirmation, Account entitlement, email and access event | Download and retain a lawful local copy |
| Token Pack delivered | Purchased quantity posted to the Account ledger | Provider success, order record and Token ledger entry | Refresh Account; do not repurchase while status is checked |
| Generation succeeds | Tokens deducted and output made available | Prompt event, model job status, output identifier and access event | Review and download the output |
| Generation fails technically | Applicable Tokens restored automatically or manually | Failed job status, error event and Token ledger correction | Retry after restoration or contact support |
| Payment captured but no entitlement | Order reconciled and released, redelivered, voided or refunded | Provider capture, missing entitlement, email and support record | Report with order reference and observed status |
| Order held for review | Fulfilment released after proportionate verification | Authentication, provider and risk-review result | Respond only through the secure support route |
| User-side email or browser issue | Recovery or redelivery after entitlement is confirmed | Valid order plus failed email, session or compatibility evidence | Complete troubleshooting and request a fresh access route |
5. Normal delivery timing
5.1 Successful ready-made content and Token Pack orders are normally fulfilled immediately or within several minutes. Pixel Mill verifies normal delivery timing against payment status, entitlement creation, file or output availability, email events and user troubleshooting and records the action in the release, redelivery, restoration, service notice or refund outcome.
5.2 Generation timing depends on prompt complexity, queue, model availability, safety checks and technical load and is complete only when the file is accessible. The normal delivery timing record supports user communication, internal control and any provider, authority or court process that lawfully follows. Payment, fraud, sanctions, security or technical review may extend delivery up to 24 hours.
6. Account and email prerequisites
6.1 The user must provide a valid email, maintain access to the Account and ensure that the order is placed while signed into the intended profile. The practical standard for account and email prerequisites is tested using registration data, authentication events, authority, session history and recovery evidence; the verified Account status, access restriction or recovery confirmation then evidences the action taken.
6.2 The user should verify the address, check spam or filtered folders, refresh the entitlement page and use the latest supported browser before reporting non-delivery.
6.3 Pixel Mill is not responsible for delay caused solely by an incorrect address, full mailbox, blocked messages, lost credentials or use of the wrong Account, but will provide reasonable recovery support. Timing, scope and any exception under account and email prerequisites are determined from the actual Service stage rather than a generic classification.
7. Ready-made content delivery
7.1 The catalogue page identifies the file or bundle and material format, resolution, quantity or licence features before purchase.
7.2 After payment, the user receives an Account download control, order link or both, and should store a secure local copy where the licence permits. Operational review of ready-made content delivery 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 Temporary link expiry or later Account closure does not convert a properly delivered file into non-delivery, although reasonable redelivery may be offered where records confirm entitlement.
7.4 The ready-made content delivery distinction prevents an Account, payment, content or rights issue from being treated as if every consequence were identical.
8. Token Pack crediting
8.1 Purchased Tokens are credited only to the Account associated with the checkout and cannot be withdrawn, transferred, resold or redeemed for cash. For token pack crediting, 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 The ledger records purchase, promotional credit, generation deduction, restoration, refund reversal and administrative correction. The token pack crediting outcome remains proportionate to severity, recurrence, user impact and the legal or contractual duty involved. A visible balance discrepancy is reviewed against the order and ledger rather than resolved through a second purchase.
9. Generation request fulfilment
9.1 A generation request begins when the user submits an eligible prompt and any permitted input, and the stated Token cost is accepted. In practice, generation request fulfilment is assessed through prompt event, permitted inputs, processing status, safety result, Token deduction and output availability, with the result reflected in the output record, Token outcome and any moderation or support action.
9.2 A completed request provides an output that may not be unique, may resemble outputs provided to others and may require user review for suitability, accuracy and rights.
9.3 A failed request caused by Pixel Mill or its processing chain should not permanently consume the applicable Tokens and may result in automatic or manual restoration. When applying generation request fulfilment, those indicators are considered together rather than relying on a single unverified assertion.
10. Safety review and refused generation
10.1 Prompts or uploads may be screened for illegal, abusive, infringing, exploitative or technically harmful content under the Acceptable Use Policy.
10.2 A prohibited request may be blocked and may not qualify as successful fulfilment, while deliberate repeated abuse can lead to suspension or termination. The operational checkpoint for safety review and refused generation is prompt event, permitted inputs, processing status, safety result, Token deduction and output availability; completion is shown by the output record, Token outcome and any moderation or support action.
10.3 Token treatment depends on whether material processing occurred, the disclosed generation rule and any mandatory consumer remedy.
10.4 This treatment of safety review and refused generation is traceable without expanding collection or restriction beyond what the situation requires.
11. Manual payment or fraud review
11.1 An order may be held where provider status, authentication, descriptor, geography, velocity, account history or other signals require proportionate verification. For manual payment or fraud review, relevant indicators include checkout disclosure, provider status, issuer response, amount, currency and authentication result, and the resulting action is documented through the reconciled order, provider reference and financial-status record.
11.2 Pixel Mill may request confirmation of Account control or limited transaction details but will not request a full card number or security code by email. The manual payment or fraud review approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy. A legitimate order is released or corrected as soon as review is complete, normally within the 24-hour review ceiling.
12. Delayed, pending or failed delivery
12.1 A user should first determine whether payment is pending, declined, captured or confirmed and whether the entitlement appears in another Account or filtered email. Implementation of delayed, pending or failed delivery links payment status, entitlement creation, file or output availability, email events and user troubleshooting to the release, redelivery, restoration, service notice or refund outcome, so the practical consequence can be explained and reviewed.
12.2 Pixel Mill will reconcile the provider reference, order, entitlement ledger, generation event, email event and access logs.
12.3 The remedy may be release, re-credit, re-generation, redelivery, void or refund, and captured funds are not retained without the purchased entitlement or appropriate correction. No delayed, pending or failed delivery outcome is based solely on a technical label where reliable contrary evidence is available.
13. Duplicate orders and repeated attempts
13.1 Rapid checkout retries can produce multiple approved orders even where an earlier page appeared unresponsive.
13.2 The user should not repurchase until the Account, email and issuer status have been checked. Pixel Mill verifies duplicate orders and repeated attempts against the payment, order, entitlement, Token ledger, output and access records and records the action in the confirmed delivery state and corrective action.
13.3 A verified duplicate is handled under the Refund Policy and any corresponding duplicate Tokens or licences are reversed.
13.4 The duplicate orders and repeated attempts record supports user communication, internal control and any provider, authority or court process that lawfully follows.
14. Incorrect Account or user error
14.1 Pixel Mill will use reasonable measures to locate an order credited to the wrong Account controlled by the same verified person. The practical standard for incorrect account or user error is tested using registration data, authentication events, authority, session history and recovery evidence; the verified Account status, access restriction or recovery confirmation then evidences the action taken.
14.2 Transfers between unrelated users are not supported and cannot be used to trade Tokens or conceal a payment source. Timing, scope and any exception under incorrect account or user error are determined from the actual Service stage rather than a generic classification. Where a user submits an unsuitable prompt, downloads the wrong selected product or fails to save a delivered file, the contractual and statutory remedy depends on the actual disclosure, performance and defect position.
15. Evidence of fulfilment
15.1 Pixel Mill may retain provider identifiers, masked method data, order confirmation, consent records, Account identifiers, Token ledger entries, prompt and output event metadata, file availability, email events, timestamps, device signals and support communications. Operational review of evidence of fulfilment focuses on payment status, entitlement creation, file or output availability, email events and user troubleshooting, after which the release, redelivery, restoration, service notice or refund outcome confirms the result.
15.2 These records are used for customer support, accounting, fraud prevention, refunds and payment disputes in accordance with the Privacy Policy.
15.3 A record is assessed in context and is not treated as conclusive where credible contrary evidence shows a technical or security failure. The evidence of fulfilment distinction prevents an Account, payment, content or rights issue from being treated as if every consequence were identical.
16. Downloads, compatibility and storage
16.1 Users are responsible for a compatible device, supported browser, sufficient local storage and software capable of opening the disclosed file format.
16.2 A product is not defective merely because the user’s undisclosed environment cannot open a standard stated format, but a materially misdescribed or corrupt file will be corrected. For downloads, compatibility and storage, Pixel Mill considers age requirement, Account control, payment authority and any credible safeguarding information and uses the eligibility decision, protective restriction and limited disclosure record to close or escalate the matter.
16.3 Pixel Mill does not guarantee indefinite cloud storage and users should maintain lawful backups after delivery.
16.4 The downloads, compatibility and storage outcome remains proportionate to severity, recurrence, user impact and the legal or contractual duty involved.
17. Maintenance, outages and external events
17.1 Scheduled maintenance, hosting incidents, model-provider outages, network failure, cyberattack or legal restrictions may delay digital supply. In practice, maintenance, outages and external events is assessed through age requirement, Account control, payment authority and any credible safeguarding information, with the result reflected in the eligibility decision, protective restriction and limited disclosure record.
17.2 Pixel Mill uses reasonable continuity and recovery measures and will communicate material prolonged interruption where practical. When applying maintenance, outages and external events, those indicators are considered together rather than relying on a single unverified assertion. External cause does not remove the obligation to correct a captured but undelivered order or preserve mandatory consumer rights.
18. Refunds, cancellation and chargebacks
18.1 Non-delivery, defective content, failed generation, duplicate payment and unauthorised use are assessed under the Refund Policy. The operational checkpoint for refunds, cancellation and chargebacks is order status, payment capture, fulfilment evidence and the remedy already supplied; completion is shown by the case decision, payment instruction and corresponding Token or licence adjustment.
18.2 Cooling-off and Account-closure consequences are described in the Cancellation Policy.
18.3 An active chargeback may pause a parallel merchant refund to prevent double reimbursement while essential delivery and dispute records are preserved. This treatment of refunds, cancellation and chargebacks is traceable without expanding collection or restriction beyond what the situation requires.
19. Support and escalation
19.1 A non-delivery report should be sent to info@pixel-mill.com with the Account email, order reference, date, product, amount, payment status, observed error and troubleshooting already completed.
19.2 Users should include a relevant screenshot where safe, but must not send full card credentials, passwords or unrelated identity documents. For support and escalation, relevant indicators include the payment, order, entitlement, Token ledger, output and access records, and the resulting action is documented through the confirmed delivery state and corrective action.
19.3 Pixel Mill aims to acknowledge the report within two business days and normally decide the corrective action within ten business days, with urgent access incidents prioritised.
19.4 The support and escalation approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy.
20. Age, consumer rights and governing law
20.1 Only users aged 18 or over may purchase or hold a Token balance. Implementation of age, consumer rights and governing law links age requirement, Account control, payment authority and any credible safeguarding information to the eligibility decision, protective restriction and limited disclosure record, so the practical consequence can be explained and reviewed.
20.2 Nothing in this Policy excludes rights for digital content that is not supplied, not as described, not of satisfactory quality or otherwise subject to a non-excludable remedy. No age, consumer rights and governing law outcome is based solely on a technical label where reliable contrary evidence is available. The Policy is governed by the laws of England and Wales, subject to mandatory consumer law and forum protections in the user’s country of residence.
21. Before reporting non-delivery
21.1 The user should confirm the order email and Account address, allow the normal several-minute window, check spam, refresh and sign out and back in. Pixel Mill verifies before reporting non-delivery against payment status, entitlement creation, file or output availability, email events and user troubleshooting and records the action in the release, redelivery, restoration, service notice or refund outcome.
21.2 The user should then verify issuer status, avoid a duplicate purchase, test a supported browser and record the error and time.
21.3 A complete report allows Pixel Mill to reconcile payment and fulfilment quickly and choose the correct release, restoration, redelivery or refund action. The before reporting non-delivery record supports user communication, internal control and any provider, authority or court process that lawfully follows.