← Back to Career Compass

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

If you sign in with LinkedIn

What is stored, where and for how long

WhatWhereHow long
Profile: name, what you do, LinkedIn link, what you offer and seekThe app's database in London. On the live site at wayrise.app that is Postgres, run by Neon for Vercel; when the team runs the app from a laptop it is Snowflake, London (UK South) regionUntil it is deleted. To have your account and invitations deleted, ask the team.
Your latest position and its accuracyThe 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 acceptedThe 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 addressThe 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) addressOn the live site at wayrise.app: the app's database (see above), so every server that answers you sees the same code. When the team runs the app from a laptop without a database: only in that server's memory.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 timeResend, 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 addressThe app's database (see above), and the team's own sign-in server (Logto, at auth.dustpowered.studio), which emails the one-time code. That server is shared with the team's other project, Cila, so your email becomes a sign-in account there as well.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 frontThe 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 readThe 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

NameTypePurpose
cc.tokenLocal storageRandom session token that keeps you signed in. Removed when you sign out.
cc_consentCookie, 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 valuesSession storageOnly during email sign-in. Deleted as soon as you come back from the sign-in page.
cc_ecCookie, up to 10 minutes, only readable by our serverOnly 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 cookiesCookies set by the sign-in server on its own addressOnly if you sign in with email. They keep you signed in there until you sign out.
cc_li_stateCookie, 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 cookiesCookies set by LinkedIn on its own addressOnly 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 shownBrowser cache, up to 5 minutesSo 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

Last updated 21 November 2026.