Privacy Policy

This English version is a translation for reference. The Japanese version is the original and the only binding text. If the two differ, the Japanese version applies.

Doocts Inc. ("we" or "us") handles users' personal information in Ginro, our online werewolf game at https://ginro.app ("Ginro" or "the Service"), as set out below. Unless stated otherwise, words in this policy have the same meaning as in the Ginro Terms of Service.

Article 1 (About This Policy)

  • 1.
    This policy applies to the information about users that we collect through the Service.
  • 2.
    We comply with the Act on the Protection of Personal Information (APPI), related laws and regulations, and the guidelines of the Personal Information Protection Commission.
  • 3.
    The Ginro Cookie Policy covers cookies and the information sent from your device to outside parties.

Article 2 (Who We Are)

Article 3 (Information We Collect)

We collect the following information.

Type
What it includes
How we get it
Type
Login information
What it includes
Email address
How we get it
You enter it when you register and log in
Type
Google account information
What it includes
Google account identifier and email address
How we get it
We receive it from Google when you log in with Google
Type
Profile
What it includes
Display name, user ID, avatar (the combination of parts you chose and the picture we make from it), bio, social media account names
How we get it
You set it
Type
Game information
What it includes
Games you joined, role assignments, votes, ability use, text chat, wins and losses, rating, rank, achievements, leave records
How we get it
Recorded as the game runs
Type
Connections
What it includes
Follows and followers, blocks, registration invitations (who invited whom)
How we get it
Recorded when you use these features
Type
Online status
What it includes
Whether you are connected
How we get it
Recorded when you connect
Type
Reports and appeals
What it includes
What you report or appeal, details you add, records of how we handled it
How we get it
You send it
Type
Inquiries
What it includes
What you ask and your contact details
How we get it
You send it
Type
Notification address
What it includes
The address your browser's push service gives for notifications, the keys used to encrypt them, and their language
How we get it
Received from your browser when you turn notifications on
Type
Connection information
What it includes
IP address, browser type, date and time of access
How we get it
Collected automatically when you connect
Type
Usage
What it includes
Pages viewed (with IDs and similar parts hidden), types of actions, browser and device type, approximate region
How we get it
Collected automatically by analytics tools (see the Cookie Policy)

Notifications are delivered through the push service your browser uses (Google for Chrome, Apple for Safari, Mozilla for Firefox). We encrypt the text before sending it, so the push service cannot read it.

We do not collect your real name, address, phone number, date of birth or payment information. We also do not store voice (Article 6).

Article 4 (How We Use Information)

We use the information we collect for the following purposes:

  • 1.
    Registering accounts and logging in, and sending verification codes by email
  • 2.
    Providing games (matchmaking, running games, and relaying text and voice)
  • 3.
    Showing ratings, rankings, achievements, game history and profiles
  • 4.
    Providing following, blocking and invitations
  • 5.
    Reviewing reports and appeals, investigating and acting on breaches of the terms, and stopping people with a permanent ban from registering again
  • 6.
    Rate limits to prevent unauthorized logins and excessive load
  • 7.
    Investigating outages and correcting game results and ratings
  • 8.
    Answering inquiries
  • 9.
    Important notices, such as changes to the terms or the end of the Service
  • 10.
    Analyzing usage and improving the Service. For this, we use statistics that do not identify individuals
  • 11.
    Responding as required by law

If we change a purpose of use, we will keep the new purpose within the scope that can reasonably be seen as related to the old one. We will publish the changed purpose on the Service.

Article 5 (Information Other Users Can See)

  • 1.
    What other users and third parties can see (public profiles, rankings, game histories, online status and so on), and who can see it, is set out in Article 13 (Public Information) of the Terms of Service. Before you join, we tell you on screen that anyone can see the history of ranked games, and of casual games whose logs are made public, once the game ends.
  • 2.
    In anonymous villages, we show aliases and do not show your display name, avatar, profile or invitation relationships to others (Article 10 of the Terms of Service).
  • 3.
    Only you and we can see the list of people you invited.

Article 6 (Voice)

  • 1.
    We do not record voice during games, and we do not transcribe it.
  • 2.
    Voice reaches other participants through Cloudflare relay servers, which we use as a contractor. We do not store the content of voice.
  • 3.
    For a report about voice, we record only the game, the day and phase, a rough time, and any details the reporter adds.
  • 4.
    We cannot technically stop other users from recording on their own devices. The Terms of Service prohibit recording and publishing without permission.

Article 7 (Staff Access to Records)

  • 1.
    Our staff read a game's text chat (including private chats) only when the user who reported agrees to send the record of the chat they could read. Staff read only what was sent, and only to review that report and any appeal against an action based on it. This does not apply to histories anyone can see (Article 5, paragraph 1). Staff read the records of votes and abilities as far as needed for the purposes in Article 4, items 5 and 7.
  • 2.
    Staff can read only the cases they are handling and the information needed to review them. Moderators (staff in charge of handling reports) cannot see login information such as email addresses.
  • 3.
    Staff check the link between an alias in an anonymous village and an account only within the case they are handling.
  • 4.
    While a game is in progress, even staff cannot see hidden roles, private night chats, or votes and ability actions that are not yet final.
  • 5.
    When staff read records, we record who read which game, when, and why.

Article 8 (Avatars)

  • 1.
    You make your avatar by choosing from art parts that we provide. We store only the combination of parts you chose and the picture we make from it.

Article 9 (How Long We Keep Information)

We keep each type of information for the period below and delete it when the period ends.

Information
How long we keep it
Information
Game results, role assignments, rating changes, and per-player summaries (such as the day a player was eliminated and how many times they spoke; not what they said or whom they voted for)
How long we keep it
As long as we provide the Service
Information
Detailed records of votes, ability use and text chat
How long we keep it
90 days from the end of the game
Information
Report and appeal contents, records of how we handled them, and records preserved for review
How long we keep it
180 days after we finish handling every related case. If we review a case again during that time, 180 days after the new review ends
Information
Records of staff viewing, actions and changes to settings
How long we keep it
1 year from the operation
Information
Voice
How long we keep it
Not stored
Information
Login information, profile, avatar, follow connections
How long we keep it
Until you delete your account. We delete them within 30 days of deletion (Article 10)
Information
Notification address
How long we keep it
Until you turn notifications off or delete your account. It is also deleted when the push service tells us the address is no longer in use
Information
Matching values for people with a permanent ban (Article 10, paragraph 4)
How long we keep it
Until we lift the permanent ban or the Service ends. If we lift it, we delete them within 30 days of lifting it
Information
Matching values for people who deleted their account while a report about them was still being handled (Article 10, paragraph 5)
How long we keep it
Until we finish handling every report about the person, or until 180 days after they deleted their account. If we decide on a permanent ban in that time, we keep them as the values in Article 10, paragraph 4
Information
Connection information (such as IP addresses)
How long we keep it
Records for logged-in sessions: until the login expires (up to 30 days after last use). Records for counting login attempts: 1 day after last use
Information
Inquiries
How long we keep it
1 year after we finish handling them

After the retention period for detailed records ends, game results and ratings remain. In that case, the history shows that the retention period for detailed records has ended.

Information left in backups disappears after 7 days. When we are asked by law to preserve records, we may keep a copy of the information asked for beyond the periods above, until a date we set in line with the request.

Article 10 (When You Delete Your Account)

  • 1.
    When you delete your account, you can no longer log in, and we close your public profile right away. You are also removed from rankings and from following and follower lists.
  • 2.
    Your email address, link to your Google account, profile, avatar, and follow and follower relationships are deleted within 30 days of account deletion.
  • 3.
    Past game results, rating records and used invitation slots are kept in a form not linked to your profile, with the name shown as "Deleted user". Reports, appeals and staff records are kept until the periods in Article 9 end.
  • 4.
    If a person with a permanent ban deletes their account, we still delete the information in paragraph 2. However, to stop them from registering again, we keep, managed separately, values made from their email address and Google account identifier that cannot be turned back (HMAC with a key only we hold), together with the record of the action, and use them only to check new registrations.
  • 5.
    If a report about a person has not been fully handled when they delete their account, we also keep, managed separately, values made from their email address and Google account identifier in the same way as in the previous paragraph. We use these values to check new registrations, as the values in the previous paragraph, only if we decide on a permanent ban when reviewing that report. We delete them once every report about the person has been handled without a permanent ban, or once 180 days have passed since they deleted their account.

Article 11 (Sharing With Third Parties)

  • 1.
    We do not provide personal data to third parties without your consent, except where permitted by the Act on the Protection of Personal Information, such as when required by law.
  • 2.
    The following cases are not "providing to third parties" under the previous paragraph:
    • (1)
      When we outsource work to the extent needed to achieve the purposes of use (Article 12)
    • (2)
      When we move data to a company that takes over our business in a merger or business transfer. In that case, we will give users notice in advance

Article 12 (Contractors)

We outsource the following work to outside companies. We make agreements with them to handle personal information properly, and we supervise them as needed.

Contractor
Work
Main information handled
Contractor
Cloudflare, Inc. (United States)
Work
Running servers, storing records, relaying voice, content delivery and protection, relaying usage analytics
Main information handled
All types (voice is relayed only)
Contractor
Supabase, Inc. (United States; data stored on servers in Tokyo)
Work
Running the database
Main information handled
Records of accounts, profiles, games, reports and similar
Contractor
Plus Five Five, Inc. (operator of Resend, United States)
Work
Sending verification code emails
Main information handled
Email addresses
Contractor
Functional Software, Inc. (operator of Sentry, United States)
Work
Recording and analyzing errors in the app and on our servers, and receiving feedback
Main information handled
Error details, what you write as feedback and the state of the screen when you opened the feedback window, account ID, browser and device type, IP addresses

Information sent from your device to outside companies (usage analytics, font display, logging in with Google and so on) is set out in the Cookie Policy.

Article 13 (Handling Outside Japan)

  • 1.
    Some of the contractors in Article 12 are foreign companies. Cloudflare also has servers around the world and may handle information on a server near where you are, so we cannot name in advance the countries where it is handled.
  • 2.
    We ensure that our overseas contractors keep taking measures at the level the Act on the Protection of Personal Information requires (a "system meeting the standards" under Article 28, paragraph 1 of the Act). Specifically, we sign contracts with them on handling personal data, check their security measures through their published materials and third-party certifications, and review their handling regularly.
  • 3.
    The United States has no comprehensive nationwide law equivalent to Japan's APPI. Each state has its own laws. You can look up foreign systems in the Personal Information Protection Commission's "Survey on Personal Information Protection Systems in Foreign Countries."
  • 4.
    If you ask, we will tell you what the measures in paragraph 2 are and how we checked that they are being carried out.

Article 14 (Security Measures)

To prevent leaks, loss or damage of personal data, we name who is responsible and set rules for handling it (organizational measures), have staff promise confidentiality and teach them how to handle it (human measures), protect devices against theft and loss (physical measures), and limit staff permissions, record viewings and actions, and encrypt communications (technical measures). Personal data handled overseas is handled with an understanding of that country's system (Article 13).

Article 15 (Minors)

  • 1.
    The Service is for people 13 and older. We do not knowingly collect personal information from people under 13. If we find that a person under 13 has registered, we delete the account and the information.
  • 2.
    If you are under 18, get consent from your parent or guardian before you register.
  • 3.
    Parents and guardians can make the requests in Article 16 about their child's information.

Article 16 (Requests for Disclosure and Other Rights)

  • 1.
    You can make the following requests about the personal data we hold about you:
    • (1)
      To tell you the purposes of use
    • (2)
      To disclose it (you can choose the method, including electronic means)
    • (3)
      To correct, add to or delete its content
    • (4)
      To stop using it, to erase it, or to stop providing it to third parties
    • (5)
      To disclose records of providing it to third parties
  • 2.
    Send your request to the contact point in Article 20. If you use the contact page, choose Personal data as the topic and enter your registered email address as the reply address. We confirm your identity through your registered email address or by your logging in to the Service. If a parent, guardian or agent makes the request, we will ask for documents that confirm their authority.
  • 3.
    There is no fee for requests.
  • 4.
    We respond without delay. If we decline a request on legal grounds, we will tell you why.
  • 5.
    Once you delete your account, it becomes harder for us to confirm your identity. Make your request before you delete your account, or after deletion, contact us to discuss it.

Article 17 (Settings You Control)

You can do the following yourself:

  • 1.
    Change or delete your profile, bio and social media account names
  • 2.
    Hide your online status from followers
  • 3.
    Turning notifications about villages from people you follow on or off for each browser
  • 4.
    Block other users
  • 5.
    Delete your account
  • 6.
    Stop usage analytics (see the Cookie Policy)

Article 18 (If a Data Breach Happens)

If a leak of personal data or a similar incident happens and it falls under the cases set out in APPI, we will report it to the Personal Information Protection Commission and notify the people affected. If we cannot readily notify the people affected, we will take the alternative measures needed to protect their rights and interests, such as announcing the incident on the Service.

Article 19 (Changes to This Policy)

  • 1.
    We may change this policy to keep up with changes in the law or in the Service.
  • 2.
    Before an important change, such as a change in the purposes of use, takes effect, we will announce it on the Service and by in-app notice.

Article 20 (Contact)

Send questions or complaints about how we handle personal information, and requests under Article 16, to:

  • Online: the contact page on the Service
  • By post: Doocts Inc., Personal Information Inquiries, 2F-C, Shibuya Dogenzaka Tokyu Bldg., 1-10-8 Dogenzaka, Shibuya-ku, Tokyo 150-0043, Japan

We are not a member of any accredited personal information protection organization.

Effective date: November 11, 2026