Pianium
Sign in

Privacy Policy

Easpe Inc. (hereinafter referred to as "the Company") establishes the following privacy policy (hereinafter referred to as "this Policy") regarding the handling of users' personal information in the mobile application "Pianium" and the Company's website (hereinafter collectively referred to as "this Service") provided by the Company.

Data handling (updated October 16, 2026)

With explicit consent, AI chat sends conversation text, project and drill content, practice history such as time spent, tool results and conversation summaries to the external providers disclosed before sending. Recording and MIDI files and profiles are not automatically included. Information you type into messages is sent. The tracker works without consent; withdraw consent for future requests in your profile.

During beta, exceeding a quota or cancelling a paid plan does not automatically delete originals. Your explicit deletion request overrides that retention: owned originals, derived files, conversations and summaries are erased. Failed erasure is retried and acceptance is distinct from completion. Body-free AI cost and delivery records are retained for 13 months, then aggregated into monthly totals without user identifiers. Store billing records, backups and data already received by external providers have separate retention terms.

Request deletion without the app; scope and instructions

Advertising and age groups (policy adopted October 18, 2026)

The initial release is intended for ages 13 and older. In versions supporting advertising privacy choices, personalized ads are allowed only for users who declare they are 18 or older and opt in, subject to required regional consent and iOS tracking permission. Ads are restricted for ages 13–17, unknown ages or declined consent or permission. Ads are not shown if required conditions cannot be verified. Recording, saving and playback remain available if you decline.

The free plan uses Google AdMob. For ad serving, measurement and fraud prevention, the advertising SDK may send Google and relevant partners IP addresses (which may be used to estimate general location), device identifiers, ad impressions and interactions, and diagnostic information. Regional consent forms identify advertising partners and purposes. Recording and MIDI files and AI conversation text are not supplied for ad targeting.

Advertising settings do not request a date of birth. Your advertising age group and ad preference are saved on your device, and age-related restriction signals are configured in the advertising SDK. In supported versions, review or change preferences and regional consent in Profile → Ads and privacy. Manage OS tracking permission in device settings. Advertising consent is not treated as consent for a separate analytics service.

How Google uses advertising data

Practice, community and sharing data

Supported features store an optionally self-declared birth year with your account and calculate a year-based age band on the server for safety. This is neither a full date of birth nor verified age. Your birth year is not displayed in your public profile. It is separate from the advertising age group saved on your device. Providing a birth year does not consent to personalized ads, OS tracking permission or sending information to external AI.

For ages 13–17 and unknown ages, we restrict search and discovery of new connections and comments or mentions from non-friends. When either person is in these groups, reactions are limited to designated emoji. We do not offer DMs or teams. Posts are displayed according to visibility and blocking settings.

We use practice saves and starting context, duration, pieces, ratings, notes, visibility, comparison playback starts, plan offer displays and their triggers, and purchase, trial and renewal states to restore records, provide features, adjust display frequency and aggregate usage. Devices may retain unsent edits, ad and plan display history, and encouragement and reminder scheduling, delivery and interaction records. A uniform 13-month retention period does not apply to these records.

We store challenge and pair enrollment and targets, practice-based achievements, and avatar selections and unlock history. Achievement badges are decorative service features, not qualifications or certifications of skill. Achievement evidence is checked on the server. Pruning the original enrollment history alone does not revoke an earned award. Invitations use hard-to-guess codes; the server stores a hash rather than the raw code, alongside issuer, target and redeemer identifiers, purpose, expiry and redemption state. Expiry limits code use; it is not a record deletion deadline. We also record invitation redemption attempt counts to prevent abuse.

You can use generated avatars or existing profile photo uploads. We do not automatically review photos or send them to external AI for image review. An indication that you have an uploaded photo does not publicly expose the original image URL. Switching avatars alone does not republish a hidden photo.

Reports store target type and identifier, reason category, reporter, priority, and handling and notification states for operator review and manual hiding, suspension or bans. We do not use an automated AI word filter. Operator email notifications include the report ID, target type and priority, without the reported text or image attached. Minor safety and threat reports receive high priority. We aim to review reports within 24 hours in principle; this is not a guarantee of resolution.

Notifications use Firebase and send destination device information and, depending on notification type, display names, profile image URLs, relevant identifiers and information used to open a screen. For comment and mention notifications, the delivery payload includes the full comment text sent to Firebase and the device’s notification services. The displayed notification body uses a comment excerpt of at most 100 characters, including any ellipsis; this excerpt limit is not a limit on the full delivery payload. On-device practice and trial reminders are scheduled with OS notification services. If you allow notifications, review how they appear on your device, including its lock screen.

Creating share cards or comparison videos processes the practice information, images and audio you select and creates temporary files in the app. When you save or share, copies passed to the OS, selected apps or recipients are managed at those destinations. Account deletion cannot recall copies saved to device photos or files or held by recipients.

Community guidelines, reporting and support

Storage, deletion and external services

Logging out does not delete your account. On-device records needed for recovery may remain. Identity-confirmed account deletion requests are recorded to erase owned originals, derived files, conversations, summaries and applicable account records. Failed or unconfirmed steps remain pending for retry. Some on-device edit history, notification records and sharing caches require cleanup integration or confirmation of ownership. Server acceptance or completion alone does not mean every local byte has been erased. Sharing cleanup covers application-managed caches.

We use AWS, including S3 and CloudFront, for cloud storage and delivery; Firebase for notifications; AWS email delivery for operational mail; and Sentry for fault diagnosis. Sentry processes errors and device and app diagnostics. The mobile app includes pre-send filtering to remove user information and request bodies, among other data. The website also includes sampled session replay alongside fault and performance diagnosis. We include filtering to exclude diagnostic sending on paths containing deletion secrets. We also process operational server logs. These flows are separate from website analytics using GA4. External AI uses the providers disclosed in the consent screen, such as OpenAI, and advertising follows the AdMob explanation above.

Report and moderation records undergo removal of identifying associations when the target or account is deleted, but handling states and notification retry records may remain. Unlinking purchases and deletion by external providers are separate from deleting account database rows. Records needed for payments, accounting or legal obligations, backups and information received by external providers follow their respective retention conditions. We do not guarantee immediate erasure or one fixed retention period for every record. Use the deletion instructions or support to ask about deletion and progress.

Website analytics (updated October 30, 2026)

This website uses Google Analytics (GA4) only if you consent, measuring page views and interaction events with cookies. Before you consent, the measurement tag is not loaded. We do not use this data for advertising. You can withdraw consent at any time from "Analytics settings" at the bottom of the home page. For how Google handles data, see https://policies.google.com/technologies/partner-sites. The handling of app usage records and information needed to operate the service is described above.

Article 1 (Personal Information)

"Personal Information" refers to "personal information" as defined in the Personal Information Protection Act, and means information about a living individual that can identify a specific individual by the name, date of birth, address, telephone number, contact information, and other descriptions contained in such information, as well as data relating to appearance, fingerprints, voiceprints, and information that can identify a specific individual from such information alone (personal identification information) such as the insurer number of a health insurance card.

Article 2 (Method of Collecting Personal Information)

We process names, email addresses and account identifiers needed for registration or external authentication, and profile images, recordings, MIDI, scores, practice records, drills, conversations and comments that users save or submit. Some fields are optional and depend on the features used. We receive purchase, restoration and subscription status information from the stores, but do not receive card or bank account numbers entered with the stores. Advertising and diagnostic SDK practices are described in the advertising policy above and the providers’ disclosures.

Article 3 (Purpose of Collecting and Using Personal Information)

The purposes for which the Company collects and uses personal information are as follows.

  1. To provide and operate the Company's services
  2. To respond to inquiries from users (including identity verification)
  3. To send emails about new features, updates, campaigns, etc. of the services users are using, and to provide information about other services provided by the Company
  4. To contact users as necessary for maintenance, important notices, etc.
  5. To identify users who violate the terms of use or who attempt to use the service for fraudulent or improper purposes, and to refuse their use
  6. To allow users to view, modify, and delete their own registration information and view their usage status
  7. To charge users for paid services
  8. For purposes incidental to the above purposes of use

Article 4 (Changes to Purpose of Use)

  1. The Company will change the purpose of use of personal information only when it is reasonably recognized that the purpose of use is related to the purpose before the change.
  2. When the purpose of use is changed, the Company will notify users of the changed purpose by the method specified by the Company, or publish it on this website.

Article 5 (Provision of Personal Information to Third Parties)

  1. The Company will not provide personal information to third parties without obtaining the user's prior consent, except in the following cases. However, this excludes cases permitted by the Personal Information Protection Act and other laws and regulations.
    1. When it is necessary to protect human life, body, or property and it is difficult to obtain the consent of the person
    2. When it is particularly necessary for the improvement of public health or the promotion of the healthy development of children, and it is difficult to obtain the consent of the person
    3. When it is necessary to cooperate with national institutions, local governments, or those commissioned by them in carrying out affairs stipulated by law, and obtaining the consent of the person is likely to impede the execution of such affairs
    4. When the following matters are announced or published in advance, and the Company has filed a notification with the Personal Information Protection Commission
      1. That the purpose of use includes provision to third parties
      2. Items of data to be provided to third parties
      3. Means or methods of provision to third parties
      4. To stop providing personal information to third parties upon request of the person
      5. Method of accepting requests from the person
  1. Notwithstanding the provisions of the preceding paragraph, the following cases shall not be considered as provision to third parties.
    1. When the Company entrusts all or part of the handling of personal information within the scope necessary to achieve the purpose of use
    2. When personal information is provided in connection with business succession due to merger or other reasons
    3. When personal information is used jointly with a specific person, and the person is notified in advance or placed in a state where the person can easily know the fact, the items of personal information to be used jointly, the scope of persons who use it jointly, the purpose of use of the users, and the name of the person responsible for managing such personal information

Article 6 (Disclosure of Personal Information)

  1. When the Company is requested to disclose personal information by the person, it will disclose it to the person without delay. However, if disclosure falls under any of the following cases, the Company may not disclose all or part of the information, and if it decides not to disclose, it will notify the person of this fact without delay. Please note that a fee of 1,000 yen per case will be charged for disclosure of personal information.
    1. When there is a risk of harming the life, body, property, or other rights and interests of the person or a third party
    2. When there is a risk of significantly impeding the proper implementation of the Company's business
    3. When it would otherwise violate laws and regulations
  1. Notwithstanding the provisions of the preceding paragraph, information other than personal information, such as history information and characteristic information, will not be disclosed in principle.

Article 7 (Correction and Deletion of Personal Information)

  1. If a user's personal information held by the Company is incorrect, the user may request the Company to correct, add, or delete personal information (hereinafter referred to as "correction, etc.") through the procedures established by the Company.
  2. If the Company receives a request from a user under the preceding paragraph and determines that it is necessary to comply with the request, it will correct the personal information without delay.
  3. When the Company makes corrections based on the provisions of the preceding paragraph, or when it decides not to make corrections, it will notify the user of this fact without delay.

Article 8 (Suspension of Use of Personal Information)

  1. When the Company is requested to suspend or delete the use of personal information (hereinafter referred to as "suspension of use, etc.") on the grounds that the personal information is being handled beyond the scope of the purpose of use, or that it was obtained by fraudulent means, the Company will conduct necessary investigations without delay.
  2. Based on the results of the investigation in the preceding paragraph, if the Company determines that it is necessary to comply with the request, it will suspend the use of the personal information without delay.
  3. When the Company suspends use based on the provisions of the preceding paragraph, or when it decides not to suspend use, it will notify the user of this fact without delay.
  4. Notwithstanding the provisions of the preceding two paragraphs, if suspension of use requires a large amount of expenses or if it is otherwise difficult to suspend use, and if alternative measures necessary to protect the user's rights and interests can be taken, such alternative measures will be implemented.

Article 9 (Changes to Privacy Policy)

  1. The contents of this Policy may be changed without notifying users, except for matters otherwise stipulated in laws and regulations or this Policy.
  2. Unless otherwise specified by the Company, the revised privacy policy will take effect when it is posted on this website.

Effective February 1, 2025

End