Google maps is great, but it has missing features and a bunch of bugs. I made this after getting increasingly frustrated with google maps for urbex.
Google maps worked just well enough for me to keep using it for years. But eventually, I had to make something that did the things I wanted, the way I wanted them.
Not really.
It's almost the opposite. This is an antisocial media site.
Social media sites center around sharing things broadly, and only reel it in as exceptions. Everything is some version of "public" by default, because that's the point of social media. So it's easy to find people, and to be found, and easy to make your thoughts and content visible to the world.
UrbanLens centers around private tools, just for you. The social components of the site are the exceptions to the core functionality, and that core functionality doesn't require anyone else to be a useful tool. Here, it's easy to be invisible, and easy to keep your content private, just for you.
Yes, as in speech and beer; UrbanLens is free, and open source. It's run by one person, who pays for hosting, and every other expense out of pocket. Some external APIs are limited for that reason. You can check out the source code on our GitHub page.
It's not out of the question that I'll offer subscriptions in the future to access some features that would cost me a lot of money to support. For instance: AI tools. If I do that, I won't ask anyone to pay for stuff that doesn't cost me money. The point is to make a tool for people, not to create a business.
Really? That's the standard for success? Come on.
It depends on what you mean by "reliable". But, no.
UrbanLens is still in beta, and I'm still working on it. I wrote the code all from scratch, and it's hosted on my own server that I built myself in my basement. I can't stress enough that I'm just one person.
I promise to do my best to keep the site up and protect any data you store on it. But you should not store anything on this site that you don't have another copy of somewhere else, and you shouldn't give up any other tools you're currently using quite yet.
I've put a ton of work into ensuring that you can use the site anonymously until you make an intentional decision to be more public. If you want even more anonymity, you have three options:
Yes - you can import pins from a whole bunch of other places. Every imported pin is shown to you for review before anything is saved. See the pin import guide for details.
No. Every pin is private by default. Sharing is opt-in and granular - you choose whether to share a pin with specific friends, a trip, or no one at all. Big, obvious confirmation dialogs will be shown to you before anything gets shared.
Correct. Nobody. Not even me.
The site is setup very carefully to ensure that no one has any special privileges to your data. The privacy controls you set apply to everyone, even the site admin. You can verify this by looking at our code. The version we're running shows at the bottom left of every page, and if you're not a programmer, AI tools can help you understand the codebase and verify your data is safe.
But let's also have a reality check, because I think setting good examples is important.
Anytime someone else owns the hardware your data is stored on, there is a pathway for them to see your data. Even if your data is encrypted, the hardware owner could intercept the data before encryption, or brute force the encryption key. If any mapping site out there tells you they can't see your pins without telling you this caveat, they're lying to you.
In order to get past this problem, I put a ton of time into designing something that didn't even store coordinates on my server. If you look back through the git history, you can probably find a bunch of notes I wrote about it. I experimented with several ideas, and got part of the way through designing a peer-to-peer network before I came to the conclusion that this problem might be intractable.
So the best I can do is show you every line of code in my application, and promise that I won't hack into my own software in order to see your pins. And if you're worried about it, you should take my code and put it on your own machine, where nobody has access except you.
Please don't trust anyone who doesn't explain this to you, and makes you assurances they can't keep.
A wiki is only accessible to people who already have the pin on their map.
It's entirely separate from your personal pin. It's opt-in, so most wikis are going to be blank, unless someone decides to add information to them.
The core idea behind a wiki is that sharing exploring information is hard. Sometimes you want to share updates with other explorers who already know about the place, but you don't want to broadcast the location to people who don't. Wikis let you share information exclusively with people who already have the pin, so you can freely share any information you'd like without worrying about publicizing a vulnerable place.
Yes. Trips support RSVPs, member management, and shared itineraries with per-trip and per-pin privacy controls, so you can coordinate an expedition without exposing pin details. Only people you invite to the trip can see anything, and even then, you can make some pins even more private; people on the trip who don't have the pin will see "Secret Location", until you're ready to share the exact location. Is this overkill? Probably.
I like automating things. So I automated things.
There are lots of ways to make this easier.
I'm just one person, and I bought a lot of hard drives, but I don't have unlimited space. I gave a few GB to people I've never met, and a little bit more to my friends. It adds up pretty fast.
You can see how much space you have on your profile page. Uploaded images are automatically optimized to help you fit more within your quota without losing meaningful detail.
The site tries its best to pull in supplementary data, and filter out the junk that doesn't apply. So it can show things like Wikipedia summaries, historical imagery, weather, and relevant public datasets - to help you research a location before you visit.
When these external APIs are contacted, we only send the minimum amount of data needed to get a relevant response. That usually means just the name of the place, or the coordinates.
You can turn this off during registration, or from your settings page.
When you go to a new place, you're supposed to tell a trusted friend where you're going, and ask them to check in on you when you're supposed to be back... but oh gosh, I never got in that habit. Plus, what am I supposed to do when I'm going somewhere secret, and I don't want to advertise its location? I guess if I get hurt, I just die.
A safety check-in lets you save all the details of the trip ahead of time, without sharing it with anyone until you don't come home. Only then are they contacted to help find you.
You should understand there are downsides to this approach, and you shouldn't rely on it as your only safety plan. Since your contacts aren't notified until after you're in trouble, they might be busy and just not see the message for hours, or days. Emails might end up in a spam folder. They could see that you sent a message to 3 other people, and assume one of the other 3 will do the job, so they can go to bed. The site could go down, and not send the notice out at all!
I added this feature because I wanted it for me, and the people I care about, but you should keep doing the safety stuff you already do in addition to using this feature. This shouldn't replace the safety stuff you already do.
In addition, you should choose your contacts wisely, and make sure they'll do the thing you want them to do if they get a message. If you send a poorly worded message to your grandma, she's going to call the police on you after your phone dies.
Yes. Safety check-ins support notifying contacts by email in addition to other UrbanLens users, so the people who need to know you're overdue don't need an account of their own. They don't need to login. They just need to click a link in their email.
Once contacted, they will see a map you drew of where you're going, and a trip plan you wrote for them. They'll also be able to send messages to one another, in case one of them gets important information the other people need to know.
No one who doesn't have an special link to the check-in page can see the page or those details, and no one but you can see it until you don't check in.
Yes. Any data we store about you is visible on your own profile page or your account Settings - there's no hidden user data on UrbanLens that isn't displayed back to you. We don't even store your ip.
But it's time for another reality check about ip addresses.
UrbanLens relies on services from other open source software, too, like a web server to handle your web traffic, a caching layer to make the site fast, and more. Some of those services see details about you, like your ip address, just because of the nature of web traffic. Sometimes those details are put into log files. I rotate those log files regularly, and no one without access to my server could ever see them in the first place... but, that's no reason not to use a VPN. They cost like $3 a month.
The site data is stored on a RAID 10 array, so multiple drives need to fail before any data is lost. It's backed up as reasonably close to 3-2-1 as I can manage. The drives are encrypted on the server at rest, and only decrypted when the server is online. Any sensitive data in the database is also encrypted at rest on top of that. HTTPs also encrypts your data in transit, and direct messages are end-to-end encrypted on top of everything above.
Regular database backups are run automatically and kept for a long time. Cloudflare, and other infrastructure, provide several additional protections for site reliability. The codebase has a rigorous CI/CD process that tests it for vulnerabilities every time it's changed, and it's automatically run through an AI that tries to identify any issues that managed to sneak in.
There's also an export tool, so you can make your own backups and import them somewhere else any time you'd like.
I could go on. I'm proud of it... but you still shouldn't count on it to store anything you can't bear to lose.
Yes. Account deletion is available from your profile settings and removes your personal data from UrbanLens. The site gets rid of all of it, and I really mean all of it.
You have 1 week to undo the deletion, and during that time your data will still exist on our servers in a separate backup file that isn't visible on the site. If you don't undo the deletion, your data will be gone forever.
There's an export tool you can use to get a copy of your data before you do that.
Your direct messages are end-to-end encrypted. That's a fancy way of saying: they're scrambled on your device before they're sent, and only you and the person you're talking to can unscramble them. Even if someone hacked into the site and stole the entire database, they wouldn't be able to read your messages.
To make that work, your browser generates a secret key for you the first time you log in. That key is what actually unlocks your messages. Normally you never think about it - your password unlocks it automatically, on any device, every time you log in.
The recovery key is a backup plan for the one situation your password can't cover: if you ever reset your password using the "forgot password" email link, the site can't use it to unlock your old key the normal way. Same thing if you signed up with Google or Discord and never set a password at all, and you're logging in from a brand new device. In both of those cases, the recovery key is what lets you keep reading your old encrypted messages instead of losing access to them.
So... save it somewhere safe when the site shows it to you. A password manager is perfect for this. If you ever lose both your password-based access and your recovery key, there's genuinely no way for anyone, including me, to get your old encrypted messages back - that's the tradeoff for that level of privacy. You can always start fresh with a new key from Settings, you'll just lose access to messages sent before that point.
One caveat: attachments like photos and shared maps in direct messages aren't encrypted yet, just the text of the messages themselves. Also... this only protects against someone getting a copy of the database - it doesn't protect you if someone in the real world steals your unlocked phone. Obviously.
UrbanLens is built and maintained by one person, not a company. It started as a personal tool for me, then for a small circle of friends, and it's growing from there.
Immich is a self-hosted alternative to Google Photos. It's a free, open source photo and video management app you run yourself, on your own hardware. Like UrbanLens, it's built around the idea that you should own your own data.
If you already run an Immich server, you can connect it under Settings, which will allow you to search and import photos near a pin straight from that pin's detail page, instead of having to find them by hand. This will only work if you have location metadata stored in the photos you take.
UrbanLens only talks to your own server using the API key you provide - nothing gets sent anywhere else.
API keys are generated from your own Immich server, not from UrbanLens:
Paste that key, along with your server's URL, into the Immich connection form under Settings. If you ever lose the key, just generate a new one on your Immich server and reconnect.
If you ever want to disconnect your Immich server, go back to Immich and delete the API key, and UrbanLens will no longer have an ability to access it.
Explore what UrbanLens can do, or jump straight in.