PrivacyPolicy.

We are the data controller for your account, team, billing, and security data.

When a diner chats with the assistant on a restaurant's website, the restaurant decides to offer the chat and is the data controller. We act as its data processor under a Data Processing Addendum (https://www.tasteem.com/dpa).

When you create a TASTEEM guest profile, we are the data controller for the profile. Restaurants do not receive your profile, name, or email.

• Name and email address
• Password hash (we never store plain passwords)
• If you sign in with Google: your Google account identifier and the sign-in tokens Google issues to us
• Session tokens that keep you logged in
• Your role within a team (member or admin)
• Consent records: whether you consented, when, which version of these documents you accepted, and your optional marketing consent
• Account timestamps: creation, last update, and deletion

• Team names, members, roles, and join dates
• Invitation records: invitee email, role, who invited them, and status (pending, accepted, rejected)

• Stripe identifiers: Customer ID, Subscription ID, Product ID
• Plan name and subscription status
• Daily AI token usage per team and restaurant

• Restaurant name, address, city, country, opening hours, and currency
• Logos, background images, and branding settings (colors, fonts, welcome message, chatbot tone and formality)
• Landing page settings, including social media links you provide
• Menu data: dish names, descriptions, prices, categories, ingredients, toppings, allergens, dietary flags, spice level, nutritional values, weight, availability, and images
• Vector embeddings of menu items (used for semantic search)
• API keys and demo codes you generate

• Daily and hourly recommendation session counts and total session duration
• Which dishes were recommended and how often
• Positive or negative feedback on a dish
• Menu section view counts and menu filter usage (which dietary or allergen filters were active, and how many dishes were shown)
• Monthly dish insights (recommendations, views, conversion rates, peak day)

• Email address and a password hash
• Name (optional)
• Dietary preferences and allergens you choose to save
• Nutrition targets (calories, protein, carbs, fat) and spice level preference, if you set them
• Profile creation and update timestamps
• A record of your consent (when, and which version)

When you chat with an assistant, your message is processed in real time and sent to our AI provider to generate a reply. We do not store the text of conversations in our database. If you are signed in to a guest profile, the preferences you saved (dietary flags, allergens, nutrition targets, spice level) may be included in the request so recommendations fit you. We do not send your name or email to the AI provider. Please do not enter information you do not want processed in this way.

• Activity logs for team accounts: user, team, action, and timestamp
• API key usage (last-used time)
• Authentication events and session tokens
• Error logs and system performance data

When an account or guest profile is deleted, we keep a short record that the deletion happened: the original user ID, a SHA-256 hash of the email address, request and completion dates, how the request was made and verified, what was deleted, what was retained and why, and who processed it. A hash of an email address can still be linked back to a person by someone who already knows the email, so we treat these records as personal data (pseudonymized) and keep them only for the period in section 8.

We use Google Analytics 4 on our marketing website only if you accept analytics cookies in our cookie banner. Google states that Analytics 4 does not log or store IP addresses. We do not use Google Analytics inside the restaurant dashboard, the chat widget, or guest profiles, we have turned off advertising features, and we do not send names or email addresses to Google Analytics.

• Pages visited, time on page, how you reached us, and clicks
• Approximate location (country or city) derived by Google
• Device, browser, and operating system type
• Cookie identifiers set by Google Analytics

• Provide AI-powered dish recommendations
• Generate analytics dashboards and insights for restaurants
• Manage restaurant profiles, menus, and teams
• Personalize recommendations for guests who have a Discover profile
• Process payments, manage subscriptions, and enforce plan limits

• Analyze aggregated or anonymized usage to improve recommendation accuracy
• Develop new features based on aggregate trends

• Send essential service messages (account, security, billing, email verification, password reset)
• Provide customer support
• Send marketing emails to restaurant users, only if they opted in
• Notify you of changes to our Terms or this Policy

• Detect and prevent fraud, abuse, and unauthorized access
• Investigate security incidents
• Keep accounting records as required by law
• Respond to lawful requests from authorities
• Protect our legal rights

Discover uses your saved preferences to rank and filter dishes. This is personalization only. It does not produce legal or similarly significant effects for you. You can edit or delete your preferences, or delete your profile, at any time.

• We do not sell personal data or share it for advertising
• We do not share guest profiles with restaurants
• We do not share data with data brokers or competitors
• We do not track individual diners across websites

We may disclose information when required by law, a court order, or a competent authority, or to protect our legal rights or prevent fraud or harm. We will notify you of such requests unless the law prohibits it.

If TASTEEM is transferred to another person or company, including a new legal entity we form, your data may transfer with it under the same protections, and we will notify you.

• In transit: TLS encryption for all connections
• At rest: encryption provided by our hosting and database providers
• Passwords: stored only as one-way hashes, never in plain text

• Role-based access: team members see only what their role allows
• API keys authenticate embedded chat widgets
• Access to production systems is limited to the operator

• Activity logging for team accounts
• Error and performance logs reviewed by the operator
• Incident response: we investigate suspected incidents and notify affected users and authorities as the law requires

• Our hosting and database providers handle network protection, DDoS mitigation, and backups
• Regular software updates and dependency patching

• Right to know what personal information we collect, why, and with whom we share it
• Right to delete personal information
• Right to correct inaccurate information
• Right to limit the use of sensitive personal information. We use dietary and health-related preferences only to provide the service you asked for
• Right not to be discriminated against for using these rights

We do not sell personal information and do not share it for cross-context behavioral advertising.

• Use your dashboard or profile settings where available
• Email octavianvoicu0@gmail.com
• We may ask you to verify your identity
• We respond within 30 days (GDPR) or 45 days (CCPA)
• Requests are free, except where they are clearly excessive or repetitive

• Romania (EU): where the service is operated
• EU and US: our providers, depending on the service (see the provider list in section 5)

• Standard Contractual Clauses in the providers' data processing terms, for transfers outside the EEA
• Adequacy decisions, where the European Commission has recognized a country's protection
• Encryption in transit and at rest provided by our providers
• Data processing terms with our providers

• Where a US provider is certified under the EU-US Data Privacy Framework, transfers rely on it
• Otherwise they rely on Standard Contractual Clauses
• The same security standards apply everywhere