Closed beta terms & AI disclosure

ChaseFrame is currently in closed beta, available only to invited testers. Features, scoring, and what is available at any given time can change without notice while the beta is under active development.

Beta data — including videos, matches, timelines, and reports — may be removed during maintenance, migrations, or resets of the beta environment. There is no guarantee of continuous availability, and no backup or disaster-recovery service exists for this beta today.

Only upload videos you have the right to use. See User content below.

Coaching reports — scores, findings, and recommendations — may be produced with the assistance of an AI model. Results can be incomplete, miss context, or be incorrect.

Use the timestamps and video evidence linked to each finding or recommendation to verify it yourself before acting on it. A ChaseFrame report is a coaching aid, not an official ruling — it does not represent a decision by Behaviour Interactive, DBDLeague, or any competitive organisation, and ChaseFrame is not affiliated with or endorsed by Behaviour Interactive.

ChaseFrame collects only what the coaching workflow needs:

• Your email address and account details.
• Authentication sessions (so you stay signed in).
• Videos you upload.
• Match setup: participants, roles, and loadouts.
• Timeline tagging for a match.
• Generated reports and their scores.
• Technical logs necessary to operate and debug the service.
• Usage and generation data already recorded against your reports (e.g. when a report was generated).

That splits into three kinds: content you provide (video, match setup, tags), content the application derives from it (reports, scores, findings, recommendations), and technical, operational data needed to run the service (account and session records, logs). ChaseFrame does not run marketing analytics or advertising cookies — none are integrated into this beta.

Your data is used to run the coaching workflow you asked for: storing your video, building your timeline, and generating the report tied to your account and match. It is also used to operate and secure the beta itself — authentication, abuse prevention, and debugging technical issues.

Your data is not sold, and is not used for advertising or marketing analytics.

An uploaded video is streamed back only to you, for review alongside its match and timeline, and is used to generate the coaching report tied to that match. ChaseFrame does not publish or share your videos publicly.

ChaseFrame does not yet have an automatic, fixed-length retention policy — no promise of a specific number of days is made here. In practice:

• A video stays stored while it is needed for your account or the beta, or until it is deleted.
• Data, including videos, may be removed during beta maintenance — keep your own copy of anything you cannot afford to lose.
• Deleting a match removes its participants, timeline, and reports. Its video is removed once no other match still references it — a video can be reused across matches, so it is not always deleted the instant one match stops using it.
• Uploaded videos that were never attached to any match may be reviewed and removed through an administrative cleanup process after a grace period, to avoid accumulating unused files indefinitely.

You keep whatever rights you already hold over the video you upload. By uploading it, you grant ChaseFrame only the permission needed to store, process, and use it to produce your coaching report — nothing broader than that.

Do not upload video you do not have the right to use, or that belongs to someone else without their authorization. ChaseFrame does not claim ownership of your recorded gameplay.

Signed-in users can request deletion directly from Account settings, using their current password and an explicit typed confirmation. Deletion is immediate and permanent: it removes your account, matches and participants, timeline tags, reports and scores, and videos you own.

Support remains available for anyone who cannot access their account (see Contact); we confirm identity before handling that kind of request manually. No guaranteed turnaround time exists for the manual path.

ChaseFrame takes reasonable technical measures to protect your account and data — for example, your password is always stored hashed, never in plain text, and sign-in uses a session cookie rather than passing credentials around. As a closed beta, though, this is not a hardened, audited production system, and no security measure is absolute.

Avoid uploading or entering highly sensitive personal information you would not want stored in a beta environment.

For account questions, data requests, or anything else about the beta, reach us at support@chaseframe.com.

You must be at least 16 years old to participate in the closed beta.

ChaseFrame is an active beta, and this page may be updated as it evolves. The current version of this page always applies; continuing to use the closed beta after a change means you accept the updated terms.