Privacy Policy

SetList is operated by [OPERATOR NAME], who decides how the data described here is used. Contact: [CONTACT EMAIL].

This policy covers SetList’s website, dashboards, radio stations and in-world objects. Second Life itself is run by Linden Lab under its own privacy policy.

Avatar names and keys

The name and UUID key of avatars that pay, own a venue, DJ, tip, turn alerts on, ask for a dashboard link or receive a venue kit. Our in-world objects send them to our server.

Payments

Payer, amount, weeks bought, time, the terminal used, the paid-until date before and after, and refund details (when, by whom, why).

Tips

Tipper, amount, time, the DJ on deck, the split percentage, each share, and whether the DJ’s share was transferred.

Venue setup

Venue name, owner, paid-until date and status, tip split, DJ list (Second Life username, display name and avatar key), lineup, and live state (who is on air and what is playing).

DJ streaming logins

A streaming username and password for each DJ. Passwords are stored encrypted.

Discord webhook

The webhook URL, only if the venue owner adds one. Stored encrypted.

Uploaded music

The audio files a venue owner uploads for AutoDJ, and the track details in them, such as title and artist.

Alert sign-ups

Avatar key and display name of each avatar that turns alerts on at a board, and whether alerts are on or off.

SetList objects

For each terminal, board and tip jar: its object key, owner, region name, script version and when it last contacted us.

Venue kit deliveries

Which avatar was sent a venue kit or update, when, and whether it was sent.

Dashboard logins

One-time links (we store only a fingerprint of each link, never the link itself), the avatar and role each is for, and when it was used. A cookie keeps you signed in (see Cookies).

Server logs

IP address, time, what was requested, and technical details sent by your browser or media player. This covers visits to this website, listeners (when you hear a venue’s stream, your viewer connects straight to our server) and DJs connecting their streaming software.

Audit log

A record of important actions, such as payments, refunds, setting changes, logins and admin actions, with the avatar or object involved and the time.

Messages to us

If you email us: your email address and what you write.

• Your real-life name, address, phone number or email address (unless you email us).
• Payment card, bank or government ID details. All payments are in L$ inside Second Life.
• Local chat or voice.
• Song requests. A request typed at a board goes straight to the DJ on air as an IM from the board. It does not pass through our server.
• Your location, beyond the region name where a SetList object is rezzed.
• Analytics or advertising trackers of any kind.

• To run the service: create and run each venue’s station, DJ logins, lineup, board, alerts, tip splits and kit deliveries.
• To handle billing: apply paid time, send renewal reminders, and pause and delete lapsed venues.
• For refunds and accounting: including checking our records against the Second Life transaction history of the SetList business account.
• To keep the service secure: check that requests really come from our objects, block replayed requests, investigate abuse and keep the audit log.
• To help you when you contact us.
• To meet legal obligations, such as handling copyright notices.

We don’t sell or rent your data, use it for advertising, or build profiles of you.

Anyone at the venue

The board shows the venue’s status, the DJ on air, what is playing, the next set and the lineup. The board’s web display shows the same to anyone who has its address.

The DJ on air

Song requests, with the name of the avatar who sent them.

A Discord channel

Only if the owner adds a webhook: the DJ’s name, the venue name and the current track’s title and artist when a DJ goes live.

The venue owner

Their venue’s DJs, lineup, payments and tips, including tippers’ names and DJ shares.

DJs

The venues they DJ for, their own streaming login and their upcoming sets.

SetList admins

Everything listed in this policy, to run and support the service.

OVH (hosting, US)

Our website, database and radio stations run on servers in the United States provided by OVH. All the data in this policy is stored there. If you use SetList from outside the US, your data is processed in the US.

Cloudflare (DNS only)

Cloudflare answers lookups for our domain name. Website and stream traffic does not pass through Cloudflare.

Discord

Only if a venue owner adds a webhook. Discord receives the go-live messages described above.

Linden Lab

L$ payments, IMs and our in-world objects all run inside Second Life, so Linden Lab handles that activity under its own privacy policy.

The radio stations run on AzuraCast, open-source software that we run ourselves on those servers. AzuraCast is software, not a company we send data to.

We may also disclose data when the law requires it, to deal with a copyright notice, or to protect the service and the people who use it. We don’t share data with anyone else.

• All website, dashboard and object traffic uses HTTPS.
• Every request from a SetList object is signed and checked, and a request can’t be replayed.
• Dashboards have no passwords. One-time links expire (24 hours for setup links, 15 minutes for login links), work once, and are stored only as a fingerprint.
• DJ streaming passwords, Discord webhook URLs and object secrets are stored encrypted.
• Only SetList admins can see data across venues.

No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.

While a venue runs

Everything the venue needs, for as long as it is paid or in grace.

Paused venue

All of it, for 30 days after the pause, so the owner can pay and pick up where they left off.

30 days after the pause

Deleted: the station and uploaded music, DJs and their streaming logins, the lineup, alert sign-ups and pending alerts, login links and the Discord webhook. Tippers’ names and avatar keys are removed from the venue’s tip records.

Accounting and security records

Payment records, tip amounts and shares (with the DJ’s avatar key), the venue’s name and owner, object records, kit deliveries and the audit log: 3 years[DRAFT] from the date of each record, then deleted.

Alert sign-ups

Until the venue is deleted. “Alerts off” at the board stops alerts at once.

Sign-in cookie

Up to 7 days, or until you sign out.

Server logs (IP addresses)

30 days[DRAFT].

Emails to us

As long as we need them to deal with your request.

• Alerts: choose “Alerts off” at any SetList board.
• Discord: the venue owner can remove the webhook at any time.
• DJs: ask the venue owner to remove you, or ask us.
• A copy, a correction or deletion: email [CONTACT EMAIL] with your avatar name. We answer within 30 days[DRAFT]. Because we only know you by your avatar, we may ask you to confirm the request from that avatar in Second Life before we act.

Some records have to stay for accounting (see How long we keep it). Where we can, we remove your avatar name and key from those records instead of deleting them. Deleting a venue owner’s data ends their venue, and paid time is not refunded except as set out in the Refund Policy.

Depending on where you live, you may have further rights under local law, including the right to complain to your data protection authority.

We set one cookie, sl_session, when you open a dashboard link. It keeps you signed in for up to 7 days or until you sign out, and it is signed so it can’t be altered. We use no analytics, advertising or third-party cookies. The board’s web display sets no cookies at all.

SetList is not aimed at children. Second Life sets its own age rules, and you must follow them to use SetList. If you believe we hold data about a child, contact us and we will delete it.

We may update this policy. We post the new version on this page with a new effective date, and give at least 14 days’[DRAFT] notice of material changes before they take effect.

Questions or requests about your data: [OPERATOR NAME], [CONTACT EMAIL].