Privacy policy

You start a search with a ZIP code, a street address, a city name, your browser’s location, a dragged pin or a link someone shared.

A ZIP code goes to our server, which turns it into a point on the map. Georgia ZIP codes are in a table we keep ourselves, so looking one up sends nothing to anybody else. One we do not have is looked up with Geocodio, and if that returns nothing, with Nominatim, the OpenStreetMap geocoder. Only the five digits are sent to them.

A street address goes to our server and on to Geocodio, which returns the point it stands at. Geocodio is sent the address and nothing else about you, and we do not save the address in our database unless you save it on your account. Your browser is told to keep the answer for a day; no shared cache is allowed to.

To fill the map, your browser asks our server for the jobs in fixed squares of Georgia, each about 10 miles across: the squares the part of the map on your screen touches while it is zoomed in, those within about 5 miles of the point you chose (10 miles when there are no jobs within 5), and the square of the location you have selected, or of one a link you opened points to. When the map is zoomed out, it also asks for one count of jobs per square across the state. The requests name the squares and nothing else. They do not carry the point you chose, your filters or what you typed in the search box: your browser applies those itself. The server does not save the request.

The employers directory still asks by point. If your browser holds the point you last set on the map, the directory sends it, rounded to a grid about half a kilometre wide, to our server so it can show which employers have jobs near you. The server does not save it.

Your browser keeps your last ZIP or point and your filters in its own storage (wj_prefs:v1) so the map opens where you left it. A copy saved by an earlier version of the site may still hold a distance you chose; nothing reads it. It also keeps the referral tag from the link you arrived on (wj_utm_source:v1) and, if you joined the waitlist, a note that you did (wj_waitlist:v1, wj_signup_id:v1). If you are signed in and have saved a home address, your browser keeps a copy of it (wj_home:v1) so the map can open on it without waiting for our server; signing out removes that copy. On a phone-sized screen it also keeps how far open you left the job list (wj_sheet:v1), for that tab’s session only. Clearing the site’s data in your browser removes them all.

The map itself is drawn from CARTO’s basemap tiles, which your browser fetches from CARTO directly.

If you are signed in and have saved a home or set a starting point on the map, a job’s page can show how long it takes to walk, bike and drive there. Our server measures from the home saved on your account. If you have not saved one, your browser sends our server the starting point you last set on the map in that browser.

If you are signed in, a job’s panel on the map shows these times too. There your browser sends our server the point the panel measures its distance from, so the times and the distance start from the same place: its own copy of your saved home if you have one, and otherwise the starting point you set on the map.

The server rounds the point it measures from to about 250 metres and sends it, with the job’s location, to Mapbox, which works out the routes. A job more than 30 miles away in a straight line is not sent: it reads as over an hour away. Mapbox is sent nothing else about you: not your address, your account or your network address. Our server saves neither the rounded point nor the times. Your browser keeps the times it has shown you in the page’s memory, not in its storage, and can show them again without asking when the trip is the same: the same job, on the map or on its own page, or another job at the same place on the map, from a starting point our server would round to the same point. A saved home and the map’s starting point that round to the same point count as the same. Closing or reloading the page, or signing out, clears them.

We count how many routes the site asks Mapbox for each month, which says nothing about who asked. So that no one account can use up the month, we also keep, for each account, how many it asked for today: the account, the date and the count. That record is deleted once the day is over, the next time anyone’s travel times are worked out, and straight away if you delete your account.

When the map finds no jobs within 10 miles of your starting point, with no filter or search on, we save the area so we know where to add coverage: the ZIP, the point rounded to about a kilometre, whether it came from a ZIP or your browser, that 10-mile distance, and the referral tag if there was one.

If you give us your email to hear when we cover the area, we add it to that record. We also send the email and the same fields to PostHog, our analytics service, so the signup shows up alongside your other activity on the site.

The contact form on the About page stores your name if you gave one, your email, your message and the page it came from.

Claiming an employer from the employers directory, an employer’s page or an employer’s page for one city stores your name if you gave one, your work email, the employer you named, your role and note if you gave them, and the page you claimed from.

The feedback dialog stores your message, your email if you gave one, and the page you were on. A thumbs up or thumbs down on its own goes to PostHog as a rating and is not stored with a message.

Submissions that fill in a hidden field meant for bots are dropped, not stored.

A report stores which job it is about, the reason you picked, a note if you wrote one and your email if you gave it. PostHog gets the reason and where you reported from.

If we remove the job a report is about, the report is deleted with it. What we keep is a count of the reports that job had and the reasons picked, without your note or your email.

Every request to the site carries your network (IP) address, as on any website. Our server uses it to count requests per address for a short window, a minute for map and location lookups and ten minutes for forms and reports, so that no one client can flood it. Travel time requests are counted for a minute, per address and per account. These per-minute counts live in the server’s memory and are never written to the database; the daily count of travel-time routes is described under Travel times above.

We use PostHog to see how the site is used and where it breaks. Your browser sends it page views, the actions you take on the map (setting a location, changing a filter, opening a job, clicking apply or copying the number or address a job gives to apply to, saving a job or removing one), the links you follow to an employer’s jobs in one city, and any error the page hits. Saving or removing a job sends the job’s title and employer and where you did it; because you are signed in when you do, that event is linked to the email address on your account.

My jobs reports each status you set, the status it replaced and where you set it, and one event for every other change, such as a note, a next step, a correction, or hiding, removing or adding a job, naming only which kind of change it was. The words you write, the pay and the links you enter are never sent, and neither is which job it was. These events are linked to the email address on your account too.

Some of those events carry what you entered. Each time the map loads results, PostHog gets the ZIP you typed, the point rounded to about a kilometre, the filters, any search text and how many jobs came back. A location request reports whether your browser granted it and how accurate the fix was, not the coordinates. A waitlist signup is tagged with your email, so events from that browser link to it.

Creating an account sends one event when the form is accepted, carrying whether you chose Looking for work or Hiring and nothing you typed in it. The account page reports that you opened it, that you changed your name, your password, your home address or the My jobs setting, and that you deleted the account. Which one you changed is sent; the name, the password and the address never are.

Asking to link your account to an employer reports that you sent a request, whether the employer was on our list, and how you relate to it. Which employer you picked, the business name and the website are never sent to PostHog. The report is linked to the email address on your account.

From an account linked to an employer, adding a location reports that you added one and whether we placed it or are checking it. Posting a job reports that you posted one, whether it is full-time or part-time, whether you gave pay, which of a link, a number for text messages and an email address you gave for applying, and the industry you chose. Closing a job reports that you closed one. Opening the preview of a job reports that you opened one and whether the job was hidden, visible, closed or removed. An account owner adding a person reports that one was added, and nothing about the address. The address, the job’s title, description and apply link, phone number or email address, the employer and a client company are never sent to PostHog.

The requests go through our own domain to PostHog’s servers in the United States. PostHog keeps a visitor id in a cookie and in your browser’s storage to tell one visit from the next. After a waitlist signup that id is your email.

The site is in English and Spanish. It opens in the language your browser asks for, and the address says which: Spanish pages start with /es.

If you follow the language link, or open an address in a language your browser did not ask for, your browser keeps that choice in a cookie (NEXT_LOCALE) for a year, so the site opens in that language next time. The cookie holds en or es and nothing else.

Every analytics event carries the language of the page it came from. Following the language link sends one more, naming the two languages and the page you were on.

Anyone can create an account with an email address and a password, or with a Google account. We can also make one for you, as described below, when we add you to an employer. An account holds your email address, your password if you set one, the role it was given (member, employer or admin; an account you create is a member), whether you chose Looking for work or Hiring if you created it with an email address, the name you typed on the account page if you gave one, the date you last changed your password through the site, the date and time recorded for your welcome email, as described under Emails we send, and what Google shared if you use it, as described below. Supabase stores all of it. Choosing Hiring grants nothing; it means that confirming your email, or continuing with Google from Create account, takes you to the employer account page, and that the welcome email you then get is the Hiring one.

If you save a home address on the account page, that account also holds the address you entered and the point it resolved to. We use them to open the map on your home and to measure jobs from it. They are not shown to employers or to anyone else. The account also keeps a distance in miles that the site no longer uses. Clearing the address and saving deletes it with the rest.

My jobs is a list on your account of the jobs you are pursuing. A job lands on it when you save it, or when you press Apply on a job, or copy the phone number or email address it gives to apply to, while signed in, unless you turn that off on the account page. We never see the application itself, since you apply on the employer’s own site or the job board its listing links to, or in a text message or an email you send from your own phone or mail app, so the list holds only what happened here and what you tell it: which job, with its title and employer as they were then, and when it arrived, each status you give it and when, your notes, the next steps you add (the kind, the date and time, how and where, and a note), your own version of the job’s type, schedule and pay, and whether you have hidden it. A job you applied to elsewhere and add by hand holds the title, the employer and the link you type; we do not open the link or look up anything about it. A job stays on the list after the employer closes the posting, or we drop it from our listings, marked closed. Saving a job, or pressing Apply on it or copying its number or address, more than six months after you last updated it starts a new entry, and the earlier one stays with it.

Only you can see My jobs. It is not shown to employers or to anyone else, and we never sell it. We use it only to improve WalkableJobs, looking across everyone’s lists together, for example to decide which job sites to add from the ones people apply on. Unsaving a job that has nothing else on it, or removing a job from the list, deletes it and its notes straight away; the Undo offered just after a removal puts back the copy your open page still holds.

On the employer account page you can ask for your account to be linked to an employer, once. The request stores the employer you picked from our list, or the business name and website you typed if we do not list it, how you relate to the business, when you asked, and whether and when we approved or declined it. We read it beside your account’s email address to decide. Approving it links your account to that employer and gives the account the employer role; the page then names the employer. While it waits, and if we decline it, the request is not shown to the employer or to anyone else. It cannot be changed or withdrawn on the site; email hello@walkablejobs.com to do either.

More than one account can be linked to the same employer. Everyone linked to an employer sees, on the People page, the email address of every account linked to it and the date each was linked, with the first of them marked as the account owner. Each of them also sees, edits, shows, closes and renews every job posted for that employer, whoever posted it, and can add locations. The People page is not shown to anyone else.

We can also add you to an employer ourselves, given your email address, and so can the account owner of an employer, from its People page, until five accounts are linked to it. Whoever adds you types only your email address. If that address already has an account you have confirmed, we link it. If it has none, we make an account for it and link that, so the address, its link to the employer and its place on the People page are stored before you have signed in or agreed to anything. An account that someone created by signing up with the address, and that was never confirmed, is deleted and made again, so that a password chosen for it earlier does not carry over. An account owner who types your address is told only that it was added or that it was not. When it was not, they are not told why. Unless the answer is that their own employer already has five accounts, or that something failed and they should try again, being told it was not added does mean the address has an account tied to another business, because nothing else gets that answer: one linked to another employer, one another employer has added, or one with a request waiting. They are not told which. We send that address an email saying so, as described under Emails we send. If you did not want the account, email hello@walkablejobs.com and we will delete it.

Once your account is linked to an employer you can add locations and post jobs for it. An address you add is stored with your account, the employer and when you sent it. Our server sends the address, and nothing else about you, to Geocodio to find where it stands; if Geocodio cannot place it, OpenStreetMap’s Nominatim and the U.S. Census Bureau’s geocoder are asked. A placed address becomes a location of that employer, and an address we cannot place exactly also goes on a list we work through by hand. A location is public once a visible job is posted at it.

A job you post stores its title, description, location, whether it is full-time or part-time, how people apply (a link, a phone number that takes text messages and an email address, whichever of them you gave), the industry you chose, the experience level, shifts, availability and minimum age if you gave them, the pay if you gave it, and which account posted it. It starts hidden, and a hidden job is shown only on the listings pages of the accounts linked to that employer. When you make it visible, everything in that list except which account posted it is published under the employer’s name: on the map, on the job’s own page and on the employer’s page. A phone number or an email address you give for applying is printed on the job for anyone to read and copy while the job is open. A job seeker’s text or email to it goes from their own phone or mail app straight to you; we never see it. A visible job closes when you close it, and by itself 30 days after you made it visible or last renewed it. A closed job leaves the map and the employer’s page, and its own page stays up, marked closed, for 30 days.

If we remove a job you posted, we delete what was published. A page that already showed the job, its own page included, can go on showing it for about a day. Your record of the job stays in your listings, marked removed, and we store when we removed it and a note of why, which is not shown on the site. You cannot edit it or make it visible again unless we lift the removal; the listing links to the contact form to ask us to review it.

If you are the account owner of an employer and asked to be linked as an external recruiter, you can add a client company to a job posted for it. It is stored with the job and shown only on your own listings pages: the other accounts linked to that employer can edit the job but are not shown the client company and cannot change it. The account owner is the account that was linked first, so if that account is deleted or unlinked the next one becomes the owner and, if it is an external recruiter’s, is shown the client company on the jobs that remain. It is never published, and it is not part of anything we send to PostHog. If we remove the job, it stays in the record we keep of it, described below.

Your name, your home address and the My jobs setting change on the account page, and are yours to edit or clear; the email address cannot be changed there. When your password changes, on the account page or through an emailed link to set a new one, the site tries to sign out every other browser and device. If it could not, the account page tells you; the page the link opens does not. My jobs changes on its own page, and where you save a job or press Apply.

Deleting your account from that page removes the account, your name, your role, your saved home address, everything in My jobs, your employer request or link, the record of the addresses you added as an employer, our record of the jobs you posted with any client company on them (with the one exception below), the record of your welcome email and the day’s travel-time count immediately, and we cannot undo it. The jobs you posted leave the listings of everyone else linked to the employer too. A job you had made visible is closed at once, as if you had closed it: what was published stays on its own page, marked closed, for 30 days. The locations your addresses became stay with the employer. Email hello@walkablejobs.com to have either removed. The exception is a job we removed and had not handed back when you deleted the account. We keep our record of it: the title, the description, the other details you typed for it, any client company included, and our note of why we removed it. We keep it so that we can recognise the same listing if it is posted again in breach of our terms. It is no longer tied to your account: beyond what you typed into the job itself it holds no name or email address, only the employer it was posted for, and it is not shown to anyone who posts for that employer later. We hold it until we delete it, and you can ask us to through the contact form. Anything you sent us separately, such as a message, a report or a waitlist signup, is stored on its own and stays until you ask us to delete it, or, for a report, until we remove the job it is about.

When you create an account, the email address and password you enter, and whether you chose Looking for work or Hiring, go to our server and on to Supabase, which keeps the accounts. Supabase emails a link to confirm the address through Resend, which receives the address and the message, and you can sign in once you have opened it. Asking for that link again sends only the address. If the address already has an account, neither the password you typed nor your choice replaces what it holds, and the page answers exactly as it does for a new address, so what you see does not say whether the address has an account.

If you ask for a link to set a new password, the email address you enter goes to our server and on to Supabase. When the address has an account, Supabase sends the link by email through Resend, which receives the address and the message. Either way the page tells you the link was sent, so what you see does not say whether the address has an account.

The new password you then choose goes to our server and on to Supabase, which stores it. We never see it and it is not kept anywhere else.

If you continue with Google, Google asks you, the first time, to agree to share your Google account with WalkableJobs, then sends Supabase its id, your name, your email address, whether Google has verified that address, the address of your profile picture and, for a work or school account, its organisation’s domain. Supabase stores them with your account and updates them each time you sign in with Google. We never receive your Google password. When Google has verified the address, an address with no account gets a new one with no confirmation email, and an address that already has an account signs in to it and links Google to it; if that account had never been confirmed, the password set on it is removed. Until you type a name on the account page, the page shows the name Google shared.

Connecting Google on the account page links the Google account you choose to the account you are signed in to, even when the two email addresses differ. Disconnecting it removes that link. Where the Google account’s address is not your account’s, Google no longer signs you in to it. Where it is the same, Continue with Google still signs you in to this account and connects Google again, as it would for any account with that address. What Google shared when you signed in with it stays with your account until you delete it.

Every email we send is about your own account and goes to the address on it, or, when you are added to an employer, to the address that was given for you. Supabase sends the ones that keep an account secure: the link that confirms a new account, the link that sets a new password, a notice that your password was changed, and an invitation if we invite you to an account.

Our own server sends the rest. The first time you sign in to a new account, it sends one welcome email saying what the account is for. There are two versions. With an email sign-up, you get the one that matches your choice of Looking for work or Hiring; with a Google sign-up, you get the Hiring one if signing in took you to the employer account page. So that you get it only once, your account records the date and time just before the email is sent, and deleting your account deletes that record with it. An account that existed before we began sending the welcome was marked the same way without being sent one.

When we approve or decline your request to link your account to an employer, our server sends one email to say so. It names the employer you picked or the business name you typed, and nothing else from the request.

When we or an account owner add you to an employer, our server sends an email to the address that was added. It names the employer. Adding the same address to the same employer again, before the account has been signed in to, sends another with a new link, and the earlier link stops working. If we made the account, its button holds a link that signs you in once, and you get no welcome email: the account is marked as welcomed when it is made. If you already had an account, the button opens the employer account page and you sign in as usual.

All of these are delivered by Resend, which receives the address and the message. A reply to a welcome, to an answer about your request or to a notice that you were added goes to hello@walkablejobs.com. None of them is sent on a schedule or for marketing, so there is nothing to unsubscribe from.

Eleven services run parts of the site and receive data as described above:

• Supabase stores the database: the listings and the records described above.
• Vercel serves the site, so every request passes through it.
• PostHog receives the analytics events described above.
• Google signs you in when you choose Continue with Google or connect Google on the account page, and sends Supabase the details of your Google account described above.
• Resend delivers every email described under Emails we send, so it receives the address each one goes to and the message.
• CARTO serves the map tiles your browser draws.
• Geocodio looks up a street address you type, an address an employer account adds as a location, and a ZIP code we do not have in our own table.
• OpenStreetMap’s Nominatim looks up a ZIP code Geocodio could not answer for, and an employer account’s address Geocodio could not place.
• The U.S. Census Bureau’s geocoder looks up an employer account’s address Geocodio could not place.
• Anthropic reads the description of a job an employer account posts, as it reads every listing’s, to pick out details such as pay and schedule.
• Mapbox works out the walk, bike and drive times on a job’s page and in the map’s job panel, from a starting point rounded to about 250 metres.

We keep a waitlist record, a message or a report until you ask us to delete it, or, for a report, until we remove the job it is about. Email hello@walkablejobs.com from the address you gave and we will remove it. What your browser stores is yours to clear. We do not sell any of it.

We may change this policy. When we do, the date at the top of this page changes with it, and using the site after that means you accept the new policy. Questions go to hello@walkablejobs.com.