Privacy Policy

Last updated: September 3, 2026

Data We Collect

  • Account data (email, username) — via Clerk, our authentication provider.
  • Uploaded content — video files, titles, game tags, and associated metadata.
  • Usage data — view counts on your clips, storage used, upload timestamps.
  • Payment data — handled by Clerk Billing and its processor Stripe. We never see or store your card numbers.
  • Technical data — IP address, browser, and device info collected via standard server logs.

Who Can See Your Clips

Clips are unlisted, not private. Each one gets a long random address of the form rekaptr.dev/v/3f9c…, and anyone holding that address can watch it without an account. That is deliberate — it is what makes a clip play inline when you paste it into Discord instead of showing a login wall. We do not publish a directory of clips and we do not submit them to search engines.

Two consequences we would rather state plainly than have you discover:

  • Sharing a clip into a squad shows it to that squad inside the app, but it does not make the link private. Anyone who obtains the address can still open it.
  • The video file is served from our CDN at its own unguessable address, so what removes access is deleting the clip — not unsharing it from a squad.

Deleting a clip deletes the underlying file. Deleting your account deletes every clip you uploaded, together with your comments, reactions, votes and squad memberships; squads you created are handed to another member, or deleted if you were the only one left.

The Desktop App

Rekaptr for Windows records to your own disk. Your recordings, clips, settings and logs stay on your machine unless you choose to share a clip. Nothing is uploaded in the background, and the app works fully signed out.

When you share a clip, the video is uploaded along with its title, game name, duration and file size. With squad linking enabled it also carries its recording time — the wall-clock time of the clip's first frame — so several people's recordings of the same moment can be lined up by subtracting one from another. Nothing about the clip's audio is analysed or sent for this, and with squad linking off the recording time is not sent either.

The clip also carries a waveform: about 500 numbers, measured on your computer, saying how loud the clip is from one moment to the next, so the player can draw its timeline. It is loudness only. It cannot be played back or turned into speech, and it is not used for anything else.

Discord Voice Presence

Which voice channel you were in. When you share a clip with squad linking on, the desktop app reads the log file the Discord application keeps on your computer to see which voice channel you were in, and when, while that clip was recorded. This needs no Discord connection and only the time covered by the clip is used. The channel ID is turned into a code made for that squad (a keyed SHA-256) on your computer before upload, so we receive neither the channel's ID nor its name, and the same channel has a different code in every squad. We use it only to tell whether two squadmates were in the same channel while they recorded the same moment. If Discord changes that log, this simply stops finding anything.

Who was with you. If you connect Discord in the desktop app's settings, Rekaptr reads which people are in your voice channel from the Discord application already running on your computer, over its local connection. Rekaptr does not sign in to Discord on your behalf, cannot read messages, and cannot post anything.

  • Nothing is read until you connect Discord yourself. After that, Rekaptr stays connected to your Discord app while it runs, but it writes the roster down only while a recording is actually running.
  • The roster is written to a local database beside that game's recordings. Those entries contain real Discord user IDs and never leave your computer.
  • When you share a clip with alignment enabled, the IDs covering that clip's time window, and when each person joined or left during it, are hashed (SHA-256) before upload. We receive the hashes, not the IDs. Two clips are only suggested as the same fight if the two people were in the same voice channel at the same time while that footage was recorded.
  • We store those hashes with the clip, for as long as the clip exists. We compare them only against people on that squad who have connected Discord to their own Rekaptr account. A hash matching nobody is never resolved to a person.

Being honest about the limits of this: the hashing uses a fixed value published in Rekaptr's open-source code, so it is not a secret. It prevents someone's raw Discord ID from being uploaded or stored; it would not stop someone who already had a specific ID in mind from testing whether it matched. If you would rather none of this happen, do not connect Discord — every other part of the app works without it.

If you link your own Discord account, we also store your Discord user ID and username, so squadmates' clips can be matched to you. You can unlink at any time in the desktop app's settings, which deletes both.

Reporting a Clip

Anyone watching a clip can report it, with or without an account. A report stores the reason you picked, anything you typed, your account ID if you were signed in, and a one-way hash of your IP address — enough to stop one person filing the same report a thousand times, without keeping addresses in our database. Reports are used to moderate content and for nothing else; we do not tell the uploader who reported them.

How We Use Your Data

  • To operate the Service (store, serve, and share your clips).
  • To process subscription payments.
  • To enforce storage limits and usage policies.
  • To respond to support requests and legal obligations (e.g. DMCA).

We do not sell your data or use it for advertising.

Third-Party Services

  • Clerk — authentication and billing. See Clerk's privacy policy.
  • Stripe — payment processing (via Clerk Billing). See Stripe's privacy policy.
  • Bunny.net — video storage, transcoding, and delivery (Bunny Stream).
  • Supabase — database hosting.
  • Vercel — application hosting.
  • Steam — game artwork lookups (no personal data sent).
  • DiceBear — generates the robot-style profile pictures and squad icons. The app and the website request each image from api.dicebear.comusing your account ID as the seed, so DiceBear receives that ID and the network address the request came from. No name, email or clip data is sent. The desktop app caches each image on disk so it is requested once, not on every launch.
  • Discord — the copy of Discord running on your own computer, and only if you connect it. See the section above. When you connect, the desktop app also exchanges Discord's one-time sign-in code for an access token with Discord's servers, and renews it about once a week. Those calls carry that token and nothing about your clips, squads or recordings. Rekaptr's servers do not contact Discord about you.
  • Cloudflare and Google time servers — the desktop app checks the current time against time.cloudflare.com and time.google.com, so clips recorded on different machines can be lined up. These carry no account information.

Data Retention

Free-tier clips are deleted automatically 30 days after upload. Paid-tier clips are retained until you delete them or cancel your subscription and exceed the free-tier limit. Account data is retained until you delete your account.

Data the desktop app keeps on your own computer — recordings, saved clips, settings and the local Discord voice roster — is governed by the retention settings you choose in the app, not by us. A voice roster is deleted once the footage it describes can no longer be clipped: after your saved-clip retention if you set one, otherwise after 30 days. You can also delete all of them at once under Settings, Connections. Uninstalling Rekaptr does not delete your recordings or clips; remove that folder yourself if you want them gone.

Your Rights

Depending on your jurisdiction (EU, UK, California, etc.), you may have the right to access, correct, export, or delete your personal data, and to object to certain processing. Contact privacy@rekaptr.dev to exercise these rights.

Children

Rekaptr is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us and we will delete it.

Security

We use industry-standard security practices. No internet service is 100% secure, and we cannot guarantee absolute security.

Changes

We may update this policy. Material changes will be announced in-app at least 14 days before taking effect.

Contact

privacy@rekaptr.dev