Everyone's Vertical Calendar API and AI Connection Terms of Use

Everyone's Vertical Calendar (“みんなの縦型カレンダー”) · Established: October 22, 2026 · Revised: November 7, 2026

日本語

Article 1 (Purpose and Scope)

These Terms set out the conditions for using the API and AI connection features (the “Feature”) of “Everyone's Vertical Calendar” provided by Funeasy Soft, Inc. (“we” or “us”). Anyone who uses the Feature (a “User”) is deemed to have agreed to these Terms when requesting an API key. Matters not covered by these Terms are governed by the Everyone's Vertical Calendar Premium Terms of Use (Japanese) and our Privacy Policy.

Article 2 (Definitions)

1. “API key” means a string issued by us for using the Feature.
2. “Requester” means the User who requested the API key.
3. “Connected service” means an AI service, app, tool or similar service provided by someone other than us, to which a User connects using an API key.
4. “Target calendar” means the calendar for which the API key was issued.

Article 3 (Conditions of Use)

1. Only Users with administrator or editor permissions on a calendar with an active Family, Pro or Business plan may request the Feature.
2. We set conditions such as the number of API keys, the number of calls, eligible items and the number of items, and announce them in the app or on our website. If the conditions are no longer met, the API key is stopped automatically and resumes when they are met again.
3. Items that import events from Google Calendar, and events imported from Google Calendar, are not covered by the Feature.
4. An API key becomes active 24 hours after it is requested.

Article 4 (Managing API Keys)

1. The Requester manages the API key at their own responsibility and must not disclose, transfer or lend it to any third party.
2. The API key is shown to the Requester only once. We will not show it again.
3. If the API key has been, or may have been, leaked, the Requester must revoke it immediately.
4. Operations performed with the API key are deemed to have been performed by the Requester.

Article 5 (Consideration for Other Members)

1. Because an API key can read and write all items and schedules in the target calendar, schedules entered by other members are also passed to the connected service.
2. The Requester must explain this to the other members of the target calendar and obtain their understanding before using the Feature.
3. We notify all members of the target calendar when an API key is requested, activated, stopped or revoked. Administrators of the target calendar can revoke an API key at any time.

Article 6 (Connected Services)

1. Connected services are chosen by Users at their own discretion and are not provided or managed by us.
2. The handling of data passed to a connected service (including storage and use for AI training) is governed by that service's terms and privacy policy. We are not responsible for how connected services handle data.
3. We are not responsible if the Feature becomes unavailable because of changes to, suspension of, or failures in a connected service.

Article 7 (Operations by AI and Other Services)

1. Connected services (including AI) may misinterpret a User's instructions and add, change or delete schedules unintentionally.
2. Users are responsible for checking the results of operations by connected services. Changes can be reviewed in the edit history and reverted within the app's features.

Article 8 (Call Limits)

1. We set limits on the number of calls per calendar (the total of all API keys of the calendar) and per API key (for example, per minute and per day). The limits may differ depending on the calendar's plan. Calls exceeding the limits are not processed.
2. We may change the limits to keep the service stable.

Article 9 (Prohibited Acts)

When using the Feature, Users must not:

1. circumvent call limits or other conditions (including by using multiple accounts or calendars to avoid limits);
2. place, or risk placing, an excessive load on the Feature or our servers;
3. attempt to gain unauthorized access to data other than the target calendar;
4. provide or resell the Feature as a service for third parties without our permission;
5. violate laws or public order and morals, or infringe the rights of third parties; or
6. do anything else we consider inappropriate.

Article 10 (Suspension and Revocation)

1. We may suspend or revoke an API key without prior notice if a User violates these Terms or if we consider it necessary for operating the Feature.
2. An API key expires automatically 90 days after it was last used (or, if never used, 90 days after it became active).

Article 11 (Changes and Termination)

We may change the Feature, or suspend or end its provision, without prior notice to Users.

Article 12 (Disclaimer)

1. We do not guarantee that the Feature fits any particular purpose of a User, has the expected functions, accuracy or usefulness, or is free from defects.
2. Except in cases of our willful misconduct or gross negligence, we are not liable for any damage to Users arising from the use of, or inability to use, the Feature.

Article 13 (Changes to These Terms)

We may change these Terms when we consider it necessary. The changed Terms take effect when posted on our website.

Supplementary provision: These Terms take effect on October 22, 2026.

For how to use the Feature, see AI connection (API). For questions, contact support or email admin@funeasy-soft.com.