Privacy Policy
Last updated: October 31, 2026
Mooores Inc. ("we", "us") provides R2C, an AI sales assistant (the "Service"). We handle the personal information and related information of our customers and of the visitors to the websites of customers who have installed the Service ("end users") appropriately and in compliance with the Act on the Protection of Personal Information and other applicable laws.
1. Information we collect
We collect the following information to provide the Service.
| Conversation logs | The content of conversations between end users and the Service's AI (messages sent and received, timestamps, session information), including the content of conversations after a handover to a human agent. |
|---|---|
| Images sent by end users | Images that an end user sends during a conversation, when the customer has enabled "consultation by image". We do not store the image files themselves. A received image is checked for format and re-generated (which removes incidental information such as shooting location and device model), used only for the AI to read its content, and then discarded after processing. What we record is the result of reading (a summary, text in the image, and words describing features such as color and shape), a value that identifies the image (a hash), and whether the image was used in the reply. We do not use close-up face images, selfies, identity documents, or images judged to be sexual or violent in a reply. Images that may show a face, name, address, phone number, email address or card number are used in a reply, but we do not keep the summary or the text in the image from the reading result. |
| Visitor identifier | An identifier used to recognize and distinguish end users (a visitor identifier). It is assigned to keep a conversation going and to improve quality. |
| Conversations through external AI services such as ChatGPT and Claude | When an end user asks a store a question from an AI service such as ChatGPT or Claude, using the Service's connection (connector), we record the content of the question and the Service's answer as a conversation of that store. The Service does not obtain account information on the AI service's side (such as name or email address). An anonymous identifier assigned by the AI service may be used to limit the number of uses (to prevent abuse). |
| Conversations through LINE | When an end user sends a message to a LINE official account that a store has linked with the Service, we record the content of the message and the answer as a conversation of that store. We do not store the LINE user ID itself. We tell conversations apart by a pseudonymized identifier that differs for each store (a value that cannot be turned back into the original ID). We do not obtain LINE display names or profile pictures. |
| Account information | The name, email address and billing information of customers who contract for the Service, including the email address and other details submitted when applying for a demo. |
| Usage and technical information | Access date and time, referrer, browser and device information, and measurements such as the number of conversations and usage. On our own site (r2c.biz), we count the pages viewed, referrers and browser types without using cookies (Cloudflare Web Analytics). |
| Inquiries and applications | What is submitted through the inquiry, document request and free demo forms on our site (r2c.biz): name, company name, email address, site URL, the type and content of the inquiry, the product of interest, country or region, and the source of the visit (a value that identifies an ad or a link). |
| Content customers register | FAQs, product information, knowledge and other content that customers register in the Service. |
During a conversation, the Service may ask for a name or contact details, at the customer's discretion. Credit card numbers used for payment are processed by the payment processor and are not held by us (Stripe, Inc.).
2. Purposes of use
- To provide and operate the Service and to respond to end users (including reading the content of images that end users send and reflecting it in replies)
- To guide end users toward inquiries, bookings and purchases, and to provide performance reports to customers
- To evaluate and improve the quality of conversations, and to improve the Service and develop new features
- To calculate and charge fees and to measure usage
- To prevent misuse, to ensure security, and to fulfill legal obligations
- To contact and support customers and to send important notices
- To reply to inquiries and to notify those who asked to be told when a product launches
- To improve our site (counting how it is viewed)
On the free plan, conversation data may be contributed to a shared learning pool for improving the Service. Customers on a paid plan can separately choose (opt out of) use for learning within their own account and contribution to the shared learning pool, in the settings of the admin console.
Because we do not store the image files that end users send, they are not used for learning or analysis. For images that may show a face, name, address, phone number, email address or card number, we do not keep the summary or the text in the image, and they are not used for learning or analysis.
3. Disclosure to external services and transfer abroad (important)
To generate AI replies and to process audio and text, the Service sends information such as conversation content to the following external providers (cloud AI and processing platforms). These providers' servers may be located outside Japan (for example, in the United States), which may count as providing or transferring personal information to a third party in a foreign country.
| OpenAI | Generating AI replies and similar (conversation content is sent). Country: United States |
|---|---|
| Groq | Generating AI replies and similar (conversation content is sent). Country: United States |
| Google (Gemini) | Generating AI replies and similar (conversation content is sent), and reading the content of images that end users send (a re-generated, sanitized image is sent). Country: United States |
| Cloudflare, Inc. | Relaying and protecting the Service's traffic (traffic that includes conversation content passes through it); sending emails such as automatic replies to inquiries (name, email address and similar are sent); preventing abusive form submissions (Turnstile; technical information about the browser and device is sent); counting how our site is viewed (Web Analytics; the page viewed, referrer, browser type and similar are sent; no cookies are used); and delivering the admin console. Country: United States |
| Our analysis platform (Hermes) | Analyzing conversation quality and generating improvement suggestions. The conversations of customers with data sharing enabled (always enabled on the free plan) are sent. Image files are not sent. The result of reading an image (summary, text in the image, words describing features) is included only for images with no suspected personal information, after the forms of phone numbers, email addresses and postal codes are masked. Country: Finland (Helsinki; servers of Hetzner Online GmbH, the cloud provider we use) |
| PostHog (usage analytics) | Only when a customer (store) has set up the analytics integration, the visitor's browser on that site sends the widget's usage (counts and times of the widget being opened or closed, messages being sent and conversions being recorded; the URL of the page viewed; the length of messages and replies and the response time; the tenant ID; and an identifier assigned at random for each conversation). The text of conversations, what was typed, and images are not sent. We do not record screens, build heatmaps or collect automatically. Technical information such as the IP address reaches the provider because of how communication works. Country: the EU region is used (the operator is a US company) |
| LY Corporation (LINE) | Relays messages between end users and a store on the LINE official account that the store has linked (the content of the end user's message and the Service's answer pass through LINE's service). Country: Japan (the service's storage may include locations outside Japan) |
| Other processors | LiveKit, Inc. (audio and avatar communication platform; United States) / Stripe, Inc. (payment processing; United States) / Supabase (authentication and database platform; Australia (Sydney, region ap-southeast-2)) / Hetzner Online GmbH (the cloud platform that hosts the Service's servers and stores conversation data; Finland (Helsinki)) |
When an end user uses the Service through an AI service such as ChatGPT or Claude, the end user's input and conversation on that AI service are handled under the terms and privacy policy of the provider of that AI service. We are not responsible for that handling.
The destination countries are as shown in the table above. Each provider handles personal information under standard contractual clauses (SCCs) or a data processing agreement (DPA) that it provides. By starting to use the Service, you are deemed to agree to the transfers above.
Other than the above, we do not provide personal information to a third party without the person's prior consent, except where required by law or where necessary to protect a person's life, body or property.
4. Cookies and similar technologies
The Service does not use cookies for tracking, such as third-party advertising or analytics. Even when usage analytics (PostHog) is used, the identifier assigned by its SDK is not stored in the browser (it is written to neither cookies nor local storage, and is discarded when the page is closed or navigated away from), and pages are linked using a per-conversation identifier held in the browser's session storage. To keep conversations going, prevent abuse and take measurements, we store our own visitor identifier in the browser's local storage or session storage, and send conversation content and similar to the providers listed in "3. Disclosure to external services and transfer abroad". We count views of our site (r2c.biz) with Cloudflare Web Analytics, which does not store an identifier in cookies or browser storage. To turn these off, you can delete cookies and local storage in your browser settings, but then features such as continuing a conversation will no longer be available.
5. Retention periods
We keep information for as long as needed to achieve the purposes of use and for the periods required by law. For conversation data, we regularly delete data that has passed its retention period automatically.
- Conversation data: 180 days. However, conversations of customers with data sharing enabled (always enabled on the free plan) may be kept longer than 180 days until our analysis platform (Hermes) has extracted them. After extraction, they are deleted according to the retention period above.
- Image files sent by end users: not stored (they exist only in our server's memory during receiving and reading, and are discarded afterwards). Summaries and similar results of reading are kept for the same period as conversation data. How AI providers handle data follows each provider's terms and data processing agreement.
- When a customer leaves: we delete the customer's conversation data 30 days after the contract ends.
- Inquiries and applications on our site: 2 years from the last exchange, then deleted. Even within that period, we delete them on request (see "6. Requests for disclosure, correction and deletion").
Information that we are legally required to retain (such as transaction records) is kept for the period set by the relevant law.
6. Requests for disclosure, correction and deletion
On request from the person concerned (or, for end users, through the customer that installed the Service), we respond to requests for disclosure (export of data), correction, suspension of use and deletion of the personal information we hold. The Service can disclose (export) and delete the relevant data by visitor identifier.
- Requests concerning end users are, in principle, accepted through the customer (the site operator) that installed the Service.
- Contact for requests: info@r2c.biz
- Identity verification and fees: we confirm that the requester matches the registered information, for example by a confirmation message to the email address registered at contract. There is, in principle, no fee.
7. Security measures
To prevent the leakage, loss or damage of the information we hold and to keep it secure, we take necessary and appropriate measures such as access control, encryption of communications and audit logging. Specifically, we use encryption of communications (TLS), access control for the database, hashed storage of API keys, logging of operations, and prompt review of access rights when permissions change.
8. Personal information manager and contact
For questions about this policy, and for complaints or consultations about our handling of personal information, please contact us as follows.
| Company | Mooores Inc. |
|---|---|
| Manager | Hiroki Kobayashi (Representative Director) |
| Contact | info@r2c.biz / GS Heim Shinjuku Minamiguchi 402, 5-32-5 Sendagaya, Shibuya-ku, Tokyo 151-0051, Japan |
9. Changes to this policy
We may revise this policy in response to changes in law or in the Service. When we make an important change, we will announce it on the Service or by another appropriate means.