Legal
Privacy Policy
Last updated:
The short version
- Students and visitors use the NaviCampus app without a name or password. Giving an email address is optional; we use it to tell you when the iOS and Android apps are ready.
- Your route settings and your last 20 routes are saved with your app profile on our servers so the app can suggest where you're going. Routes are worked out on your phone.
- The app uses your location only if you allow it, on your phone, to show where you are and route you from there. It is never sent to us.
- "Delete my data" in the app's settings erases your profile, contact details and recent routes.
- University staff who use the dashboard have an account with their name and email, and we record who changed which map.
- We don't sell data, and we don't show ads.
1. Who we are
NaviCampus ("NaviCampus", "we", "us") is operated from Sharjah, United Arab Emirates, started by students at the University of Sharjah. You can reach us at [email protected] for privacy requests and support, or [email protected] for university partnerships. This policy explains how we handle personal data across the NaviCampus app (the iOS and Android apps and the early-access web version at navicampus.app/app), this website and the staff dashboard (sign-in, dashboard, map editor and admin pages).
Universities decide what goes on their campus maps. For the staff accounts a university asks us to create, we process data on that university's behalf.
2. The app (students and visitors)
This section applies to the iOS and Android apps and to the early-access web version alike.
No sign-up. When you open the app, it signs in to our backend anonymously. This creates a random identifier that is not linked to your name. Your app profile (below) is stored under this identifier.
Email address (optional). During setup the app asks for an email address. You can skip this and use the app fully without it. If you give one, we store it with your app profile and use it to let you know when the NaviCampus iOS and Android apps are ready. We don't use it for marketing, and we don't sell or share it. Only the NaviCampus team can see it; universities' staff accounts can't. The app no longer asks for a phone number, and it removes any number saved by an earlier version from your device and our servers.
Settings. Your preferred route mode (for example fastest or air-conditioned) and whether route suggestions are turned on are saved with your app profile on our servers, so they're kept if you reinstall or switch devices.
Recent routes and suggestions. The app saves your recent routes to your app profile on our servers. Each entry holds the campus, the start and end places (their IDs and names) and when you took it. We keep up to your last 20 routes and use them to suggest places you're likely to go next. They're linked to your app profile and, if you gave one, your email address.
Routes. The app downloads a campus map and calculates routes on your phone. Apart from the recent routes described above, we don't receive what you search for.
Location. The app asks for permission before it uses your location. If you allow it, your location is used only on your phone to show where you are on the map and to start routes from there. It is never sent to or stored by NaviCampus. You can say no, or withdraw permission later in your phone's or browser's settings; you can still choose a starting point by hand. In the web version, location only updates while the app is open.
Delete my data. The app's settings have a "Delete my data" option. It permanently erases your recent routes and your profile (settings and email address) from our servers.
Analytics. The app doesn't include an analytics or advertising SDK.
Feedback (optional). If you send feedback, by shaking your phone in the app or through the feedback form on this website, we store your message and its category, your email address if you add one so we can reply, and details that help us understand the problem: where it was sent from (iOS, Android, the web app or the website), the app version, the screen or page you were on, the university and campus you had open, your browser or device description (user agent) and, from the app, your anonymous app identifier. We use it only to fix problems and improve NaviCampus, and the NaviCampus team gets a copy by email. Only the NaviCampus team can read it.
Your app identifier. The anonymous identifier described above doesn't expire at the moment. It contains no personal details.
3. The staff dashboard
If your university gives you a NaviCampus staff account, we process:
- Account details: your name, email address, your role and which university you work for. If you sign in with Google, Google shares your name, email and profile picture with us.
- Sign-in data: your password is handled by our authentication provider and is never visible to us. Sign-in times are kept by that provider.
- Activity on maps: which account created, edited, submitted, reviewed, published or archived a map or campus, and when. This keeps a clear record of who changed what.
- Content you upload: site maps, location names, notes and photos. Once published, map content (not your name or email) is public in the app.
The map editor's "Pick on map" feature loads satellite and street map tiles from Esri and OpenStreetMap, and place searches you type are sent to OpenStreetMap's Nominatim service. Those providers receive your IP address and the search text under their own privacy policies.
4. This website
The website is served by Cloudflare, which processes technical request data such as your IP address to deliver
and protect the site. Fonts are loaded from Google Fonts. We don't use advertising cookies or cross-site trackers.
We store functional preferences locally in your browser's storage (localStorage keys
navicampus_theme, navicampus_active_univ, and tour completion flags, plus
sessionStorage key navicampus_intro_played); those settings never leave your device for
tracking. We use Cloudflare Web Analytics to count visits and see which pages are used and how fast they load. It doesn't use
cookies, doesn't store your IP address and doesn't follow you across other websites.
Campus directory lookup counts. When you click "Get directions" on a
destination card on /campuses or a campus
page, the site increments an aggregate counter (university ID, campus ID, destination ID, name, Arabic name, code,
category and total count) in Firestore (campus_analytics) so universities see which destinations are
most searched. No IP address, account ID, or personal data is recorded with those counts.
Mobile app waitlist (optional). If you join the launch waitlist on
/waitlist, we store the email address,
platform preference (iOS, Android, or both), optional university name, marketing consent choice, source page,
timestamp, and browser user agent string you submit so we can notify you when the mobile app launches and, if you
checked the optional box, when new university campuses are added. Any unlisted university name you enter is also
saved to our requested universities list (university_requests, without your email) so it appears as
a suggestion to other visitors.
5. Why we use data
- To provide the app and the dashboard, and to let staff sign in (performance of our agreement with your university).
- To keep the service secure, prevent abuse and keep an audit trail of map changes (our legitimate interests).
- To understand, in aggregate, how the website is used so we can improve it (our legitimate interests).
- To send account emails such as password set-up and reset links.
- To read and answer feedback you send us, and to fix the problems it reports (our legitimate interests).
- To suggest routes from your recent routes and keep your settings (to provide the app you asked for).
- To tell you when the iOS and Android apps are ready, using the email address you chose to give (your consent, which you can withdraw by deleting your data). Never for marketing.
We don't sell personal data, use it for advertising, or make automated decisions about people with it.
6. Where data is stored and who processes it
We use these service providers, which process data only to run NaviCampus:
- Google Firebase (Google Cloud): authentication, database, file storage and server functions. The map database is hosted in the Middle East (Dammam, me-central1); server functions run in the United States (us-central1).
- Cloudflare: website hosting and delivery, and privacy-friendly visit statistics (Web Analytics).
- Expo (EAS Hosting, delivered through Cloudflare): hosting of the early-access web app. Like any web host, it processes technical request data such as your IP address to deliver the app.
- Google (Gmail): delivers the email copy of feedback to the NaviCampus team.
- Esri and OpenStreetMap: map tiles and place search in the staff map editor.
Some of these providers may process data outside your country. Where the law requires it, transfers rely on appropriate safeguards offered by those providers.
7. How long we keep it
- Staff accounts are kept while your university uses NaviCampus and you have access. Ask your university admin or us to remove your account.
- Archived universities, campuses and maps are deleted automatically 30 days after they are archived.
- Published map content stays in the app until the university or NaviCampus removes it.
- Anonymous app identifiers don't expire at the moment.
- Your app profile (settings and email address) and recent routes are kept until you use "Delete my data" or ask us to delete them. Only your last 20 routes are kept; older ones are replaced.
- An email submitted to the launch waitlist is kept until the launch notification is sent or until you ask us to delete it.
- Feedback is kept while it helps us improve NaviCampus, or until you ask us to delete it.
- Aggregate campus destination lookup counts (which contain no personal identifiers) and requested university names are kept as aggregated directory metrics while the listing is active.
8. Your choices and rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, to object to or restrict how we use it, and to complain to a data protection authority. App users can erase everything we keep about them at any time with "Delete my data" in the app's settings, or by emailing us. Staff can ask us, or their university admin, for a copy of their data or to delete their account. We'll answer within the time the law requires.
9. Security
All traffic is encrypted in transit. Access to data is enforced by server-side security rules: staff can only change their own university's maps, only reviewers can publish, and each app user can read and change only their own profile and recent routes, and only the NaviCampus team can read app users' contact details. No system is perfectly secure, and we'll tell affected people and authorities about a breach when the law requires it.
10. Children
NaviCampus is made for university campuses. Apart from the optional email address, the app doesn't ask for personal details, and we don't knowingly collect personal data from children.
11. Changes to this policy
If we change this policy, we'll update the date at the top. For significant changes affecting staff accounts, we'll also let universities know.
12. Contact
Questions or requests about privacy, including access or deletion requests: [email protected].