Privacy policy
Note by note Piano is published by VALENTREE LLC. The piano course works without an account. Online battles are optional.
Updated September 20, 2026
The course stays on your device
Your lesson progress, practice results, sound preferences and note-label settings are stored on your device. The app does not upload this course data to our app servers. The course, piano sounds and learning materials are bundled with the app.
You can copy a progress backup and keep it somewhere you choose. Your device's operating-system backup services may also include app data, depending on your device and backup settings. Those backups are controlled by you and your platform provider. Clearing app data or uninstalling can remove local progress.
Optional online battles
Battle accounts use a username and password, with authentication provided by Amazon Cognito. We do not ask for an email address when you create a battle account. The service uses your account identifier, connection and room information, note answers, round timing, scores and match results to authenticate you, connect opponents and run games.
Your sign-in username is private to your account. Opponents see neutral labels such as Player 1 and Player 2. There is no player chat.
Battle data is processed with Amazon Web Services in the US East (Northern Virginia) region, us-east-1. AWS also processes network and request information needed to provide and secure the service. If you use the app from Canada, this processing takes place in the United States.
What we do not use
The app has no advertising or analytics SDKs. It does not request microphone or location access. Piano sound is played from bundled recordings; the app does not listen to or record you playing a real piano.
Public website and support
The public account-deletion page uses your existing battle username and password to sign you in. Its sign-in tokens stay in memory for that page session; the page does not save them in browser storage. Reloading or leaving the page ends that local session. The public site does not use advertising or analytics.
If you email support@valentree.com, we receive your email address, your message and any information you choose to include so we can respond. Do not send your password. Support correspondence may be retained as needed to address your request and related follow-up.
Account deletion and retention
In the app, open Battle → Account → Delete battle account. You can also use the account-deletion page linked from our public support website. Sign in, review what will be removed and confirm deletion. This removes your battle sign-in account and its related live service data. Deletion cannot be undone; your local course progress is not changed.
A limited deletion-security record keeps an account identifier and request identifiers, not your username or password. It lets cleanup finish and prevents an old session from reconnecting. A pending record remains until cleanup completes. The completion record is scheduled to expire after one day, with asynchronous database cleanup afterward. Previously created backups and operational records are not immediately rewritten by account deletion.
- Match records are scheduled to expire after about one day. Database expiry cleanup runs asynchronously, so removal may occur later.
- Database recovery backups can retain earlier data for up to 35 days.
- Application-function logs are configured for seven days, and failed background-work messages for 14 days.
- AWS provides 90 days of management-event history. This describes that history, not a maximum retention period for every kind of security or service record.
If you cannot sign in, contact support@valentree.com for help requesting deletion. We may need to verify that you own the account before taking action. Because battle accounts do not request an email address, there is no automatic email-based password recovery.
Contact and changes
For privacy questions or a request about your information, contact VALENTREE LLC at support@valentree.com. We will update this page when our data practices change. The date above identifies this version.