Flash Gen · Acceptable Use Policy · v1.0 · effective 21 July 2026
| Field | Value |
| Operator | ARIES ACCESSIBILITY LTD |
| Company number | 15588986 |
| Registered office | 20 Wenlock Road, London, England, N1 7GU |
| Trading name / brand | Flash Gen |
| Website | https://flash-gen.com |
| Contact email | info@flash-gen.com |
| Support / complaints | info@flash-gen.com |
| Governing law | England and Wales |
| Document version | v1.0 |
| Effective date | 21 July 2026 |
| Important: Use Flash Gen only for lawful, authorised image creation. Prompts, uploads and outputs involving exploitation, impersonation, fraud, prohibited sexual content, harassment, unlawful discrimination, intellectual-property abuse or attempts to defeat safety controls are prohibited. |
1. Scope and relationship with other documents
1.1 The controlling rule is as follows: This Policy governs Accounts, prompts, uploads, generation jobs, downloads, Tokens, payment behaviour and use of outputs. It forms part of the Terms and Conditions.
1.2 For scope and relationship with other documents, assessment considers purpose, content, technical method, payment behaviour, foreseeable harm and prior history. A technically possible action is not necessarily permitted by the contract or law.
1.3 Mandatory consumer, privacy and payment rights continue to apply to scope and relationship with other documents; this Policy cannot be used to waive a protection that the law makes non-excludable.
2. Core principle of permitted use
2.1 For the Flash Gen service, Users may create and use images for lawful personal or commercial purposes where they have all necessary rights and do not expose people, property, systems or the public to unlawful harm.
2.2 Evidence concerning core principle of permitted use may include prompts, uploads, outputs, safety events, access logs, payment records and reports. Only information reasonably necessary for investigation and enforcement is used.
2.3 A user may ask support to review a material outcome concerning core principle of permitted use. Review can confirm the result, correct an error, narrow a restriction or identify the proper statutory process.
3. Account integrity and identity
3.1 This section allocates responsibility clearly. Users must provide accurate information, protect credentials, use authorised access and avoid impersonation. Shared business access must be controlled by an Account administrator and may not conceal the true responsible organisation.
3.2 An enforcement response to account integrity and identity is calibrated to severity and recurrence. Immediate restriction is available where delay would create serious safety, legal, rights or payment risk.
4. Prohibited payment and checkout behaviour
4.1 The Account and transaction outcome follows this position: Stolen methods, false billing data, card testing, refund fraud, chargeback-as-theft, sanctions evasion, transaction splitting and repeated disputed purchases are prohibited.
4.2 A user who encounters prohibited payment and checkout behaviour accidentally should stop the activity, avoid distribution, preserve context and report the issue. Good-faith reporting is treated differently from exploitation or concealment.
4.3 Reasonable verification may be required for prohibited payment and checkout behaviour, especially where value, Account control or sensitive data is involved. Verification is proportionate to the risk and information requested.
5. Prohibited generation and fair-use abuse
5.1 To keep the Service predictable, Users must not automate excessive jobs, exploit Token-calculation errors, duplicate credits, create multi-Accounts for promotions, resell Account access or deliberately consume capacity in a way that degrades other users.
5.2 Where prohibited generation and fair-use abuse affects a third party, Flash Gen may restrict access while authority, consent, ownership or safety is assessed. A restriction is not a final finding unless confirmed after review.
5.3 The treatment of prohibited generation and fair-use abuse is recorded so that support, billing and enforcement remain consistent. A corrected error is reflected in the Account or transaction history.
6. Prohibited technical interference
6.1 The practical and contractual position is this: Malware, vulnerability exploitation, credential attacks, reverse engineering beyond legal rights, scraping, unauthorised interfaces, safety-filter evasion, denial-of-service activity and interference with logs or job controls are prohibited.
6.2 Business users must ensure that staff and contractors understand prohibited technical interference. Delegating Account access does not transfer contractual responsibility or make prohibited conduct acceptable.
7. Content, conduct and communications standards
7.1 In operational terms, Prohibited content includes child sexual abuse material, sexualised minors, non-consensual intimate imagery, unlawful extremist material, credible threats, targeted harassment, deceptive impersonation, fraud assets and content facilitating serious crime.
7.2 Rights complaints about content, conduct and communications standards should identify the protected material and contested output. Bad-faith notices, fabricated authority and retaliatory reporting are themselves prohibited.
7.3 No delay in enforcing content, conduct and communications standards is a permanent waiver. A later response remains available where the underlying breach, error or risk continues.
Prohibited behaviour
| Behaviour | Why prohibited | Likely response |
| Stolen cards, card testing or false billing identity | Fraud and payment-system harm | Payment block, Account restriction and evidence preservation |
| Chargeback after knowingly receiving and retaining value | Abusive double recovery | Access hold, dispute response and Token reversal |
| Sexualised minors or child sexual abuse material | Severe illegality and harm | Immediate block, termination and lawful reporting |
| Non-consensual intimate or deceptive impersonation imagery | Privacy, dignity and fraud risk | Removal, restriction and investigation |
| Safety-filter evasion or technical exploitation | Threatens users and platform integrity | Job blocking, suspension or termination |
| Infringing uploads or requests | Violates third-party rights | Removal, warning, repeat-infringer termination |
| Account or Token resale and multi-Account promotion abuse | Circumvents service and payment rules | Token reversal and linked-Account action |
| Deceptive high-impact use | Can cause unlawful or material real-world harm | Restriction, termination and referral where required |
8. Intellectual property and unauthorised commercial exploitation
8.1 Users must not upload or request protected works, logos, datasets, likenesses or confidential material without authority. Outputs may not be represented as officially endorsed, exclusive or rights-cleared where that is untrue.
8.2 Lawful security research relating to intellectual property and unauthorised commercial exploitation requires an authorised route and must not access another user’s data, disrupt service or disclose exploit details before reasonable remediation.
8.3 If part of the rule on intellectual property and unauthorised commercial exploitation is unenforceable, it is adjusted only to the minimum extent necessary and the remaining provisions continue.
9. Account trading, transfers and Token misuse
9.1 The controlling rule is as follows: Accounts and Tokens may not be sold, leased, transferred, exchanged for money, pooled through unauthorised brokers or used as collateral. Exploit-created or reversed Tokens may be removed.
9.2 For account trading, transfers and token misuse, assessment considers purpose, content, technical method, payment behaviour, foreseeable harm and prior history. A technically possible action is not necessarily permitted by the contract or law.
10. High-impact and deceptive uses
10.1 For the Flash Gen service, Flash Gen must not be used to make decisions or evidence in employment, credit, housing, insurance, healthcare, law enforcement or legal proceedings where an image could create unlawful or materially misleading effects.
10.2 Evidence concerning high-impact and deceptive uses may include prompts, uploads, outputs, safety events, access logs, payment records and reports. Only information reasonably necessary for investigation and enforcement is used.
10.3 Records supporting high-impact and deceptive uses are retained only for the applicable business, legal and evidential period and are protected under the Privacy Policy.
11. Children, age and protective restrictions
11.1 This section allocates responsibility clearly. The Service is for adults aged 18 or over. Users must not generate exploitative depictions of minors or use a minor’s likeness without lawful authority and appropriate safeguards.
11.2 An enforcement response to children, age and protective restrictions is calibrated to severity and recurrence. Immediate restriction is available where delay would create serious safety, legal, rights or payment risk.
11.3 A business Account may allocate internal roles for children, age and protective restrictions, but the registered Account holder remains responsible for authorised access and accurate instructions.
12. Reporting, investigations and cooperation
12.1 The Account and transaction outcome follows this position: Reports should include the Account or output reference, date, nature of concern and available evidence. Flash Gen may preserve records, restrict access and request clarification while assessing law, rights and safety.
12.2 A user who encounters reporting, investigations and cooperation accidentally should stop the activity, avoid distribution, preserve context and report the issue. Good-faith reporting is treated differently from exploitation or concealment.
13. Enforcement measures
13.1 To keep the Service predictable, Responses may include removal, warning, Token reversal, job blocking, feature restriction, temporary suspension, termination, payment review, rights-holder response or referral to authorities, proportionate to severity and recurrence.
13.2 Where enforcement measures affects a third party, Flash Gen may restrict access while authority, consent, ownership or safety is assessed. A restriction is not a final finding unless confirmed after review.
13.3 Users should raise concerns about enforcement measures promptly and preserve relevant confirmations, errors and communications so the issue can be resolved on reliable evidence.
14. Relationship to refunds, cancellation and data requests
14.1 The practical and contractual position is this: Enforcement does not automatically create a refund. Account closure, Token treatment and data retention follow the Cancellation, Refund and Privacy Policies, including preservation of evidence needed for disputes and safety.
14.2 Business users must ensure that staff and contractors understand relationship to refunds, cancellation and data requests. Delegating Account access does not transfer contractual responsibility or make prohibited conduct acceptable.
14.3 Any discretionary accommodation for relationship to refunds, cancellation and data requests is assessed consistently but does not create an automatic entitlement for materially different circumstances.
15. User good-faith expectations
15.1 In operational terms, Users should disclose uncertainty, avoid misleading audiences, review outputs before publication, respect opt-outs and rights complaints, maintain provenance where material and promptly correct harmful or inaccurate uses.
15.2 Rights complaints about user good-faith expectations should identify the protected material and contested output. Bad-faith notices, fabricated authority and retaliatory reporting are themselves prohibited.
16. Governing law and statutory rights
16.1 This Policy is governed by the law of England and Wales. It does not restrict lawful consumer, privacy, whistleblowing, security-research or reporting rights that cannot be excluded.
16.2 Lawful security research relating to governing law and statutory rights requires an authorised route and must not access another user’s data, disrupt service or disclose exploit details before reasonable remediation.
16.3 The user remains responsible for downstream use connected with governing law and statutory rights, including context, disclosures, third-party rights and compliance after an output is downloaded.
17. Amendments and version control
17.1 The controlling rule is as follows: Updates may respond to emerging abuse patterns, law, model capabilities and provider requirements. Material restrictions are communicated prospectively where reasonably practicable.
17.2 For amendments and version control, assessment considers purpose, content, technical method, payment behaviour, foreseeable harm and prior history. A technically possible action is not necessarily permitted by the contract or law.
17.3 A restriction concerning amendments and version control can remain in place while a payment, safety or rights investigation is active and is reviewed when material new evidence becomes available.
18. Contact
18.1 For the Flash Gen service, Report misuse, infringement or safety concerns to info@flash-gen.com with enough detail for investigation.
18.2 Evidence concerning contact may include prompts, uploads, outputs, safety events, access logs, payment records and reports. Only information reasonably necessary for investigation and enforcement is used.
Illustrative Examples of Unacceptable Use
These examples are illustrative. Similar conduct may be prohibited where it creates equivalent legal, safety, payment or technical risk.
| Scenario / step | Practical rule |
| Unacceptable | Creating a fake executive image to authorise payment or mislead staff. |
| Unacceptable | Uploading a private person’s intimate image to create non-consensual variants. |
| Unacceptable | Using multiple Accounts to repeat a one-time Token promotion. |
| Unacceptable | Opening a chargeback while retaining delivered value and falsely claiming non-delivery. |
| Unacceptable | Attempting to bypass safety filters through coded prompts or automated retries. |
| Good faith | Report accidental harmful output, stop distribution, preserve context and cooperate with remediation. |
| Good faith | Label synthetic material where context makes omission deceptive or harmful. |
| Good faith | Respect rights-holder complaints and remove contested use while authority is assessed. |
User Good-Faith Expectations
GF1. Review prompts and outputs with the care appropriate to their audience and likely impact.
GF2. Use provenance labels or disclosure where an unlabeled synthetic image could materially mislead.
GF3. Stop distributing contested content while a credible rights, privacy or safety complaint is assessed.
GF4. Report accidental exposure of harmful content or vulnerabilities rather than exploiting or amplifying it.
Flash Gen · Acceptable Use Policy · v1.0 · effective 21 July 2026 · Published on the website; subject to update; the current published version governs.
