日本語

Privacy Policy

Last updated: November 9, 2026

Contents

This Privacy Policy explains how personal information and other data are handled in the app "Utakata Studio Mobile IDE" (the Google Play version, the direct version distributed from our website, and the iPhone version distributed on the App Store; together, the "App"). It is set by the provider of the App (the business listed in our Disclosure under the Act on Specified Commercial Transactions; "we" or "us").

1. Our approach

The App is a development environment for building Flutter apps on your device. Your project files are stored on your device and are never sent to our servers.

You can use all of the App without signing in. Signing in is optional.

The only personal information we handle is account information for users who sign in and the content of messages you send us.

The App has no advertising, no usage analytics (nothing that collects how you use the App) and no crash reporting (nothing that sends error reports to us automatically).

2. Information we collect

2-1. Information stored only on your device

The following is stored only on your device and is never sent to us.

  • Projects you create (source code, images and other files) and their build outputs
  • App settings (theme, language, editor preferences and so on) and your list of recent projects
  • Your build history (date, version, signing key name and a copy of each build output; signing key passwords are not included)
  • Development tools (Flutter SDK, JDK, Android SDK and so on) and the cache of packages downloaded for your builds
  • A log of times the App stopped or hit an unexpected error (date and time, App version, the kind and text of the error, and where in the App's own code it happened; up to the latest 20 entries). File locations, tokens, email addresses and similar details are masked, and file contents are never recorded. It goes into an email only when you choose to attach it in "Send feedback" (2-5)

Files and folders you pick with the system file picker are read and written only within what you selected. When you export a project as a zip file, the App writes it only to the location you choose in the system save dialog.

2-2. Account information (only if you sign in)

When you sign in with Google or Apple, we obtain the following through our authentication service (Firebase Authentication).

Information Purpose
User ID (UID) Identifying your account
Email address Identifying your account, important notices, responding to inquiries
Display name (if provided) Display in the App
Profile photo URL (if you sign in with Google and it is provided) Account management (the App does not display or use the photo; Google provides it at sign-in, so it is recorded by our authentication service)
Sign-in method, account creation date and time, last sign-in date and time Account management
IP address and device and App type and version at sign-in Preventing fraudulent sign-ins (collected by Firebase Authentication)

If you choose "Hide My Email" with Sign in with Apple, we receive a relay address issued by Apple. We never learn your actual address.

2-3. Purchase information

Pro (subscription) is not available yet. For now, we do not collect any purchase information and do not send any information to our purchase management service (RevenueCat). We will update this section when we start offering Pro.

2-4. Information about the release AAB allowance (only if you build AABs)

For now, nothing is sent to us when you build release AABs (AABs and APKs are built entirely on your device).

2-5. Messages you send us

If you contact us by email, we obtain your email address, your name (if given) and the content of your message. "Send feedback" in the App only hands a draft email (our address, plus the App version, device model, OS version and display language) to your email app; you decide whether to send it. If you choose to attach the error log (2-1), it is added to the message. You can check everything in the App and in your email app before sending.

3. How we use information

  • Data on your device (2-1): used only on your device, for editing, building, preview and keeping your settings
  • Account information (2-2): signing in and verifying your identity, handling account deletion requests, and important notices such as changes to the Terms (including by email)
  • Messages (2-5): replying to you and keeping a record of the inquiry

We never use this information for advertising and never sell it to third parties.

4. Sharing with third parties

4-1. Service providers that handle information for us

The App uses the following services, and information is sent to them to the extent needed to provide the features. These providers handle the information on our behalf and process it under their own privacy policies.

Service Provider Information that may be sent Country
Firebase Authentication Google LLC Account information (2-2) United States

Transfers to third parties in other countries: the providers above are based in the United States. For information on the US system for protecting personal information, see the Personal Information Protection Commission of Japan's survey of foreign systems (in Japanese). Firebase Authentication processes information only in data centers in the United States. The measures Google takes are set out in Google's privacy policy and in the data processing terms between us and Google (Firebase Data Processing and Security Terms).

We do not sell or provide your information to any other third party, except where disclosure is required by law.

4-2. Services the App connects to when you take certain actions

When you take certain actions, the App connects to the following. The destination receives the information needed for the connection (your IP address, the names and versions of requested packages and so on). This information is handled under each destination's policies; we do not receive it.

Destination When
Google Play Delivering the App and the development tools installed with it (such as the NDK). Opening Termux's store listing when you tap "Install Termux" (Google Play version)
Flutter's distribution server (storage.googleapis.com, operated by Google) When you install the debug engine or the Flutter Web SDK for web preview under "Extra components" (Android)
Google Fonts (fonts.gstatic.com, operated by Google) When you install the web preview component under "Extra components", to download fonts used in the preview (Japanese, emoji and so on) (Android)
utakata-code.com and GitHub (github.com and its file servers) The list of extra components and downloading the NDK (direct version only)
pub.dev (the Dart package repository) Downloading packages not bundled with the App when you build, get packages or update dependencies, and when you install common plugins or code generators under "Extra components"
Maven repositories (Google Maven, Maven Central, Gradle Plugin Portal and others, depending on the project's settings) Downloading libraries and plugins not bundled with the App when you build
Destinations you specify Commands you run in the terminal, SSH hosts you register in the terminal (by default, Termux on the same device), Git remotes you register (such as GitHub) for push, pull and clone, and network traffic from apps you build when you preview them

If the iPhone version connects to different destinations, we will update this table when we start distributing the iPhone version.

Apps you build run inside the App when you preview them. Any network traffic or data handling by those apps is your responsibility as their developer.

Connecting to an external AI: only while you have "Connect an external AI" turned on for a project, an app that has been given the token (an AI tool you run, for example in a terminal app) can, through an endpoint on the same device (127.0.0.1, protected by a token), read that project's files, run the preview, view and operate the screen, and run development commands (flutter, dart, git and so on) in that project. Commands run in the same environment and with the same permissions as the App's terminal. The endpoint cannot be reached from outside the device. It is off by default and opens only when you turn it on (including when you open the project's Claude Code or Termux tab in the App; you can turn this off in Settings). The token changes each time you turn it on. How the AI tool handles what it receives is subject to that tool's policies.

Sharing: when you tap "Share" in your build history, the file is passed only to the app you choose in the system share sheet.

SSH keys and Git tokens: SSH keys for the terminal are created on your device, and private keys never leave it. Tokens you register for Git remotes are stored encrypted on your device and used only when communicating with that remote.

5. Retention and deletion

5-1. Data on your device

Data on your device (2-1) stays there until you delete it in the App (you can delete the error log with "Delete log" in "Send feedback") or uninstall the App. Uninstalling deletes the data in the App's storage (settings, development tools, build history and so on).

Zip files you exported and saved elsewhere remain after you uninstall the App. Depending on the OS version and the device, the Android project folder (section 7) may remain after you uninstall the App. Delete any projects you do not want to keep in the App before uninstalling it.

5-2. Deleting your account and data on our servers

You can delete your account in either of these ways:

  • In the App: Settings → General → Account → "Delete account". Deletion takes effect immediately.
  • On our account deletion page, if you cannot use the App, you can request deletion by email. We will verify your identity and delete your data within 30 days.
Deleted Not deleted
The account you sign in with (2-2: UID, email address, display name, profile photo URL, sign-in method and dates) Projects and settings on your device (deleted when you uninstall the App)
Zip files you exported
Records of messages you sent us, including your deletion request (for the period in 5-3)

After deletion, account information is also erased from the systems and backups of Firebase Authentication (Google) within 180 days. Google keeps the IP addresses logged at sign-in for a few weeks (under Google's own terms).

5-3. Messages

We keep messages for 1 year after we finish responding, and then delete them.

6. Your choices

How
Not giving us any information If you do not sign in, no personal information is sent to us (you can still use the App)
Signing out Settings → General → Account in the App
Deleting your account and data on our servers "Delete account" in the App (5-2)
Changing notification permission In your device settings. The App works without it (you just won't see build and preview notifications)
Stopping the external AI connection Turn off "Connect an external AI" for the project

7. Security

Account information is sent over encrypted connections (HTTPS).

Settings and development tools are stored in the area the OS protects separately for each app. On Android, projects are stored in a folder reserved for the App in the device's shared storage (Android/media/code.utakata.mide/) so that file manager apps can open them. Apps on the device that have been granted "All files access" can also read this folder.

However, no transmission over the internet can be guaranteed to be completely secure.

8. Your rights and legal bases

  • You can ask us to notify you of the purpose of use of the personal information we hold about you, and to disclose, correct, add to, delete, stop using or erase it, or stop providing it to third parties. Contact us at the address in section 10 from the email address you signed in with. We will verify your identity and respond without delay as required by law. There is no fee.
  • If you live in the European Economic Area or the United Kingdom, we process information on the following legal bases.
    • Account information: to provide the service under our Terms (performance of a contract)
    • Information used to prevent fraudulent sign-ins (IP address): our legitimate interests
    • You have the right to access, rectify and erase your data, to restrict or object to its processing, and to data portability, and the right to lodge a complaint with the supervisory authority in your country

9. Children

The App is intended for developers and is not directed at children.

10. Contact

support@utakata-code.com

The name, address and representative of the business handling personal information are listed in our Disclosure under the Act on Specified Commercial Transactions (in Japanese).

11. Changes to this policy

We may update this policy to reflect changes in laws, guidelines or our services. When we do, we will announce it on this page and update the "Last updated" date. We will also notify you in the App of important changes that expand the information we collect or how we use it.

Appendix: Permissions and SDKs

Device permissions

Permission Purpose
Internet (INTERNET) and network state (ACCESS_NETWORK_STATE) Downloading packages, signing in, communication between tools on the device (127.0.0.1), checking connectivity
Foreground service (FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE) Keeping builds and previews running when you switch to another app
Notifications (POST_NOTIFICATIONS) Showing build and preview progress and a "Stop" action in notifications
Google Play billing (com.android.vending.BILLING) For purchasing Pro on Google Play. Pro is not available yet, so this is not used for now
Request install packages (REQUEST_INSTALL_PACKAGES; direct version only) Installing apps you build when you choose to

SDKs included in the App also add other permissions (USE_BIOMETRIC, USE_FINGERPRINT and com.google.android.providers.gsf.permission.READ_GSERVICES), but the App does not use them.

SDKs

SDK Purpose Information sent to us
Play Feature Delivery (Google) Receiving the development tools installed with the App from Google Play None
Firebase Authentication and Google Sign-In (Google); Sign in with Apple (iPhone version) Signing in (only if you sign in) Information in 2-2
RevenueCat For managing Pro. Pro is not available yet, so it is not started for now (nothing is sent, even if you sign in) None
Google Play Billing Library (Google) For purchasing on Google Play. Not used for now None