Legal & Policies

EconMind Platform / Official document

Privacy Notice

Personal information, responsibilities, visibility, service providers, younger participants and rights requests.

Website version 2.0Published 2026-10-21 · effective on successful website publicationSource: League review R2 · 21 October 2026
In this document 9 sections

EconMind League

1 Who handles information#

EconMind League is an independently operated, student initiated online academic exchange platform with participants and operators in different countries. It is not a separately incorporated legal person. The individuals who actually determine a processing activity's purposes and means are responsible under applicable data protection law; the project name and an internal division of work do not replace their identities or duties.

The Leadership Group coordinates governance. Samuel leads online platform and information storage coordination, with the technical team; Yale leads social media and community channel coordination, with the publicity team. These descriptions allocate internal work and do not by themselves settle whether people are controllers, joint controllers or processors for a particular activity.

Privacy contact: admin@econmind.group. A signed-in support form may also be used if available. You can use email if you cannot sign in. We may need proportionate identity or guardian authority checks before disclosing or changing private records. Do not send passwords, sign-in codes, identity documents or highly sensitive information in an initial message.

2 Scope and collection#

This notice covers the core economics education website at econmind.group, currently labelled EconMind OS, its related learning tools and League participation area, account functions, academic submissions, support and the project managed community channels to which it is linked. EconMind League is the official initiative name. Separately governed services are outside this notice and require their own applicable notices. An external service also handles information under its own terms. A future feature requires its own accurate explanation before use.

We handle the following information to the extent the relevant activity is actually used:

  • Required account and authentication information: email, username, authentication identifiers and the credentials needed for the chosen sign-in method. Username is distinct from an optional display name. A password, where used for email authentication, is processed by the authentication provider; it is not a public profile field. Google Sign-In does not disclose your Google password to the platform. Never send passwords in profile fields or support messages.
  • Optional profile and self reported participation information: display name, school and grade or graduation year. Club name, city or region and an activity or coordination role are handled where you choose to provide them or for an activity whose necessary fields are explained in advance. School and grade are not required for basic account registration.
  • Optional Google Sign-In information: email and provider account identifier, and display name or profile image URL if supplied by Google. This sign-in method is used through the authentication provider. It does not request access to Gmail, Drive, Calendar or contacts, and the platform does not receive your Google password.
  • Work and contribution information: submissions, saved work where offered, author details, permissions, references and associated activity information necessary to display or manage the work. Do not upload personal information about research subjects without the necessary authority and safeguards.
  • Communications and administration: support messages, reported material, responses and restricted notes needed for safety, privacy, integrity and access review. Reports can include information about someone other than the sender.
  • Technical information: authentication sessions, local preferences and drafts where stored by the website, and connection or security information generated by hosting and authentication services, which may include IP address, browser information and timestamps. Not every locally stored item is sent to the operators; the use depends on the feature.
  • Support funding records: if an individual handles project support, that recipient may hold payer identity, communications and transaction or expense records. The recipient must explain their own processing and any necessary disclosure before collection. This notice does not authorise sharing payment or banking information with the wider membership.

Information comes from you, an authentication provider you choose, people who submit a relevant report or contribution, and the technical operation of the services. We do not seek private information about you from a school merely because you enter its name.

Information is used to authenticate and secure accounts; provide requested learning and submission functions; manage permissions and attribution; communicate about participation; resolve support and rights requests; and address misuse or security incidents. Optional public display needs a separate, clear choice or other specific lawful basis. We do not sell personal information or use it for behavioural advertising.

Information must be handled on a lawful basis under the applicable local requirements. Where consent is required, it must be informed and specific, with separate consent where the law requires it. Acceptance of the Terms is not consent for unrelated uses, sensitive information or a cross-border transfer.

The current service does not use personal information for advertising profiles. This notice does not authorise using private submissions or personal information to train AI models. Any proposal to add external AI processing, marketing analytics or a new profiling purpose requires a separate assessment and accurate notice before use, and consent where legally required.

4 Who can see information#

Private account identifiers, email addresses, authentication information, private submissions and moderation notes are not intended for public display. Access is limited by the relevant feature audience and the responsibilities of authorised administrators and service providers. A role title does not entitle someone to inspect unrelated records.

School names shown on the homepage indicate participants' self reported affiliations. Cities and regions may also be self reported; map positions are approximate. These displays are not official school participation or endorsement, official geographical data or students' live locations. We do not ask participants to publish home addresses or precise personal locations for these displays.

A school or club coordinator’s name, username, role or office, profile image and contact details are not published by default in a directory or publicity material. Each requires that person’s affirmative, specific opt-in permission; a role label cannot be released automatically with the school name. The person may withdraw optional public display permission through the available signed-in support route or, if unavailable, admin@econmind.group. No self-service display switch or club page is claimed to exist. Public contact details, a research paper with author information or another identifiable public contribution require a clear publication basis and the relevant permission. A club or public sharing function, if introduced, must clearly show the audience and let the user choose to activate optional publication. This notice does not say that a club display page or a public sharing control currently exists. A club coordinator may not consent on behalf of all members merely by holding that role.

Public pages can be indexed, copied or retained by others. Removing material from the platform does not guarantee removal of independent copies, but we will consider reasonable steps and legal duties applicable to the request. A link to an external community group does not transfer private account data to that group. Joining an external group can reveal your external profile and messages under that service's settings; avoid posting sensitive information.

School and club submissions may be reviewed by authorised administrators for listing and role management. Review is not an official school endorsement. Data sharing must follow the stated activity purpose, the person’s valid authorisation where needed, minimum necessary access and applicable law. A publicity, technical or leadership role does not authorise unrelated use or onward disclosure.

5 Service providers and cross-border access#

Authentication and database storage use Supabase according to the currently published service description. Google handles optional Google Sign-In. Hosting, source-control deployment, email and any external community channel providers may process technical or communications data for the functions actually used. They may act on instructions for some activities and independently for others. Access must be limited to necessary purposes and covered by appropriate arrangements.

Operators, providers and participants may be located in different countries. Storage abroad, remote administrator access and public publication can each create different data protection issues. A statement that users should obey local law does not satisfy the operators' own notice, consent, security or transfer duties.

6 Retention and deletion#

Personal information is kept only for a defined purpose and a period justified by that purpose and applicable law. An active account does not justify indefinite retention of every related record. Private work and communications are reviewed for removal when no longer needed. Attribution and shared academic records may need a limited record after account closure, but personal information must be removed, anonymised or restricted where required. Pseudonyms and removal of a name alone do not guarantee anonymity.

Records may be restricted and kept for a lawful security investigation, an unresolved dispute or a required financial record period. Retention must be limited to what is necessary and reviewed when that reason ends. Backups may follow a separate deletion cycle and must not be used to revive deleted information into ordinary service use without applying the deletion again.

You may request account closure and deletion by email or the available signed-in support route. A self-service deletion control, if offered to your account, may be used under the conditions explained at that control. Shared records may require review to protect others' rights; this is not an automatic refusal of deletion. If a request cannot be granted in full, the responsible operator should explain the legal reason and any remaining retention. Loss of sign-in access is not a reason to deny all requests; an alternative proportionate verification route must be considered.

7 Children and guardians#

The platform is principally intended for secondary school and older learners, usually aged 14 or above. A younger person may use a relevant function only where lawful and after required guardian arrangements and protections are completed. Other local age thresholds may apply. Collect only the minimum age information necessary for an appropriate arrangement.

Current registration uses a Terms acknowledgement and the user’s declaration that they are at least 14 or have guardian permission. No independent guardian verification is operated through that declaration. A child’s own statement, a Terms checkbox, an invitation or Google Sign-In is not verified guardian consent. School participation does not automatically replace it. Where required safeguards are unavailable, the relevant collection, account or activity cannot be offered. If we learn that a child's information was collected without a required lawful basis or consent, the responsible operators must assess restriction, deletion, guardian contact and any notification required by law.

Children and authorised guardians may contact admin@econmind.group about access, correction, removal or safety. A guardian request must be handled with appropriate checks, the child's rights and best interests, and safeguards against disclosure to an unauthorised person. Do not collect identity documents as a routine substitute for a properly designed age and consent process.

8 Security and rights#

The operators must use appropriate access controls, administrator permissions and safeguards proportionate to the information and risks. No system can guarantee absolute security. Report a suspected exposure promptly without distributing affected records.

Depending on applicable law, you may have rights to be informed, access or obtain a copy, correct, delete, restrict or object to processing, withdraw consent, request portability where applicable, and complain to a competent data protection authority or seek a remedy. Withdrawing consent does not affect earlier processing that was lawful on that basis. A request is assessed under the applicable law, with reasons for any lawful restriction and response within the applicable deadline. You need not first exhaust an internal appeal to complain to an authority.

Optional profile information can be corrected through available account controls or a request. Withholding optional information or withdrawing optional publication consent should not remove unrelated basic access. Information genuinely required for a service may affect whether that service can be provided; this must be explained before collection.

For account access, correction and deletion, use the signed-in request route first where available; if you cannot sign in, email admin@econmind.group. A proportionate manual identity check may be used according to the request and risk. An email alone does not authorise disclosure of private records, and lack of sign-in access does not invalidate the request. Requests are handled within a reasonable period subject to applicable legal deadlines, without a fixed service-day guarantee.

9 Updates#

The approved notice will show a version and effective date. Material changes to purposes, recipients, public visibility or transfers require appropriate notice before the change takes effect and fresh consent where required. Silence or continued browsing is not automatically consent. Updated wording does not retrospectively legalise an earlier practice. Contact admin@econmind.group for questions or a copy of the applicable notice.