Privacy
Privacy policy
This page says what davelalande.com collects when you use it, what happens to it, and what you can do about it. We wrote it from what the site's code actually does.
We do not sell your information.
Who runs this site
American Adventurer (davelalande.com) is made by Dave Lalande, who also runs the studio behind momatio.com and tinycorp.ai. A real person reads every message sent through the contact page. That page is the way to reach us about anything here.
This policy covers davelalande.com, its open data API (/api/) and its MCP server (/mcp). The other sites have their own pages.
The short version
- There are no accounts, no passwords and no ads. The site, the app and the MCP server set no cookies. There is no third-party analytics.
- Reading camp pages, the API or the MCP server needs no sign-in and no personal details.
- We keep an email address only if you give us one: in the contact form, the camp-correction form, the sign-up list, or by making a rig “kit.”
- Our server also records the internet address of anyone who calls the API, the page counter or a form, and of anyone who hits the MCP door (in the web server log). Calls through the MCP server are stored in the API log as a scrambled one-way code.
- There is no button that deletes your information. You can stop our emails with one click. You can ask us to remove you by hand. We do that within 30 days. See “What you can do.”
What we collect, and why
| What | What is in it | Why | How long |
|---|---|---|---|
| Web server log | Our web server writes an access log. It records the address that connected, the time, the page asked for (including anything after a ?, such as coordinates from “Camps near me”) and the browser name. | Running and protecting the site. | 14 days. The log rotates every day. |
| Page counter | When a page loads in a browser, a small request records the page path, the page you came from, your internet address, the time, and one letter saying whether you have a rig saved in that browser or linked to an email. Known search-engine and other robot visits are skipped. No cookie and no ID number is used. | To count which pages people use. | 120 days. Old rows are deleted automatically by a nightly cleanup. |
| API and MCP log | One row for each call to the API, including each lookup an AI assistant makes through the MCP server: the time, which endpoint, the search words, how many results came back, a guess at what kind of caller it was, the caller’s browser name and referring page, and how long it took. For a direct API call, the row holds the internet address. For a call through the MCP server, the row holds a scrambled one-way code made from that address. For “camps near” searches the position is saved rounded to one decimal of a degree (roughly 7 miles). Calls we turn away for going over the rate limit are not logged. | To see what people ask for, including what we do not have, and to keep the service running. | About 120 days. Old rows are deleted automatically after every 500th logged call. |
| Contact form | Your name (optional), email, what you drive, where you are headed, the plan you asked about, your message, which page the form was on, your internet address and the time. | To read and answer your message. | Until you ask us to remove it. We delete it by hand within 30 days. |
| Camp correction | On a camp page: the boxes you ticked, your note (up to 400 characters), the camp’s page name, your internet address, the time, and an email only if you choose to give one. | To check the page against the agency’s own record. A reader’s report never changes a page by itself. | Until you ask us to remove it. We delete it by hand within 30 days. |
| Sign-up list | The email, which form it came from, your internet address and the time. | Occasional news, starting with the spring launch. Nothing has been mailed to this list so far. Every mail will carry a one-click unsubscribe, built before the first send. | Until you ask us to remove it. We delete it by hand within 30 days. |
| Kit (saved rig and watched states) | The email, a long random key that makes up your private link, your rig numbers (people, tank sizes, propane and so on), the states you watch, your saved camps and forests, your filters, and the times it was made, changed and last opened. | So your rig follows you to any device, and so we can email you when new camps appear in the states you watch. | Until you ask us to remove it. We delete it by hand within 30 days. “Stop” turns the emails off and clears the watched states, but keeps the email, rig and saved camps until then. |
| Email we send you | The link to your kit, an email when new camps land in a state you watch, and a weekly season digest. Each carries a one-click stop link. We also keep a record of each digest sent: your email, the states, the number of changes, the sending service’s message number and the date. | To deliver what you asked for. | The send record is kept until you ask us to remove it. We delete it by hand within 30 days. |
| Copies of our own alerts | Every email our server sends is also copied (subject, recipient and the first 8,000 characters of the text, including any contact message or email address in it) into an internal alert register on the tinycorp.ai server. It is a database file on that server, not on a public page, and it is not in our own nightly database backups. | So we can check that mail went out and notice problems. | Until you ask us to remove it, like the message itself. We delete it by hand within 30 days. |
| Copies in our own inboxes | The same messages that go to the alert register also arrive in two mailboxes we use: team@tinycorp.ai (Namecheap Private Email) and Dave’s davelalande.com mailbox (Google). That covers contact messages, camp corrections, sign-up and kit notices, and your kit link. A monitor on our server reads team@tinycorp.ai every 4 hours, read only: it marks nothing and deletes nothing, and keeps only each message’s ID number. If a message looks like it needs Dave, the monitor emails him its subject and sender. | So a real person reads and answers you. | Until you ask us to remove it, like the message itself. We delete it by hand within 30 days. Nothing deletes these copies on a timer. |
| Server notes | The app writes a plain log file. It has lines such as the email on a new contact, sign-up or kit, the internet address behind it, and when a kit is stopped. | Troubleshooting. | Log files rotate every week and the last 4 rotated weeks are kept, so a line is gone after about 5 weeks. |
What stays in your browser
The site saves a few things in your own browser (local storage, not cookies): light or dark mode, your rig numbers, your saved camps and forests, and, if you made a kit, the key for it. These stay on your device unless you link them to an email. Clearing your browser’s site data removes them.
The “Camps near me” button on the home page asks your browser for your position only when you tap it. If you allow it, the position goes to our /api/near search to find camps within 60 miles. The API log keeps it rounded to one decimal of a degree, as described above. The web server log keeps the full page address, including those coordinates, for 14 days.
Who else receives information
These are the outside services our code actually talks to. We found no others.
- Namecheap Private Email (mail.privateemail.com) carries the email our server sends: the link to your kit, new-camp emails, and the notes sent to us when someone writes in or signs up.
- Resend (api.resend.com) carries the weekly season digest. It receives your email address and the digest text.
- Google Fi: when a contact form or camp correction arrives, a short text goes to Dave’s phone through the carrier’s email-to-text address. For a contact it includes the name and email you typed. For a correction it includes the camp and what you ticked. No more than 12 such texts are sent in a day.
- Google (Gmail) hosts Dave’s davelalande.com mailbox, so Google handles the copies of the notices above that arrive there.
- Google Fonts (fonts.googleapis.com and fonts.gstatic.com): our pages load their type from Google, so Google sees your browser’s address and the page you are on.
- Weather, fire, air and water sources. When a camp or town page shows a forecast, nearby fires, air quality or a stream reading, our server asks weather.gov (National Weather Service), NIFC (fire locations, through ArcGIS), AirNow (air quality, only when a key is installed) and USGS (stream gauges). We send the camp’s coordinates, or the coordinates your browser asked about. We do not send your internet address to them. They see our server, not you.
- The MCP server reads public files from davelalande.com and, for the game’s trip-code lookup, momatio.com. See the MCP section.
We do not sell your information. The code has no feature that gives your information to advertisers or data brokers.
The site makes no requests to outside map-tile services. Our web server’s content policy only allows images from our own site.
Our MCP server (davelalande.com/mcp)
An AI assistant can connect to https://davelalande.com/mcp to look up camps, forests and four-night trip plans. There is no sign-in and no key. The tools ask for places, dates, coordinates and rig numbers, not for anything about you.
What the MCP server itself does
- It stores nothing and writes no access log. Its code writes only crash messages.
- To enforce its limit of 120 requests a minute per address, it keeps a scrambled one-way code made from the connecting address in memory. The scrambling key is random and new each time the service starts. The rate limit still works per caller.
- It keeps short-lived copies of public answers in memory (from seconds up to a day).
What gets logged after that
Every lookup the MCP server makes goes to our own API, and the API log (above) records it. The MCP server passes a scrambled one-way code made from the caller’s address. The API log stores that code. The row also holds the time, the endpoint, and the search words or camp name the assistant asked for. A “camps near” lookup keeps the position rounded to one decimal of a degree. The assistant’s own browser name is not passed on; the row shows the MCP server’s. These rows are deleted after about 120 days.
Our web server’s access log also records each request to /mcp (address, time, size and result, not the content of the message). Those lines are kept for 14 days. If an AI company runs the connector, the address in that log may be the company’s server.
The trip_status tool reads one saved game trip from momatio.com using the code it is given. It only reads. It never changes the trip.
Please do not put personal details into a question to an assistant that you would not want in our log. The tools only need places and numbers.
What you can do
- Stop the emails. Every kit email has a “Stop” link. One click turns off all our emails to that address and clears the states you watch. Saving your kit again from your own link turns them back on. The news list has not been mailed yet. When it is, every mail will carry its own one-click “stop” link, and that link also turns off any kit emails to the same address.
- Keep your link private. Your kit link is its key. Anyone who has it can read and change your kit. Without the link, typing your email into the form does not let anyone read or change your kit; it only mails the link to you.
- Ask us to remove you. Use the contact page and say what to remove (your kit, a sign-up, a message). There is no delete button. We do this by hand within 30 days.
- Ask what we hold. Use the same contact page.
- Say no to location. The “Camps near me” button only runs if you tap it and allow it.
Security
The forms and the kit save are limited by address to slow down misuse. Kit keys are long random strings. The mail password is kept in a file only the site’s account can read, not in the code. No system is perfectly safe, and we cannot promise that ours is.
Children
This site is not for children under 13. It has no accounts and never asks anyone’s age. It is made for adults planning trips. If a child’s information reaches us, tell us through the contact page and we will remove it.
Changes to this policy
If we change how the site handles information, we will change this page and its date. Last updated: November 13, 2026.