TERMS OF SERVICE
Last Updated: June 22, 2026
1. Acceptance of Terms
By launching and interacting with the Track or Trash web deployment (accessible via trackortrash.me), you affirm that you understand and unconditionally agree to these Terms of Service. If you do not accept these constraints, please discontinue your access immediately.
2. Purpose and Permitted Use
Track or Trash is delivered as an interactive client utility intended for individual library organization purposes. You are granted a limited, revocable, non-exclusive right to utilize this interface for checking, sorting, or removing personal tracks within your personal streaming libraries.
3. User Account Security and API Limits
You acknowledge that you are using your own Developer Credentials (such as Spotify Client IDs or Google OAuth configurations) to leverage this layout. You are solely responsible for:
- Maintaining the confidentiality of your API keys and local browser tokens.
- Adhering to the Developer Terms of Service stipulated respectively by Spotify AB and Google LLC.
- Any accidental data modifications, playlist deletions, or permanent item removals occurring as a result of using this application.
4. Disclaimer of Warranties ("As-Is" Provision)
TRACK OR TRASH IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. THE DEVELOPER DISCLAIMS ALL GUARANTEES REGARDING OPERATIONAL STABILITY, ABSENCE OF GLITCHES, DATA SYNCHRONIZATION ACCURACY, OR THE RECOVERY OF TRASHED PLAYLIST CONTEXTS. USER ACKNOWLEDGES THAT DELETION PROCEDURES INITIATED VIA SWIPING ACTIONS ARE PERMANENT AND NON-REVERSIBLE VIA THIS INTERFACE.
5. Limitation of Liability
IN NO EVENT SHALL THE APP CREATOR BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, SPECIAL, OR INDIRECT DAMAGES, INCLUDING BUT NOT LIMITED TO LOSS OF ACCESS, API RATE-LIMIT BANNINGS, LOSS OF PLAYLIST DATA, OR UNANTICIPATED BEHAVIORS INDUCED BY API ADJUSTMENTS IMPLEMENTED BY THIRD-PARTY STREAMING NETWORKS.
6. Modifications to Application and Terms
The architecture reserves the right to alter script paths, operational interfaces, or these legal requirements at any moment without prior notice. Continued execution after adjustments denotes acceptance of revised frameworks.