DJCLIPZ Privacy Policy
Last updated
August 25, 2026
About this policy
DJCLIPZ is a browser-based two-deck DJ/VJ mixer offered as a production beta. This policy explains the information processed when someone visits DJCLIPZ, submits the access form, accepts the Terms, changes analytics settings, searches supported media, loads media, performs with the mixer, or uses the Agent Controller or legacy Performer adapter.
Information users provide
When someone enters or requests access to DJCLIPZ, we may receive:
- email address;
- optional name;
- optional role;
- optional intended-use information;
- marketing preference;
- Terms and Privacy acceptance records;
- the version and time of that acceptance.
The form is processed through Formspree. Marketing permission is separate from Terms acceptance and analytics choices.
Core Mix Intelligence
When someone uses the mixer, DJCLIPZ records first-party Mix Intelligence.
This may include:
- the media platform;
- validated media or video ID;
- canonical media URL;
- available media title;
- available creator or channel name;
- media duration and playback availability;
- playlist items and their order;
- items added, removed, or reordered;
- media loaded into Deck A or Deck B;
- playback, pause, restart, and seek activity;
- cue and loop activity;
- crossfader positions and transitions;
- which media assets are mixed together;
- playback errors;
- Agent Controller and legacy Performer start, pause, resume, takeover, and stop activity;
- whether a command came from a human, the Agent Controller, the legacy Performer adapter, or the system;
- command success or rejection;
- event times;
- a random mix-session identifier.
This collection is part of the DJCLIPZ production beta and begins only after the current Terms and Privacy notice have been accepted.
Server-assisted media search
After the current Terms and Privacy notice have been accepted and a human starts Agent Performance, the browser-local Agent Controller can send a media-search request to the first-party /api/media-search Worker. The Worker processes the search text transiently through the YouTube Data API to return validated, embeddable video-only results.
DJCLIPZ does not log raw search text in application or Worker logs, return it in the API response, or write it to D1. A one-way hash of the search text and requested result count may be used as a short-lived cache key. Selected video identifiers and limited public metadata may be written to the existing media metadata table and are subject to the metadata retention period below.
Separation from access-form identity
The DJCLIPZ application does not place the user’s access-form email, name, role, intended-use text, or marketing preference into Mix Intelligence events.
Mix Intelligence uses a random session identifier rather than the access-form email.
DJCLIPZ does not intentionally combine Mix Intelligence with Formspree identity records.
Why Mix Intelligence is used
DJCLIPZ uses Mix Intelligence to:
- operate and improve the mixer;
- understand which media and media combinations are used;
- measure session activity and feature adoption;
- compare human, Agent Controller, and legacy Performer activity;
- diagnose playback and control errors;
- prioritize product development;
- demonstrate demand and engagement;
- support business planning and fundraising;
- create de-identified aggregate community insights.
DJCLIPZ does not use Mix Intelligence to infer sensitive traits, political beliefs, health information, religion, race, sexual orientation, or other sensitive characteristics from a person’s media choices.
Community metrics
DJCLIPZ may publish aggregate product metrics such as the most mixed media on DJCLIPZ, common DJCLIPZ pairings, feature-use counts, and overall session trends.
These are DJCLIPZ product metrics. They are not YouTube view counts, YouTube audience measurements, creator-performance rankings, or YouTube endorsements.
DJCLIPZ does not publish individual mix histories, raw set lists tied to a session, or access-form identities. Small groups are suppressed before publication.
Google Analytics
Google Analytics is optional.
When allowed, it is used for general traffic, session, returning-use, and high-level funnel measurement.
DJCLIPZ does not intentionally send media IDs, titles, URLs, playlists, set lists, or detailed mixer events to Google Analytics.
Users can allow or decline Google Analytics through Analytics settings without losing mixer functionality.
Site, security, and performance information
Cloudflare processes normal website-request, security, and performance information when serving and protecting djclipz.com.
Cloudflare Web Analytics is used for general traffic and page-performance measurement.
DJCLIPZ’s first-party Mix Intelligence endpoint and database are also operated through Cloudflare infrastructure.
The public DJCLIPZ Agent documentation at /agents is served as static content with the rest of the DJCLIPZ site. It does not make a Pendium runtime request.
YouTube and embedded media
DJCLIPZ uses YouTube API Services and visible embedded YouTube players.
YouTube and Google process information when a player loads or plays media. Their processing is governed by their own policies, including the Google Privacy Policy.
DJCLIPZ does not download, record, cache, extract, or redistribute YouTube audiovisual content.
DJCLIPZ retrieves limited public media metadata and Made for Kids status to operate the mixer, support Mix Intelligence, and meet platform requirements. DJCLIPZ disables media-specific Mix Intelligence for videos designated Made for Kids.
Browser storage
DJCLIPZ may use browser storage for:
- the current Terms and Privacy acceptance version;
- the current mix-session identifier and mixer state;
- the Google Analytics choice;
- optional remembered-browser functionality when enabled;
- monitor-window state.
DJCLIPZ stores BPM and downbeat calibration in your browser so it can restore those settings on that browser. These calibration values are not synced to Formula Creative or other users.
A mix-session identifier does not persist beyond the applicable session-storage lifecycle.
Users can remove browser-held information by clearing site data.
Service providers
DJCLIPZ currently uses:
- Cloudflare for network delivery, security, analytics, Workers, and first-party D1 data infrastructure;
- Formspree for access and consent forms;
- Google Analytics when allowed by the visitor;
- YouTube and Google for embedded media playback and related media information.
DJCLIPZ does not currently sell Mix Intelligence or use it for cross-context behavioral advertising.
Retention
Detailed Mix Intelligence, reconstructable set lists, and Agent Controller or legacy Performer command records are retained for up to 30 days.
YouTube metadata is refreshed or deleted within 30 days.
DJCLIPZ may retain de-identified aggregate product metrics for up to 24 months for product, community, business-planning, and fundraising analysis.
Access, acceptance, and marketing records are retained only as long as reasonably needed for the applicable beta, communication, legal, or suppression purpose.
User choices and requests
Users can:
- allow or decline optional Google Analytics;
- decline marketing communications;
- unsubscribe from marketing communications;
- clear browser storage;
- delete the current first-party mix session;
- request access, correction, or deletion where applicable.
Because Mix Intelligence is not intentionally linked to the access-form email, DJCLIPZ may need the browser-held session reference or approximate session date and time to locate a record.
Deleting DJCLIPZ-held information does not delete information independently held by YouTube, Google, Formspree, or other providers.
Contact
Privacy and data requests may be submitted to:
Changes
DJCLIPZ may update this policy as the beta, Agent Controller, legacy Performer compatibility, media support, and measurement systems change.
When a change materially expands the information collected or how it is used, DJCLIPZ may require users to accept the updated notice before continuing.