pairmoni
|EN
← Back to App

Privacy Policy

Last updated: August 19, 2026

This Privacy Policy (the "Policy") sets out how user information is handled in "playhub" (the "App"). The Developer handles your information appropriately, in accordance with this Policy.

1. We do not create accounts

The App has no account registration and no sign-in. It never asks you for your name, email address, phone number, date of birth, or anything similar.

The only things the App asks you to enter are a "display name" that is shown to the other members (free text; it does not have to be your real name) and the 6-character "share code" used to join a song.

2. Information we collect

2.1 Information stored on your device

  • Song data: song title, tempo, time signature, and count-in settings
  • Recorded data: the recordings themselves (audio files), recording names, and volume and mute adjustments
  • Your display name and the list of songs you have joined

These are stored on your device. If you only record and overdub on your own, you can use the App entirely on your device without any communication (when used offline, none of this information is sent to the server).

2.2 How the identification key is handled

The App issues a random identification key (32 random bytes) for each device and attaches it to the communication used to sync a song with the other members. The server keeps only a hash value derived from that key; it never stores the key itself. The key is not shown on screen and is not shown to other users (what other users see is only the display name described below and your per-song member number).

This key is stored only inside the App. No external sync service such as iCloud is used. As a result, if you delete the App, the key is also removed from your device. If you reinstall the App after deleting it, a new key is issued and you are treated as a different user from before (you can no longer access the songs you had joined). Note that the key is included in a full device backup (an iCloud backup or an encrypted local backup). Therefore, on a device restored from such a backup, the key is restored as well and you continue as the same user.

Also, the key is never automatically shared or synced to your other devices, even devices signed in with the same Apple ID. If you want to carry your data to another device without restoring from a backup (for example when starting on a brand-new device), you need to issue a "transfer code" (8 characters, valid for 24 hours from issuance, single use) inside the App yourself and enter that code on the new device. When the code is used, the new device is treated as having the same key (that is, as the same user) as the original device, and access to the songs you have joined carries over. Using the code does not invalidate the key on the original device. After the code has been used, both devices can therefore be used in parallel as the same user.

As described above, the identification key is a per-device identifier that disappears when you delete the App. Before reinstalling the App, always prepare the handover with the "transfer code" inside the App. If you delete the App without doing so, you will never again be able to access the songs and recordings you had joined (when you change devices, things carry over as they are if you restore from a device backup; if you do not restore from a backup, a transfer code is likewise required). For how to erase your own data, including this key, see Section 7.

2.3 Information sent to the server when syncing a song with the other members

When you create a new song, join as a member with a share code, or sync a recording with the other members, the App sends and stores the following information on the Developer's server (Cloudflare).

  • Your display name (you enter it when you join a song)
  • Song data: song title, tempo, time signature, and count-in settings
  • The recordings themselves (audio files in AAC format; recordings made with earlier versions are in WAV format), recording names, and status such as submitted, approved, or rejected
  • The identification key (stored as a hash, as described in Section 2.2)

Your name, email address, phone number, and location are not sent.

2.4 Recordings and how members can see each other's work

The App is a tool for building one song together with bandmates who are apart. Audio that a user records can be downloaded and played back only by the members of that song (it is not made public to people who are not members).

  • When you show a recording to the other members (submit it), its recording name, the display name of the person who recorded it, and its submitted / approved / rejected status are shown to every member of that song.
  • The person who created the song (the song's owner) listens to submitted recordings and decides whether to approve them into the song or reject them. An approved recording immediately becomes part of the song for every member.
  • The song's owner can also remove a recording that was once approved. Removing it does not delete the recording itself (the person who made it can submit it again at any time).

The App uses the microphone. A recording may contain singing or speech as well as the sound of the instrument being played. As described above, the contents of a recording are shared with the other members of the same song, so please be careful not to record or submit anything you would not want others to hear.

2.5 Inviting and managing members

  • You invite people to a song by giving them a 6-character share code. Anyone who knows this code can join the song, and you are responsible for managing your share codes.
  • When you join a song, your display name and your per-song member number are shown to the other members of that song. Raw device identification information is never disclosed to third parties other than the members and the Developer.
  • The song's owner can remove members from the song. Even after someone is removed, the data they recorded is not deleted and keeps playing as part of the song. A removed person can join again as a member by entering the same share code.
  • "Removing" is a measure that stops someone from writing anything new (recording and submitting). Because the record of their membership up to the moment of removal remains, a removed person may still be able to download and play back recordings. It is not a feature that shuts someone out completely, so please share your share code only with people you trust.

2.6 Technical information involved in communication

  • When communicating with the server, technical information such as the source IP address may be processed temporarily by the server provider (Cloudflare, Inc.) in order to carry out the communication, prevent abuse, and keep the service running stably. The Developer does not use this information in connection with any individual user.

2.7 Information relating to subscriptions (in-app purchases)

The App uses RevenueCat, Inc. to manage subscription purchases and expiry dates. The purchase itself takes place on Apple's App Store, and the Developer never receives your card number or any other payment details.

  • When you purchase, Apple's receipt (which product was bought, the purchase date, the expiry date, and whether it renewed or was cancelled) is sent to RevenueCat and processed by RevenueCat and by the Developer's server in order to decide whether a subscription is active.
  • This subscription record is tied not to the identification key described in Section 2.2, but to a separate identifier derived one-way from it. It contains no name, email address, or Apple ID.
  • The Developer's server stores only the expiry date and whether the subscription has expired, been refunded, or been paused. It does not store the amount paid or the payment method.
  • This information is used to give subscribers the features they paid for, and to count how many people are subscribed.

Cancelling from Subscriptions in the App Store happens on Apple's side; the Developer does not receive that action directly, only the resulting expiry notification. Deleting your data as described in Section 7 also erases the subscription record on the Developer's server, but it does not cancel the purchase attached to your Apple ID - tapping "Restore purchases" with the same Apple ID brings an active subscription back.

2.8 Information we do not collect

  • The App does not collect location data, contacts, photos or media, or camera data. The microphone is used only for the recording feature (see Section 2.4).
  • The App does not ask you to enter your name, email address, or phone number.
  • The App does not collect the device's advertising identifier.
  • The App does not use third-party analytics tools that track behavior (such as Google Analytics or Firebase).
  • The App does not display ads.
  • The App does not track you across other companies' apps or websites. It never asks for iOS tracking permission (App Tracking Transparency).

3. Purpose of use

  • Providing the App's features, such as recording, overdubbing, and exporting
  • Sharing songs with the other members and managing the submission, approval, and rejection of recordings
  • Carrying your data over with a transfer code, for example when you change devices
  • Checking subscription status and providing subscribers with the features they paid for (see Section 2.7)
  • Preventing abuse, keeping the App running stably, addressing defects, and improving quality and features

4. Provision to third parties and external services

Except as required by law, the Developer does not provide user information to third parties. However, to the extent necessary to provide and operate the App, the handling of information is entrusted to the following external services. This may involve information being processed outside Japan to the extent necessary.

  • Cloudflare, Inc. (providing the server, the database, and storage for recordings)
  • RevenueCat, Inc. (managing subscription status; see Section 2.7)
  • Apple Inc. (processing in-app purchases through the App Store; see Section 2.7)

In addition, as described in Sections 2.4 and 2.5, the members who have joined a song are shown and share the display names, member numbers, recording names, the display name of the person who made each recording, the submitted / approved / rejected status, and the recorded audio itself.

5. Retention period

Information stored on your device is kept on your device until you delete it or uninstall the App. The identification key is likewise stored only on your device, as described in Section 2.2, and deleting the App removes it, together with the identification key, from your device.

Songs, recordings, display names, and similar information stored on the server are retained for as long as needed to provide the song features, until you perform the deletion described in Section 7.

6. Security measures

The Developer takes the measures necessary and appropriate to prevent leakage, loss, or damage of the information it collects and to otherwise manage it safely.

7. Disclosure, correction, and deletion

You may request disclosure, correction, or deletion of your own information held by the Developer. The App includes a feature that deletes your own data from within the App. Performing it deletes the following.

  • The songs, recordings, display names, and similar data about you that are stored on the server
  • The data stored on your device
  • The identification key itself described in Section 2.2 (the key file stored inside the App)

A song you made on your own (with no other members) is deleted in its entirety. For a song that has other members, the recordings you uploaded are deleted, but the records of the song and of the recordings themselves remain, with the owner information replaced by "deleted", in order to protect the other members' data. In addition, copies of recordings that have already reached the other members' devices at the time of deletion cannot be deleted by this operation (they stay on those devices and keep playing as part of the song). Recordings that the other members have not yet downloaded can no longer be obtained after this operation.

Please delete your data stored on the server with the in-App operation above before you delete (uninstall) the App. As described in Section 2.2, the identification key is removed from your device when the App is deleted. After you delete the App, the Developer has no way to connect that key to you, so even if you request deletion or disclosure of the data stored on the server, we may be unable to identify what to act on and unable to respond.

Note: because the App does not create accounts, the Developer has no way to connect the identification key to a specific individual such as a name or contact details. Using the in-App deletion above is the most reliable method. If you want data on the server deleted or disclosed without using the App, please contact the Developer with information that lets us identify what is yours, such as the song name, your display name, and roughly when you used the App (please contact us before deleting the App; after deletion we may be unable to respond, as described above). If we cannot confirm that the request comes from you, we may be unable to comply.

8. Children's use

The App can be used regardless of age, but as described above, display names and recorded audio are shared with the other members of the same song. Guardians are asked to make sure that children do not enter their real name as a display name and do not give share codes to strangers.

9. GDPR and other laws outside Japan

The App respects data protection laws in each country, including the EU General Data Protection Regulation (GDPR).

  • Data minimization: the App handles only the minimum information needed to provide its features, and does not collect information that directly identifies an individual, such as a name, email address, or contact details.
  • Nature as an identifier: the identification key cannot by itself identify a specific individual, but it is treated as within the scope of this Policy on the basis that it may constitute personal data (an online identifier) under the GDPR. This key is stored only on your device and is not synced to any external cloud service (deleting the App removes it from your device).
  • Legal basis for processing: information processed in connection with providing the song and recording sharing features is processed to the extent necessary to provide the service you have requested (performance of a contract).
  • Managing your data: you can delete your own data using the in-App deletion feature in Section 7 (the limits that apply to songs with other members are as described in Section 7).

10. Revisions

The Developer may revise this Policy in response to changes in laws or in the service. If there are material changes, we will notify you within the App or by a method the Developer deems appropriate.

11. Contact

For inquiries regarding this Policy, please contact us at the following.

  • Developer: Pairmoni
  • Email: support@pairmoni.com