Privacy Policy
Effective September 29, 2026
StayTonight is operated by MilePost Labs, LLC, a one-person company run by Mark Fugel (“Jersey Mark”). Throughout this page, “I” and “me” mean MilePost Labs, LLC. This page explains, in plain English, what information the app collects, why, where it goes, and what control you have over it. If you have any questions, email me at mfugel@milepostlabs.com.
What I collect
- Your account. When you sign in, my authentication provider (Clerk) gets your email, name, and — if you sign in with Google — your Google profile photo. That's the bare minimum to keep you logged in across devices.
- Your camping profile. Your rig length, hookups, camping style (the 1–5 weights), POI preferences, theme, and saved favorites are stored in my database so they sync across devices when you sign in.
- Your home address (optional). If you choose to enter one in Preferences, it's saved with your account. I use it only to make trip planning easier; I don't share it.
- Your location, when you ask for it. If you tap “Current Location” on the search form, your browser sends approximate coordinates so the app can find nearby spots. The coordinates are used for that search and aren't stored long-term.
- Voice recordings, only when you use the 🎤 button. Your audio is sent to OpenAI's Whisper service to transcribe to text and then discarded; only the text fills the search field.
- Standard server logs. Vercel (the host) records basic request metadata — IP address, timestamps, user-agent — for security and debugging, per its own policy.
- What you put in the Journal — the stays you record, your bucket list, gear and meals lists, and any photos you attach. Stored under your account and shown only to you (details below).
How I use it
Strictly to run the service: rank places to sleep, remember what you like, let you sign in across devices, and respond to bugs or feedback. I do not sell or share your personal data, and there are no advertising or tracking cookies in the app.
Your Journal, photos, and Google Photos
The Journal is your travel log: the stays you record (place, dates, coordinates or a town, notes, ratings), your bucket list, gear and meals lists, and any photos you attach. All of it lives under your account and is shown only to you. The app also uses your own past stays to inform your future recommendations — that never leaves your account.
Photos you add are shrunk on your device before upload (which strips camera metadata such as GPS tags) and stored in a private Vercel Blob store. They have no public web address; the app serves each one only to the signed-in account that owns the stay.
Google Photos is optional. If you connect it, StayTonight asks Google for one permission only: to open Google's own photo picker (the photospicker.mediaitems.readonly scope). The app cannot browse, search or list your Google Photos library. It receives only the specific photos you choose in Google's picker, copies them into your private store as described above, and closes the picker session. It keeps a Google token so it can open the picker again for you, and holds no other Google data. You can disconnect at any time with the Disconnect Google Photoslink in the Journal, which revokes that token, or from your Google account'sthird-party access page. StayTonight's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Third-party services I use
Running StayTonight means sending small pieces of data to a few specialized services. Each one gets only what it needs to do its job:
- Clerk — handles sign-in, sessions, and account management.
- Neon — the database that stores your preferences, favorites, and Journal (stays, lists, and photo records).
- Vercel — hosts the app and serves the pages; a private Vercel Blob store holds your Journal photos.
- Google — only if you connect Google Photos: opens Google's photo picker and hands back the photos you chose (see the Journal section above).
- OpenAI — ranks tonight's candidates against your preferences and (optionally) transcribes voice input.
- Service data providers — Recreation.gov (RIDB), OpenStreetMap, Geoapify, NOAA / NWS, OpenCellID, USGS, AirNow, EIA, and MapLibre tiles. When the app queries these, it sends a location (and in OpenCellID's case, an approximate radius), not your account or personal details.
Each of these has its own privacy policy. I've picked services that don't require your personal information.
Cookies and local storage
The app uses a session cookie from Clerk to keep you signed in. It also uses your browser's localStorage to cache your preferences and favorites for instant load — that cache mirrors what's in the database. There are no advertising or third-party tracking cookies.
To see how many people visit and which pages they use, the site counts visits with Vercel Web Analytics. It sets no cookies, doesn't follow you to other sites, and gives me totals (pages viewed, the site that sent you, country, device type), not a profile of you.
Keeping and deleting your data
I keep your account, preferences, favorites, Journal entries, lists, and photos for as long as your account is active. You can delete them at any time:
- Open ⚙ Preferences → Profile and click Delete account. That removes your profile, Journal, and photos from the database and storage, revokes any Google Photos connection, and signs you out. Some platform logs (e.g. Vercel access logs) may persist until they auto-rotate, per the host's policy.
- You can also email me at mfugel@milepostlabs.com and I'll handle it.
Children
StayTonight is not directed at children under 13 and I don't knowingly collect data from them. If you believe a child has signed up, email me and I'll delete the account.
Your rights
Most of the data the app holds about you is visible inside the Preferences panel. To access, correct, or delete it, sign in and edit your profile, or email me. Depending on where you live (e.g. California, the EU), you may have additional rights — happy to respect them; just ask.
Changes to this policy
If anything material changes (new third-party service, new data type), I'll update this page and bump the effective date. For substantial changes I'll also surface a notice the next time you sign in.