Privacy notice
Career Compass is a student prototype built at KCL FirstYearHack on 21 November 2026. This page describes what the app's code does today. It has not had a legal review.
What other people see
- On the compass: only signed-in people whose app reports a position within 500 m of yours, and only while you are visible and your own app is reporting a position.
- In the People tab: anyone you have invited, or who has invited you, keeps your name, your picture, what you do, your LinkedIn link and your tags in their list. That does not depend on distance, and it stays after you go invisible, sign out or decline.
- Your name, your picture, what you do, your LinkedIn link, and what you offer and are looking for.
- Your picture is shown on your card on the compass and next to your name in the People tab. It is the photo you picked on the profile form. If you picked none and signed in with LinkedIn, it is your LinkedIn picture, for as long as LinkedIn's link to it works. Otherwise it is a coloured tile with your initials.
- The picture is loaded from an address that contains a random ID for you and does not ask for sign-in. Anyone who has been shown that address (everyone who has had you on their compass or in their People tab) can load your current picture from it later, including after you go invisible or sign out. It gives a face or initials, never a position or an email address.
- A direction and a distance to you, measured from the position their app reports. The app never sends your coordinates to another user and shows no map, but a direction and a distance from a known spot are enough to work out where you are to within GPS accuracy, and the app does not check that the other person is really where their app says.
- If you sign in with email (through Logto or with a code we email you), your email address is never shown to other users. The name box is pre-filled with the part of your address before the @; change it if you do not want others to see that.
If you sign in with LinkedIn
- You are sent to LinkedIn to sign in. LinkedIn then tells the app its own ID for you, your name (full, given and family), your email address and whether LinkedIn has verified it, the link to your profile photo, and your language setting. LinkedIn may leave the email out.
- LinkedIn does not tell the app your profile address or what you do. The LinkedIn link other people see is the profile share link you paste on the profile form (only its
linkedin.com/in/…address is kept), and the app does not check that it is yours. The app cannot read your profile address from LinkedIn's cookies or from a LinkedIn tab, and does not try. - The app reads this at the moment you sign in, and again only when you sign in again, never in the background. The access LinkedIn grants is used for that one read and is not kept. The app asks LinkedIn only for sign-in, your basic profile and your email: it does not ask to post for you, to read your connections or to send connection requests. “Connect on LinkedIn” only opens the other person's LinkedIn link.
- The name box is pre-filled with your LinkedIn name; you can change it. Other users see that name and your picture. Your LinkedIn email address, LinkedIn's ID for you and your language setting are never shown to other users.
- Signing out of Career Compass does not sign you out of LinkedIn. On a shared device, sign out at linkedin.com as well.
What is stored, where and for how long
| What | Where | How long |
|---|---|---|
| Profile: name, what you do, LinkedIn link, what you offer and seek | The app's database in London. On the live site at wayrise. | Until it is deleted. To have your account and invitations deleted, ask the team. |
| Your latest position and its accuracy | The app's database (see above). One row per person: each update replaces the last, so the app keeps no history. Both database services can restore replaced or deleted rows for a short period: Neon within its restore window, Snowflake through Time Travel (1 day by default, then 7 days of Fail-safe). | Shown to others for at most 45 seconds after your last update. “Go invisible” deletes it. Signing out, closing the page, or your phone refusing location asks the server to delete it, but that request can be lost (no signal, or the phone closes the browser); the last position then stays in the database, not shown to anyone, until your app next reports a position, which replaces it, or your account is deleted. |
| Invitations you send or receive, and whether they were accepted | The app's database (see above) | Until your account is deleted |
| A hash of your session token (not the token itself) | The app's database (see above) | Until your account is deleted. Signing out removes the token from your device only; the hash stays on the server and the token keeps working until you sign in again with LinkedIn or with email, which replaces it. An account made with “Try the demo without an account” cannot be signed in to again, so its token keeps working until the account is deleted. |
| If you sign in with a code we email you: your email address | The app's database (see above). If you also sign in with LinkedIn, and LinkedIn says your LinkedIn email address is this same address and is verified, both sign-ins open this one account; otherwise they are separate accounts. | Until your account is deleted. To have it deleted, ask the team. |
| While you sign in with an emailed code: your email address, a keyed hash of the code (not the code itself; the key stays in your browser), its expiry and wrong guesses; and, for each code sent, the time with a one-way hash of your address and of your internet (IP) address | On the live site at wayrise. | The code record: until it is used or after 5 wrong guesses; once its 10 minutes are up it is removed the next time anyone signs in by email. The send records: one day. In a laptop server's memory, all of it is also lost when the server restarts. |
| The email with your code: your address, the code and the time | Resend, the email service that sends it for us from hello@wayrise.app (its EU region, Ireland). Resend handles it under its own privacy policy. | Resend keeps a record of sent emails under its own policy. |
| If you sign in with email: your sign-in ID and email address | The app's database (see above), and the team's own sign-in server (Logto, at auth. | Until the team deletes it in both places. |
If you sign in with LinkedIn: your sign-in ID, which is LinkedIn's ID for you with linkedin| in front | The app's database (see above), with your profile. Your LinkedIn email address is not put there. | Until your account is deleted. “Delete my LinkedIn data” does not remove it: it is how the app recognises you when you sign in again. |
| If you sign in with LinkedIn, the LinkedIn record: LinkedIn's ID for you; your name, given name and family name; your email address and whether LinkedIn says it is verified; the link to your LinkedIn photo; your language setting; the LinkedIn profile address you pasted; LinkedIn's answer exactly as the app received it; and the times it was first recorded and last read | The app's database (see above), in a table of its own. In Snowflake only once the team has switched on the extra tables (see the note below). | Until you delete it with “Delete my LinkedIn data”, or the team deletes it. Each time you sign in with LinkedIn it is replaced with what LinkedIn says then; the first-recorded time is kept. |
| The photo you pick on the profile form, if you pick one. Your device crops it square and shrinks it to a 256 px JPEG before sending it; the original file is not uploaded. | The app's database (see above), in a table of its own. In Snowflake only once the team has switched on the extra tables (see the note below). | Until the team deletes it. Once your profile is saved, the page has no button yet to change or remove the photo. |
The LinkedIn record and the photo need two extra database tables. On the live site they exist from the start. On 21 November 2026 the team had not yet switched them on in its Snowflake account; until it does, when the app runs on Snowflake the app saves neither of them anywhere, no LinkedIn picture is shown, and everyone's picture is the tile with initials. Signing in with LinkedIn still creates your account, with the sign-in ID above and the name LinkedIn gave.
Your LinkedIn photo itself is not stored. When someone's app loads your picture and you have picked no photo, the server fetches it from LinkedIn's link and passes it on, so that person's browser does not contact LinkedIn.
If the app runs without a database (for example in an offline demo), the same data is kept only in the server's memory and disappears when it restarts.
When the team puts the app on phones, it is reached through a temporary https address from Cloudflare that leads to the team's laptop. Everything your phone sends to the app and gets back, including your position and your session token, passes through Cloudflare's network on the way.
On your device
| Name | Type | Purpose |
|---|---|---|
cc.token | Local storage | Random session token that keeps you signed in. Removed when you sign out. |
cc_consent | Cookie, up to 6 months (Safari may shorten this to 7 days) | Remembers your choice in the “Before you start” dialog, including “No thanks”. It holds the choice, a random ID and the time you chose. |
| Sign-in check values | Session storage | Only during email sign-in. Deleted as soon as you come back from the sign-in page. |
cc_ec | Cookie, up to 10 minutes, only readable by our server | Only while you sign in with an emailed code. A random key that lets only this browser use the code. Removed when you sign in. |
| Sign-in session cookies | Cookies set by the sign-in server on its own address | Only if you sign in with email. They keep you signed in there until you sign out. |
cc_li_state | Cookie, 10 minutes at most. Page scripts cannot read it (HttpOnly), and it is sent only to the app's own LinkedIn sign-in addresses (path /api/linkedin, SameSite=Lax, Secure on https). | Only if you tap “Sign in with LinkedIn”. A random value that ties the return from LinkedIn to this browser, so that a sign-in link made in someone else's browser cannot sign you in to their account. Deleted when the sign-in completes or is turned down on the way back from LinkedIn; otherwise it expires by itself. |
| LinkedIn's own cookies | Cookies set by LinkedIn on its own address | Only if you sign in with LinkedIn. LinkedIn's own privacy policy covers them. Signing out of Career Compass does not remove them or sign you out of LinkedIn. |
| Pictures of people you were shown | Browser cache, up to 5 minutes | So a picture is not fetched again on every update. Other people's browsers keep yours the same way. |
There are no adverts, analytics or tracking cookies.
If you reply to a sign-in email, the reply goes to hello@wayrise.app, which forwards it (through Cloudflare's email routing) to a team member's inbox.
Why we use it
Only to point your compass at people nearby and let you invite them. We ask for your agreement before you start, and you can change your mind at any time. Your phone asks you separately before it shares your location; an iPhone also asks before sharing its motion sensors.
Of what LinkedIn tells it, the app today uses LinkedIn's ID for you (to recognise you when you sign in again), your name (to pre-fill the profile form), the link to your photo (to show your picture) and, only when LinkedIn says it is verified, your email address (so that if you have already signed in with a code sent to that address, you get that same account instead of a second one), and it tells you in the People tab what it keeps. The rest (your language setting and LinkedIn's answer as received) is kept in the LinkedIn record for a possible later feature; no code uses it today.
Demo people
During demos the app can place made-up “demo people” around you. They are not real users and are marked as demo data in the database. Their pictures are always tiles with initials, never photos.
Your choices
- Go invisible, or sign out, at any time: both buttons are under “Demo tools and what runs underneath” on the compass screen.
- Refuse location access. The app never makes up a position for you: without one from your phone it reports none, you are on nobody's compass, nobody is on yours, and the page says why and what to do. If you had been sharing a position, the app asks the server to remove it. People you have exchanged invitations with still see you in their People tab. In demo mode the page then offers “Use a demo position instead”; only if you tap it does the app report a fixed demo position (Bush House, London) as yours and show your profile to people near that spot, including everyone else who chose it.
- If you signed in with LinkedIn: see what the app keeps from LinkedIn, and delete it, in the People tab under “Your LinkedIn data”. “Delete my LinkedIn data” deletes the whole LinkedIn record described above: your LinkedIn email address, the link to your LinkedIn photo, your language setting, the name parts, LinkedIn's answer and the copies of LinkedIn's ID and of your profile address held in it. It does not delete your account, your profile in the app (including your name, which first came from LinkedIn, and the LinkedIn link you typed), a photo you picked, your invitations, or the sign-in ID that holds LinkedIn's ID for you. Your picture then becomes the photo you picked or your initials; a browser that has already loaded the old picture may go on showing it for up to 5 minutes. The record is made again the next time you sign in with LinkedIn. Like positions, deleted rows can be restored by Snowflake for a short period.
- Change your agreement:
- Ask the team to delete your account, your photo and your invitations. The app itself has no button for that.
Last updated 21 November 2026.