Last updated: November 15, 2026
Privacy Policy
Tracklyst ("Tracklyst", "we", "us") is built by Darklight Audio. This policy explains what data we collect when you use tracklyst.app, why, and who we share it with. It covers creators (people with a Tracklyst account) and listeners (people who open a share link or use the listener portal).
Who we are
The data controller is Aaron Trimble, operating as Darklight Audio, a sole proprietorship based in Tennessee, United States. Contact us at support@tracklyst.app, or by mail at:
Darklight Audio
6688 Nolensville Rd Ste 108 PMB 3025
Brentwood, TN 37027
United States
The short version
Your audio files live in your own Dropbox or OneDrive. We never store them on our servers. We store what's needed to make sharing and feedback work (share links, comments, approvals, play counts). We don't sell your data. Analytics stay off until you accept them in the cookie banner.
Information we collect
Account & storage connection. When you sign in, you authorize Tracklyst through Dropbox or Microsoft OneDrive (OAuth). We receive your email address, your display name, and access and refresh tokens that let Tracklyst read and write files in the folders you connect. We keep your refresh token on our servers so your share links keep working when you're not signed in. It's never sent to listeners. If you link a Dropbox and a Microsoft account to one subscription, we record that link. We never receive your Dropbox or Microsoft password.
Your audio & files. Tracks, artwork, and folder structure stay in your own Dropbox or OneDrive. We don't store copies of your audio. A few things are stored by us:
- A brand logo or default banner you upload in Settings. These are public, because link previews and listener pages show them.
- Waveform data and track credits (songwriter, producer, mix engineer), shown to listeners.
- A playlist's cover image, cached for about an hour so link previews load quickly.
- Share link data: playlist and track names and settings. Anyone who has the link can see this data.
- Share links created before October 2026 may include the creator's email address in the link itself. Creators can revoke an old link and share a new one at any time to replace it.
Lyrics transcription. If you transcribe a track's lyrics, our server fetches the track from your storage and sends it to our transcription provider (Groq) to generate the text. The audio isn't kept. The transcript is saved as a text file in your own storage.
Feedback & activity data. When a listener opens a share link, plays a track, leaves a comment, rates or approves a track, we store that activity (share link ID, the name the listener gives, comment text, ratings, approval status, timestamps, play and view counts) so the feedback thread and dashboard work. To stop password guessing on protected links, we store a keyed one-way hash of the IP address of anyone who enters a wrong password, never the address itself.
Listener portal. If you use the listener portal, we store your email address and send you a single-use sign-in link so you can see the playlists shared with you.
Recipient links. If a creator sends a playlist to someone as a separate link, we store the label the creator gives it (for example, a label's name).
Payment information. Subscription payments are processed by Lemon Squeezy. We never see or store your full card number. We receive your email address, order details, and transaction status to activate your plan. If you redeem a prepaid code, we record the code and your account. Track and download sales are processed by Stripe on the creator's own Stripe account. When you buy, we receive your email address, the amount, the currency, the Stripe session and payment IDs, and which playlist or track you bought, so we can unlock your download. We also keep a record of your download access and when it expires. The creator, as the seller, also receives your purchase details through Stripe and handles them under their own responsibility. If you're a creator who sells, you connect your own Stripe account and give your identity, bank and tax details directly to Stripe. We store only your Stripe account ID and whether it's set up to accept payments.
Email. We send transactional email through Resend, for example listener portal sign-in links, plan verification codes, feedback and comment notifications, usage summaries, and plan reminders. If you email support, your message passes through Cloudflare (email routing) and is stored in Google (Gmail).
Newsletter. Product update emails go through Kit (ConvertKit) and are opt-in only. We never add you automatically. When you opt in or out in the app, we keep a record of when, where, and the exact wording you agreed to. You can unsubscribe at any time using the link in any email.
API keys & webhooks. If you create an API key, we store only a one-way hash of it. If you set up a webhook, we send the event data you choose (for example, new comments or approvals) to the address you enter. Once that data reaches your destination, its handling is up to you and that service.
Analytics. We use Google Analytics (GA4) to understand overall site usage. It's off by default and only loads after you click "Accept" on the cookie banner. We use it for analytics only, not advertising. See Cookies below.
Standard logs. Like any web app, our hosting provider (Netlify) and database provider (Supabase) keep ordinary server logs (IP address, timestamps, request paths) for security and debugging.
How we use information, and our legal bases
We use this information only to run Tracklyst: to provide your account and share links, show feedback, process payments and unlock purchases, send the emails described above, provide support, prevent abuse, and keep the service secure and reliable. Where the GDPR or UK GDPR applies, we rely on:
- Contract: providing your account, storage connection, share links, feedback, lyrics transcription, the listener portal, payments, and support (Art. 6(1)(b) GDPR).
- Consent: Google Analytics and newsletter emails (Art. 6(1)(a) GDPR). You can withdraw consent at any time, through the cookie banner or the unsubscribe link.
- Legitimate interests: preventing fraud and abuse, limiting password guessing with hashed IP addresses, server logs, and keeping the service secure and reliable (Art. 6(1)(f) GDPR).
- Legal obligation: keeping payment and tax records (Art. 6(1)(c) GDPR).
Cookies & local storage
Tracklyst doesn't use tracking cookies. Sign-in state, app preferences (theme, connected account), your cookie choice, listener portal sessions, and purchase access are stored in your browser's localStorage, not in cookies. They only leave your device to authenticate a request. Google Analytics, if you accept it, sets its own cookies under Google's cookie policy.
Who we share data with
We share data only with the service providers needed to run Tracklyst:
- Dropbox and Microsoft (OneDrive) for storage and sign-in
- Supabase (database) and Netlify (hosting and file storage)
- Groq (lyrics transcription)
- Lemon Squeezy (subscriptions) and Stripe (track and download sales, made on the creator's own Stripe account)
- Resend (transactional email)
- Cloudflare and Google (support email)
- Kit (newsletter, opt-in only)
- Google (Analytics, opt-in only)
People you share a link with can see what that link contains (see "Your audio & files" above). Webhook data goes wherever you send it. We don't sell personal data, and we don't share it with anyone for their own marketing.
International data transfers
We and the providers listed above are based in, or process data in, the United States. If you're in the EEA, UK, or Switzerland, your information is transferred to the United States. Where required, these transfers rely on safeguards our providers offer, such as the European Commission's Standard Contractual Clauses.
Data retention
- Account data, share links, comments, and activity: for as long as your account is active, or until you delete the project or link. Revoking a share link stops new activity from being recorded against it.
- Listener portal email addresses: until you ask us to delete them, or the creator removes the playlists shared with you.
- Subscription payment records: for as long as needed to provide your plan, and at least 7 years for tax and accounting.
- Track and download purchase records: deleted 1 year after your download access ends, or sooner if the creator deletes the playlist.
- Newsletter consent records: for as long as you're subscribed, and afterward as long as needed to show you consented.
- Support email: for as long as needed to resolve your request.
- Failed-password records: up to 24 hours.
- Server logs: for the short periods our providers keep them.
When you ask us to delete your account, we delete or anonymize your data, except records we must keep by law.
Your rights
Depending on where you live (for example, under the GDPR, UK GDPR, or CCPA), you may have the right to:
- access the personal data we hold about you
- correct it
- delete it
- export it
- restrict or object to certain processing
- withdraw consent at any time
- complain to your local data protection authority
To exercise these, email support@tracklyst.app. We'll respond within the time the law requires, normally within one month. You can also revoke Tracklyst's access to your storage at any time in your Dropbox or Microsoft account's app permissions.
Children's privacy
Tracklyst is a professional tool for audio engineers, producers, and their clients. It isn't directed at children, and we don't knowingly collect personal information from anyone under 13.
Security
We use industry-standard measures to protect data in transit and at rest, including encrypted connections, refresh tokens kept server-side, and hashed API keys. No system is 100% secure. Report suspected issues to support@tracklyst.app.
Changes to this policy
We'll update the date at the top of this page when this policy changes. Material changes will be noted in the changelog.
Contact
Questions, requests, or complaints about this policy: support@tracklyst.app, or by mail to the address under "Who we are".