Bars, restaurants, museums, concerts, games — everything worth leaving the house for. Every pick has a reason, written by someone who actually went.
Dashi helps you find bars, restaurants and things to do in the cities we cover. We built it to be useful, not to harvest data. This page says what we collect, why we collect it, who else touches it, and how to get rid of it. It is written by the people who run the app, not by a template.
You can explore the deck, search, read guides and open booking links without signing in. As a guest, nothing you look at, swipe or save is sent to us or tied to you. It stays on your device. The one exception is a booking tap, described below.
You can sign in with Apple, with Google, or with a one-time code we email you; accounts made earlier with a password keep working. One email address is one account, whichever way you sign in. We store your email address, and the name and profile photo Apple or Google share with us if you sign in that way. Apple shares your name only once and, if you choose Hide My Email, gives us a private relay address instead of your real one; that is fine with us. When you ask for a sign-in code we keep your email address with a scrambled copy of the code (never the code itself) and delete it within a day of the code expiring. Passwords are handled by Firebase Authentication; we never see them. You can add a display name, a home city, a photo and a short bio to your profile.
While you are signed in we keep the things you do in the app so they are there next time, on any device:
We use this to run those features and, in aggregate, to see which places are trending in each city. We do not build advertising profiles from it.
When you add photos or a menu to a venue, we store each file, the caption if you write one, the venue, the time and your account ID. Everyone who opens that venue sees them, with your display name and profile photo if you set them, whether or not they have an account. Before a photo leaves your phone the app shrinks it and saves it again as a new image, which drops the camera’s metadata, including where it was taken. A PDF menu is uploaded as it is.
You can remove any of your uploads from the venue at any time. We may hide an upload that is offensive, spam or not of that place. Deleting your account deletes all of them.
Your guides live on your device. When you publish one, we store a copy: its name, description, city and the places in it, when you published or last changed it, and your account ID. We review it before anyone else sees it. Once we approve it, everyone who opens the Guides tab in that city sees its name, description and places, whether or not they have an account, but not your name. Places you added from Google are left out of the published copy. If you change a published guide, it is sent again and goes back to review.
Unpublishing the guide or deleting it removes the copy from our servers, and so does deleting your account. We may take down a guide that is offensive, spam or not about real places.
If you report someone’s photo or menu, we store which upload you reported, the reason you picked, the time and your account ID, so we can review it. The person who added it is not told who reported it. The upload disappears for you straight away. If you delete your account, your reports stay on file for review without your account ID.
If you block a member, we store that you blocked them and when, so their photos and menus stay hidden for you on every device. They are not told. You can unblock them under Profile → Account & Data → Blocked members. A block is deleted when either of you deletes your account.
When you tap a booking link (OpenTable, Resy, SevenRooms, Tock or a venue’s own site) we log the venue, the platform, the city and the time, plus your account ID if you are signed in. That tells us which places people actually want to go to. Each person counts once a day per venue, however many times they tap. As a guest that count rides on a one-way code made from the day and your network address, cleared after two days and never used to identify you. What happens on the booking site is between you and that company, and their privacy policy applies there.
If you send a report from Profile → Report a problem, we receive your message, the screen you were on, your city, your platform, the app build, your device model, the screenshot you chose to attach, and your email address so we can reply. We use reports only to fix the problem. If you later delete your account, reports you sent stay on file with your account removed from them.
Distances on venue cards come from your phone’s location, if you allow it. That calculation happens on your device. Your coordinates are never sent to us and never stored anywhere. Say no to the permission and the app works the same, without distances.
Your chosen city, language, a few preferences and your guides live in the app’s local storage, apart from the copy of a guide you publish. A sign-in token keeps you signed in. On the web, an invite cookie remembers that you entered an invite code. When the Passport map comes from Google Maps, a map session token, good for about two weeks, lets it load map tiles; it is not tied to you or your account. Clearing the app’s data, or your browser data, removes all of it. None of it is used to track you.
Dashi runs on Google Cloud in the United States: Cloud SQL and Cloud Storage store the data above, including the photos and menus you add, Cloud Run serves the app, Firebase Authentication handles sign-in, and Google Workspace sends sign-in codes. Google Places supplies venue details and photos, and Unsplash supplies city photos, so your device loads those images from their servers. The Passport map is drawn from map tiles that your device loads straight from the map provider: OpenStreetMap today, and Google Maps once we move the map over to it. Either way the provider receives the part of the map you are looking at and your device’s network address, as any map in a browser does. When the map comes from Google, the app also keeps a short-lived map session token on your device so it does not have to ask Google again for every tile. Dashi uses Google Maps: Google Places today, and the map itself once it moves over. Google’s privacy policy and terms of service apply to both. Apple and Google give us install and crash statistics for the App Store and Google Play versions under their own terms, and if you test Dashi through TestFlight, Apple passes us the feedback and screenshots you submit there.
There are no advertising networks, analytics SDKs or data brokers in Dashi.
Go to Profile → Account & Data and tap Delete Account, or open app.get-dashi.com/settings/account. This immediately removes your sign-in and everything tied to it: your profile and profile photo, saves, likes and passes, visits, rankings, venue suggestions, the guides you published, the photos and menus you added, the members you blocked, and your membership in every crew. The crews themselves are not deleted: a crew you created keeps its name, city and invite code and carries on for the people still in it, with you removed and nobody recorded as its creator. Booking taps, problem reports and reports of uploads are kept for our statistics, bug fixing and moderation, with your account detached from them; the email address on a problem report is erased.
Wherever you live, you can ask us for a copy of the data we hold about you, ask us to correct it, or ask us to delete it. That includes the rights you have under the GDPR in the EU and UK and under the LFPDPPP in Mexico. Email us and we will answer within 30 days.
If we change how we handle data in a meaningful way, we will update this page and the date at the top, and tell you in the app before the change takes effect.
Reach out anytime at hello@get-dashi.com. We are a small team and we actually read our email.
© 2026 Dashi Ventures LLC · Austin, TX · Back to app