This English translation is provided for reference only. In case of any discrepancy between this translation and the Japanese version, the Japanese version shall prevail.
Xincere Inc. handles the information it obtains in providing the scheduling service "DandoriSchedule" (the "Service") in accordance with this Policy.
This Policy sets out the handling specific to the Service. The handling of personal information by Xincere Inc. as a whole is governed by the privacy policy posted on our corporate website, but with respect to the use of the Service, this Policy applies with priority.
1Definition of Personal Information
In this Policy, "personal information" means information about a living individual that can identify a specific individual by name, date of birth, or other descriptions (including information that can be easily collated with other information and thereby identify a specific individual). It also includes email addresses, passwords, and information about the attributes of Users.
2Information We Collect
2-1. Information collected from Users (hosts)
- Account information: name, email address, username, and password (stored in hashed form)
- Booking page settings: title, description, booking hours, notification settings, etc.
- External service integration information: the identifier and email address of the Google account, and tokens for accessing the calendar (stored in encrypted form)
- Calendar availability: the start and end times of time slots in which events are scheduled in the linked calendar (free/busy information of Google Calendar). We do not read the titles of events to determine available times. We do not obtain the titles, descriptions, attendees, attachments, or meeting URLs of events
2-2. Information collected from Guests (people who make bookings)
- Name, email address, and any optional message entered
- The selected date and time, and the time zone used for display
2-3. Information collected automatically
- Access logs (IP address, date and time, referrer, user agent, etc.)
- Cookies for maintaining login status (those necessary for session management)
- Cookies and other identifiers for access analysis (details are described in "7. Use of External Services (Access Analysis)")
3Purposes of Use
- Providing the Service, verifying identity, and managing accounts
- Determining available times, confirming bookings, registering them in calendars, and issuing online meeting URLs
- Notifications of booking confirmations, changes, cancellations, and reminders
- Preventing unauthorized use, responding to failures, and improving quality
- Responding to inquiries
- Understanding and improving how the Service is used
4Voluntary Nature of Providing Information
Providing information to the Service is voluntary. However, if required items are not entered, you may be unable to use all or part of the Service, such as creating an account, linking a calendar, or accepting bookings.
5Handling of Google User Data
The use and transfer to others of information obtained by the Service through Google APIs ("Google user data") will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5-1. Scope of access
The Service requests only the minimum scopes necessary to provide its features. For calendars, it uses a read-only permission to determine available times (calendar.readonly) and a permission to register confirmed bookings (calendar.events).
5-2. Purposes of use
Google user data is used solely to provide the features of the Service: determining available times, confirming bookings and registering them in calendars, and sending notifications about bookings. We do not use it for advertising purposes, do not sell or provide it to advertisers or other third parties, and do not allow humans to read it (except where required by law, where necessary for security investigations, or with the User's explicit consent).
5-3. Handling with respect to AI and machine learning (compliance with Limited Use)
The Service does not use AI or machine learning models, nor does it integrate with AI or machine learning services provided by third parties. Accordingly, we do not use, transfer, or sell Google user data, in any form, whether raw, aggregated, anonymized, or derived, to create, train, or improve foundation models or any other generalized machine learning or artificial intelligence models.
The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
5-4. Information we store and information we do not store
- Stored: the identifier and email address of the Google account, the access token and refresh token for accessing the calendar (both stored in encrypted form), the identifiers of calendars the User has selected for integration, and the dates and times of confirmed bookings
- Not stored: the titles, descriptions, attendees, and attachments of events. The start and end times of events used to determine available times are processed only in the server's memory for that determination and are not stored in the database
5-5. Protective measures
Xincere Inc. takes the following security measures for sensitive data, including Google user data.
- Encryption in transit: All communications between the User's browser and the Service, and between the Service and Google APIs, are encrypted with TLS. The Service is provided only over HTTPS
- Encryption at rest: Access tokens and refresh tokens for calendars are encrypted with AES-256-GCM and stored in the database. Tokens are never stored in plaintext in the database
- Separation of encryption keys: The keys used for encryption are managed separately from the database, only in a configuration file on the server with restricted access permissions, and are not included in source code or version control systems
- Access control: Connections to the database are limited to those from within the server and are not exposed to external networks. Administrative connections to the server are limited to public key authentication and are made only by operations personnel
- Protection of credentials: User passwords are stored in hashed form and are not kept in plaintext. Login session identifiers are also stored in hashed form
- Least privilege and data minimization: We request only the minimum scopes necessary to provide the features, and we neither obtain nor store unnecessary information
- No recording in logs: Access tokens, refresh tokens, encryption keys, and passwords are not output to application logs or error monitoring records
5-6. Disconnecting the integration and deletion
The integration with Google Calendar can be disconnected at any time from the "Settings" screen of the dashboard. When disconnected, the stored access token and refresh token are deleted from the database. Likewise, if an account is deleted, the stored Google user data is deleted. You can also disconnect the integration from the Google account side via "Third-party apps & services" in your Google Account.
6Provision to Third Parties
Xincere Inc. does not provide personal information it has obtained to third parties, except in the following cases.
- Where the individual has consented
- Where required by law, or where necessary to protect the life, body, or property of a person
- Where we have contractors (for servers, email delivery, calendar integration, etc.) handle the information to the extent necessary to provide the Service. In this case, Xincere Inc. will appropriately supervise the contractors
- Where the information is provided in connection with the succession of business due to a merger, company split, business transfer, or other reasons. In this case, we will require the successor to handle the information in a manner equivalent to this Policy
- Where the information is disclosed or published after being statistically processed into a form that cannot identify individuals
When a booking is made, the name, email address, and message entered by the Guest are notified to the User (host) with whom the booking was made. This provision is necessary to carry out scheduling, which is the purpose of the Service.
Xincere Inc. does not sell personal information or Google user data it has obtained to third parties, nor does it provide such information to third parties for advertising or marketing purposes.
7Use of External Services (Access Analysis)
7-1. Analytics tools used by Xincere Inc.
Xincere Inc. uses the following analytics tools to understand and improve how the Service is used. These use cookies and other identifiers, but we never send them information obtained from Google Calendar (such as availability) or the names and email addresses entered by Guests. Xincere Inc. does not place advertisements for the Service and does not track Users for its own advertising purposes.
- Google Analytics (Google LLC) — measurement of page views. For how to opt out, see the Google Analytics Opt-out Browser Add-on
- Microsoft Clarity (Microsoft Corporation) — measurement of trends in on-screen interactions. Used only on the sign-up, contact, and adoption consultation form screens, with the contents of input fields masked
7-2. Tracking tags set by hosts
The Service has a feature that allows Users (hosts) to set, on their own booking pages, the identifier of a Meta (Facebook) pixel that they manage. Only on booking pages for which a host has made this setting, the Meta Platforms, Inc. tag is loaded on the screen shown when a booking is completed, and the fact that "a booking was made" is sent to that host's measurement destination. Entered information such as names, email addresses, and messages is not sent.
This tag is installed by the host at the host's own discretion, and the destination and the handling of the information obtained are the responsibility of that host. It is not loaded on booking pages where it has not been set. You can change the settings for the ads delivered to you from Meta's ad preferences.
7-3. Disabling cookies
You can also refuse such collection by disabling cookies in your browser settings. However, if you disable the cookies necessary for maintaining login status, you will not be able to use the Service.
8Retention Period
- Account information and booking page settings: for as long as the account exists
- Booking information: retained for a certain period after the booking has taken place or been canceled, in order to respond to inquiries
- Access logs: for the period necessary for failure investigation and prevention of unauthorized use
9Security Management
Xincere Inc. takes the following security measures to prevent leakage, loss, or damage of the information it obtains. Details of the measures for sensitive data, including Google user data, are described in "5-5. Protective measures".
- Communications with Users' browsers and with external services are encrypted with TLS
- Passwords and session identifiers are stored in hashed form and are not kept in plaintext
- Tokens for calendar integration are encrypted with AES-256-GCM and stored, and the encryption keys are managed separately from the database in an area on the server with restricted access permissions
- Access to the database is limited to within the server and is not exposed externally
- Credentials and encryption keys are not output to application logs or error monitoring records
- We continuously fix vulnerabilities and monitor the operating status
10Management Structure
- Xincere Inc. has appointed a personal information protection manager and has established internal rules on the handling of personal information
- We provide necessary supervision of employees who handle personal information
- Personal information that no longer needs to be used, and personal information whose retention period has expired, is erased or disposed of without delay
11Requests for Disclosure, Correction, and Deletion
At the request of the individual, we will respond to requests for disclosure, correction, suspension of use, or deletion of retained personal data. Please send requests via the contact form. We will respond after verifying your identity.
12Changes to This Policy
We may change this Policy in response to amendments to laws and regulations or changes to the Service. When making important changes, we will give notice by posting on the Service or by other means.
13Contact
Please contact the personal information protection officer of Xincere Inc. via the contact form.