Legal 08
Account Closure and Data Deletion Policy
Contents (14 sections)
- 8.1 Your options
- 8.2 Starting a request
- 8.3 Renewal and subscription consequences
- 8.4 Research access and export
- 8.5 Deletion process
- 8.6 Records that may remain
- 8.7 Shared or public content
- 8.8 Requests and appeals
- 8.9 Separate actions and consent implications
- 8.10 Eligibility and requester identity
- 8.11 Pre-closure checklist and exports
- 8.12 Deletion orchestration and exceptions
- 8.13 Shared and published materials
- 8.14 Confirmation and appeal
8.1 Your options
Dear member, this Policy explains how you may close an INRGIFT account and request deletion of eligible personal information and saved research. Closing an account is different from merely cancelling a paid membership. Before closure, you should review any active renewal, download available records and consider the effect on watchlists, saved research records and Ginie conversations.
8.2 Starting a request
Where supported, submit a request from Account Settings. You may also write to support@inrgift.com with the subject Account Closure. We may require proportionate identity verification before acting, particularly when an account holds private research or billing details. We will not ask for a password or OTP by email as proof of identity.
8.3 Renewal and subscription consequences
A closure flow should clearly warn of any active paid subscription, upcoming renewal or outstanding payment dispute. It should avoid charging again after a properly completed cancellation, subject to the processor and applicable law. Closing a free profile and cancelling a renewal mandate are distinct steps and should be coordinated to avoid an unwanted charge.
8.4 Research access and export
Before permanent deletion where feasible, members should be able to export user-authored notes, assumptions and other eligible research in a supported format. Underlying proprietary market datasets or licensed chart materials may not be exportable for redistribution. An export option should explain whether financial snapshots, original notes, AI conversations or version history are included.
8.5 Deletion process
Following verified closure, we should revoke active sessions, disable login, discontinue optional communications, remove user-visible saved items and delete or anonymise records according to the applicable retention and backup rules. A request may be processed in stages because databases, archives, audit logs, billing records and disaster-recovery backups have different operational and legal constraints.
8.6 Records that may remain
Certain records may need to be retained for taxation, payment disputes, legal proceedings, security, fraud prevention, audit trails or other lawful reasons. Where deletion is restricted by a legal obligation, access should be limited to the permitted purpose. We should describe the actual retention periods and backup lifecycle once they have been approved, rather than claiming immediate deletion from every system.
8.7 Shared or public content
If community or sharing features are activated, account closure should address comments, shared material and replies already viewed by others. Lawful retention, quotation or moderation records may require case-specific handling. No user should be told that content is fully private after they affirmatively published it to a community; default private research must remain private.
8.8 Requests and appeals
You may seek correction of an erroneous account record or challenge a deletion decision through Privacy Request or Formal Grievance channels. Nothing in this Policy reduces rights available under applicable law. Contact support@inrgift.com for closure assistance.
8.9 Separate actions and consent implications
Closing an account, cancelling paid renewals, disconnecting Google sign-in, withdrawing marketing permissions and exercising a statutory deletion right are separate actions. The UI must explain each consequence without creating deceptive friction or combining unrelated choices. The user must not be required to provide optional marketing consent as a condition of closing the account.
8.10 Eligibility and requester identity
A deletion request should be linked to an authenticated account or another proportionate identity-verification process. Contacting support from an email address alone may not prove control of a private research profile. Ensure that staff cannot delete another member's notes without authorisation and that requests by authorised representatives are supported only where relevant law and evidence permit.
8.11 Pre-closure checklist and exports
Present active subscription details, upcoming renewal, saved research count, research exports, shared records and the expected loss of account access. Export eligible original content in a documented format, while respecting provider licences and excluding restricted raw datasets or copyrighted charts. Warn users that some exported calculations may refer to source data they may not have redistribution rights for.
8.12 Deletion orchestration and exceptions
After verification, revoke active sessions, terminate optional messaging, mark the account for deletion, remove eligible application records and coordinate processors according to contract. Account records, security logs, tax records, payment disputes, consent receipts, legal holds and disaster-recovery backups require different retention decisions. Report accurately whether deletion is complete, staged, limited or legally deferred.
8.13 Shared and published materials
If later collaboration or publication features exist, a user's account closure may affect shared access, team ownership and content already lawfully accessed by others. The product should distinguish private default notes from deliberately published material and explain what can be withdrawn or de-identified. No hidden public copy of private saved research should survive because of a broken permission boundary.
8.14 Confirmation and appeal
The user should receive a reference number and a truthful completion/exception notice. A permanent account closure should not be represented as reversible if it is not. Where a request is rejected or limited, explain the legally permitted reason and provide a contact or challenge channel, without revealing security-sensitive internal details.