EconMind World — Official Documents

EconMind World / Official document

Privacy Notice

World participation data, commands, reports, access boundaries, retention and privacy requests.

Official source edition · 21 October 2026Published 2026-10-21 · effective on successful website publication
In this document 12 sections

01. Scope & Operating Responsibility#

This Notice explains personal-information handling in EconMind World, including participation, formal economic operations, competition administration, and simulation reports. It supplements the EconMind OS Privacy Notice for general account and platform services. The notices apply within their respective scope and must be read consistently with applicable law.

EconMind is the authorised operator and the organiser of Season One. It is a student-led alliance without a separately incorporated legal entity. Samuel is the Original Creator and holder of the applicable core intellectual property rights in his legally protected original contributions. The EconMind Technical Department contributes to development and maintenance. Those authorship and contribution positions do not, by themselves, determine every personal-information responsibility or confer access to participant records.

Samuel is EconMind's Initial Founder. Within the Project's internal management structure, Samuel directs data-management decisions, with the EconMind Technical Department assisting in technical implementation and administration. These internal management responsibilities do not, by themselves, establish Samuel as the sole statutory data controller in every jurisdiction.

The independently fictional simulation comprises 70 fictional economies and six Offices: Captain, Finance, Central Bank, Trade, Industry, and Labour. Fictional economic data can constitute personal information when linked to an identifiable account, Office holder, school, or other individual. Intellectual property ownership of the Project does not amount to ownership of participants' personal information.

General enquiries may be directed to admin@econmind.group. Account and privacy requests should follow the published routes identified in Section 09 and the platform Privacy Notice. This general contact reference does not establish a separate legal-notice or identity-verification procedure.

02. Account, Identity & Participation Information#

The platform handles the account email address and authentication identifier, together with an optional display name and relevant profile information supplied through the applicable features. School, team, economy, Office assignments, membership status, and authorisation information support participation and access decisions. Not every general platform profile field is required for every World activity.

Under the platform authentication arrangements, Google Sign-In is optional. If that method is chosen, authentication information can include the email address, provider identifier, and any display name or profile-image reference supplied by the provider. It does not grant access to Gmail, Google Drive, Calendar, contacts, or other account content. EconMind does not receive the user's Google password.

Participant submissions and relevant support or integrity correspondence may contain information needed to operate the selected activity or address a concern. Information supplied about other persons must be limited to what the submitter is lawfully entitled to provide. Team membership does not authorise unnecessary disclosure of another person's information.

03. Formal Commands, Events & Receipts#

3.1 Scope of the Economic Record#

The system records formally processed economic operations through a command–event–receipt structure. A command identifies the submitted economic instruction; related events record resulting economic facts where applicable; the receipt records its processing outcome and associated links.

Relevant information includes the account or authentication identifier and responsible actor; the world, economy, and Office where applicable; command type and parameters; real and simulation timestamps; command and correlation references; duplicate-prevention identifiers; relevant World State versions; and the result, related events, and reason for rejection where applicable. Authorisation versions and membership information support the relevant access and authority checks.

The clock uses 10× progression: one second of effective real time corresponds to ten seconds of simulation time, and the simulated year contains 360 simulated days. Applicable pause and resume rules determine effective running time. The real and simulated timestamps therefore serve different purposes and are not interchangeable.

3.2 Processing Outcomes & Corrections#

The command record distinguishes successful processing, rejection within the command system, and an inability to proceed following a change in authorisation. A request rejected before it enters the command system is not necessarily represented by a persistent command record. A rejected command need not produce a change in economic state.

Authoritative economic history is append-only: established facts are not silently overwritten, and corrections are expressed through linked subsequent events. Revoking an authorisation, removing a participant, or withdrawing consent for a separate optional use does not, by itself, reverse a completed economic transaction or erase an accepted simulation contract. The personal-information implications of continued retention remain subject to Section 08 and applicable law.

3.3 Gameplay Records & Browsing Behaviour#

Formal command recording is not a claim that all browsing, scrolling, typing, or interface clicks are captured as economic decisions. A preview, local draft, or unsubmitted intention is not, merely by appearing in the interface, a settled command.

Account sessions and essential browser storage support authentication, preferences, and drafts under the general platform arrangements. Hosting and service infrastructure may also process connection, operational, or security information for service delivery and protection. Such processing is distinct from the official economic command record and remains limited by its applicable purpose and notice. It must not be inferred that no technical information is handled merely because an interaction is not a gameplay command.

04. Purposes & Limits of Use#

Personal information is used as necessary to authenticate participants; maintain membership, economy, and Office assignments; verify authority and information access; process and settle formal economic operations; preserve the meaning and integrity of relevant records; administer competitions; address errors, support requests, and misuse; and provide reports to their authorised audiences.

Processing must have a specified purpose, be limited to the information necessary for that purpose, and be supported by an applicable lawful basis. Acceptance of Terms or participation in a school team is not consent to every subsequent use. Where consent or a separate authorisation is required, it must be obtained for the relevant purpose; withdrawal operates subject to applicable law and does not retrospectively invalidate processing already lawfully undertaken.

EconMind does not sell personal information or use it to build behavioural advertising profiles. A general educational purpose does not authorise unrestricted publicity, unrelated research, or undisclosed individual profiling. Any materially different purpose, audience, or processing arrangement must be addressed through appropriate notice and any required authorisation.

05. Information Access & Visibility#

Access is determined through server-verified identity, valid membership, economy, Office assignment where applicable, and current authorisation. Hiding a button, page, or menu is not the access-control boundary. Being a participant, contributor, administrator, or member of the technical department does not confer unrestricted access to all information.

Scope Access boundary
Public Information designated for lawful public release, including the corresponding public world, country, or results material. Publication of selected source data does not make all live or private records public.
National Information authorised for members of the relevant economy. Membership of one economy does not confer access to another economy's private records.
Office-private Information restricted to the relevant economy and authorised Office assignment. National membership alone does not grant every Office-private permission.
Negotiation-party Information restricted to the authorised parties to the relevant negotiation or arrangement. It is not generally available merely because other users participate in the same world.
Administrative Information available within the authorised administrative scope for the relevant operational or competition responsibility. Administrative access does not confer unrestricted authority to rewrite the economic ledger.

Technical and competition personnel may handle records only within their actual assigned authority and permitted purpose. Their department or job title is not a substitute for an access decision. Email addresses, authentication identifiers, private drafts, support correspondence, and administrative notes are not public-directory material merely because they concern a participant.

Public world and country source previews identify the nature of the material they display. A selected source dataset is not, merely by being officially published, a live authoritative World State or permission to access restricted participant records.

06. Final Simulation Reports & Public Results#

The platform generates Final Simulation Reports from formal economic operations and related simulation data. Their purposes include decision review, economic performance analysis, policy timelines, strategic evaluation, team reflection, and academic discussion. A Final Simulation Report is distinct from a final settlement or processing receipt for an individual command.

The Full Report is accessible to the relevant team and authorised competition personnel, subject to applicable access and confidentiality requirements. That audience does not imply inclusion of every Office-private record, third-party negotiation detail, or unrelated personal record. Report content must respect the access and disclosure boundaries applicable to its sources.

The Public Report is a controlled version from which appropriate personal, restricted, or confidential information is excluded. EconMind manages its publication under the competition rules and applicable privacy requirements. Identifying details that are unnecessary for the authorised publication are excluded; any permitted identifiable disclosure requires its own lawful basis and any required authorisation.

Reports distinguish recorded actions and outcomes from participant-supplied explanations and analytical interpretation. An action log does not, by itself, establish private reasoning, motive, or political belief. Simulated results and correlations are not empirical proof of real-world causation or certification of a participant's professional competence.

Internal report access does not automatically authorise institutional promotion, publication of a Full Report, or research involving identifiable information. Team representatives cannot consent on behalf of other persons solely by holding a Captain or other Office role. Any additional disclosure or research use must remain within its lawful, notified purpose and permitted scope.

07. Participant Sharing & Service Providers#

7.1 Sharing Boundaries#

The limited non-commercial sharing permission is set out in the World Terms of Use, Section 08. It does not require additional attribution for ordinary permitted sharing, but it preserves existing rights notices and does not waive privacy, confidentiality, third-party rights, or report-audience restrictions.

Screenshots, recordings, and shared results must exclude personal information, private communications, and restricted material that the sharer is not entitled to disclose. Public Reports may be shared within the scope of their authorised release. A publicly accessible world or country page is not a private-report sharing permission.

Where a report or feature provides a link, the stated audience and actual access conditions govern its use. This Notice does not guarantee a special sharing token, expiry period, revocation facility, hiding mechanism, or prevention of copying or downloads. Information disclosed to an authorised recipient may subsequently be retained by that recipient; sharing must therefore be limited at the point of disclosure.

7.2 Infrastructure & Provider Categories#

The service architecture uses the following provider categories within their respective functions:

  • Supabase: shared account authentication and database services relevant to platform identity and authorised application records.
  • GitHub and GitHub Pages: source-code hosting, build and publication workflows, release artefacts, and static website delivery.
  • Cloudflare: public information-reading services and API or execution-service hosting within the applicable service configuration.

These roles do not mean that every provider receives every participant record, that private gameplay records are published in a source repository, or that an infrastructure provider is authorised to reuse personal information without restriction. Provider access must remain limited to the relevant service, instructions, contractual arrangements, and lawful purpose.

Storage location, international access, and any cross-border transfer depend on the actual service configuration and applicable arrangements. They cannot be inferred from a domain name or provider brand. Any required disclosures, transfer safeguards, or consents must be addressed for the actual processing; this Notice makes no claim of a particular storage country or the absence of cross-border processing.

Personal information must be retained only for as long as necessary for the disclosed purpose and any applicable legal obligation. Account and role information, command and event history, support and integrity records, reports, identity links, technical logs, and backups may require different treatment. Relevant considerations include the operation of the account or season, the preservation of legitimate shared records, resolution of a dispute or integrity issue, security needs, and applicable legal duties.

Different categories may have different lawful grounds and criteria for retention. Their purposes and the assessment of continued necessity are distinguished as follows:

Data category Retention purpose and assessment criteria
A. Account & Identity Data Supports account identity, authorisation, membership, and necessary account administration. Continued retention is assessed against the account's status, valid access and membership arrangements, necessary administration, and applicable legal duties.
B. Simulation Commands & Event Records Preserves economic-state integrity, authoritative event history, transaction verification, and simulation consistency. The need to preserve economic facts is assessed separately from the necessity of retaining personal identifiers or identity links.
C. Competition Administration Records Supports competition administration, confirmation of results, necessary review, and related dispute handling. Continued retention is assessed against the relevant activity and any unresolved administrative, integrity, or dispute matter, together with applicable legal duties.
D. Final Simulation Reports Supports post-season analysis, team reflection, and presentation of achievements within the applicable rules. Continued retention is assessed against those purposes, the authorised report audience, and the necessity of retaining any identifying information.
E. Technical & Security Logs Supports system security, error investigation, access control, and necessary technical maintenance. Continued retention is assessed against the relevant security, diagnostic, or maintenance need and applicable legal duties.
F. Backups & Recovery Data Supports applicable system-recovery and data-integrity requirements. Continued retention and disposal are assessed against those requirements, applicable law, and the actual recovery and deletion capabilities of the relevant systems.

An append-only ledger protects the integrity of economic facts; it is not a policy of permanent identifiable retention. Correction of an economic event is also distinct from correction or deletion of a person's profile information. The need to preserve a simulation history does not remove personal-information duties.

Leaving an Office, leaving a team, withdrawing from a competition, and deleting an account are different actions. Loss of access does not automatically remove every shared historical record. Conversely, a connection to World does not create a blanket exemption from lawful deletion, restriction, or removal of unnecessary identity links.

Account and privacy requests are considered under the applicable platform arrangements and law, taking account of other participants' legitimate records. This Notice does not guarantee automated deletion of World-linked accounts, erasure of authoritative transactions, immediate removal from all backups, or a particular fixed retention period.

Where information is de-identified, its remaining context must be considered. A replacement identifier or removal of a name does not necessarily make a record anonymous: school, Office, timing, and activity may still allow identification. Information must not be treated as outside personal-information protections merely because it has been labelled de-identified.

Retention and deletion must be handled in accordance with applicable law and the actual technical capabilities of the relevant systems. A technical limitation does not, by itself, remove applicable legal obligations.

09. Privacy Rights, Requests & General Contact#

Depending on applicable law and the relevant activity, individuals may request access to or copies of their personal information, correction or supplementation, deletion, explanation of processing, and withdrawal of consent or restriction of processing where those rights apply. A privacy request is distinct from a challenge to the economic merits of an in-game decision or a competition result.

The EconMind OS Privacy Notice and Legal & Policy Hub identify the platform's published request channels, including the signed-in Contact form for matters requiring account verification or access to private records. General questions or assistance with sign-in access may be directed to admin@econmind.group. An unauthenticated email alone does not authorise account deletion or disclosure of private records.

Requests are subject to appropriate identity verification, applicable rights, and lawful exceptions. No additional identity document or public disclosure of a person's legal identity is required by this Notice merely because a request is made. Responses, any refusal, and available remedies remain subject to applicable law; this Notice does not invent a separate verification procedure, fixed response deadline, or guaranteed outcome.

10. School Participation & Younger Users#

School participation remains subject to the applicable school, parent or guardian, and local requirements. School affiliation is not automatic consent to every form of processing, public report, or secondary use.

Where applicable law requires guardian consent, age-related safeguards, or particular information for younger users, those requirements must be satisfied for the relevant activity. This Notice does not prescribe a universal minimum participation age, assert that an unestablished guardian-consent procedure exists, or transfer the operator's own responsibilities to a school merely because its students participate.

11. Security & Incident Handling#

The authorisation model separates public, national, Office-private, negotiation-party, and administrative information and checks authority on the server. A public projection, interface setting, or administrator label must not be treated as a substitute for the applicable permission check.

Appropriate organisational and technical safeguards must reflect the information, purpose, and risks involved. Persons handling records must act within their assigned authority. Where a personal-information incident occurs, the responsible persons must take appropriate remedial action and provide notifications required by applicable law.

No system is represented as absolutely secure. This Notice does not claim an unverified security certification, that every technical staff member may inspect all data, or that a hidden interface control protects information from unauthorised access. These limitations do not remove any duty imposed by applicable law.

Material changes to purposes, categories, audiences, providers, or other relevant processing arrangements must be addressed through appropriate notice and any consent or authorisation required by applicable law. Acknowledgement of an updated policy is not consent to every possible use. The copyright year does not, by itself, establish a policy effective date.

The World Terms govern participation and intellectual property permissions; this Notice and the general platform Privacy Notice govern personal-information matters within their respective scope. A season rule or content licence does not silently enlarge the permitted use of personal information.


© 2026 Samuel. Created by Samuel, operated under EconMind. All rights reserved.

This notice reserves rights in Samuel's legally protected original contributions. Other lawful rights holders retain their rights; no ownership of participants' personal information is asserted.