The Life At app and its Life at Charlotte campus service form an independent student-built dashboard. This policy explains what the app collects, why, and the choices you have. It describes what the app actually does.
What the app collects
- Your account. Creating an account stores your email and your password as a salted hash; the password itself is never stored or logged. Browsing as a guest stores neither: a guest board runs under a random identifier tied to a cookie in your browser, and when that cookie expires or is cleared there is no way back to it.
- What you put in your workspace. Goals, tasks, calendar events, class schedules, notes, uploaded-file text, key ideas, and study sets. You provide this, and the app stores it so it persists. Uploaded source files are read for their text and are not kept as files.
- Chat messages you post in the shared student chat or a friend group, and reports you file in the shared student chat.
- A profile photo you choose to add to your public friend profile.
- Your public friend profile. The app stores the name on your board and assigns a permanent six digit # number. It also stores friend requests, friendships, group membership, and your sharing choices.
- A home or living location, only if you add one. If you enter an address, it is sent to the U.S. Census geocoder to place a pin. A location you mark private is stored with your own account so your map works across your devices and is kept out of vault exports. It reaches a friend or group only while living location sharing is on for that view. A pin captured from your device cannot be shared.
- Anonymous click counts. The website and the app keep a daily tally of which buttons and tabs get pressed, so we know what to improve. A tally holds the screen and the control's name, never your account, a guest id, your network address, or anything you typed.
What the app does not do
- It does not sell your data.
- It does not put personal data in URLs or query strings.
- It does not log your address or your chat contents to third parties.
- It does not track your device location. Friend map pins come from saved schedules. If nothing shared is scheduled, the map shows no current pin.
- It does not read your student-portal or learning-management-system account. You provide an exported schedule or calendar feed yourself.
How your data is stored and protected
- Workspace, notes, friend, group, and chat data are stored in the app's database.
- While a note is waiting to sync, the app keeps a recovery copy in this browser under the signed-in account and campus. It lets the same account recover work after a connection or session problem. The copy is removed after a confirmed save or when that account is deleted.
- API responses are marked private and are not cached by shared caches.
- Address lookups go only to the fixed U.S. Census endpoint.
- To slow down password guessing, the app counts recent failed sign-ins against a one-way hash of the network address and the email that was tried. The counters cannot be read back as an address or an email, they clear when you sign in, and they are discarded within a day.
- To limit friend search and request abuse across app servers, the app keeps recent request counts under one-way hashes of the account key and network address. Old windows are cleared during later use, and account deletion clears that account's counters.
- After account deletion, the app keeps only an opaque internal account key and a one-way proxy identity link. They contain no email, profile, workspace, messages, or friend data. They stop an old session or delayed request from restoring deleted data. Contact the address below if you later want to start again with the same upstream sign-in.
Third parties
- Map tiles come from OpenStreetMap. Loading the map sends tile requests to OpenStreetMap, subject to their policy. "© OpenStreetMap contributors" is shown.
- Address geocoding uses the U.S. Census Geocoder for addresses you enter.
- Public campus search for organizations, events, research, courses, professors, and careers queries public sources for the campus you selected and links you back to the source. You sign in at the source, not here.
Your choices
- Edit or delete anything in your workspace at any time.
- Choose what friends can see. Class schedules, other plans, schedule based pins, and living pins start on for new accounts and each has a control. You can set a main rule, then change it for one friend or group. Turning off all sharing overrides every other setting.
- Delete your account and personal data. The Profile area erases your workspace, friend links, requests, groups, messages, feedback, reports, seat watches, seat alerts, and push tokens. Only the security keys described above remain.
Seat alerts
Seat alerts are for UNC Charlotte classes and need an account. This is everything they keep, why, who handles it, and how long it stays.
- Your watches. The term, course, section, CRN (class number), and title you watch, when you made each watch, when it ends, and the latest public seat count for it. I use them to know which sections to check and who to tell.
- Your alerts. Each opening I told you about: the section, the seat count and the time Charlotte's Banner class search showed it, when the phone alert went out, and when you saw it. They make the history on your seat list and keep you from getting the same alert twice.
- Your email address. Seat alerts do not email you for now, and they keep no copy of your address.
- Your phone's push token, only if you allow notifications. The iPhone app sends the token Apple gives it, the app's build number, and when it was last seen, so Apple can deliver alerts to that phone. The phone keeps a copy of the token too.
- Nothing about you goes to UNC Charlotte. The checks run on Life at Charlotte's servers and ask Banner's public class search about a course or a section, never about a person. The university does not get your name, email, or watches from me.
Who handles it:
- Cloudflare runs the database and the checks.
- Apple delivers phone alerts through its push service (APNs), which receives your phone's token and the words of the alert.
How long it stays:
- Checks for a Spring 2027 watch end after Jan 19, the last day to add a class. Ended watches stay on your list until you remove them or delete your account.
- Stopping or removing a watch deletes it and any alert from it you have not seen yet. Alerts you have already seen are kept, out of sight, until you delete your account.
- A push token is deleted when you sign out of the iPhone app, turn seat alerts off there, sign in to another account on that phone, when Apple says the token no longer works, or when you delete your account.
- Deleting your account deletes all of it: watches, alerts, and push tokens.
To stop, use STOP on your seat list, or turn off notifications for Life At on your phone or in your browser. To have your seat data deleted without deleting your account, write to support@lifeatcarolina.com.
Children
The app is intended for university students and is not directed to children under 13.
Chat safety
Slurs are blocked and profanity is masked automatically. Messages in the shared campus chat and friend-group chat can be reported, and their authors blocked, on both campuses. Reports are reviewed within 24 hours. If the app becomes aware of child sexual abuse material, it will report it to the National Center for Missing & Exploited Children as required by law.
Changes
Material changes to this policy will be posted here with a new date.
Contact
Questions about this policy, a data request, or something to report: email liam.gergen@gmail.com.