Account Deletion
Email emylou2086@gmail.com to request deletion of your CampusFinder 2.0 account without installing or updating the app. Production account-deletion protections and fulfillment are not yet fully deployed. Requests remain pending until safe fulfillment is available; no automatic deletion or fixed completion time is promised. Supported versions also offer Settings > Data & Privacy > Request account deletion. A request is not completed deletion.
Ordinary accounts
Email support, or save an in-app request where available and then email support. Support verifies control of the registered email and inventories legacy and nested private records. The prepared fulfillment procedure disables account access, removes the private document tree and owned drafts, deletes the Firebase Authentication account and verifies cleanup. Protection against still-valid sessions depends on updated Security Rules that are not yet deployed. Requests remain pending until safe fulfillment can proceed; no completed deletion is claimed in advance.
Administrator records
Identify any former administrator role in your request. The owner verifies account ownership, revokes access, removes private drafts and reviews personal identifiers in publication/audit records. Institutional map content remains independently of the deleted account. Administrator audit identifiers follow the 24-month retention period from each activity, with documented legal or security exceptions. A saved request does not automatically notify support: email emylou2086@gmail.com.
Without the Android app
Email emylou2086@gmail.com with the subject CampusFinder account deletion. Prefer sending from the account email address. Include the email used to sign in and whether you were an administrator; your UID is optional if known. Do not send passwords, verification codes, access tokens or identity documents. Support must verify control of the registered email before deleting anything. Opening an email draft does not send it: review and send it in your mail application. Receipt and fulfillment are not confirmed by this page.
Completion and retries
The operator verifies server deletion before confirming it and explains any retained institutional identifiers or documented exceptions. Interrupted server cleanup remains processing and can be retried using the same request. Account access is disabled once fulfillment starts. Server completion does not remotely erase local device storage, Firestore caches, exported files or copies on other devices. Support provides instructions to clear app storage on devices you control and review exported copies; do not assume uninstalling alone deletes the server account.
Request and correspondence retention
Requests and correspondence are retained while processing. The policy is to remove completed request records, verification files and correspondence 90 days after completion through reviewed manual maintenance, unless a documented legal obligation or dispute requires retention. A deletion lock is removed only after the account and known private records are absent; processing or unresolved cases retain protection. Preserved operational backups have a separate custody and expiry review, as explained in the Privacy Policy; they are not automatically purged at 90 days. Exceptions need a reason, approver and review date. No automatic scheduling or fixed response time is promised.