Privacy Policy

Effective September 13, 2026

Jinru Xue d/b/a SushiLog, California, USA, operates SushiLog Business. This policy explains how we handle information about restaurant staff, Diners, and visitors, including through the Studio, public menus, billing, and support. Contact sushilog@sushilog.app with privacy questions or requests.

1. Information we handle and why

Account and security information: email address, account and Venue names, password hashes, verification and password-reset records, sessions, and technical information such as IP addresses and browser details. We use this information to authenticate staff, maintain the Venue Account, prevent abuse, and send account and security messages.

Venue content: menus, dish names, descriptions, notes, Drink Pairings, photos, videos, media metadata, original text, translations, and revision history. We use it to provide authoring, translation, storage, and menu presentation. Diners do not need an account to view published menus.

Billing information: we send the Venue’s email, name, and account identifier to Stripe. We store customer and subscription identifiers, plan and access status, billing dates, and payment-event records to manage access and support. Payment details are entered into Stripe/Link’s hosted service; SushiLog does not receive or store full payment-card numbers or security codes.

Support and feedback: if you email us or submit our linked Zoho form, we receive the information you choose to provide. The form also identifies whether you opened it from the landing page or Studio. We use submissions to respond, troubleshoot, and improve the service. Do not include secrets or unnecessary personal information.

Operational information: our infrastructure and service providers process request details, timestamps, IP addresses, device/browser information, errors, and usage or security records to deliver, protect, and troubleshoot the service. Error records may include excerpts returned by a service provider.

2. Public menus and uploaded media

Published menus are accessible without an account and may be shared or saved by Diners. Uploaded photos and videos are accessible to anyone who has their direct URLs, including uploads attached to drafts or removed from a menu. Do not use uploads to store confidential or sensitive material.

Unpublishing removes a menu from the public menu experience. Removing a media attachment or deleting an item does not automatically delete stored files, resized copies, or historical text, and does not revoke existing direct media links. Contact us for removal of stored media. Copies downloaded by others may remain outside our control.

3. Cloud and AI service providers

We use multiple cloud service providers. Cloudflare hosts the application, databases, media storage and delivery, image processing, and operational infrastructure. Resend delivers account, security, and service emails. Stripe/Link handles payment transactions, invoices, subscription management, fraud prevention, and transaction support. Zoho hosts the optional feedback form.

For translation, menu and dish text, dish-name context, and relevant earlier source text and translations may be sent through AI routing or hosting services such as OpenRouter and DeepInfra to services using OpenAI, DeepSeek, or Google Gemini models. We may switch among these services and models for quality, availability, and cost; not every provider receives every request. A model’s name does not necessarily identify its hosting provider. The translation workflow does not send account credentials, payment details, uploaded media, or the Studio-only Kitchen Name as translation inputs.

AI providers’ logging, retention, processing locations, and use of inputs for model improvement depend on the provider, service, and account settings. Some configurations may allow retention or model improvement; we do not promise zero retention or a universal prohibition on provider training. Do not include personal, confidential, or sensitive information in text to be translated. You can contact us to ask about the services currently in use. Publishing can trigger translation automatically; there is currently no per-Venue switch to disable it.

We disclose information to service providers as needed for these purposes. We may also disclose information when legally required, to protect rights and safety, to professional advisers under confidentiality obligations, or in a business transfer subject to applicable privacy obligations. Stripe/Link and services you visit directly also process information under their own policies.

4. Analytics, cookies, and browser storage

Our product analytics aggregate UTC date, event name, and English/Japanese interface locale. The product analytics records do not contain visitor identifiers, IP addresses, or user-agent strings and are not used to build visitor profiles. This is separate from account, security, infrastructure, and third-party processing described above.

Authentication uses cookies; browser storage remembers preferences such as language and theme and helps complete account flows. You can clear or block cookies and browser storage through your browser, but sign-in and saved preferences may stop working.

We do not sell personal information or share it for cross-context behavioral advertising, and we do not run advertising trackers. Do Not Track and Global Privacy Control signals do not change our current service behavior because we do not perform that advertising tracking or sale. External payment and feedback services may use their own cookies and collect activity under their policies when you visit them.

5. Retention and deletion

We retain account and content records to provide the service, preserve editing history, support recovery, and resolve support or security issues. Subscription cancellation is not a deletion request. Uploaded originals, resized images, text revisions, and translation records currently have no automatic deletion schedule and may remain stored until manually removed, even after you remove content in the Studio.

To request access, correction, an available copy of your information, account closure, or deletion, email sushilog@sushilog.app. Requests are handled manually; we may verify your identity and authority for the Venue. We aim to respond within 30 days and will comply with any applicable legal deadline. This is a response target, not a promise that every copy will be erased within 30 days.

We assess what must be removed from active systems and service providers and explain any information retained for legal, accounting, fraud-prevention, security, or dispute purposes. Backup and cached copies can persist until replaced or expired; third-party retention varies. We do not promise immediate erasure of all copies. Requests concerning Link’s payment records or a Link account may also need to be made to Link.

6. International processing and your choices

We operate from the United States and use providers with international infrastructure. Information may be processed in the United States and other countries where our providers and their hosting partners operate. We do not promise storage or processing exclusively in your country. AI processing locations can change with the selected provider and route.

Depending on your location and applicable law, you may have rights to access, correct, delete, or receive a copy of your information, restrict or object to processing, withdraw consent where consent is the legal basis, or complain to a privacy authority. Contact sushilog@sushilog.app to exercise rights or question a response. We do not deny service merely because you make a privacy request, though deletion of information needed to run your account can end access.

Where a legal basis is required, we process information to provide the contracted service, meet legal obligations, and pursue legitimate interests in security, support, and service improvement; we seek consent where required. Restaurants are responsible for the personal information they choose to include in menu content. You may contact either the restaurant or us about information appearing in a menu.

7. Children, security, and policy updates

Venue Accounts are for authorized adults aged 18 or older. The service is not directed to children under 13, and we do not knowingly collect their personal information. Contact us if you believe a child has supplied personal information so we can investigate and address it.

We use access controls and other technical and organizational measures to protect information, but no service can guarantee complete security. Public menu and direct media links are intended for sharing and are not private storage.

We will post updates here with a revised effective date. For material changes, we will notify registered Venues by account email before the changes take effect and obtain consent where required. Provider changes within the purposes described above may occur over time; a materially different use of information requires an updated notice.

Related service policies