Privacy policy
This privacy policy describes how Awnexa (the “Operator”) handles personal information in the Awnexa website (the “Site”), the Awnexa command-line tool and MCP server (the “CLI”), and related services (together, the “Services”).
1. Basic policy
Section titled “1. Basic policy”The Operator complies with the Act on the Protection of Personal Information of Japan (the “APPI”) and other applicable laws, and handles personal information only as needed to provide the Services.
2. The CLI
Section titled “2. The CLI”The CLI calls AWS APIs read-only with the user’s own credentials and stores the configuration it collects on the user’s machine. The CLI does not send AWS configuration (resource IDs, ARNs, names, tags, settings, etc.), AWS account IDs or credentials to the Operator or to any third party. The Operator does not receive or hold this information.
The only data the CLI sends to the Operator is the usage statistics below.
2-1. Usage statistics
Section titled “2-1. Usage statistics”Usage statistics describe how the CLI is used (the names of the commands and options run, how the command ended, the error category, the duration, counts as ranges, the Awnexa and Node.js versions, the operating system, etc.) and are sent to the Operator’s own backend. Every field sent, and what is never sent, is listed on Data the CLI sends. A new field is listed on that page before the release that sends it. Only CLI releases from the one named on that page onward send usage statistics.
- They are on by default. The first time the CLI runs, it shows that usage statistics are sent and how to turn them off, and sends nothing on that run. When run in a terminal, it also asks whether to keep them on. Sending starts with the next run.
- They can be turned off at any time with
awnexa telemetry disable, or the environment variableAWNEXA_TELEMETRY=0orDO_NOT_TRACK=1.awnexa telemetry disablealso deletes the install ID and any unsent usage statistics on the user’s machine. While an environment variable turns them off, nothing is recorded or sent. awnexa telemetry showshows what will be sent and what was sent.- The install ID is a random value the CLI creates for each machine. It is not derived from the AWS account, user name or host name.
- Before sending, the CLI checks for strings that look like an AWS account ID, an ARN or an IP address, and does not send usage statistics that contain one. The Operator’s backend makes the same check and does not store usage statistics that do not match the listed fields.
- The sender’s IP address is processed only to deliver the request and to refuse requests from addresses that send an excessive amount in a short time; it is not recorded or stored.
Usage statistics are designed so that they cannot identify a specific individual on their own. The Operator does not use them to identify individuals and does not combine them with other information. The purposes in section 3, the retention in section 5, the storage location in section 7 and the security measures in section 8 also apply to usage statistics.
2-2. Transmission of user information
Section titled “2-2. Transmission of user information”The Operator publishes the following about the usage statistics sent by the CLI.
| Information sent | Recipient | Purpose at the recipient |
|---|---|---|
| The fields listed on Data the CLI sends (including the install ID) | The Operator (https://api.awnexa.net/v1/events) |
The usage statistics purposes in section 3 |
The Operator does not provide or sell usage statistics to third parties and does not use them for advertising.
3. Information collected and purposes
Section titled “3. Information collected and purposes”| Information | How it is collected | Purposes |
|---|---|---|
| The content of inquiries, email addresses, names (if given) and other information in emails | Emails from users | Answering inquiries, verifying identity, improving the Services, handling bugs and security issues |
| Information about access to the Site (IP address, time, requested URL, referrer, browser type / User-Agent, etc.) | Recorded automatically when the Site is served, if access logging is enabled | Operating the Site reliably, responding to unauthorized access and attacks, and counting page views in a form that does not identify individuals |
| Usage statistics (section 2-1; the fields listed on Data the CLI sends) | Sent by the CLI (can be turned off) | Improving the Services (understanding which features are used and trends in collection failures and errors, prioritizing features), finding and fixing bugs, designing the pricing and the scope of the free and paid editions, and counting usage in a form that does not identify individuals |
| An install ID given in a request to delete usage statistics | Emails from users | Deleting the matching usage statistics |
The Operator does not handle personal information beyond these purposes. Any change of purpose stays within a scope reasonably related to the original purpose and is announced on the Site.
4. Cookies and analytics
Section titled “4. Cookies and analytics”The Site does not use cookies, third-party analytics or advertising services. The Site may store settings such as the display theme in the browser’s local storage or session storage; these stay in the user’s browser and are not sent to the Operator.
5. Retention
Section titled “5. Retention”- Inquiry emails: kept for 1 year from the date of receipt, then deleted. Where the law requires them to be kept, or they are needed to handle a dispute, misuse or a security issue, they are kept for as long as that requires.
- Information about access to the Site: if recorded, kept for up to 90 days, then deleted. Aggregated results that do not identify individuals may be kept.
- Usage statistics: kept for 13 months from the date of receipt, then deleted. Aggregated results that do not contain install IDs may be kept. Records of the receiving process (such as the number of events accepted; they contain no IP addresses or install IDs) are deleted after 30 days.
6. Disclosure to third parties
Section titled “6. Disclosure to third parties”The Operator does not provide personal data to third parties without the person’s prior consent, except:
- where required by law;
- where necessary to protect a person’s life, body or property and it is difficult to obtain the person’s consent;
- where necessary to cooperate with a national or local government body (or its contractor) performing duties prescribed by law, and obtaining consent could impede those duties; or
- in other cases permitted by the APPI.
7. External services and storage locations
Section titled “7. External services and storage locations”The Operator uses the following external services to run the Services and stores personal information on their facilities.
| Service | Use | Storage location (country) |
|---|---|---|
| Amazon Web Services (AWS) | Serving the Site; storing access information; receiving and storing usage statistics | United States (us-east-1 Region) |
| Google Workspace (Google LLC) | Sending, receiving and storing inquiry emails | United States and other countries |
Under their contracts, these providers do not handle the data the Operator stores without the Operator’s instructions. The Operator takes the security measures in section 8 with an understanding of the personal information protection systems of these countries. For the United States, see the information published by the Personal Information Protection Commission of Japan.
8. Security measures
Section titled “8. Security measures”To prevent leakage, loss or damage of personal data, the Operator takes the following measures:
- Policy and rules: this policy, and defined methods and responsibilities for collecting, using, storing and deleting personal data.
- Organizational and personnel measures: limiting who handles personal data, checking how it is handled, and defining how incidents such as leaks are reported.
- Physical measures: preventing the loss or theft of devices that handle personal data, with screen locks and disk encryption.
- Technical measures: multi-factor authentication and least-privilege access to external services, and encryption in transit and at rest.
- Understanding the external environment: taking the measures above with an understanding of the personal information protection systems of the countries in section 7.
9. Requests
Section titled “9. Requests”A person may request notification of the purposes of use, disclosure (including records of provision to third parties), correction, addition or deletion, suspension of use or erasure, and suspension of provision to third parties of their personal data held by the Operator. Please send requests by email to the contact in section 11. After verifying the person’s identity, the Operator responds without delay in accordance with the law. There is no fee.
Usage statistics are not linked to information that identifies a person, so to have them deleted,
please include the install ID (installId) shown by awnexa telemetry status. The Operator
deletes the usage statistics with that install ID. To stop future sending, turn usage statistics
off as described in section 2-1.
10. Changes to this policy
Section titled “10. Changes to this policy”The Operator may change this policy to reflect changes in law or in the Services (including the addition of usage statistics fields or a waitlist). Material changes are announced on the Site before they take effect.
11. Contact
Section titled “11. Contact”- Operator: Awnexa
- Contact: support@awnexa.net
- The Operator’s address and the name of its representative are provided without delay on request.
Established: October 24, 2026