Privacy Policy

Who runs DaedalMap

DaedalMap is operated by Bryan Hellard. There is no separate company yet; when one exists, this page will name it. Bryan Hellard is responsible for the personal information described here.

What we collect

If you create an account, we store your email address. Email is used for login and account recovery. We send product updates only if you ask for them. You can request deletion at any time.

If you join a waitlist or ask to be kept informed, we store your email address and which page you used, and email you only about what that form describes.

If you use the feedback button, we store the message text and whether you were logged in. On onboarding prompts we may also store the current workflow stage, anonymous attempt identifiers, row/result counts, and the next action you selected. Uploaded rows and coordinates are not attached to feedback. No other personal information is attached.

The app logs basic usage data for reliability and debugging: query types, error rates, and response times. IP addresses in these logs are stored only as salted one-way hashes. Usage logs are not sold or shared.

Chat

Messages you type into the Explore, Research, and Ops chat are sent to Anthropic, whose Claude models generate the replies. Anthropic's handling of that text is governed by Anthropic's privacy policy.

We also store chat messages, the start of each reply, and a session identifier so we can find and fix errors and see which questions the service fails to answer. These records include a hashed IP address and your browser type, are not used for advertising, and are not sold. Please do not enter personal or confidential information in chat.

Try Data

Files you open on the Try Data page are read in your browser. Only the geography values needed for matching, such as place codes or coordinates, are sent to DaedalMap's lookup tools; the other columns stay in your browser.

If you sign in, DaedalMap also stores session identifiers needed to keep you logged in across daedalmap.com and app.daedalmap.com. These identifiers are used only for authentication, session continuity, and account access across the two DaedalMap subdomains.

Analytics

DaedalMap uses Google Analytics to understand which pages and tools are used, and a first-party analytics cookie of its own to count a visit as one visit when you move between daedalmap.com, app.daedalmap.com, and downloads.daedalmap.com. This measures product usage: which pages are read, which tools are run, and which data packages are downloaded.

The first-party analytics cookie holds a random identifier that is not derived from your name, email, account, or IP address, along with a short record of how you first arrived (for example a search engine, a link from another site, or a campaign link). It is used for counting and reporting only. It is never used to decide what you can access, what you are charged, or how much of the service you may use.

Visitors from the European Union, the European Economic Area, the United Kingdom, and Switzerland, and anyone whose location we cannot determine, are asked first: analytics stay off and no analytics cookie is set unless you accept. Elsewhere analytics are on by default. Anyone can change their choice at any time; declining deletes the analytics cookies.

Change cookie settings

To determine whether to ask, our website reads the country Cloudflare derives from your connection and stores only the result (ask or do not ask), not the country or your IP address.

Address search

The address-search card uses Google Places Autocomplete. Text you type into that card is sent directly from your browser to Google so it can return suggestions; DaedalMap does not receive or store the typed address. Google's handling of that input is governed by Google's privacy policy.

After you choose a suggestion, DaedalMap receives its coordinates so it can resolve the containing loc_id. We record that an address suggestion was selected, whether it resolved, response timing, and anonymous or signed-in usage context. We do not put the address text or coordinates into the analytics event.

What we do not collect

DaedalMap does not use advertising networks or advertising cookies, does not sell data, and does not share personal information with third parties for marketing purposes. Analytics are used to improve the product, not to build marketing profiles or to target advertising.

Billing

Payments are processed by Stripe. DaedalMap does not store card numbers or payment details. Stripe's handling of payment data is governed by Stripe's privacy policy. We receive only a billing status and customer identifier from Stripe.

Data storage

Account data, waitlist entries, feedback, and chat records are stored in Supabase, a hosted database service. Logs are stored on Railway, the hosting platform. Chat text is processed by Anthropic as described under Chat. None of this is sold or shared with third parties for purposes beyond operating the service.

Cookies

DaedalMap uses login/session cookies and browser storage to keep you signed in if you create an account. These are used to maintain authenticated access across daedalmap.com and app.daedalmap.com. When the website sends you into the app, it uses an explicit one-time login handoff instead of long-lived shared auth cookies across subdomains. No advertising cookies are set by DaedalMap.

The current auth/session storage may include:

• session tokens needed to keep you signed in
• refresh tokens used to renew the session without forcing you to log in every page load
• browser local storage used by the auth client to maintain session continuity
• short-lived login handoff state when moving from the website into the app

These auth/session cookies are considered necessary for account login and account-linked app behavior. You can clear them by signing out or by clearing browser cookies and site storage.

Analytics cookies are separate from the above and are described under Analytics. They are:

• a first-party DaedalMap analytics identifier and first-arrival record, kept for up to 400 days
• Google Analytics measurement cookies set by Google on our behalf

Two small cookies support the consent choice itself and are not used for analytics: one records whether this browser should be asked (kept 30 days), and one records your answer (kept about six months, after which you are asked again).

Your rights

You can request deletion of your account and associated data at any time by contacting us. Your email will be removed and your account deactivated. Anonymized log data may be retained for system reliability purposes.

Contact

Questions about privacy can be directed to [email protected], through the feedback button on the app, or via the About page.