Privacy policy

In short

• Logging in is optional. Without it, your work lives in an anonymous workspace in this browser.
• If you log in with Google, we receive your Google account id, email address, name and profile picture, and permission to send email from your Gmail. We cannot read your email.
• We send an email only when you click Send or Send all. Google's access token is never stored.
• We don't sell data, show ads, use analytics or tracking cookies, or use your Google data to train AI models.
• You can delete your account and everything in it at any time from the account menu.

Information we collect

• What you give us: your brand name, products, website address and location, the cities and venue types you choose, edits to drafts, and your do-not-contact list.
• What we create for you: runs (ranked venues and the reasons), venue contacts, email drafts, and a log of the calls each run made (to Qloo, the AI model and other services) so every result can be traced.
• Technical data: a workspace token kept in your browser's local storage, and your IP address, stored only as a salted hash to limit how many runs one visitor can start.
• From Google, if you log in: described in the next section.
• From public sources: venue details from Qloo and OpenStreetMap, the text of your website, and business email addresses venues publish themselves.

Google user data

What we access

• Google Sign-In (through our sign-in provider, Supabase Auth): your Google account id, email address, name and profile picture.
• Gmail, send only (https://www.googleapis.com/auth/gmail.send): permission to send email as you. It gives no access to read, search, delete or label your messages, or to your contacts or settings. Besides this and the basic sign-in scopes (your email address and profile), we request no Google scopes.
• Gmail message ids: when Gmail sends an email for you, it returns an id for that message, which we store.

How we use it

• Your account id and email address sign you in and keep your runs in one workspace across your devices.
• Your name, email and picture are shown to you in the account menu.
• The Gmail permission is used only to send the emails you choose: Send with Gmail sends one draft; Send all sends the approved drafts on the page that have not gone yet, after you confirm how many. Each goes once, exactly as shown, to the address shown. We never send on a schedule or in the background.
• Gmail message ids mark a draft as sent, so it can't be sent twice.

How we share it

We do not sell Google user data or share it with advertisers, data brokers, Qloo, our AI model provider, OpenStreetMap or Hunter. Supabase, our sign-in and database provider, stores your account details on our behalf. Your emails pass to Google, which delivers them. We would disclose data only if the law requires it.

How we store and protect it

• Your account id and email are stored in our database at Supabase (Tokyo region). Supabase Auth keeps your Google id, email, name and picture.
• Your Google token stays in this browser's local storage for up to 55 minutes. It reaches our server over HTTPS only with an email you are sending, is used for that request, and is never written to our database, files or logs.
• All traffic uses HTTPS (TLS). Supabase encrypts stored data. Only our API server can connect to the database, with a secret credential; row-level security blocks every public route into it. Secret keys never reach the browser.

How long we keep it, and how to delete it

• We keep your account data while you have an account.
• Delete account and data in the account menu deletes your account, your Google identity at Supabase, and all your runs, contacts, drafts and do-not-contact list, immediately and for good. It also deletes your runs' logs of AI prompts and of the web pages we read; your runs' Qloo calls keep only their time and status, with no content, so the monthly Qloo limit still counts them.
• You can also ask us to delete it by writing to the support email shown on our Google sign-in screen; we do so within 30 days.
• You can withdraw TasteRoute's access to your Google account at any time at myaccount.google.com/permissions. After that we cannot send email for you.

Limited Use

TasteRoute's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• We use Google user data only to provide the features described above, which you can see and use in the app.
• We don't transfer it to others, except as needed to provide those features, to comply with the law, or as part of a merger or sale with notice to you.
• We don't use it for advertising, including retargeting, personalised or interest-based ads.
• No person reads it, unless you ask us to, it is needed for security or to investigate abuse, or the law requires it.
• We do not use Google Workspace API data, including Gmail data, to develop, improve or train generalised or non-personalised AI or machine-learning models.

How we use other information

To rank venues, find published contacts, write drafts, keep the service working and fair (rate limits), and trace how each result was produced. We don't use it for advertising, and we don't sell it.

Service providers

Each gets only what it needs for its part.

• Qloo: your brand and product names, the city and venue types, to rank venues by taste.
• Ollama Cloud (AI model and web search): your brand profile and facts about each venue, to write drafts; venue names and cities, to search for a published email.
• OpenStreetMap services (Nominatim, Photon, Overpass): the places and cities you search for.
• Hunter, only if enabled: venue website domains, to find published business emails.
• Venue and brand websites: our server visits the pages it reads, like a browser would.
• Supabase (database and sign-in), Google (sign-in and sending), Render and Vercel (hosting).
• Map tiles (OpenFreeMap, OpenStreetMap) load straight into your browser, so those servers see your IP address.

Cookies and local storage

We use no cookies for tracking. Your browser's local storage holds your workspace token and, when you log in, your sign-in session and Google's short-lived sending token. Logging out clears them.

Venue contacts

We collect only business email addresses that venues publish themselves: on their own website, their OpenStreetMap listing, or a public page about them. We never guess or build an address. Every draft carries an opt-out line, and anyone on a do-not-contact list is never looked up, drafted, exported or sent to again. A venue that wants its address removed can write to the support email shown on our Google sign-in screen.

Your choices and rights

• Download your runs, contacts and approved drafts as a CSV from any run.
• Delete your account and data from the account menu, or ask us to see, correct or delete your data at the support email shown on our Google sign-in screen.
• Without logging in, your work isn't tied to your identity; to delete it, send us a link to the run.
• Depending on where you live, you may have further rights (for example under the GDPR or CCPA); write to us to use them.

Children, changes and contact

TasteRoute is for businesses and is not directed at children under 16. If this policy changes, we update the date above. Questions: the support email shown on our Google sign-in screen. See also the terms of service.