Privacy Policy
Last updated: October 23, 2026
The Japanese version of this document is the governing text; this English translation is provided for convenience. In the event of any discrepancy, the Japanese version prevails.
Crabgrass Inc. ("we", "us" or the "Company") sets out in this Privacy Policy (this "Policy") how we handle personal information and other information of users of "ZENITH Code", the Japanese equity data API service we provide (the "Service"), in compliance with the Act on the Protection of Personal Information of Japan (the "APPI") and other applicable laws and guidelines.
1. Information We Collect
In providing the Service we collect the following information.
- (1)Account information: your name, email address, profile image and the identifiers used for authentication. We obtain these through the authentication platform we use (Clerk). If you sign in with an external account such as Google, we receive the email address, name, profile image and similar data provided by that service. Passwords are held by Clerk; we do not store them.
- (2)API key issuance and usage data: the name of each API key, a hash of the key, the dates of issuance and last use, your plan, and per-request usage logs (timestamp, endpoint, token cost, response status, response time, data volume, cache layer and country of origin). The plaintext key is shown only once, at issuance; we store only its hash.
- (3)Subscription and billing data: your plan, the customer ID, subscription ID and transaction IDs issued by Paddle, subscription status, billing period, and the date and amount of each transaction. Payment details such as card numbers, expiry dates, security codes and billing addresses are collected and stored by Paddle, our Merchant of Record; we do not receive them.
- (4)Technical data and analytics: IP address, browser and operating system, referrer, pages viewed, access times, and identifiers such as cookies. Our website and API are delivered through the Cloudflare network, and we obtain this data through the logging and analytics features Cloudflare provides and through Google Analytics (Section 4).
- (5)Enquiry data: the name, email address and content you provide when you contact us, and the record of our correspondence.
- (6)Information about contacts at corporate customers: the names, departments, titles, email addresses and addresses of contacts and signatories provided by corporate customers for quotes, contracts and billing, and records of invoices issued and bank transfers.
2. How We Use Information
We use the information we collect for the following purposes.
- (1)Providing the Service, verifying identity, and managing accounts and API keys.
- (2)Enforcing usage limits (monthly quotas and rate limits) and displaying usage in the dashboard.
- (3)Sending service notifications by email, such as usage alerts that tell you when your monthly token usage reaches a share of your limit. You can turn usage alerts off, or add recipients, at any time on the settings page of the dashboard.
- (4)Managing paid-plan subscriptions, billing and confirming payment status, including through our integration with Paddle.
- (5)Detecting and preventing abuse, breaches of the Terms of Service and security threats.
- (6)Responding to enquiries and sending important notices such as outages, maintenance and changes to our terms.
- (7)Improving the Service and developing new features through statistical analysis of usage.
- (8)Under an organisation contract (an Enterprise organisation), showing or reporting members' participation, number of API keys and usage (such as token counts) to the administrators of the contracting organisation, and handling quotes, contracts and billing.
- (9)Complying with legal obligations and handling disputes.
- (10)Sending information about the Service, such as new features and plans. You can opt out of these communications at any time.
5. Security Measures
To prevent the leakage, loss or damage of the personal information we handle, and otherwise to keep it secure, we take the following measures.
- (1)Encryption of all communications with TLS.
- (2)Storing API keys only as hashes, and not storing passwords.
- (3)Minimising access rights and using multi-factor authentication.
- (4)Checking the security arrangements of providers before entrusting them with data.
- (5)Maintaining and periodically reviewing security measures required under the APPI.
6. Retention
We keep personal information only for as long as necessary for the purposes described above, after which we delete or anonymise it without undue delay. As a guide:
- (1)Account information and API keys: deleted within 30 days of account deletion (and progressively removed from backups).
- (2)API usage logs: per-request logs are kept for 90 days; daily and monthly aggregates are kept for the life of the account.
- (3)Subscription and transaction records: kept for 7 years after the transaction, in line with retention obligations under tax and other laws.
- (4)Email delivery records (time sent, masked recipient, subject and delivery result): kept for 90 days after sending. We do not store message bodies.
- (5)Enquiry records: kept for 3 years after the matter is closed.
7. Your Rights
Under the APPI you may ask us to notify you of the purposes of use of your personal information, to disclose it, to correct, add to or delete it, to suspend its use or erase it, and to stop providing it to third parties.
Please send requests from your registered email address to our contact address (support@zenithcode.net). After verifying your identity we will respond within a reasonable period in accordance with the law. If the law does not allow us to comply with a request, we will tell you so and why. As a rule we do not charge a fee for such requests.
You can view and change your account information (name, email address, profile image and so on) yourself in the dashboard settings. You can revoke API keys from the dashboard at any time.
8. Links to External Services
The Service may contain links to external websites and services, such as the Paddle checkout and the websites of our data sources. We are not responsible for how those external services handle personal information.
9. Changes to this Policy
We may change this Policy in response to changes in the law, the Service or otherwise. We will announce material changes by posting on the Service or by notice to your registered email address. The amended Policy takes effect when it is posted on the Service.
10. Controller and Contact
For questions, complaints and requests concerning personal information, please contact: Controller: Crabgrass Inc.; Personal information protection manager: Sohei Taniguchi, Representative Director; Contact: support@zenithcode.net. Our address and other company details are given in the operator block at the end of this page.
Operator
- Company
- Crabgrass Inc.
- Representative
- Sohei Taniguchi, Representative Director
- Address
- Wakore Shinjuku Daiichi Bldg., 7-7-26 Nishi-Shinjuku, Shinjuku-ku, Tokyo 160-0023, Japan
- Established
- 2024
- Payment processor
- Paddle.com Market Limited (UK) and its affiliates
- Contact
- contact@zenithcode.net

