SetLab is a tool for DJs. We take your data seriously and keep this policy short and plain. If you have questions, email kelcwu@gmail.com.
SetLab is a web app that helps DJs plan setlists. It imports your Serato library, uses AI (Claude by Anthropic) to generate a sequenced set based on your gig context, and exports the result back to Serato as a .crate file.
SetLab is operated by Kel Wu, an individual developer. Contact: kelcwu@gmail.com
Account
Serato Library
When you upload your Serato library file, SetLab extracts and stores per-track metadata:
Audio files are never uploaded. Only the text metadata above is stored.
Generated Setlists
When a setlist is generated, we store:
Setlists are private by default. You can publish a setlist to get a public share URL — see Section 5 for how that works.
Track ID (Audio Recognition)
When you use Track ID — recording a few seconds of a song through your microphone, or uploading an audio file or DJ mix to identify the tracks in it — SetLab sends that audio to ACRCloud, a third-party music-recognition service, to find a match. See Section 4 for details.
SetLab does not store your audio recordings or uploaded files. The audio is forwarded to ACRCloud for recognition and then discarded. We retain only the result of each request — the matched track metadata (artist, title, BPM, genre), whether a match was found, and a timestamp — so we can show your history and enforce monthly usage limits.
Subscriptions & Payments
SetLab offers a paid Pro subscription. Payments are processed entirely by Stripe —SetLab never sees or stores your card number. We store only a Stripe customer ID, your subscription status and tier, and the current billing period, so we can unlock Pro features and generate invoices. See Section 4 for details.
What We Do NOT Collect
We do not sell your data. We do not share it with third parties except as described in Section 4.
Supabase
Supabase provides our database and authentication. All user data — accounts, library metadata, and setlists — is stored in Supabase on AWS infrastructure in us-east-1. Row-Level Security policies ensure each user can only access their own data. Supabase Privacy Policy ↗
Vercel
SetLabis hosted on Vercel. Standard server logs (request metadata, IP addresses) are retained per Vercel's own policy. Vercel Privacy Policy ↗
Anthropic (Claude AI)
When you generate a setlist, SetLab sends your library metadata (artist, title, BPM, key, genre) and gig parameters to the Anthropic Claude API. No personally identifying information is included. Anthropic does not use API inputs to train its models by default. Anthropic Privacy Policy ↗
ACRCloud
When you use Track ID, the audio you record or upload is sent to ACRCloud for music recognition. ACRCloud processes the audio to return a match and does not receive your account information. SetLab does not retain the audio after recognition. ACRCloud Privacy Policy ↗
Stripe
Stripe processes all payments for SetLab Pro. When you subscribe, your card details are entered directly with Stripe and never pass through SetLab's servers. We receive only a Stripe customer ID and your subscription status. Stripe Privacy Policy ↗
Resend
SetLab uses Resend to send transactional email such as invoices. Your email address is shared with Resend solely to deliver these messages. We do not send marketing email. Resend Privacy Policy ↗
Last.fm
To enrich track metadata (such as genre and tags), SetLab may send an artist and title to the Last.fm API. No personally identifying information is included. Last.fm Privacy Policy ↗
Setlists are private by default. If you click “Make Public” on a setlist, it becomes accessible to anyone with the link at setlab.ai/set/[slug]. Public setlists show the track list, energy arc, and metadata — no account information is exposed. You cannot currently undo a public setlist through the UI; contact kelcwu@gmail.com to make one private again.
SetLab uses one cookie: the Supabase session cookie (prefixed sb-), set when you log in. It is HTTP-only, Secure, and SameSite. It expires when you sign out or after the session token expires (~1 hour, auto-refreshed while you're active).
No advertising cookies. No analytics cookies. No third-party tracking of any kind.
All data is stored in Supabase with Row-Level Security — database policies prevent any user from reading another user's data, even if they have valid credentials. Connections are encrypted in transit (TLS). Passwords are hashed by Supabase Auth (bcrypt).
SetLab is a small indie project. While we follow reasonable security practices, no system is perfectly secure. Do not store sensitive personal information in setlist names or notes.
SetLab is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. If you believe a child has provided us with personal data, contact us and we will delete it promptly.
When we make material changes, we'll update the “Last updated” date at the top. Continued use of SetLabafter changes means you accept the updated policy. For significant changes, we'll notify users by email if possible.
Questions, deletion requests, or anything else: kelcwu@gmail.com
SetLab is operated by Kel Wu · kelcwu@gmail.com