CityAmble beta

Privacy, in plain language.

This page explains how the current CityAmble website and Austin beta handle information. For a privacy question or a request about your information, contact support@cityamble.com.

This public website

These information pages do not contain an account form, analytics scripts, advertising pixels or embedded third-party media. They do not set application cookies or use browser storage. Our hosting provider receives connection information, such as your IP address and the page requested, when it delivers a page.

Your account and shared trips

The separate beta uses Google to sign you in. CityAmble verifies Google’s sign-in response and stores a Google account identifier linked to an internal account. The current account database does not copy your Google email, profile photo or Google profile name. CityAmble does not ask for access to your Gmail inbox, calendar or contacts.

If you choose a traveler name, it is stored with your account and shown to owners of trips you join. We store the trips you create or join, your membership and access level, itinerary selections, saved places, dates, hotels, notes, purchases marked in the planner, completion marks and travel details you enter. A purchase mark records your choice; it does not process a payment.

People you invite can see the trip and its saved travel details. Editors can change itinerary and travel entries; viewers can read them. Trip owners control invitations and membership. Do not put passwords, passport details, card numbers or private information into shared trip notes.

Sign-in cookies and browser storage

The beta uses secure cookies for sign-in challenges and sessions. It also uses browser storage to remember planner preferences, recover saves and imports, and cache some route results. Signing out ends the current session; it does not delete your account, trips or every item in browser storage. Clearing site data in your browser removes local copies but does not delete saved server records.

Maps, search and your location

The planner requests map tiles, place information, weather and walking routes from outside services. Depending on the feature and deployment, requests go directly to a provider or through a CityAmble service. Providers can receive requested map areas, place queries or route coordinates and connection information. The current planner uses services associated with OpenStreetMap, Esri and MET Norway. Venue pictures can also load from outside image or venue websites; those hosts receive the image request and connection information.

Using your location requires your browser’s permission. Location coordinates are used to find routes from where you are; they are not saved as your trip’s hotel or in the account database. Hotel-based routes may be cached in the browser session. Current-location walking routes are not written to that session cache. You can deny or revoke location permission in your browser settings.

Services that help run CityAmble

Cloudflare hosts the beta and stores account and trip records in its database service. Google provides sign-in. Outside map, route, search and weather providers handle the requests described above. If you open a booking, directions or venue link, that destination handles your visit under its own policies.

Support email sent to support@cityamble.com is forwarded to Gmail for handling. Your message and contact details are used to respond to your request. Please send only the information needed to explain the problem.

Your choices and requests

You can change your chosen name, remove saved travel entries and control location permission. Trip owners can revoke unused invitation links and remove members. The beta’s itinerary export does not currently include the separate saved travel entries.

Contact support@cityamble.com to ask about access, correction or deletion of account information. The beta does not currently provide a complete self-service account deletion tool. We may need to verify that a request concerns your account before acting on it. Deleting an entry from the planner is not a promise that all service logs or backups are erased immediately.

Changes to the beta

Features and the services they use can change as the beta develops. This page will need to change with them. There are no active affiliate offers on this public website; planned affiliate links are explained in our affiliate disclosure.