Privacy Policy

Mangiamo is a product of Droidel, Inc., an Illinois corporation, operating under the Mangiamo name. References to "we," "us," and "our" in this policy mean Droidel, Inc.

Mangiamo is a private dining guide. Privacy isn't an afterthought — it's the product.

We will never sell your personal information to third parties. We do not use your data to train AI models or build advertising profiles. The only people who can see your lists, Private Notes, and social connections are the people you've explicitly invited into your circle.

This policy describes what data we collect, why we collect it, who we share it with, and how it stays under your control.

Account information. Your name, email address, and profile photo, collected when you create an account.

Restaurant data you create. Restaurant entries, Private Notes, lists, visit counts, favorites, reservations, and Table Talk comments you add. This exists solely to power your personal dining guide. Your Visited status is private by default. You may choose to share it with your connected friends by enabling "Share my Visited history with friends" in Account Settings, and you can turn this off at any time — doing so removes your visit activity from friends' views.

Collaborative Lists. Any personal list can be linked to one of your Friend Groups, turning it into a shared, co-curated list. A list can only be linked to one Friend Group at a time. Everyone in that group can see the list's name, its restaurants, and each member's display name, and can add or remove restaurants from it. Only the person who created the list can rename, archive, unlink, or delete it. Unlinking a list from a group makes it private again immediately, and revokes every other group member's access to it. Duplicating a list to link it to a different Friend Group creates an independent copy — comments, activity, and edits made in the new group are never shared back with the original one. If you leave or are removed from a Friend Group, your access to that group's Collaborative Lists ends immediately, though any restaurants you'd already added stay on the list for the remaining members.

Reservation cancellations. Canceling or rescheduling a reservation in Mangiamo only updates your own personal dining log — we don't communicate with, modify, or cancel your actual booking with Resy, OpenTable, SevenRooms, Tock, or the restaurant directly. Any reason you enter for a cancellation is stored securely and strictly confidential to your account; it's never shared with venues, third-party booking platforms, or your connected friends.

Table Talk comments and mentions. Comments you post on a restaurant's page are visible only to your confirmed mutual friends — never to the public, and never indexed by search engines. Two sharing settings are on by default for every account: "Allow connected friends to reply to my recommendations" and "Share my Comments with connected friends." You can turn either off at any time in Account Settings. If you @mention a friend in a comment, we notify them that they were mentioned; you can only mention your existing mutual friends. You can delete any comment you've written at any time — comment authorship and deletion rights belong solely to the person who wrote it.

Push notification subscription tokens. If you enable reservation reminders, we store a browser push subscription token so we can deliver those alerts. See Section 4 for details.

Social graph. Friendship connections can form in a few ways. One-to-one: when you invite someone directly, or accept someone's individual invitation. Through Friend Groups: joining a Friend Group via its invite link automatically forms mutual friend connections between you and every existing member of that group, and with anyone who joins later — the join screen tells you this before you join. If a group owner adds someone directly rather than through the invite link, that person must explicitly accept before the connection forms. Existing members are notified when someone new joins a group they're in; this notification is informational only and isn't an approval step — the connection is already in place regardless of when or whether it's acknowledged. You can leave any Friend Group at any time from the Friends Drawer, which removes you from that group and stops further group-based connections from being made through it; it does not undo the direct friend connections you've already formed with other members, which stay in place until removed individually. Group invite links expire automatically after 30 days for security; a group owner can generate a new link at any time without affecting the group's name, history, or current members. Regardless of how a connection was formed, you can remove any individual friend at any time, and doing so does not affect anyone else's connections in that group. When tagging a Dining Companion on a reservation, you can only select from your existing mutual friends — Mangiamo doesn't support searching or tagging anyone outside your established connections.

Community Passes. Some invite passes (for example, Seed or Founder passes) grant access to Mangiamo and tag your account with a cohort label. Unlike Friend Groups, holding or using a Community Pass does not automatically connect you as friends with anyone — not other pass holders, and not the person who created the pass. Any friend connections beyond that still require the standard invite process described above.

Contacts and external sharing. Mangiamo never requests access to your phone or device contact book, and our systems are not designed to scan, import, or store your contacts. When you invite someone or share a reservation outside the app, that happens entirely through your own device's native tools — iMessage, SMS, WhatsApp, email, or clipboard copy. We don't see, access, or store any information about who you sent it to, unless that person follows the link back into Mangiamo and creates an account.

Location data. Mangiamo uses location in three distinct ways, at different levels of precision:

Default regional view. Your Primary Dining City or set location determines your default view when you open the app or browse maps, and powers features like Surprise Me. Before you've set either, we may use a coarse, IP-derived city estimate as a temporary default.

Places and lists you search or save. When you search a neighborhood or city, or save a restaurant, that location is stored as ordinary place data (an address or coordinates tied to the restaurant, not to your device).

"Near Me" search. When you tap "Near Me" or otherwise enable device location access, your browser or device shares your precise location with the app for that session. We use this only in the moment to calculate distances and show nearby restaurants. This precise location is processed in your browser session and is never written to our database — we don't store a history of your movements. You can deny or revoke device location access at any time in your device settings; core features remain usable without it.

We may use your Primary Dining City and coarse location data in aggregate, anonymized form for internal business and product planning purposes. This aggregate use never involves your precise, device-level location.

Usage analytics. Aggregate, anonymized analytics — page views, feature interactions, search counts — used to understand how the product is used. These events are not tied back to individual accounts.

Device and technical data. Standard server logs, which may include your IP address, browser type, and timestamps, retained for security and debugging. We may also use your IP address to determine your approximate city-level location — coarse, network-level data only, never precise coordinates or a street address — to set a default regional view before you've set a Primary Dining City or enabled device location. We don't retain a history of IP addresses tied to your account for this purpose.

Error and performance monitoring. When something breaks or performs slowly, we may collect technical telemetry — your browser and device type, and a stack trace showing where the error occurred — to help us find and fix it. We configure this monitoring to avoid capturing personal information where possible, but a stack trace can occasionally include incidental technical context depending on where in the app an error occurs.

If you enable reservation reminders, we store a browser push notification subscription token so we can deliver alerts ahead of your reservations — for example, 24-hour and 2-hour reminders. Reminders are strictly opt-in and disabled by default; enabling either reminder window requires you to turn it on yourself in Account Settings.

Reminder delivery is triggered by an automated scheduling process that checks, on a regular interval, whether any reminders are due. This trigger is authenticated using a secret key we control. The scheduling service is not designed to receive your reservation details, notification content, or any other personal data — it only signals our system to run the check.

You can disable reminders and push notifications at any time in Account Settings. Doing so stops future notifications and removes your stored push subscription token.

We don't sell, rent, or share your data with advertisers, data brokers, or marketing platforms — ever. We do rely on a small number of infrastructure providers to operate the app. Each is listed below with what it handles and why.

Clerk — Account creation, login, authentication. Manages your account credentials and session security.

Google Firebase / Firestore — Application data storage (restaurant entries, lists, social graph). Hosts the database that powers the app.

Google Maps Platform — Location search, map rendering, place data. Powers map view and location-based search.

Vercel — Application hosting. Serves the web app itself.

Google Tag Manager — Aggregate, privacy-compliant product analytics and site performance measurement. Helps us understand how the product is used.

Sentry — Real-time error logging, performance monitoring, and crash reporting. Helps us find and fix bugs quickly.

UptimeRobot — Server availability and uptime monitoring via synthetic endpoint checks. Alerts us if the app goes down.

Each provider processes data on our behalf under its own data processing terms and is contractually restricted from using your data for its own purposes. We may add or change providers as the product evolves; material changes will be reflected in updates to this policy.

We also use a scheduling trigger service to run our reservation reminder checks on a timer (see Section 4). This service does not receive or process personal data and is not a data processor under this policy. UptimeRobot similarly pings our servers on a schedule to confirm the app is running — it checks for a response, not your data, and does not process personal information.

We may also disclose data if required by law, subpoena, or court order, and will notify you to the extent the law allows.

Account, restaurant, and social graph data: kept for as long as your account or connection is active. When you delete your account, this data is erased from our live systems immediately and permanently — we do not run scheduled backups, so there is no residual copy elsewhere. This includes your authored Table Talk comments, which are removed from every restaurant page they appeared on, and any notifications referencing you in other users' activity — we don't leave behind anonymized or "ghost" versions of deleted content. If you're the curator of a Collaborative List, deleting your account also deletes that list for every group member — it isn't transferred to anyone else. If you're a collaborator on someone else's list, deleting your account removes your name and profile from it, but restaurants you'd added stay on the list for the remaining members.

Push notification subscription tokens: kept while reminders are enabled; no longer used once you disable the feature or delete your account.

Edge server diagnostic logs (Vercel): retained for a short period based on our hosting plan, then automatically deleted.

Crash and error telemetry (Sentry): retained for a limited period based on our monitoring plan, then automatically deleted.

"Near Me" precise device location: processed only in your browser session to show nearby restaurants; never written to our database.

Usage analytics: retained in aggregate, anonymized form and not tied to an individual account, so it is not deleted on a per-account basis.

Our infrastructure providers, including Google (Firebase, Google Maps Platform), may process and store data on servers located outside your country of residence, including in the United States. Where we transfer personal data out of the European Economic Area, United Kingdom, or Switzerland, we rely on Standard Contractual Clauses or an equivalent legally recognized transfer mechanism with our providers.

If you are located in the European Economic Area, United Kingdom, or a jurisdiction with similar protections, the following rights apply to you. We extend these same rights to all Mangiamo users regardless of location as a matter of practice.

Access. Request a copy of the personal data we hold about you.

Correction (rectification). Update inaccurate account information directly within the app, or request a correction from us.

Deletion (erasure). Delete your account from Account Settings. This permanently removes your profile, restaurant data, social connections, and associated records from our systems immediately — we don't run scheduled backups, so there's no residual copy elsewhere. Deletion cannot be reversed.

Portability. Receive your data in a structured, machine-readable format.

Objection and restriction. Object to or request restriction of certain processing of your data. We will honor this unless we have a compelling legitimate ground to continue, or are required by law to retain it.

Withdraw consent. Where processing is based on your consent, withdraw it at any time without affecting the lawfulness of processing before withdrawal.

Lodge a complaint. If you believe we have not handled your data properly, you have the right to lodge a complaint with your local data protection supervisory authority, in addition to contacting us directly.

To exercise any of these rights, contact privacy@getmangiamo.com. We aim to respond within 30 days. If you're contacting us from the European Economic Area, United Kingdom, or Switzerland, we will respond within one month as required by GDPR, extendable by up to two further months for complex requests.

Legal basis for processing:

Creating and managing your account — Performance of a contract (our Terms & Conditions).

Storing your restaurant data, lists, and social graph — Performance of a contract.

Posting and displaying Table Talk comments — Performance of a contract (a core feature of the service).

Sharing comments and replies with friends by default — Legitimate interest (supporting the core social experience), with an opt-out available in Account Settings.

Sharing a list's contents with a linked Friend Group — Consent (given by linking the list, same basis as forming the underlying Friend Group connection).

Location-based search — Consent (granted via device permission).

Collecting your Primary Dining City — Consent (optional — you can skip it).

Determining approximate location from IP address (regional content) — Legitimate interest.

Sharing Visited history with friends — Consent (opt-in, toggled by you).

Forming mutual friend connections via a Friend Group invite — Consent (given by joining the group through its invite link).

Sending reservation reminder push notifications — Consent (opt-in, toggled by you).

Aggregate usage analytics — Legitimate interest (improving the product).

Error logging and crash reporting — Legitimate interest (maintaining and fixing the service).

Aggregate location/city analytics — Legitimate interest (business and product planning).

Security and fraud prevention logging — Legitimate interest.

Responding to legal requests — Legal obligation.

Mangiamo uses only strictly necessary cookies required to maintain your authenticated session. We don't use third-party advertising cookies or cross-site trackers.

Our analytics don't fingerprint users or share data with third-party ad networks. You can use Mangiamo with standard ad blockers or tracking protection enabled without losing functionality.

This section is provided as a matter of good practice. Mangiamo's current scale is below the thresholds at which the CCPA/CPRA generally applies to a business. We're including these disclosures proactively and will update this section as the product grows.

If you are a California resident, you have the right to:

Know — what categories of personal information we collect and how it's used (see Section 3).

Delete — your personal information (see Section 8, Deletion).

Correct — inaccurate personal information.

Opt out of sale or sharing — not applicable, as we do not sell or share personal information for cross-context behavioral advertising.

Limit use of sensitive personal information — Mangiamo processes one category of Sensitive Personal Information under CPRA: precise geolocation, when you use "Near Me" search. We use this solely to perform the service you've directly requested — showing you nearby restaurants in real time — and never to infer characteristics about you, build a profile, or for any purpose beyond that immediate request. Under Cal. Civ. Code § 1798.121 and 11 CCR § 7027(m), use limited to the service you asked for doesn't require a "Limit the Use of My Sensitive Personal Information" opt-out link. You can revoke location access at any time in your device or browser settings.

Non-discrimination — we will not deny you service, charge different prices, or provide a different quality of service because you exercised a privacy right.

To exercise any California privacy right, contact privacy@getmangiamo.com.

Mangiamo is not directed at children under 13, and we do not knowingly collect personal information from them without verifiable parental consent. If you believe a child under 13 has created an account or provided us personal information, contact us at privacy@getmangiamo.com and we will delete that information.

We use industry-standard technical and organizational measures, including encryption in transit and access controls, to protect your data. No system is completely secure, and we can't guarantee absolute security of information transmitted to Mangiamo.

We may update this Privacy Policy from time to time. When we do, we'll revise the effective date at the top of this page. For material changes, we'll make reasonable efforts to notify active users through the application.

Questions about this policy? privacy@getmangiamo.com