Pixel Mill · Acceptable Use 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: Users remain responsible for prompts, uploads and downstream use. Payment abuse, unlawful content, safety-control circumvention, Token trading, scraping and model extraction are prohibited. |
1. Scope and acceptance
1.1 This Acceptable Use Policy governs every use of pixel-mill.com, Accounts, catalogue, checkout, Token ledger, prompts, uploads, generation tools, downloads, support channels and application interfaces made available by Pixel Mill.
1.2 It applies to direct activity, attempted activity, automation and conduct performed through another person, Account, device or organisation. In practice, scope and acceptance is assessed through the conduct, content, technical event, payment record, risk and user explanation, with the result reflected in the proportionate enforcement outcome and review record.
1.3 Using the Service requires compliance with this Policy, the Terms and applicable law.
1.4 When applying scope and acceptance, those indicators are considered together rather than relying on a single unverified assertion.
2. Core standard of conduct
2.1 Users must act lawfully, honestly, safely and in good faith and must not use the Service to harm another person, evade safeguards or obtain an unfair technical or payment advantage. The operational checkpoint for core standard of conduct is the conduct, content, technical event, payment record, risk and user explanation; completion is shown by the proportionate enforcement outcome and review record.
2.2 A user remains responsible for prompts, uploads, instructions, outputs selected for use and downstream publication or distribution. This treatment of core standard of conduct is traceable without expanding collection or restriction beyond what the situation requires. Apparent technical capability does not mean that a particular use is permitted or that Pixel Mill has cleared rights in the user’s intended context.
3. Account integrity
3.1 Users must maintain accurate registration details, protect credentials and use only Accounts they control or are authorised to operate. For account integrity, relevant indicators include registration data, authentication events, authority, session history and recovery evidence, and the resulting action is documented through the verified Account status, access restriction or recovery confirmation.
3.2 Credential sharing, account sale, identity misrepresentation, session theft, unauthorised access and creation of deceptive multiple Accounts are prohibited.
3.3 Suspected compromise must be reported promptly and users must cooperate with proportionate recovery and verification measures. The account integrity approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy.
4. Payment integrity and chargeback conduct
4.1 Users must use payment methods with informed authority and must not test cards, manipulate authentication, disguise location, exploit checkout errors or create artificial payment patterns.
4.2 A user must not make a knowingly false fraud or non-delivery report, pursue a merchant refund and chargeback for the same value, or consume Tokens while denying the underlying authorised purchase. Implementation of payment integrity and chargeback conduct 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 A genuine billing error or statutory dispute remains protected and should be reported with accurate evidence.
4.4 No payment integrity and chargeback conduct outcome is based solely on a technical label where reliable contrary evidence is available.
5. Token and promotion abuse
5.1 Tokens may be used only within the Account and generation functions for which they were issued. Pixel Mill verifies token and promotion abuse against purchase record, Account identifier, Token ledger, generation deductions and reversals and records the action in the corrected balance, entitlement status and linked transaction history.
5.2 Users must not sell, transfer, broker, pool, cash out, counterfeit or externally value Tokens, or manipulate multiple Accounts, promotions, referral benefits or technical faults to obtain unearned credits. The token and promotion abuse record supports user communication, internal control and any provider, authority or court process that lawfully follows. Pixel Mill may reverse erroneous or abusive credits and preserve the underlying ledger evidence.
6. Generation-system abuse
6.1 Users must not overload generation queues, evade rate or quantity controls, automate excessive requests, extract model behaviour, scrape outputs at scale or reproduce internal prompts or safety logic. The practical standard for generation-system abuse is tested using prompt event, permitted inputs, processing status, safety result, Token deduction and output availability; the output record, Token outcome and any moderation or support action then evidences the action taken.
6.2 Reverse engineering, model extraction, adversarial probing, benchmark harvesting and use designed to substitute for unauthorised access to the underlying model or infrastructure are prohibited.
6.3 Reasonable ordinary generation for lawful creative and commercial end products remains permitted within the purchased entitlement. Timing, scope and any exception under generation-system abuse are determined from the actual Service stage rather than a generic classification.
7. Security and technical interference
7.1 Users must not introduce malware, destructive code, credential harvesters, denial-of-service traffic or instructions intended to compromise the Service or another system.
7.2 Probing vulnerabilities, bypassing access controls, intercepting traffic, altering logs, abusing interfaces or scanning without prior written authorisation is prohibited. Operational review of security and technical interference focuses on risk signals, access logs, payment evidence, technical events, severity and recurrence, after which the proportionate protective measure, preserved evidence and review route confirms the result.
7.3 Good-faith security concerns should be reported privately to info@pixel-mill.com with enough detail to investigate and without public exploitation.
7.4 The security and technical interference distinction prevents an Account, payment, content or rights issue from being treated as if every consequence were identical.
8. Illegal and harmful content
8.1 The Service must not be used to create, upload, request, store or distribute content that is illegal, threatening, harassing, exploitative, fraudulent, defamatory or designed to facilitate serious wrongdoing. For illegal and harmful content, Pixel Mill considers product disclosure, source material, rights information, intended use and distribution context and uses the licence position, restriction, removal or rights-holder response to close or escalate the matter.
8.2 Prohibited material includes child sexual abuse or exploitation, non-consensual intimate imagery, trafficking content, credible violent threats and instructions materially facilitating unlawful access, fraud or physical harm. The illegal and harmful content outcome remains proportionate to severity, recurrence, user impact and the legal or contractual duty involved. Pixel Mill may block a request, preserve evidence and make a lawful report where required or necessary to protect people.
9. Intellectual property and personality rights
9.1 Users must have the rights and permissions necessary for prompts, reference images, logos, characters, datasets, likenesses and other submitted material. In practice, intellectual property and personality rights is assessed through applicable status, user location, request details, correspondence and mandatory legal conditions, with the result reflected in the reasoned response, escalation route and preserved statutory option.
9.2 They must not request or use outputs to counterfeit goods, impersonate a rights holder, falsely imply endorsement, remove rights-management information or reproduce protected material in a manner that infringes law.
9.3 Outputs may not be unique, and users must perform context-appropriate rights review before high-risk publication or commercial exploitation. When applying intellectual property and personality rights, those indicators are considered together rather than relying on a single unverified assertion.
10. Privacy, identity and biometric misuse
10.1 Users must not upload or generate personal data, private communications, identity documents, sensitive traits or biometric-style material without a lawful basis and appropriate authority.
10.2 The Service must not be used for covert surveillance, facial identification databases, discriminatory profiling, doxxing, identity theft or deceptive impersonation. The operational checkpoint for privacy, identity and biometric misuse is registration data, authentication events, authority, session history and recovery evidence; completion is shown by the verified Account status, access restriction or recovery confirmation.
10.3 Extra care is required for real-person likenesses, health, children, employment, credit, insurance, housing, education and other consequential contexts.
10.4 This treatment of privacy, identity and biometric misuse is traceable without expanding collection or restriction beyond what the situation requires.
11. Deceptive and regulated uses
11.1 Users must not present Generated Outputs as authentic evidence of an event, person, document, product or authority where that presentation is materially deceptive. For deceptive and regulated uses, relevant indicators include the conduct, content, technical event, payment record, risk and user explanation, and the resulting action is documented through the proportionate enforcement outcome and review record.
11.2 The Service may not be used to create forged identity or financial documents, misleading medical or legal evidence, deceptive political impersonation, counterfeit credentials or regulated advice falsely attributed to a professional. The deceptive and regulated uses approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy. Appropriate disclosure and human review are required where synthetic content could reasonably mislead an audience about authenticity or source.
12. Children and vulnerable persons
12.1 Only persons aged 18 or over may use the Service or purchase Tokens. Implementation of children and vulnerable persons 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.
12.2 Users must not create sexualised, exploitative, coercive, humiliating or otherwise harmful content involving a child or person presented as a child, even where no real child image is used.
12.3 Requests involving vulnerable persons, self-harm, abuse or coercion may be restricted or escalated where necessary for safety and law. No children and vulnerable persons outcome is based solely on a technical label where reliable contrary evidence is available.
13. Standalone resale and model-training restrictions
13.1 Purchased content and Generated Outputs may be incorporated into lawful end products under the Terms, but may not be resold or sublicensed as substantially standalone competing files.
13.2 Users must not use Pixel Mill content, outputs, prompts or metadata to train, fine-tune, evaluate or build a competing generative model or dataset without prior written permission. Pixel Mill verifies standalone resale and model-training restrictions against product disclosure, source material, rights information, intended use and distribution context and records the action in the licence position, restriction, removal or rights-holder response.
13.3 False exclusivity claims and attempts to register broad rights that block other lawful users from independently similar outputs are prohibited.
13.4 The standalone resale and model-training restrictions record supports user communication, internal control and any provider, authority or court process that lawfully follows.
14. Reporting suspected misuse
14.1 Users and rights holders may report suspected misuse to info@pixel-mill.com with relevant URLs, Account or order information, dates, explanation and supporting evidence. The practical standard for reporting suspected misuse is tested using risk signals, access logs, payment evidence, technical events, severity and recurrence; the proportionate protective measure, preserved evidence and review route then evidences the action taken.
14.2 Reports should avoid unnecessary personal data and must not contain passwords or full card credentials. Timing, scope and any exception under reporting suspected misuse are determined from the actual Service stage rather than a generic classification. Pixel Mill may acknowledge receipt, request clarification and take interim protective action without disclosing confidential security or investigation detail.
15. Investigation and evidence
15.1 Pixel Mill may review relevant Account, payment, Token, prompt, upload, output, device, network, access and communication records where necessary and proportionate. Operational review of investigation and evidence focuses on the conduct, content, technical event, payment record, risk and user explanation, after which the proportionate enforcement outcome and review record confirms the result.
15.2 Information may be preserved or shared with payment providers, hosting or model suppliers, advisers, rights holders, authorities or courts where there is a lawful basis.
15.3 A report or automated flag is evaluated in context and does not automatically establish wrongdoing. The investigation and evidence distinction prevents an Account, payment, content or rights issue from being treated as if every consequence were identical.
16. Enforcement measures
16.1 Depending on severity and risk, Pixel Mill may warn, remove or block content, restore or deduct Tokens, rate-limit, require verification, suspend a feature, freeze an Account or terminate access.
16.2 Immediate action is appropriate for child exploitation, credible threats, fraud, payment abuse, account compromise, malicious code, serious infringement or attempts to defeat safeguards. For enforcement measures, Pixel Mill considers the conduct, content, technical event, payment record, risk and user explanation and uses the proportionate enforcement outcome and review record to close or escalate the matter.
16.3 Where practical and safe, Pixel Mill may explain the category of breach and provide a route to contest a material decision.
16.4 The enforcement measures outcome remains proportionate to severity, recurrence, user impact and the legal or contractual duty involved.
Prohibited behaviour and likely response matrix
| Behaviour | Why prohibited | Likely response |
| Use of stolen or unauthorised payment credentials | Fraud, financial harm and card-scheme abuse | Payment block, Account freeze, evidence preservation and termination |
| Knowingly false chargeback or non-delivery claim | Attempts double recovery and corrupts payment evidence | Refund pause, provider response, Token or licence reversal and enforcement |
| Multiple Accounts to manipulate promotions or limits | Obtains unearned value and evades fair-use controls | Linked-Account review, credit reversal, restriction or termination |
| Sale or transfer of an Account or Tokens | Defeats security and the non-transferable service-credit model | Transfer blocked, balance frozen and Accounts restricted |
| Circumvention of generation safety controls | Creates foreseeable legal, rights and safety harm | Prompt refusal, rate restriction, suspension or termination |
| Child exploitative or non-consensual intimate content | Severe unlawful and personal harm | Immediate block, evidence preservation, termination and lawful reporting |
| Scraping, model extraction or denial-of-service activity | Threatens infrastructure, suppliers and intellectual property | Technical blocking, suspension, termination and legal escalation |
| Standalone resale or unauthorised model training | Exceeds the content licence and competes with protected assets | Removal demand, licence termination, Account action and rights enforcement |
17. Effect on payments, refunds and licences
17.1 Enforcement does not create an automatic refund for Tokens consumed or access lost through the user’s material breach. In practice, effect on payments, refunds and licences is assessed through order status, payment capture, fulfilment evidence and the remedy already supplied, with the result reflected in the case decision, payment instruction and corresponding Token or licence adjustment.
17.2 A refunded or reversed transaction ends the associated licence and removes or reverses the relevant Tokens. When applying effect on payments, refunds and licences, those indicators are considered together rather than relying on a single unverified assertion. Mandatory consumer, privacy and genuine unauthorised-payment rights remain separately assessable despite an enforcement action.
18. Appeals and good-faith correction
18.1 A user may contest a decision by emailing info@pixel-mill.com with the Account email, date, affected feature, explanation and evidence. The operational checkpoint for appeals and good-faith correction is applicable status, user location, request details, correspondence and mandatory legal conditions; completion is shown by the reasoned response, escalation route and preserved statutory option.
18.2 Pixel Mill will review whether the correct Account, policy category, context and proportional measure were used and may uphold, narrow, reverse or replace the action.
18.3 Repeated appeals that add no material information need not suspend a necessary protective measure. This treatment of appeals and good-faith correction is traceable without expanding collection or restriction beyond what the situation requires.
19. Changes and governing law
19.1 Pixel Mill may update this Policy to address new abuse patterns, technology, provider requirements or law and will identify the effective version.
19.2 This Policy is governed by the laws of England and Wales, subject to mandatory consumer and data-protection rights. For changes and governing law, relevant indicators include applicable status, user location, request details, correspondence and mandatory legal conditions, and the resulting action is documented through the reasoned response, escalation route and preserved statutory option.
19.3 Questions and reports may be sent to info@pixel-mill.com or in writing to the registered office.
19.4 The changes and governing law approach is calibrated to the transaction, request or risk actually identified and preserves any mandatory remedy.
20. Illustrative good-faith expectations
20.1 Users should describe lawful creative goals accurately, verify ownership or permission for uploaded material and use generated files in a transparent context appropriate to the audience. Implementation of illustrative good-faith expectations links the conduct, content, technical event, payment record, risk and user explanation to the proportionate enforcement outcome and review record, so the practical consequence can be explained and reviewed.
20.2 They should test ordinary features without bypassing limits, report defects rather than exploiting them and resolve billing concerns with complete and truthful information. No illustrative good-faith expectations outcome is based solely on a technical label where reliable contrary evidence is available. Organisations should supervise authorised users, maintain internal rights controls and review high-risk outputs before publication.