Privacy Policy
CampusFinder 2.0 is developed by Emylou Codamon. Contact emylou2086@gmail.com for support, privacy questions or account deletion. This policy describes the available features and distinguishes planned security changes from controls already in production.
Account information
When you register or sign in, Firebase Authentication processes your email, display name, account identifier and authentication credentials. Passwords are handled by Firebase Authentication, not stored as readable passwords in the app. Firebase may process service and security information such as IP addresses and user agents.
Cloud and local records
Firestore can store an account profile (UID, email, display name, last-seen timestamp and app version) and optional private backups. Favorites are saved in account-specific Isar storage and published maps are cached locally in current client source. The updated publishing workflow separates administrator attribution into restricted audit records, but this workflow and its Security Rules have not yet been deployed to production. Published revision and upload metadata can contain administrator UIDs until reviewed retention cleanup; shared map content must not be assumed anonymous.
Location and map requests
Foreground precise or approximate location is requested when you use location-dependent features. Navigation reads location and calculates routes on the device. The app does not upload a navigation location history to Firebase. Administrators can deliberately record walking paths and publish coordinates or upload them in a backup. OpenStreetMap tile requests include the viewed map area, IP address and app user agent; centering on your location can reveal the area you are viewing. Optional image URLs contact their respective hosting providers. Location therefore must not be described as entirely on-device.
Providers and sharing
Firebase provides authentication and Firestore storage. OpenStreetMap provides map tiles. Information is transmitted to those providers to operate these features. You can explicitly export and share map files using Android sharing. This build does not integrate advertising, Firebase Analytics, Crashlytics or messaging SDKs. Provider operational logs may still exist. Firebase and map-tile service requests use HTTPS in remote configurations. Optional image URLs depend on the configured host and scheme. Isolated local test builds use emulator connections.
Storage and protection
Production Firestore Rules restrict private account records to their authenticated UID owner. The updated Rules add claim-plus-registry administrator authorization and deletion locks, but are not yet deployed. Once enabled, campus publications will be publicly readable, while private drafts and audit attribution are restricted to authorized administrators, not exclusively to the administrator who created them. These controls do not guarantee absolute security or erase previously downloaded copies. Exported files are outside app-private storage. Encryption of every local database or user export is not promised.
Deletion and retention
Email emylou2086@gmail.com to request deletion, including if your installed version has no request screen. In supported versions, Settings > Data & Privacy can save a request after reauthentication; this does not notify support or complete deletion. Support verifies registered-email control and reviews all private records, including nested legacy data. The prepared operator procedure removes private cloud records and drafts, deletes the Authentication account and verifies cleanup. Its old-session deletion-lock protection requires the updated Security Rules, which are not yet deployed; a request stays pending until safe fulfillment is available. Shared institutional maps are preserved and administrator attribution follows the separate retention schedule. Server deletion cannot remotely wipe devices or exports. On shared devices, obtain the other users' agreement before clearing all app storage.
Backups and recovery
An encrypted operational backup may retain older account and private-record data after active records change. The existing backup is preserved for recovery review; no automatic backup expiry or off-device key recovery is in place. The developer must review backup custody and expiry by 14 November 2026 and reconcile later deletions before restoring data to service. The 90-day completed-request schedule does not mean every backup copy is automatically purged. Any minimal deletion-suppression record retained for the life of an approved backup needs a documented purpose, restricted access and reviewed expiry.
This legal website
Firebase Hosting serves these pages and may process request information such as IP addresses for service operation and security. These pages contain no analytics scripts, advertising, account sign-in, submission forms or application cookies. Email links open your mail application; sending a message shares its contents with the email providers involved. A page visit or opening an email draft does not submit a deletion request.
Retention schedule
Administrator personal identifiers are retained for 24 months from the recorded activity, then removed by operator-run maintenance unless a documented legal or security exception applies. Immutable institutional events and nonpersonal publication history remain while needed for CampusFinder operations, recovery and rollback. UID hashing or pseudonymization is not treated as anonymization. The maintenance tool removes known identifying metadata; the owner must separately review free-text content, legacy records, backups and support correspondence. Completed deletion-request records and associated correspondence are removed 90 days after completion unless a documented legal obligation or dispute requires retention. Exceptions record a reason, approver and review date. There is no automatic scheduled cleanup on the current Spark setup; the owner must run and verify maintenance when records become due. Missing dates or incomplete cleanup are reported for review, not silently treated as completion.
Choices and contact
You can browse cached map information without signing in, deny location permission in Android settings, and avoid optional backup/export features. Contact Emylou Codamon at emylou2086@gmail.com for privacy questions or deletion requests. Updates will be identified with an approved effective date.