Privacy Policy
QUMITATE ("we," "us," or "our") explains below how we handle user information in TableTact (the "Service"), a service for learning table manners. We collect only the information needed to record learning and improve the Service, including its restaurant discovery feature, and we do not store your individual answers to questions.
1. Information We Collect
Depending on how you use the Service, we collect the following information.
- Only with your analytics consent, we also collect the measurement specification version, production or development environment, page type, and page and referrer URLs with query strings and fragments removed. We use these fields to check measurement quality and improve navigation between pages.
- To improve learning and display, only with your analytics consent: whether practice links remained visible and their sign-in requirement; a random identifier for a single attempt; time while the page is visible and you have interacted recently, with an observation completeness flag; result-save failure categories; guide search filters, result counts and selections, excluding the search text itself; and page loading, responsiveness and layout stability metrics with a broad viewport-size group. Attempt identifiers do not identify users and are also stored with unfinished lessons in your browser for up to 14 days. We do not collect keystroke contents, screen recordings or input values.
- As a guest: your progress, study streaks, weekly goal, and the name shown on certificates. These are stored in your browser (localStorage) and are not sent to our servers while you use the Service as a guest. When you sign in, the progress and study streaks stored in that browser are transferred to and saved in your account (your weekly goal is transferred only if your account does not have one yet; the name shown on certificates is not transferred and stays in your browser).
- Unfinished lessons: so that you can pick up where you left off, the questions you were given and your answers are kept temporarily in your browser (localStorage). They are removed when your results are saved or after 14 days, and are not sent to our servers.
- Occasion checklists: the checks you tick on occasion pages (the outfit check and the prep checklist) are stored in your browser (localStorage). Whether or not you are signed in, they are not sent to our servers and are not shared with your other devices.
- When you sign in: your Google display name and email address (held by Firebase Authentication). Our database also stores your display language, weekly goal, per-lesson progress (latest and best score, number of completions, last studied time, next review date), learning stats (study streak, number of days studied, and number of lessons completed that week), and IDs of restaurants you bookmark. We do not store your individual answers.
- If you used Web Push review reminders in the past: notification tokens may remain as legacy data. They are no longer used for notifications and are deleted with legacy device data when you delete your account.
- Analytics (only with your consent): pages viewed, lesson starts, resumes and completions, per-question correctness, score and time taken, Dining Guide views and practice link selections, short practice starts and completions, occasion page views, link selections and checklist toggles (only the IDs of the occasion and item), the filters used on the restaurant list (including the dress code filter and whether you entered search text, but not the search text itself) and the number of matching results, restaurant detail views, clicks to official restaurant sites or Google Maps, badge and certificate views, language changes, contact form and mistake report submissions (the type only), sign-in events (where you tapped the sign-in button, that you signed in and with which method, and the type of failure), whether you are signed in, your consent to analytics, starting the app offline, and errors. Google Analytics may collect identifiers such as cookies, device and browser information, and IP address. The event fields we send do not include your name, email address, or Firebase user ID.
- When you contact us: the type and content of your message, a reply email address (optional; if you are signed in, the email address you sign in with is filled in beforehand), your display language, the page and question ID shown when you sent it, and, if you are signed in, your user ID (so we can look into your learning status when responding).
- When an error occurs: only if you have consented to analytics, we send the error type, a short summary of the error, and the page where it occurred to Google Analytics as an analytics event. Error details may contain information you entered, so we limit what is sent and take reasonable steps to remove identifiers and personal information.
2. How We Use Information
We use this information to:
- handle sign-in and save and sync your progress, settings, and restaurant bookmarks across devices
- provide learning features such as review scheduling, badges, streaks, and certificates
- analyze how clear our lessons are and how difficult our questions are, and improve the Service
- analyze how people use restaurant search and details, and improve the restaurant listings and recommendations
- investigate and fix bugs
- respond to inquiries and reports of mistakes
- respond to violations of our Terms and misuse of the Service
3. External Services and Storage Outside Japan
The Service uses the external services below. Their providers handle information on our behalf or in accordance with their own privacy policies.
Our Google Cloud Firestore database is located in the United States (us-east1 region). Other services may also store or process information outside Japan. Storage locations, retention, and transfer safeguards depend on service settings, contracts, and each provider's published information. We will provide information about overseas handling that we can confirm in response to an inquiry.
- Google Firebase / Google Cloud (Google LLC): hosting, delivery of lesson images (Cloud Storage), sign-in (Firebase Authentication), database (Cloud Firestore), server processing (Cloud Functions), operational logs (Cloud Logging), and abuse prevention (App Check; when you use our database or server processing, such as when you sign in or send an inquiry, we use Google reCAPTCHA Enterprise, which may collect information such as device and browser information)
- Google Analytics 4 (Google LLC): usage analytics, used only with your consent. Analytics data is exported to Google BigQuery to analyze learning quality and improve restaurant discovery.
- Google Fonts (Google LLC): delivery of the fonts used to display the Service. When the fonts load, your IP address and browser information are sent to that service.
- Official websites of the listed restaurants: the restaurant list and restaurant detail pages show photos from each restaurant's official website, loaded directly from that site. When they are shown, your IP address, browser information, and the Service's domain name are sent to each site.
4. Disclosure to Third Parties
We do not provide your personal information to third parties except:
- with your consent
- where required by law
- where necessary to protect a person's life, physical safety, or property and it is difficult to obtain your consent
- where we entrust handling to service providers, such as those listed above, to the extent needed for the purposes described in this Policy
5. Retention
We keep information only as long as needed for the purposes above and delete it afterward.
- Account and learning data (settings, progress, learning stats): until you delete your account
- Push notification tokens registered before Web Push review reminders were discontinued: no longer used for notifications and deleted with legacy device data when you delete your account
- Google Analytics data: the user-level retention setting in Google Analytics is 14 months. Data exported to BigQuery is managed separately and deleted according to the retention settings for its dataset and tables.
- Server operational logs: according to Cloud Logging settings. Logs contain processing status and error information.
- Inquiries (including the reply email address): 2 years after we finish responding (inquiries we have not resolved are also deleted automatically 2 years after we receive them). When you delete your account, we erase the user ID recorded with your inquiries, but the content of your inquiries and the reply email address remain after your account is deleted until this period ends. If you would like them deleted sooner, contact us and we will delete them
- Error reports: handled as part of the analytics data, in the same way as the Google Analytics data above
- Guest data: stored in your browser and removed when you clear the site data in your browser
- Unfinished lessons: removed when your results are saved or after 14 days
- Backups: to recover from outages and mistakes, we keep database backups for up to 14 days. Deleted data may remain in these backups during that period
6. Your Choices
You can control how your information is handled as follows.
Depending on where you live, laws such as the EU General Data Protection Regulation may give you rights to access, correct, or delete your information, or to restrict or object to its use. You can make such requests through the contact below, and we will respond in accordance with applicable law.
- Analytics: you can choose whether to consent in the banner shown on your first visit. You can change or withdraw your consent at any time under "Change cookie settings" at the end of this Privacy Policy.
- Signing out: you can sign out at any time. Signing out does not delete the learning data saved to your account.
- Deleting your data: use "Delete My Account" in Settings to delete your account and learning data (we ask you to sign in with Google again to confirm it is you). We may retain inquiry records for their stated retention period after account deletion where needed to meet legal obligations, handle disputes, or prevent misuse. If you cannot delete your account in Settings, email us at qumitate@gmail.com. We will ask only for the minimum information needed to verify your identity.
- Guest data: you can delete it by clearing the site data in your browser.
7. Security
We take reasonable security measures based on the nature and risks of the information, including encrypted connections, access controls, limited administrator access, and checks on the selection and configuration of external services. We access contact messages only as needed to respond.
8. Minors
If you are a minor, please use the Service with the consent of a parent or guardian. Parents and guardians may also contact us to request access to or deletion of information.
9. Changes to This Policy
We may revise this Policy in response to changes in law or in the Service. We will announce significant changes in the Service. The revised Policy takes effect when it is posted in the Service.
10. Contact
For questions about this Policy or how we handle your information, please contact:
- Operator: QUMITATE
- Email: qumitate@gmail.com
- Address and, for a company, its representative: we will disclose these without delay in response to a request from the person concerned, as required by law.