Neba Privacy Policy

Last updated: 2026-08-11

Neba is a Chrome extension that adds an AI research assistant to Booking.com, Agoda, and Trip.com listing pages, so you can ask about a property's neighborhood, safety, and vibe without leaving the page.

What Neba stores on your device

Neba stores the following only in your browser's local storage (chrome.storage.local), never synced to any account:

• Trips you create, and which properties you've filed into each one
• Chat messages you send and the assistant's replies, for each property (before filing) and each Trip (after filing)
• Neighborhood Snapshot results (a cached AI-generated summary per listing)
• A random install identifier, generated once when you first install Neba, not tied to your name, email, or any account

This data never leaves your device except as described below, and is never synced across devices or browsers. Uninstalling Neba deletes it. Scratch conversations for properties you've never added to a Trip are automatically deleted after 14 days of inactivity.

What gets sent to Neba's server

When you send a chat message or open a listing's Neighborhood Snapshot for the first time, Neba sends the following to its own backend server, which relays it to Google's Gemini API to generate a response:

• The property's name, address, and a few excerpts from its guest reviews and description, read from the Booking.com, Agoda, or Trip.com page you're viewing
• The page's declared language
• Your typed message and, for a Trip's shared conversation, the recent conversation history so far
• Your random install identifier and the current date, used only to enforce a daily usage limit

Neba's backend does not store your chat messages or the page content sent with them. The only thing persisted server-side is a daily message count per install identifier, used to apply a soft usage limit; that counter resets automatically each day and contains no message content.

Because your message and page context are sent to Google's Gemini API to generate a response, that use is additionally subject to Google's Privacy Policy and the Gemini API Additional Terms of Service.

Real geodata: Google Maps Platform

When a listing's location can be geocoded, Neba can back the Neighborhood Snapshot's transit distance, and answer ad-hoc chat questions like "any good ramen near this hotel?", with real data from Google Maps Platform instead of the model's own recollection. When this happens:

• What's sent: the property's address (to resolve its coordinates), and, for chat, the general category of place you asked about (for example "restaurant" or "supermarket"). Never your chat message text itself, and never your install identifier.
• What comes back: nearby place names, types, and, for chat, ratings; and measured distances or travel times between the listing and a specific place.
• Caching: results are cached on Neba's backend, keyed by the general area, not by you or your install identifier, and reused across every user asking about the same location.
• When it's off: Neba works exactly as before, with Gemini's own general knowledge instead of measured data, whenever this feature has no API key configured, has reached its own monthly spend cap, or the lookup fails for any reason. The app tells you when an answer is measured versus estimated.

This use is additionally subject to Google Maps Platform's Terms of Service and Google's Privacy Policy.

What Neba does not do

• No account creation, login, or personal identifiers of any kind
• No cross-device sync
• No advertising or analytics tracking
• No selling or sharing of your data with anyone other than Google's Gemini API and Google Maps Platform, solely to generate the response to your own question
• No access to your Booking.com, Agoda, or Trip.com account, bookings, or payment information

Permissions

Neba requests the minimum Chrome permissions needed to work. See permissions-justification.md in this repository for exactly what each one is used for and why.

Changes to this policy

If this policy changes, the "Last updated" date above will change accordingly. Material changes will also be reflected in this project's CHANGELOG.md.

Contact

Questions about this policy or Neba's data handling can be raised via the project's GitHub issues page.