Privacy Policy
Effective date: September 12, 2026 (replaces the version effective September 4, 2026)
Mixtape (“Our Mixtape,” “we”) is a song-request and charitable-giving layer for live events, operated by Efficient Frontier Labs, LLC. This policy explains what we collect, what we deliberately don’t, and your choices. The short version: we never see your payment details, we never hold donated funds, and we keep as little about you as running the event requires.
What we collect from guests
We collect information when you RSVP, search for a song, request a song, complete a donation, or separately sign up for event texts. The lists below describe the first four; text signup is described under Optional event text messages.
When you RSVP:
- Your name. This is required.
- One way to reach you, either an email address or a phone number. One of the two is required. You can also give us a phone number in addition to an email address, which is optional.
- A normalized copy of the contact information you gave us. We lowercase it and strip formatting so we can match your RSVP when you arrive and match your activity during the event back to it. This copy contains the same email address or phone number you typed, in a standardized form, and we index it so the matching works.
- Whether you checked in and when, how many people arrived with you, and which host or volunteer checked you in.
Your RSVP name and contact information are never shown on the event screen or on a recap page. They are used for the guest list, check-in and RSVP confirmation. The RSVP name is separate from the optional dedication described below, which is the only place a guest name is displayed publicly.
When you search for a song:
- That a search happened, and whether it found anything. We record one entry noting that this session searched and how the search was answered — that it returned songs, that it returned none, or that the song list was not available. We do not keep the words you typed. The search text is never written down anywhere, so we cannot tell you, or anyone else, what any guest searched for.
- The same functional session identifier described below, so we can tell how many people searched rather than how many searches happened. Nothing here is tied to your name or your RSVP.
We collect this for one reason: to see how many guests looked for a song and did not end up requesting one. That gap is the only way we can tell whether the song list is too small or the flow is confusing, and it is not visible from anything else we keep.
When you request a song:
- The song and artist you requested, the charity you chose, and the amount you selected before checkout.
- An optional dedication, meaning your name and a short message, and only if you check the box agreeing to display it.
- A code identifying which QR you scanned, for example a table number, used for event analytics.
- A functional session identifier so the app remembers your charity choice during the event. We use no advertising cookies and no cross-site tracking of any kind, and no third parties place cookies through Mixtape. You can clear or block this identifier through your browser's standard cookie controls. Mixtape works without it, though it won't remember your charity choice between requests.
- Basic technical information, such as IP address and device type, used for security, rate-limiting, and abuse prevention.
- Event analytics collected server-side, for example that a request was started or completed. These are not tied to advertising profiles. We don't have any.
- If your request could not be accepted, an entry noting why — for example that the host had paused requests, that the event had ended, or that the song cannot be played at this event. This records the reason only. It does not record the song you were trying to request.
When your donation completes: donations are made on Every.org, not on our site. We never receive or store your payment card details. Those are handled entirely by Every.org and its payment processor.
When a donation completes, Every.org sends us a confirmation message. That message can include your name, email address, donation amount, chosen charity, and a charge identifier. Two things happen to it, and we want to be precise about both. First, we read out the fields the event needs and store those on their own: the amount, the charity, the charge identifier, the date, how the donation was confirmed, and, only if you opted in, your name for the dedication. Second, we keep the confirmation message itself, in full and unaltered, in a delivery log for 30 days after we receive it. We do this so that if our processing fails we can replay the message rather than drop your donation out of the event total. That stored copy can contain your name and your email address. After 30 days, we replace the message with a redaction marker; the delivery record and its non-message processing metadata stay as part of the event’s technical record. We do not read the stored message for any other purpose, we never use it to contact you, and we never add you to a mailing list.
An earlier version of this policy said that we do not store your email address. That was not accurate, because of the delivery log described above. This version corrects it.
If you join the waitlist
If you sign up on our landing page to hear about the beta, we collect your name, your email address, what you told us you want to use Mixtape for, and which page you came from. This one is a mailing list: we keep it so we can email you about Mixtape, and we hold it ourselves rather than handing it to an email vendor. It is separate from event data. Ask us at andrew@efficientfrontierlabs.com and we will remove you.
If you’re an event host
We store your Spotify account connection using encrypted tokens, plus playback state needed to run the queue. You can disconnect Spotify yourself, from the account menu on your events page. When you disconnect Spotify, we delete the tokens — the stored refresh token and the cached access token — so we can no longer reach your Spotify account, and playback stops until you reconnect. Signing out is a different thing: it ends your session and leaves the connection in place.
Disconnecting is not account deletion and we will not describe it as one. It does not remove your events, your guest lists, your donation records, the playback state we kept while running your queue, or the Spotify account identifier we hold so that reconnecting finds the same host instead of creating a second one. To have those deleted as well, email andrew@efficientfrontierlabs.com and we will remove them.
How we use information
To run the event. That means: managing the guest list and check-in, sending an RSVP confirmation when email delivery is enabled, recording optional event-text permission and honoring opt-outs, managing the request queue, displaying verified donation totals, showing dedications you opted into on the event screen and the event recap page, replaying failed donation confirmations so that totals stay accurate, preventing abuse, and understanding aggregate event performance, for example how many requests an event generated. That is the whole list.
We do not use your RSVP contact information for marketing. When confirmation email is enabled for an event, we use the email address you provide to send your confirmed RSVP details and a private link to your confirmation page. Giving only a phone number does not subscribe you to email. An RSVP confirmation is not a donation receipt, a mailing-list subscription or permission for future-event marketing.
Optional event text messages
When text signup is available, you may separately choose automated SMS event reminders and logistics from the host named on that form, via Mixtape. For the September 19, 2026 pilot, this program is Yara via Mixtape. Signing up is optional and does not create or change an RSVP. An RSVP, donation, phone number in a guest list, or host approval alone does not enroll you. This permission does not cover donation requests, marketing, or other events.
We store the number you submit, the exact permission wording and its version, the named sender and event, the signup page, and the time of your affirmative submission. We also store a private opt-out identifier and event-specific opt-outs. We do not treat entering a number as proof that you control that phone. This release collects permission; automated text delivery has not yet been activated.
You can withdraw through the private opt-out link shown after signup, or contact andrew@efficientfrontierlabs.com. When text delivery is available, reply STOP to unsubscribe or HELP for help. A new web signup does not clear an existing opt-out. We retain permission evidence and opt-out records to honor your choices and demonstrate consent; these records are not subject to an automatic deletion schedule in this release.
We do not sell, rent, or share mobile numbers or SMS opt-in information with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are excluded from sharing for those purposes. Our infrastructure providers process signup records to operate this service. When SMS delivery is activated, Twilio and telecommunications carriers will process the phone number and message content needed to deliver texts and honor opt-outs.
We record whether the email provider accepted or delivered a confirmation, or reported a bounce or complaint. We do not track email opens or clicks. Delivery does not tell us whether you read the message. Confirmation links are private: please do not share or forward them.
Who can see your information
The event host can see the guest list, including RSVP names and contact information, because the host owns the invitation. A host may also be able to grant one read-only view of their event dashboard to someone helping them run it; that view shows RSVP names, party sizes, and the invitation list the host uploaded, but not the contact information guests submitted, and it cannot export anything or change anything. Hosts do not see donor email addresses from Every.org confirmations. The service providers described below process the information needed to perform their roles.
What we don’t do
We do not sell personal information. We do not run ads or advertising trackers. We do not process payments or hold donated funds at any time. Donations flow from you to Every.org, a 501(c)(3) public charity, which grants funds to the charity you choose. Every.org’s own privacy policy (every.org/privacy) governs the checkout experience and your donation record with them.
Public display
Dedications, meaning name, message, song, and charity, appear on the event’s big screen and may appear on the event’s recap page, and only with your opt-in. RSVP names and contact information never appear on either one. If you’d like a dedication removed from a recap page, email andrew@efficientfrontierlabs.com and we’ll remove it.
Photos and video
Events using Mixtape may be photographed or recorded. See the Event Photo Notice posted at each event. Event footage may be used by the event host and by us to document and share the event and to demonstrate Mixtape.
Service providers
We use infrastructure providers to run the service (currently Vercel for hosting, Neon for our database, Upstash for real-time infrastructure), Spotify for host-controlled playback, and Every.org for donations. When confirmation email is enabled, Resend processes the recipient email address and message content, including your RSVP details and private confirmation link, to deliver the email. Every.org acts as an independent organization with its own policies, not as our processor.
Retention and your choices
We keep RSVP records, song-request records, and donation-state records as part of the event’s record. We do not currently delete them on an automatic schedule, and we would rather say so than describe a schedule we don’t run.
To access or delete information about you, email andrew@efficientfrontierlabs.com. We honor reasonable deletion requests from anyone, regardless of whether a specific privacy law requires it, except records we need for integrity, security, or legal purposes. Records that Every.org holds about your donation are governed by Every.org’s policy, and we can’t delete those on your behalf, though Every.org can.
A daily cleanup removes expired email-delivery metadata and provider callback records older than 30 days in limited batches. A backlog can take additional runs to clear. This cleanup does not remove RSVP records or the limited suppression records described below.
You can also ask us to stop confirmation emails. We keep a keyed digest of a blocked email address and the blocking reason so a retry or a later registration does not silently resume sending. This is a limited suppression record, not a marketing profile. Deleting an RSVP removes its pending confirmation from our delivery queue; requests involving copies held by our email provider also require provider-side handling.
We don’t track you across other websites, so we don’t respond differently to “Do Not Track” signals. There’s nothing to turn off.
Children
Mixtape is not directed at children under 13, and we do not knowingly collect personal information from them. Individual events may be age-restricted by their venue.
Security
All traffic is encrypted in transit (HTTPS). Host tokens are encrypted at rest. We keep the number of things we store about you small and the number of reasons few, because the best protection for data is not having it.
Changes and contact
We’ll update this page when the policy changes and adjust the effective date. Questions: andrew@efficientfrontierlabs.com.