Records · procedure · next step
Game software: five permission-file priorities
A game-software file connects the operator, component and version to the actual application branch, professional reports, remediation and authority decision. French ANJ homologation differs from Swiss casino-game permission and accredited conformity evidence. The five priorities follow documentary dependencies, not odds or success. The tool performs no security or fairness audit, does not classify every update as minor and keeps operator permission separate from the version-specific game or software act.
General information and document preparation. The facts, actual procedural acts and applicable versions must be checked.
Julie’s legal research currently covers French law. The Swiss sections prepare documents; they do not establish Swiss-law product capability.
Julie by AlphaDeep
Julie currently assists with French law. Which French homologation records would you like to organise?
3 free questions at signup. Avoid names and sensitive information.
Which operator and authority route apply?
France’s article 34 VIII gives ANJ its software functions for the operators covered. Swiss LJAr 16 requires casino-game permission in addition to concession; do not treat the acts as interchangeable.
Preparation priority
Resolve operator and version before application branch, professional evidence and actual decision.
Operator and scope
Identify permission and administrative object.
Component and version
Fix the product actually examined.
Application branch
Retain the relevant package.
Reports and correction
Link professional authors, dates and validations.
Decision and changes
Preserve the actual version-specific act.
Prepare the records
Julie’s legal research currently covers French law. The Swiss sections prepare documents; they do not establish Swiss-law product capability.
Synthetic example
Operator, component, version, professional-report, correction and decision matrix
- Operator
- Synthetic E1, actual permission missing
- Component
- Game software G1, support S1 to identify
- Version
- Proposed V2, previous V1 decision to link
- Branch
- Actual country/game/component package to establish
- Reports
- Professional R1/R2, dates/signatures incomplete
- Remediation
- P1, professional validation absent
- Changes
- M1 journal, classification not made
- Decision
- No V2 act, no operation permission inferred
This record organises supplied documents and values; it certifies no entitlement, permission or safety.
Which component, support and version are examined?
Current ET2 distinguishes new software/components and supports, with substantial changes treated as new software. Retain the actual reference and former decision, without automatic change classification.
Which French application package is actually relevant?
The current documentation links ET2 v1.0 and forms v1.1, with separate component/game branches. File metadata dates establish no legal commencement date or universal attachment list.
What professional French reports and corrections are supplied?
Link branch-specific audit reports, authors, dates, contracts, versions and remediation references. The tool publishes no vulnerability details and neither audits software nor certifies correction or fairness.
What conformity evidence accompanies Swiss automated/online games?
LJAr 18 requires the stated accredited conformity-assessment certificate. Its prior-submission exception requires proof of earlier delivery; no certificate is generated or inferred from the form.
Are small software changes automatically exempt?
French ET2 has conditional classification and possible ANJ requalification. Swiss LJAr 16 provides a simplified-procedure framework for minor changes, not automatic approval of any named update.
What periodic French change record belongs in the file?
The current quarterly form records period, software/type, version, homologation number, changes and production date. Actual submission does not replace a new decision where required.
What actual decision and outstanding evidence must remain visible?
Retain authority, operator, game/component, version, conditions and notification. Missing reports or authorisation remain unknown; the tool infers no tacit approval or deployment permission.
Frequently asked questions
Which operator and authority route apply?
France’s article 34 VIII gives ANJ its software functions for the operators covered. Swiss LJAr 16 requires casino-game permission in addition to concession; do not treat the acts as interchangeable.
Which French application package is actually relevant?
The current documentation links ET2 v1.0 and forms v1.1, with separate component/game branches. File metadata dates establish no legal commencement date or universal attachment list.
What conformity evidence accompanies Swiss automated/online games?
LJAr 18 requires the stated accredited conformity-assessment certificate. Its prior-submission exception requires proof of earlier delivery; no certificate is generated or inferred from the form.
What actual decision and outstanding evidence must remain visible?
Retain authority, operator, game/component, version, conditions and notification. Missing reports or authorisation remain unknown; the tool infers no tacit approval or deployment permission.
Sources and versions
- ANJ — documentation des opérateurs
Document officiel — version indiquée
- ANJ — homologation des logiciels, ET2 v1.0
Document officiel — version indiquée
- ANJ — modifications trimestrielles, v1.1
Document officiel — version indiquée
- ANJ — modèle de plan de remédiation, v1.0.0
Document officiel — version indiquée
- Loi fédérale sur les jeux d’argent — art. 16
État au 2023-09-01
- Loi fédérale sur les jeux d’argent — art. 18
État au 2023-09-01
- Loi du 12 mai 2010 — article 34 VIII
Version depuis le 2026-08-05