Cookie 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") runs Ginro, an online werewolf game at https://ginro.app ("Ginro" or "the Service"). This notice describes the information the Service stores on your device and the information it sends from your device to outside parties.

Article 1 (Purpose of This Notice)

  • 1.
    This notice explains the cookies and other on-device storage that the Service uses.
  • 2.
    It also discloses, under Article 27-12 of the Telecommunications Business Act, what information the Service has your device send to outside parties, who receives it, and why.
  • 3.
    Any information sent that counts as personal information is handled under the Ginro Privacy Policy.

Article 2 (Cookies and On-Device Storage)

A cookie is a small piece of data a site has the browser store, which the browser sends back the next time you open that site. The Service also uses the browser's "local storage". What is in local storage is not sent automatically. In this document, we call both together "cookies and similar".

Article 3 (Cookies and Similar Technologies the Service Uses)

1. For login and security (the Service will not work if you block these)

Name
Set by
Purpose
Duration
Name
__Secure-better-auth.session_token
Set by
Us (api.ginro.app)
Purpose
Keeps you logged in
Duration
30 days. Extended once a day when you use the Service
Name
__Secure-better-auth.session_data
Set by
Us (api.ginro.app)
Purpose
Briefly remembers your login state so it can be checked faster
Duration
5 minutes
Name
Temporary cookies used when logging in with Google (such as __Secure-better-auth.state)
Set by
Us (api.ginro.app)
Purpose
Checks that you returned from Google correctly
Duration
Until you finish logging in
Name
ginro_signed_in
Set by
Us (ginro.app)
Purpose
Takes you to your home instead of showing the top page while you are logged in
Duration
30 days. Deleted when you log out

Login cookies are set so that scripts in the browser cannot read them (HttpOnly), and they are sent only over encrypted connections (HTTPS). ginro_signed_in only marks whether you are logged in and is written by scripts in the browser. It is not used to check your login, and the service still works if you block it.

2. For remembering settings (local storage; never sent to outside parties)

We save in the browser's local storage your screen colors, display language, tutorial progress, where to return after logging in, the setting not to send usage analytics, and whether you answered the notification offer. These are not sent outside and stay until you clear them in your browser settings. A browser that turns notifications on registers a program to show them (a service worker), which is removed when you turn them off.

3. For usage analytics

Name
Set by
Purpose
Duration
Name
cf_zaraz_client
Set by
Cloudflare Zaraz
Purpose
Lets the analytics system (Zaraz) recognize the same browser
Duration
1 year
Name
cfz_google-analytics_v4
Set by
Cloudflare Zaraz (for Google Analytics)
Purpose
Counts visits from the same browser together
Duration
1 year

Article 4 (Information Sent to Outside Parties and Who Receives It)

The Service sends the following information from your device to outside companies.

Recipient
Information sent
Purpose
Recipient
Google LLC (Google Analytics). Sent through Cloudflare Zaraz, run by Cloudflare, Inc.
Information sent
The location and title of pages viewed, display language, types of actions (registering, starting and finishing the tutorial, creating and joining villages, waiting for a ranked match, sharing) and details attached to them (such as the number of players in a village, whether it is public, and the ranked format), browser and device type, referring page, approximate region estimated from your IP address, and an analytics identifier
Purpose
To analyze how the Service is used and improve it
Recipient
Cloudflare, Inc. (Cloudflare Realtime)
Information sent
Voice, IP address, connection information
Purpose
To deliver voice during games to other participants. We do not record voice
Recipient
Google LLC (logging in with Google)
Information sent
What you enter on Google's login screen, IP address, browser type
Purpose
To log you in with your Google account when you choose to
Recipient
Cloudflare, Inc. (Cloudflare Turnstile)
Information sent
IP address, browser and device type and settings, and how you interact with the page
Purpose
To check that a person, not automated spam, is sending the contact form or signing in or signing up with an email code. Sent only when you open the contact page, or when a sign-in or sign-up screen asks for the check
Recipient
Functional Software, Inc. (Sentry)
Information sent
What went wrong (the error message and where in the program it happened), the page where it happened and the pages you visited before it, browser and device type, browser language and time zone, and IP address (we set Sentry not to store it). When you send feedback, also what you wrote, the state of the screen when you opened the feedback window (the page, how far the game had got, the voice connection) and your account ID
Purpose
To find and fix bugs in the Service and improve it. Sent only when an error occurs or when you send feedback

Usage analytics and error reports never send your email address, display name, user ID, or text you type such as chat. Feedback sends what you wrote and your account ID, but not your email address, display name or chat. Usage analytics also does not send what you do inside anonymous villages, roles, or wins and losses.

For usage analytics and error reports, page addresses are sent with IDs and codes hidden (for example, /villages/:id). We hide village IDs, invitation tokens, user IDs and short link codes. Nothing after the "?" in a URL is sent.

The recipients' privacy policies are as follows.

Article 5 (How to Stop Sending)

  • 1.
    You can delete cookies or refuse them in your browser settings. However, if you block login cookies, you cannot log in to the Service.
  • 2.
    To stop usage analytics, turn on "Don't send usage analytics" in the settings screen or on this page. That browser then stops sending analytics. You can use the switch on this page without logging in. Blocking the analytics script with a browser extension or similar tool also stops it. All features of the Service keep working when analytics is off.
  • 3.
    Voice relay is needed to exchange voice in voice games. If you do not want to send voice, mute your microphone.
  • 4.
    The check is sent only when you open the contact page, or when a sign-in or sign-up screen asks for it. Those screens ask only when unusually many email codes are being requested. If you'd rather not send it, email us at support@ginro.app instead of using the contact form, and sign in another way instead of with an email code.
  • 5.
    For how to clear or block cookies, see your browser's help.
Don't send usage analytics
This setting is saved only in this browser. Every feature keeps working with analytics off.

Article 6 (Changes to This Notice)

  • 1.
    When we change the recipients or the information sent, we will update this notice.
  • 2.
    When we add a new recipient, we will update this notice before we start sending information to it.

Article 7 (Contact)

Send questions about this notice to:

  • Online: the contact page on the Service
  • By post: Doocts Inc., 2F-C, Shibuya Dogenzaka Tokyu Bldg., 1-10-8 Dogenzaka, Shibuya-ku, Tokyo 150-0043, Japan
Effective date: November 11, 2026