Legal

Privacy policy

This page describes how Tokyo IT Co., Ltd. (“we”) handles personal information and similar data for Feelism: the public site feelism.app, the Windows and Android apps, Forum, and licensing and payment. Listening, accompaniment, and playback happen on your PC or phone. We do not send audio or MIDI waveforms to our servers.

Last updated: October 15, 2026

1. What this covers

• The public site (feelism.app): contact, news, the manual, and similar pages
• The Feelism app for Windows
• The Feelism app for Android
• Forum (forum.feelism.app)
• The subscription (on Windows, Stripe payment and the license key; on Android, Google Play)

2. What we receive

2.1 Contact and downloads on the site

• Name, email address, subject, and message (contact form)
• Technical details at send time (time, IP) to limit spam
• On the confirmation page, before a message is sent, Cloudflare Turnstile processes device information and IP to block bots (Cloudflare privacy)
• When you continue to the Microsoft Store from a Get button on this site, we may record IP, an estimated country (when it comes through Cloudflare), browser type, the referring page, and the time, so we can see roughly how widely it is distributed

2.2 The apps (install and use)

On Windows and Android, when the app is online it may send the following to our license server. We do not collect a name or email for billing (Forum, the contact form, and Stripe receipts are separate).

• Install ID — an ID for that installation on that PC or phone, issued by our server. It changes if you reinstall or use another device. We do not use a machine fingerprint or an advertising ID.
• Play log — one line when you stop accompaniment or a theme. Tune ID, the title at the time, publisher, seconds played, a rights label, whether it was accompaniment or a theme, and the time. We use it to understand how widely the app is used, including for copyright. We do not keep the license key, audio, MIDI, or a bar-by-bar timeline.
• Import log — one line when a MusicXML import succeeds. Tune ID, title, publisher, whether it came from Forum or from a file you already had, and the time. We do not keep the license key or the XML body. If you are offline, it is fine if the line is never sent.

Plays made offline may be missing if they cannot be sent later. What arrives is treated as a lower bound.

2.3 Subscription (Windows, Stripe)

• Payment happens on Stripe. Receipt email and similar details follow Stripe’s policy (Stripe privacy).
• Our server stores a hash of the license key, expiry and status, Stripe customer and subscription IDs, and optionally an install ID. To limit paid playback to one PC at a time, we may remember which install is in use and when it last checked in. The key itself is not stored in the database. When we issue a key, we may send a copy to the email used in Stripe.
• We may keep one line for each event such as start, renewal, a scheduled cancellation, or the end. That line does not include the license key or an email address.

2.3.1 Subscription (Android, Google Play)

• Payment, cancellation, and changing the payment method happen in Google Play. Google handles your name and card details; we do not receive them (Google privacy).
• To confirm the subscription, the app sends the Google Play purchase token to our server, and our server asks Google for its state. Our server stores a hash of the purchase token, the order number, the product, expiry and status, and the install ID. The token itself is not stored in the database.
• To limit paid playback to one device at a time, we may remember which install is in use and when it last checked in (as on Windows).

2.3.2 Android permissions

• Microphone — to hear the pitch and loudness of your instrument, so the band can respond and your own sound can return to your headphones. This happens only on the phone. We do not send recordings or waveforms.
• Nearby devices (Bluetooth) — to find and connect a Bluetooth MIDI keyboard. It is not used for location.
• Recordings and files you export stay on the phone unless you share them yourself.

2.4 Forum

• To post, comment, and like, you can register an email address, a password (stored as a hash), and a handle. A subscription is not required.
• We may email you to confirm the address or to reset the password.
• Pack text, comments, and attachments are stored as needed to run Forum. Reports may be tied to a session.
• Cloudflare Turnstile processes device information and IP to block bots on signup, pack posts, and comments (Cloudflare privacy)

2.5 What we do not take (as a rule)

• Audio waveforms from a microphone or instrument, or a MIDI performance stream
• A fingerprint of the whole disk, or a hardware ID that uniquely ties a device
• The license key or the Google Play purchase token in plain text (in our database)
• Location, contacts, or an advertising ID

3. Why we use it

• Replies to contact messages, and support such as reissuing a license key
• A rough count of how people reach the Store (clicks through to the Store)
• Providing and checking the subscription, and limiting misuse
• Understanding how widely the app is used (play and import logs) and improving the service
• Forum identity, posts, and notices
• Incidents, security, and duties required by law

We do not sell personal information. This public site uses Google tags and the Meta Pixel to measure visits and ad results, and Microsoft Clarity to see how pages are used (sections 4 and 7).

4. Processors and outside services

• Payments: Stripe (Windows), Google Play (Android)
• Bot checks on the site and Forum: Cloudflare Turnstile
• Email: the SMTP provider we contract with
• Servers: the hosting we contract with (including a VPS in Japan)
• The feature video on this site and videos in the manual: YouTube (Google). Opening the page loads the player. Playing a video may send device information (YouTube privacy)
• Visits on this public site: Google Analytics. Opening a page may send the page address and browser type to Google (Google privacy).
• Ad results on this public site: Google Ads. Opening a page may send the same kind of information so Google can tell whether a visit came from an ad.
• Ad results on this public site: Meta Pixel (ads on Facebook and Instagram). When you open a page, and when you press "Get it on the Microsoft Store" on the download page, the page address, browser type, and the identifier in Meta's cookie may be sent to Meta (Meta privacy).
• How this public site is used: Microsoft Clarity. Clicks, scrolling, and mouse movement on a page, the page address, and the browser and device type are sent to Microsoft. We use them as session replays and heatmaps to improve the site. What you type in the contact form and what the confirm page shows are set not to be sent (Microsoft privacy).

We ask processors to handle data only as the contract requires, and to keep it appropriately.

5. Storage

• Contact messages are stored in an operations database (name, email, subject, message, IP at send time, and the time). They are also kept as email in our inbox and as a copy to the sender.
• Download logs, install IDs, play and import logs, billing events, and Forum member records are stored in each server’s database.
• After a request is finished, we may keep records for a period when the law requires it or to handle disputes.

6. Access, correction, and deletion (deleting a Feelism Forum account)

On request from you, we respond to access, correction, and deletion. Forum email, password, and handle can be changed from the account page after you sign in.

How to delete your Feelism Forum account

1. Sign in to Feelism Forum (in the Android app: Menu > Forum).
2. On the account page, under "Delete account", enter your current password and press "Delete my account". The account is deleted right away.

• Deleted at once … your email address, password (hash), handle, password reset records, and likes.
• Kept for one year … the packs (including ZIP files) and comments you posted. From the moment you leave they show only "deleted by the author", without your name or text, and cannot be imported. We keep them for abuse and rights inquiries, and delete them completely one year after you leave.
• App usage records (install ID, play and import records) are not linked to your Forum account and are kept as described in section 5.

For anything else, use Contact ([email protected]). We may be unable to respond where the law says so.

7. Cookies

The site and Forum may use cookies or similar technology for sign-in, security, and display. On this public site, Google tags measure visits (Google Analytics) and ad results (Google Ads). They may set a cookie and send the page address and rough device information to Google (Google privacy). To measure ad results, the Meta Pixel may also set a cookie and send the page address to Meta. You can choose whether this information is used for ads in the Ad preferences of Facebook or Instagram. To see how the site is used, Microsoft Clarity may set a cookie and send what you do on a page to Microsoft. Playing a video in the manual may let YouTube set a cookie. Choosing a language on this site stores a cookie so the next visit stays in that language.

8. Changes

When we change this policy, we update this page. For an important change, we may also post a notice on the site.

9. Operator

Name

東京IT株式会社

Address

〒140-0014 東京都品川区大井1-6-3 アゴラ大井町3階（首都圏イノベーションセンターMICAN内）

Contact

Contact form ([email protected])

Using the app, including free practice, and the paid plan are covered by the terms. Seller details are on the commerce disclosure.