MAIND / Mobile AI IDE

Privacy policy

MAIND Privacy Policy Version: 20 November 2026 Operator: monoづくりMode Contact: mono.dukuri.mode@gmail.com

1. Scope

This policy covers MAIND - Mobile AI IDE for Android. MAIND is a development tool for using terminals, editing files and operating external AI tools on an SSH server you choose. MAIND does not provide its own end-user account registration.

2. On-device information

Connection labels, hostnames, usernames, ports, working directories, settings and conversations are stored in the app's storage. Ordinary connection settings and conversation history are not all encrypted. Conversations and execution summaries can include information you work with. Saved SSH private keys, passwords, passphrases and supported authentication tokens use protected storage backed by Android Keystore. Biometric authentication is handled by Android; MAIND does not obtain fingerprint images, face images or biometric templates. Android automatic backup and device-to-device app-data transfer are disabled.

3. SSH, AI and Git

Your connection, sending, transfer, save and command actions send the information needed for those actions to your selected SSH server over encrypted SSH. Public-key authentication signs challenges; it does not copy your on-device private key to the server. AI runs through a remote CLI or an inference environment you choose. Prompts, attachments, working files and results may be sent to the external AI service you use. That service's terms, settings, retention, training and charges apply. Local LLM support also uses the selected remote environment, rather than running inference entirely on the phone. Git actions communicate with your selected repository host. MAIND's trial and purchase management API does not receive SSH secrets, server credentials, conversation bodies, source code or working files.

4. Trial management

To manage a trial of 100 successful new SSH connections, the app sends a derived matching ID, connection operation IDs, operation states and timestamps to our HTTPS API. The matching ID is derived from an Android identifier scoped to factors including the on-device user and app signing key. The API runs on Cloudflare Workers and D1 and stores a further HMAC-transformed matching key and the usage count. These records are pseudonymous, not fully anonymous. Trial usage can survive reinstallation, but recognition across resets, signing changes or different Android users is not guaranteed.

5. Purchases

Google Play handles the one-time product purchase. MAIND sends the purchase token to our HTTPS API to verify purchase validity, status and acknowledgement with Google. D1 stores a token hash, product ID, verification status and timestamp, rather than the original purchase token. Original tokens are used in memory while processing requests. MAIND does not obtain card numbers or bank account details. Google's policies apply to payment information it handles directly. Valid purchases can be checked using purchase restoration with the same Google Play account. Trial usage and Google's purchase records are separate.

6. Integrity and security

MAIND uses Play Integrity to prevent abuse. Google processes request hashes, app package/version/signing information, licence status and device-integrity information. Our API submits Integrity tokens to Google and uses its app, device and licensing verdicts. Original Integrity tokens and verdict responses are not persistently stored in D1. Google's terms and policies apply. API traffic uses HTTPS. Cloudflare processes source IP addresses to serve and protect requests. Our rate limiter uses an HMAC-derived IP key; D1 does not store original IP addresses. Operational error logs use processing stages, safe error categories and response statuses, and are designed not to include purchase tokens or conversation content. Cloudflare and Google may process infrastructure logs under their policies. Processing may occur outside Japan.

7. Advertising and reports

The current app includes no advertising, usage analytics or automatic crash-upload SDK. Bug reporting can generate a report containing your description, app version, time, device/OS information, saved-connection count and connection state. You review it and choose whether to save or share it. It is not automatically sent to the operator. Do not include private keys, passwords, tokens or confidential work in reports or enquiries. Information received through support is used for support and quality improvement.

8. Recipients

We use Cloudflare as our trial/purchase processing infrastructure and exchange necessary verification information with Google. We do not sell personal information or provide it for advertising. We respond to legally required disclosures within their necessary scope. Your chosen SSH, AI, Git and sharing services also apply their own policies.

9. Retention and deletion

Use the app's conversation and connection deletion controls to manage local information. Clearing app data or uninstalling removes information in app storage. Exported downloads and information on remote servers, AI services or Git hosts must be managed separately. Trial matching keys, counts and operation records are retained for as long as needed to provide trial management and prevent repeated trials. Purchase verification records are retained as needed for verification, abuse prevention and support. These D1 records currently have no fixed automatic deletion period. Uninstalling does not erase D1 or Google Play records. Contact the address above to discuss access or deletion. We identify the relevant records, verify the request and respond as required by applicable law. If records must be retained for fraud prevention, legal obligations or disputes, we explain why. A derived matching ID is not, by itself, a person's name or contact information.

10. Audience and changes

MAIND is primarily intended for developers and server users aged 15 and above, rather than young children. Minors should obtain any required parental permission and follow the age requirements of their chosen servers and AI services. We update this policy when processing changes and provide in-app notices where necessary.

Related policies Google: https://policies.google.com/privacy Play Integrity: https://developer.android.com/google/play/integrity/terms Cloudflare: https://www.cloudflare.com/privacypolicy/