Flash Gen · Cookie 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: Strictly necessary cookies operate because Flash Gen cannot provide secure login, checkout and core functionality without them. Analytics, advertising and other non-essential technologies are used only after consent where required, and consent can be changed at any time. |
1. Introduction and scope
1.1 The controlling rule is as follows: This Policy explains the cookies, local storage, pixels, software development kits and comparable technologies used when a person visits or uses Flash Gen. It should be read with the Privacy Policy.
1.2 For introduction and scope, classification follows what the technology actually does on the device or browser. A label supplied by a vendor does not override the purpose, data flow or consent requirement observed in production.
1.3 Mandatory consumer, privacy and payment rights continue to apply to introduction and scope; this Policy cannot be used to waive a protection that the law makes non-excludable.
2. What cookies and similar technologies are
2.1 For the Flash Gen service, Cookies are small data files stored by a browser. Local storage retains device-side settings; pixels and tags record an event; server logs record requests. These technologies may be first-party or set by a service provider.
2.2 The consent configuration for what cookies and similar technologies are records the selected category and policy version. Technologies requiring consent remain blocked until the user makes the relevant choice.
2.3 A user may ask support to review a material outcome concerning what cookies and similar technologies are. Review can confirm the result, correct an error, narrow a restriction or identify the proper statutory process.
3. Why we use cookies
3.1 This section allocates responsibility clearly. Technologies support authentication, checkout security, fraud controls, consent records, preferences, generation workflow, diagnostics, performance measurement and, where consented, campaign attribution and marketing.
3.2 When why we use cookies is changed, Flash Gen checks identifier, provider, purpose, duration and whether information is read from or written to the device. The inventory and preference interface are updated before material deployment.
4. Cookie categories
4.1 The Account and transaction outcome follows this position: Flash Gen groups technologies as strictly necessary, functional or preference, analytics or performance, and marketing. Classification follows the main purpose of the technology rather than its vendor label.
4.2 A user may control cookie categories through the preference tool and browser settings. Blocking strictly necessary storage can prevent authentication, security checks, checkout or file-delivery continuity.
4.3 Reasonable verification may be required for cookie categories, especially where value, Account control or sensitive data is involved. Verification is proportionate to the risk and information requested.
Cookie categories
| Category | Purpose | Consent required | Effect if disabled |
| Strictly necessary | Login, security, checkout, load balancing and consent storage | No, where strictly necessary | Core Service or checkout may not function |
| Functional / preferences | Remember interface, language and workflow choices | Yes where required | Preferences may reset or features may be less convenient |
| Analytics / performance | Measure use, errors, speed and feature performance | Yes | Service remains available but measurement is reduced |
| Marketing | Campaign attribution, audience measurement and advertising controls | Yes | Advertising is less tailored and attribution is reduced |
5. Lawful basis and consent
5.1 To keep the Service predictable, Strictly necessary technologies are used to provide a requested service or protect it. Other categories are activated only after valid consent where the Privacy and Electronic Communications Regulations require prior consent.
5.2 Evidence for lawful basis and consent includes deployment configuration, consent logs, provider documentation and browser testing. These sources are compared during periodic review to detect unlisted or misclassified technology.
5.3 The treatment of lawful basis and consent is recorded so that support, billing and enforcement remain consistent. A corrected error is reflected in the Account or transaction history.
6. Cookie inventory and example technology
6.1 The practical and contractual position is this: The inventory identifies the expected purpose, provider and duration of technologies used by the service. Identifiers may change when security, hosting or checkout components are upgraded, while category and consent rules remain controlling.
6.2 Where cookie inventory and example technology is supplied by a third party, Flash Gen limits when the component loads and contractually controls its function. The third party may separately determine some identifier and retention details.
Cookie inventory
| Cookie / technology | Type | Purpose | Duration | Provider |
| fg_session | Strictly necessary | Maintain authenticated session and Account security | Session | Flash Gen |
| fg_csrf | Strictly necessary | Prevent cross-site request forgery in forms and checkout | Session | Flash Gen |
| fg_consent | Strictly necessary | Store cookie choices and consent version | 12 months | Flash Gen |
| fg_preferences | Functional / preferences | Remember interface and generation preferences | 12 months | Flash Gen |
| fg_analytics_id | Analytics / performance | Distinguish visits and measure aggregate service use | 13 months | Analytics provider |
| fg_campaign | Marketing | Attribute consented campaign traffic and conversion | 90 days | Marketing provider |
| Checkout security cookies | Strictly necessary | Authorisation, fraud prevention and strong customer authentication | Session to 13 months | Payment service provider |
| Generation queue local storage | Functional / preferences | Display recent job status and interface continuity | 30 days | Flash Gen |
7. Third-party cookies and embedded services
7.1 In operational terms, Payment, fraud, support, media or analytics providers may set technologies when their function is opened. Their identifiers and duration may be controlled by the provider, but Flash Gen limits deployment according to consent and contractual controls.
7.2 Withdrawal affecting third-party cookies and embedded services prevents future non-essential activation where technically possible. It does not invalidate earlier consented processing or erase Account and transaction records governed by the Privacy Policy.
7.3 No delay in enforcing third-party cookies and embedded services is a permanent waiver. A later response remains available where the underlying breach, error or risk continues.
8. Managing preferences
8.1 Users may open the cookie-preference tool, reject non-essential categories, withdraw consent or use browser controls. Withdrawing consent does not invalidate earlier processing but prevents future activation where technically possible.
8.2 Server-side processing related to managing preferences remains subject to data-protection rules even where it does not place information on the device. Cookie consent and privacy-law analysis are therefore maintained separately.
8.3 If part of the rule on managing preferences is unenforceable, it is adjusted only to the minimum extent necessary and the remaining provisions continue.
9. Retention and review
9.1 The controlling rule is as follows: Each technology has a session or fixed duration appropriate to its purpose. Consent records are retained long enough to demonstrate the user’s choice and are refreshed when the technology set or legal basis materially changes.
9.2 For retention and review, classification follows what the technology actually does on the device or browser. A label supplied by a vendor does not override the purpose, data flow or consent requirement observed in production.
10. Do-Not-Track and browser signals
10.1 For the Flash Gen service, Because Do-Not-Track signals are not uniformly defined, Flash Gen relies on its consent tool and legally recognised signals where applicable. Browser blocking may affect sign-in, checkout, file delivery or saved preferences.
10.2 The consent configuration for do-not-track and browser signals records the selected category and policy version. Technologies requiring consent remain blocked until the user makes the relevant choice.
10.3 Records supporting do-not-track and browser signals are retained only for the applicable business, legal and evidential period and are protected under the Privacy Policy.
11. Children and age
11.1 This section allocates responsibility clearly. The Service is restricted to adults aged 18 or over. Flash Gen does not knowingly use behavioural advertising technologies to profile children and investigates credible reports of underage use.
11.2 When children and age is changed, Flash Gen checks identifier, provider, purpose, duration and whether information is read from or written to the device. The inventory and preference interface are updated before material deployment.
11.3 A business Account may allocate internal roles for children and age, but the registered Account holder remains responsible for authorised access and accurate instructions.
12. International data flows
12.1 The Account and transaction outcome follows this position: Cookie and analytics providers may process identifiers in other countries. Transfers are handled under the safeguards described in the Privacy Policy and are limited to the data needed for the selected purpose.
12.2 A user may control international data flows through the preference tool and browser settings. Blocking strictly necessary storage can prevent authentication, security checks, checkout or file-delivery continuity.
13. Changes
13.1 To keep the Service predictable, This Policy and the inventory are revised when technologies, purposes, providers or retention periods change materially. The effective date shows the current publication.
13.2 Evidence for changes includes deployment configuration, consent logs, provider documentation and browser testing. These sources are compared during periodic review to detect unlisted or misclassified technology.
13.3 Users should raise concerns about changes promptly and preserve relevant confirmations, errors and communications so the issue can be resolved on reliable evidence.
14. Governing law and consumer safeguards
14.1 The practical and contractual position is this: Cookie use is administered under the law of England and Wales, including applicable privacy and electronic-communications requirements. Mandatory privacy and consumer rights are not excluded.
14.2 Where governing law and consumer safeguards is supplied by a third party, Flash Gen limits when the component loads and contractually controls its function. The third party may separately determine some identifier and retention details.
14.3 Any discretionary accommodation for governing law and consumer safeguards is assessed consistently but does not create an automatic entitlement for materially different circumstances.
15. Contact
15.1 In operational terms, Questions about cookies or consent may be sent to info@flash-gen.com. Include the browser, device, approximate date and relevant screenshot where a preference control appears not to operate.
15.2 Withdrawal affecting contact prevents future non-essential activation where technically possible. It does not invalidate earlier consented processing or erase Account and transaction records governed by the Privacy Policy.
Operational Maintenance Checklist
The production cookie configuration should be maintained against this checklist so that the published inventory remains accurate and consent controls work as described.
| Scenario / step | Practical rule |
| Before release | Inventory every cookie, local-storage key, pixel and embedded service used by the production build. |
| Consent test | Confirm that non-essential technologies remain blocked until the relevant category is accepted. |
| Quarterly review | Compare deployed technologies, provider contracts, durations and purposes against this inventory. |
| Material change | Update the banner and Policy before adding a new purpose or provider that requires consent. |
| Withdrawal test | Confirm that changing preferences stops future non-essential activation and records the new choice. |
| Evidence | Retain consent version, timestamp and category selection for the stated period. |
Flash Gen · Cookie Policy · v1.0 · effective 21 July 2026 · Published on the website; subject to update; the current published version governs.
