Menopause support data should be retained only for as long as it is necessary for a clearly defined purpose, subject to applicable legal and professional obligations. The right period depends on the information collected, whether it is held by an employer, healthcare provider or digital health platform, and the laws governing that organisation. There is no universal two-year limit for menopause apps or single retention period for all African workplaces.

Symptom logs, treatment details, workplace adjustment requests and account identifiers can reveal sensitive information about a person’s health. Organisations should collect the minimum necessary, restrict access, explain how long records are kept and ensure that deletion and anonymisation procedures work in practice.

How Long Should Menopause Support Data Be Kept?

The answer depends on the purpose and the organisation holding the information. Retention periods should be recorded in a schedule that identifies each data category, its lawful basis, the reason it is needed, the review date and the disposal process.

Consumer Menopause Apps

A consumer app may need symptom histories so users can compare patterns or discuss changes with healthcare professionals. However, a proposed one- or two-year review period is an operational choice, not a statutory limit. Product teams should test whether each category of data remains necessary, allow users to access or export relevant records where appropriate, and clearly explain deletion options.

Inactive Accounts and Tracking History

Inactivity can prompt a retention review, but six months without opening an app does not automatically mean that all health records should be erased. Notify users of any inactivity policy, consider reasonable opportunities to reactivate or export information, and assess legal or contractual obligations before deleting records.

Clinical Records

Medical consultations, prescriptions and laboratory results may form part of formal clinical records and can be subject to longer professional or legal retention obligations. A universal seven-to-ten-year rule for Nigerian menopause records should not be assumed without identifying the applicable requirement. Healthcare providers should obtain jurisdiction- and record-specific guidance.

Why Does Excessive Retention Create Risk?

Longer storage increases the amount of sensitive information potentially exposed through unauthorised access, security incidents, inappropriate sharing or misuse. Menopause-related information can be especially revealing when symptom logs are combined with sleep patterns, treatment details, location data or advertising identifiers. Organisations should assess both the benefit of retention and the harm that could result from keeping information unnecessarily.

Investigations involving health apps and US regulatory actions against GoodRx and Cerebral illustrate the importance of limiting sensitive-data sharing. They are useful international examples, but do not establish Nigerian retention deadlines or prove that all menopause apps follow the same practices.

Which Menopause Data Should Organisations Retain?

Retain only data needed to deliver the service, support an agreed workplace arrangement, fulfil a valid legal obligation or carry out appropriately governed research. The following decision guide is illustrative; each organisation must establish its own documented schedule.

Retention Decision Guide

Data category	Recommended approach	Key consideration
Symptom logs	Keep while needed for tracking or care; review regularly	User controls and stated purpose
Treatment and clinical records	Follow applicable clinical and legal obligations	Different from consumer-app records
Account information	Retain minimum required for service and security	Remove unnecessary identifiers
Workplace adjustments	Record agreed support and review date	Avoid excessive medical detail
Research information	Follow approved protocol and legal basis	Assess identifiability and consent
Analytics identifiers	Minimise and apply documented expiry	Restrict third-party sharing
Closed-account data	Delete or anonymise absent valid exception	Include processors and backups

Which Data Should Be Deleted or Anonymised?

Information with no clear ongoing purpose should not remain in storage simply because it is technically easy to keep. Precise location histories, unnecessary advertising identifiers, excessive free-text health notes and duplicate exports deserve particular scrutiny. Some identifiers, such as IP addresses or device tokens, may be needed briefly for security or functionality; they should not be described as universally disposable on collection.

Deleting personal data and anonymising it are not the same. Pseudonymised records may still be linked back to individuals and remain subject to data-protection requirements. Genuine anonymisation requires a defensible assessment of re-identification risk, including the possibility of combining datasets.

What Menopause-Related Information Should Employers Keep?

Employers should generally focus on the workplace support required rather than collecting a detailed medical history. For example, HR may need to document an agreed flexible start time, access to breaks, the person responsible for implementing the arrangement and a review date. It does not automatically need the employee’s symptom diary, medication history or consultation notes.

Access to sensitive records should be limited to people with a genuine work-related need. Managers should understand how to discuss work impact respectfully, protect confidentiality and refer medical questions to qualified professionals. Employers should document the lawful basis for processing and avoid assuming that an employee’s disclosure provides unrestricted permission to retain or circulate health information.

For organisations operating in several African countries, retention and employment requirements must be assessed country by country. Nigeria’s Data Protection Act does not create one continent-wide rule. Cross-border transfers, workplace privacy and clinical obligations may differ.

What Do Nigerian and International Laws Require?

The Nigeria Data Protection Act 2023 provides the principal Nigerian data-protection framework. Health information is sensitive personal data, and organisations must identify an appropriate lawful basis, observe data-minimisation and storage-limitation principles, and implement suitable safeguards. The Nigeria Data Protection Commission’s General Application and Implementation Directive 2025 should be checked for applicable implementation requirements.

The EU General Data Protection Regulation also applies a storage-limitation principle where it governs processing. In the United States, HIPAA applies to specified covered entities and business associates rather than every consumer wellness app; other privacy and consumer-protection rules may apply. These frameworks are informative comparisons, not substitutes for legal analysis in the countries where an organisation operates.

No single law cited in this guide establishes a universal two-year menopause-app cap, a blanket 30-day deletion deadline or one clinical-record period for every Nigerian provider. Organisations should seek qualified advice for binding obligations.

How Should Consent Withdrawal and Account Closure Be Handled?

When consent is the basis for processing and is withdrawn, the organisation must stop processing on that basis. It should then assess whether erasure is required or another lawful basis or exception justifies retaining particular records. The response should explain, in plain language, what will be deleted, what may remain and why.

A deletion process should cover active databases, exports, support systems and third-party processors. Backups may follow a documented expiry cycle where immediate selective erasure is technically impracticable, provided access is restricted and deleted information is not restored into active use. A 30- or 90-day period should be described as a justified operational policy where adopted, not as a universal legal deadline.

How Can Organisations Put a Retention Policy into Practice?

1. Build a Data Inventory

Map where menopause-related information is collected and stored, including apps, clinical systems, HR files, analytics services, support tickets, shared drives and backups. Record the data owner, purpose, lawful basis, location and processor.

2. Create a Retention Schedule

For each category, define when retention starts, the review or deletion trigger, any applicable exception and who approves disposal. Make sure the schedule reflects actual product features, workplace processes and local obligations.

3. Implement Secure Disposal

Use appropriate technical deletion or cryptographic erasure where feasible, and secure destruction for physical records. Record completion, apply processor instructions and ensure backup restoration does not unintentionally reintroduce deleted data.

4. Audit and Train Staff

Review retention settings and access permissions regularly, with frequency based on risk. Train HR staff, clinicians, customer-support teams and analysts to recognise sensitive information, minimise collection and escalate suspected incidents.

Can Anonymised Data Still Identify a User?

Sometimes. Removing a name does not necessarily anonymise a record. A combination of age, location, symptoms and timestamps may still identify a person. Organisations should assess re-identification risk and treat pseudonymised information as personal data where it can still be linked to an individual.

What Happens When a Retention Rule Conflicts With a Legal Hold?

A valid legal preservation obligation may require specific records to be kept beyond their normal deletion date. The organisation should verify the scope, restrict access, document the legal reason and resume normal disposal when the obligation ends. A speculative possibility of future litigation is not a justification for indefinite blanket retention.

Frequently Asked Questions

Is two years the legal maximum for a menopause app?

No universal two-year limit has been established here. A two-year period may be considered as an internal policy where the organisation can justify it, but retention must follow purpose and applicable law.

Should employers keep employees’ menopause symptom diaries?

Usually, employers should focus on the support or adjustment needed rather than collecting detailed medical histories. Any necessary health information requires an appropriate lawful basis, safeguards and access controls.

Do clinics follow the same rules as consumer apps?

Not necessarily. Clinical records may be subject to additional professional and legal obligations, which should be confirmed for the relevant jurisdiction and type of record.

Does closing an account mean every record must be deleted immediately?

Not always. Organisations should erase data that is no longer lawfully needed, while explaining any valid exceptions and how backups or processor copies are handled.

Is encryption a substitute for deletion?

No. Encryption helps protect retained data, but it does not by itself justify keeping information after its legitimate purpose has ended.

Conclusion

Responsible menopause support depends on trust. Employers, healthcare providers and digital platforms should know why they collect sensitive information, how long it remains necessary and how it will be securely removed. A clear retention schedule, limited access, meaningful user information and regular reviews are more defensible than keeping everything by default.