Privacy policy

Who runs ScrimDB

ScrimDB is an independently operated project run by Harry. It helps Valorant teams review matches and VODs, prepare strategies, and organise their work. For support, privacy questions or data requests, email harry15sutton@gmail.com.

Information we use

• Account information. When you sign in with Google, we receive your email address, name and profile image. We store these with your ScrimDB account, username, team memberships and permissions. We do not receive your Google password.
• Team content. We store match records, player identifiers and statistics, VOD links and notes, playbooks and tactical media, tasks, calendar events, and other content you or your team add.
• Capture information. A linked tray sends match data, device and application status, recording-session metadata, and VOD identifiers to ScrimDB. Local recordings stay on your PC unless you enable the separate YouTube streaming feature.
• Support and technical information. We receive information you send by email. Our hosting services process connection and request information, such as IP addresses, browser information and errors, to deliver and protect the service.

We use this information to sign you in, enforce team permissions, display and analyse matches, connect recordings to reviews, maintain the service, and answer support requests.

Google and YouTube access

ScrimDB uses YouTube API Services. Signing in to the website does not authorise YouTube streaming. You connect your YouTube channel separately in ScrimDB Capture and can leave that feature off.

When you enable and authorise YouTube, Capture reads your channel identity and creates and manages live broadcasts and streams for your recordings. It checks broadcast and archive status so the website can attach a playable VOD to the match. The YouTube permission shown by Google allows management of YouTube videos; Capture uses it for this recording and VOD workflow.

Capture sends the recorded game video and configured audio directly to YouTube. Broadcasts are requested as Unlisted. Anyone who receives an unlisted link may be able to watch it, including people outside your team. You are responsible for selecting the correct channel and audience setting and obtaining permission from everyone whose voice or gameplay you record.

The tray stores its YouTube refresh token on your PC using Windows protection for your user account. Access tokens are held in memory. The ScrimDB server receives video, broadcast and stream identifiers, timing and processing status, but not your Google tokens or reusable stream keys.

Google and YouTube process information under the Google Privacy Policy. Embedded YouTube players may collect device and playback information and serve content, including advertisements, under Google's policies.

Who can access information

Your team's content is available to members according to their roles and permissions. Coaches can manage team information. The project operator may access service data when needed to provide support, investigate an issue, or maintain the service.

We use Vercel for website hosting and file storage, Turso for the hosted database, and Google for sign-in and optional YouTube features. These providers process information needed to supply those services and may process it outside your country. Information may also be disclosed when required by law or needed to address abuse or a security incident.

We do not sell Google or YouTube user data or use it for advertising profiles. ScrimDB's use and transfer of information received from Google APIs follow the Google API Services User Data Policy, including its Limited Use requirements.

Cookies and browser storage

ScrimDB uses cookies for the site password gate, Google sign-in and your signed-in session. Browser storage remembers interface preferences such as theme and filters. The public demo uses sample data; changes made inside it are not saved to your team's workspace. Google sign-in and embedded YouTube content can use their own cookies and similar technologies.

Retention, disconnection and deletion

Account and team records are kept to provide your workspace and match history. During the private preview, account and stored-data deletion requests are handled by the operator rather than an automatic account-deletion button. Email harry15sutton@gmail.com to request access, correction or deletion. Include your account email and the team or content concerned. We may need to verify ownership and clarify how a request affects shared team records.

• Stop future YouTube access. Disconnect YouTube in Capture. You can also revoke ScrimDB's access in your Google Account permissions. Revoking access does not itself delete existing recordings or ScrimDB records.
• Remove stored ScrimDB data. Use the available content controls or email the operator to request removal of your account, team content or stored YouTube-related records. Tell us if you have also revoked Google access.
• Delete a YouTube recording. Manage or delete the video in YouTube Studio. Removing a VOD reference from ScrimDB does not delete the video from YouTube.
• Delete a local recording. Remove the file from your PC. Disconnecting YouTube or removing a website record does not erase local media.

We retain information where needed to resolve a request, protect the service, or meet legal obligations. Provider logs and backups follow the applicable provider's retention processes. Do not send passwords, authentication tokens, stream keys or private recordings in a support email.

Changes and questions

We update this page when the service or its data practices change and revise the date above. Contact the operator through Contact with questions or complaints about privacy.