Account Deletion Policy

Effective date: 6 November 2026

1. Permanent deletion You can request permanent deletion of your Lighthouse account and associated data. This is different from logging out, uninstalling the app, temporarily deactivating an account or cancelling a subscription. Operator: LH Infra Mesh Private Limited. This page must use the same app/developer identity as the relevant App Store and Google Play listings.

2. In-app route Required implementation: Settings → Account → Delete account → review the consequences → proportionate identity confirmation → confirm deletion. Keep the option easy to find. Do not force ordinary users to telephone support or send an email as the only way to initiate deletion inside the iOS app. A confirmation step may protect against accidental deletion, but must not be a retention or sales obstacle. If the app uses Sign in with Apple, revoke the relevant tokens as part of deletion. [CONFIRM whether this authentication method is used.]

3. Web route Canonical public route: https://lighthouseinfra.com/delete-account/. W05 supplies the website page copy. Test its request mechanism and the in-app initiation route before submitting the URL to Google Play. The page must load without the app, prominently name Lighthouse, explain what is deleted/retained and allow a request through a working form, deletion control or monitored request channel. A user must not have to reinstall the app. Provide a fallback for someone who cannot sign in, with proportionate proof of account control. Do not ask for full identity documents when a less intrusive verification method is adequate.

4. What happens to data Delete ordinary profile/account data, user-created portfolio content, private project files, saved preferences and associated AI history within the confirmed operational process, except for clearly identified data that must lawfully remain. Remove or appropriately anonymise account-linked reviews and contributions consistent with legal requirements and app-store rules. Do not retain identifiable public content indefinitely under a blanket perpetual licence. Delete relevant derived indexes and embeddings and send deletion instructions to processors. Independently controlled seller or professional records may remain where they have their own lawful duties; explain this distinction to the requester.

5. Limited retention Some transaction invoices, payment/tax records, required intermediary registration or removed-content records, security evidence and valid legal-hold material may need to remain. Restrict access and use to that purpose and delete when the obligation expires. Tell the user the categories retained, reason and duration or objective expiry rule. An open dispute may justify retaining its necessary evidence, not every photo, profile field and future marketing permission. Backup copies expire under the stated cycle and must not be restored into active use without reapplying deletion. [CONFIRM actual backup period.]

6. Timing and confirmation Proposed service target: complete ordinary active-system deletion within 30 days after proportionate verification, subject to shorter applicable law. Engineering must validate this target before publication and provide the actual backup-expiry period. Acknowledge the request, explain material restrictions or necessary retention, and confirm completion. Tell the user promptly if an exceptional delay is necessary and identify the lawful basis; do not use an indefinite “processing” status.

7. Orders, payments and subscriptions Explain effects on open orders and provide a way to access required receipts or resolve claims. Do not automatically cancel third-party contractual obligations by deleting an account. Clearly explain subscription cancellation and stop Lighthouse-controlled renewals appropriately. For store-managed subscriptions, provide the relevant cancellation route. Outstanding payment or warranty records may be preserved narrowly; they do not automatically block the deletion of unrelated data.

8. Contact and product acceptance Questions or complaints go to the confirmed privacy/grievance contacts. The developer must test deletion for every login method, role-switched account, business-admin situation and logged-out web request; verify processor deletion, backup expiry and store disclosures. This draft is policy and implementation specification. A legal page alone does not satisfy the functional account-deletion requirements.

9. Initiating and verifying a request The account settings must provide a clearly discoverable route to request permanent deletion. The external web route must work without reinstalling the app and must identify Lighthouse clearly. An ordinary request must not be forced through a telephone call or email-only process where store rules require an in-app initiation route. Verify identity proportionately using an existing authenticated session or a secure recovery method. Do not ask for a full government identity document when a lower-risk check is

sufficient. If the person cannot access the registered phone or email, provide an alternative recovery and verification process. Explain the consequences before final confirmation: loss of profile access, removal of controlled public content, treatment of open transactions, business workspace membership and any narrowly retained records. Do not use repeated confirmation screens or misleading labels to obstruct deletion.

10. Multi-role and organisation accounts A user with buyer and reseller roles should be told whether deletion removes both roles or only one business membership. Leaving an organisation, transferring administrator responsibility and deleting a personal account are different actions. A departing employee cannot erase an employer’s lawful business records or another contributor’s intellectual property merely by deleting a personal login. Conversely, continued business record retention must not justify retaining unnecessary personal-profile or marketing data. Resolve disputed authority before deleting a shared workspace. Where the sole administrator requests deletion, offer a proportionate transfer or export step if needed, without creating an indefinite obstacle. Deletion should not silently transfer a company account to an unverified person.

11. Deletion propagation and confirmation The deletion task must cover active account records, public profile and portfolio copies within Lighthouse’s control, authentication tokens, unnecessary contact data, uploads and derived search/OCR/AI indexes, subject to lawful exceptions. Send processor requests where required and track completion. Invalidate sessions and revoke connected sign-in authorisations where required, including the appropriate Apple sign-in token process when used. Explain separately how to cancel an app-store subscription where the store controls billing; retaining the account must not be a condition for stopping renewal. Provide a confirmation or status update through the requested channel where feasible. If part of the request is refused or delayed, identify the category, reason, applicable period or criterion and review route. The proposed 30-day ordinary service target is not a substitute for a shorter or differently measured legal deadline.

12. Retained records, backups and public copies Transaction invoices, fraud evidence, required intermediary records and litigation holds may require narrow retention. Segregate retained information from ordinary product use and marketing. Do not keep the entire account merely because one invoice must be preserved. Backups must age out under the actual approved cycle. If restored, reapply pending deletions before ordinary access. A deletion notice must not claim instant backup erasure if the architecture does not support it. We cannot guarantee removal of copies independently and lawfully held by others or search-engine caches outside our control. We will remove controlled copies and take further

steps required by applicable law. A saved reference inside Lighthouse must not become a new independent licence to keep publishing withdrawn content.

13. International rights and children For EU/EEA or UK rights requests, apply the applicable one-month framework and lawful extension conditions. For covered California requests, apply the relevant 45-day framework and permitted extension, while opt-out requests follow their own rules. Explain these distinctions in the Privacy Policy and operate a single intake that routes correctly. If an account is found to belong to a child contrary to eligibility rules, restrict further unnecessary processing and apply a suitable verified-parent or legal-representative route where appropriate. Do not use the ordinary account holder’s acceptance as a substitute for legally required parental authority.

14. Request scope and confirmation The deletion process must distinguish deleting one project, closing a role, leaving an organisation, cancelling a subscription and permanently deleting the personal account. The user must receive a clear explanation before confirming a destructive action. Optional deactivation may be offered, but must not replace a permanent-deletion route where required. A user who cannot sign in must have an accessible alternative verification route. The process must not require reinstalling an unavailable app, purchasing support or supplying disproportionate identity documents. Verification must protect against a malicious person deleting someone else's account.

15. Shared workspaces and organisation ownership Deleting a person's login does not necessarily delete a company's independently controlled invoices, order records or shared project files. Lighthouse must explain the relevant distinction and remove or restrict the individual's unnecessary personal information as required. A business administrator cannot use ownership of a workspace to refuse every personal-data request. Where the departing person is the only administrator, the process should provide an appropriate opportunity to transfer authorised control or securely export available data, without using that step to obstruct deletion indefinitely. A disputed administrator change should be separately assessed.

16. Public content and contributor rights A deletion request should address the user's public profile, uploaded assets and controlled derivative descriptions. Where another party has an independent right to retain a collaborative project record, Lighthouse should assess the particular material and attribution rather than automatically delete the entire collaboration or continue displaying everything. Withdrawal of a licence must stop future uses within its scope. Content removed from a public page should not remain available through search previews, recommendation cards or an AI-generated retelling under Lighthouse's control. Legal evidence copies must remain restricted.

17. Deletion jobs and residual copies The operational process must identify active databases, object storage, search indexes, derived AI records, analytics identifiers and relevant providers. Where a system cannot immediately delete an immutable backup, restrict use, document the expiry cycle and reapply deletion if the backup is restored. A completion notice must accurately distinguish completed deletion from identified backup or legal-retention exceptions. Lighthouse must not certify that all data has been erased while a usable ordinary copy remains. A failed provider deletion or queued job requires follow-up rather than silent closure.

18. Financial, security and legal exceptions Outstanding orders or disputes may justify retention of specific evidence but do not justify keeping the whole account available for marketing or profiling. Record the category retained, purpose, access restriction and review or expiry condition. A legal hold must be limited to relevant records. Fraud-prevention retention should be necessary and proportionate and must not become a permanent secret blacklist without lawful grounds and appropriate review. Where law prevents disclosing a particular retained record, Lighthouse will provide the information it lawfully can.

19. Billing and communication after deletion Explain separately whether a subscription renewal has been cancelled and whether any app-store action remains necessary. Deleting the account must not be falsely presented as cancelling a payment mandate if the technical or contractual process requires another step. Provide the available route and confirmation. Necessary messages concerning a refund, remaining dispute, security issue or legally required notice may continue through an appropriate verified channel. Optional marketing must stop in accordance with the user's choices. A minimal suppression record may remain to prevent the person from being re-added to a marketing list.

20. Re-registration Creating a new account does not automatically restore previously deleted content or revoke an earlier opt-out. Relevant lawful fraud or transaction records may remain linked only as permitted. Lighthouse should not repopulate a new profile with an old portfolio without a valid current basis and appropriate user choice.