When did MEGA publish its first account inactivity or deletion policy and are archived copies available?
Executive summary
MEGA’s official help-centre page that explicitly states an inactivity rule — "If you don’t log in at least once in three months, your account is considered inactive…" — is dated March 23, 2025 on MEGA’s Help Centre (Does my MEGA account ever expire?) [1]. The reporting available here does not show an earlier official MEGA-published inactivity/deletion policy or provide archived copies of earlier versions; MEGA’s accounts index exists but the presence of an archive of historical policy text is not demonstrated in the supplied sources [2].
1. What the MEGA help pages say now and when they were posted
MEGA’s Help Centre contains a clear statement that free accounts become “inactive” if not logged into at least once every three months and that inactivity triggers warning emails and possible data deletion; that page is dated March 23, 2025 [1]. Additional MEGA support content reiterates that MEGA will send reminder emails for inactivity, security-compromise, or over-quota situations and explains deletion mechanics and recovery options; one such explainer is dated August 27, 2025 [3]. MEGA also maintains an accounts index or archive landing page for Help Centre topics, which collects those articles [2].
2. Is this the “first” published inactivity/deletion policy? The documentation gap
The materials provided show MEGA publishing explicit inactivity guidance on March 23, 2025 [1] but do not prove that this was the first time MEGA ever published an inactivity or deletion policy. The accounts index demonstrates where MEGA organizes policy and support content [2], but none of the supplied sources contains a historical timeline or a statement such as “this is the first policy” that would let one definitively claim March 23, 2025 as the first-ever publication. Absent earlier MEGA-hosted pages or a public changelog in the supplied material, the claim that March 23, 2025 is the first publication date cannot be conclusively established from these sources alone [1] [2].
3. What third parties and the community say — corroboration and reaction
Independent guides and community tools have long referenced a three-month inactivity risk for free MEGA accounts: a 2022 explainer (DigiCruncher) asserts MEGA can suspend or terminate free inactive accounts after three months, citing MEGA’s Terms and Conditions [4]. Community code repositories and utilities exist to automate sign-ins across accounts to avoid deletions, indicating users have treated inactivity deletion as a practical risk for some time (GitHub, MegaKeep) [5]. These third‑party signals corroborate the substance (three‑month inactivity rule) but do not serve as primary evidence of MEGA’s initial publication date.
4. Are archived copies of MEGA’s policy available in the supplied reporting?
The provided sources include MEGA help pages and a help-centre index [1] [3] [2] but do not include archived snapshots or direct links to earlier versions of those pages. There is no cited Wayback/Internet Archive capture or MEGA changelog in the material shown here that reproduces historical wording, so the supplied reporting does not demonstrate availability of archived copies. External archival services (not included in these sources) may hold older snapshots, but that possibility is outside the scope of the provided documents [1] [2].
5. Bottom line and what’s still unknown
From the supplied reporting, the earliest explicit MEGA help‑centre page stating the three‑month inactivity rule is dated March 23, 2025 [1], with further explanatory material dated August 27, 2025 [3], and MEGA’s help index aggregating account articles [2]. Third‑party guides and community tools reflect the same three‑month concern earlier [4] [5], but the sources provided do not contain a verifiable record of MEGA’s original publication date for an inactivity/deletion policy nor do they include archived copies of any earlier policy versions. To determine a definitive “first published” date or to obtain historical snapshots would require consulting web archives, MEGA’s own changelogs (if published), or primary historical Terms & Conditions documents not included in the supplied reporting.