Privacy Policy
In operating “MintJams Pass” (the “Service”) provided on members.mintjams.jp, MintJams Inc. (the “Company”) has adopted a system design that acquires and retains as little personal information of Members as possible. This Privacy Policy (this “Policy”) sets out the scope of the information that the Service retains and does not store, the data sent to external services, and the retention periods.
1. Information We Do Not Store
The Service does not store the following personal information:
- email addresses;
- names;
- postal addresses and telephone numbers; and
- credit card numbers and other information concerning means of payment.
2. Information We Retain
| Identifiers of the external accounts used to sign in | The name of the external provider and the user-specific identifier string issued by that provider (iss and sub in OpenID Connect). These are used to associate the Member account with the external accounts. |
|---|---|
| Purchase history | The date and time of purchase, the plan purchased and the number of days added, the period of use, the amount paid, the tax amount and the currency, the price category, and the customer identifier, payment identifier and invoice identifier issued by the payment service provider. Details of the means of payment, such as card numbers, and the billing name, billing address and email address are not included. |
| Connection log | For each MintJams CMS or MCP client connected to the Member account: the connection identifier, the type of connection, the client name, the destination (for a CMS, its host name; otherwise, the origin of the redirect destination), the scope permitted, the connection name optionally given by the Member at approval, the date and time of approval, and the date and time of last use. The Member’s user name on its MintJams CMS is not stored. |
| Handover codes and recovery codes | Their hashed values, purpose, expiration date, and the date and time of use. |
| Usage history | The date and time of member registration, the date and time of consent to the Terms of Service, the date and time of last use and, if withdrawal has been requested, the date and time of such request. In addition, for the purposes of operation and incident response, the following operations are recorded in the server logs for a certain period together with the member identifier and the date and time: the addition of an external account (provider name), the approval of a connection (client name, type of connection, destination), the issuance of handover codes and recovery codes, requests for withdrawal, package downloads (file name), and the recording of periods of use upon purchase. For requests to the Knowledge MCP server, only the date and time of the call, the tool name, the connection identifier and the names of the arguments specified are recorded. The values of arguments, such as the content of questions entered, are not recorded. |
3. Information Sent to or Shared with External Services
| Authentication providers (Google, Microsoft, etc.) | When a Member authenticates on a provider’s sign-in screen, the Company sends that provider the identifying information of the Service (client ID) and the redirect URL. Of the information provided to the Company by the provider, the Company retains only the identifiers set forth in Section 2. |
|---|---|
| Payment service providers (Stripe, etc.) | When making a purchase, the Member enters payment information, an email address and the billing information needed to calculate tax (country, postal code, address and the like; for a business, its tax registration number and name) on the payment screen provided by the payment service provider. This information is managed and retained directly by the payment service provider and does not pass through the Company’s servers. Tax is calculated by the payment service provider’s tax calculation service based on the billing information, and an invoice and a receipt stating the Company’s registration number, the tax rate and the tax amount are issued and sent directly by the payment service provider. The Company sends the payment service provider the member identifier, the plan purchased, the number of days to be added, the price and currency, and the display language of the screens. From the payment service provider, the Company receives notice that the payment has been completed, the customer identifier, the payment identifier, the invoice identifier, the amount paid and the tax amount, and information on the purchased period, and records them as the purchase history set forth in Section 2. Notices from the payment service provider may include billing information and an email address, but the Company does not store them. For the payment service provider’s policy on the handling of information, please refer to the payment service provider’s privacy policy. |
| AI platforms (Anthropic, etc.) | Connections to the Knowledge MCP server are made through an AI assistant that the Member has contracted for individually. The Company does not provide Members’ personal information to AI assistants. Data such as the content of questions sent from an AI assistant to the Knowledge MCP server is handled in accordance with the terms and policies of the provider of that AI assistant. |
4. Use of Cookies
- The Service uses cookies only for the purposes of the sign-in procedure, of keeping the Member signed in, and of remembering the chosen display language and currency. The contents of the cookies used for signing in are encrypted.
- The cookie that keeps the Member signed in contains information for identifying the Member and the name and email address received from the external provider for display on the screens while signed in. This information is not stored on the server and is lost upon signing out or when the cookie expires.
- Cookies used only during the sign-in procedure are deleted when the procedure is completed and, if the procedure is abandoned, expire within a short time.
- The cookies that remember the display language and currency record only the language chosen (Japanese or English) and the currency chosen (Japanese yen or US dollars), and contain no information that identifies the Member. They are set when a page address specifies the language or currency (including when the Member switches them on a page and when the Member comes to this site from the Portal or the payment screen) and expire after one year.
- We do not use cookies for access analytics or advertising, and we do not use any third-party tag management tools.
5. Purposes of Use
The information acquired and retained by the Company is used only for the following purposes:
- verifying the identity of Members and providing the Service on the basis of their Term of use;
- managing purchase history and reconciling data with the payment service provider;
- recovering accounts and carrying out handover procedures; and
- detecting and preventing unauthorized access, and responding to system failures.
6. Retention Period and Deletion
- The information of an account for which the withdrawal procedure has been completed will be deleted promptly after the end of the Term of use of the Service. For an account with no Term of use, the information will be deleted after the request for withdrawal has been accepted.
- Even where the withdrawal procedure has not been carried out, an account for which no use of the Service can be confirmed for two years or more from the end date of its last Term of use will be deleted automatically.
- Deleted information described in Section 2 cannot be restored. Payment transaction records retained by the payment service provider will be kept for a certain period as accounting records of the payment service provider and of the Company, in accordance with statutory bookkeeping obligations. Where such records include a Member’s email address or the like, they are managed in accordance with the rules of the payment service provider.
7. Members’ Review of Information and Deletion Procedures
- The registered information held by the Company can be reviewed at any time on the Portal screen of the MintJams CMS in use or on My Page on this site.
- Members may carry out the withdrawal procedure at any time, for any reason. Linked connections can be revoked from both the Portal screen and My Page.
8. Security Measures
The Company limits access rights to the information it retains to the minimum necessary for the system processing of the Service and, through appropriate access control, ensures that such information is separated from and protected against third parties and the Company’s other business divisions. In addition, connection-related information stored on a Member’s MintJams CMS is kept encrypted using a key unique to the Member’s MintJams CMS.
9. Changes to this Policy
When changing the content of this Policy, the Company will give notice by posting it on this page. When making an important change, such as adding items of information to be acquired or substantially changing the purposes of use, the Company will also give advance notice on My Page on this site.
10. Contact
For questions, comments or any other inquiries concerning this Policy, please contact us via the Company’s contact form.