Privacy Policy

This policy explains what ClipBuffer ("we" or "us") collects when you use the ClipBuffer website, desktop apps, iPhone app, Discord bot and clip server, why, and what you can do about it. We collect little, and only what the service needs to work.

1. Signing in with Discord

The only way to sign in is with Discord. When you do, Discord gives us your Discord user id, username, display name and avatar URL, and we store them to identify your account; your Discord id is your account id. We also ask for permission to see which Discord servers you belong to, used only to check whether you are a member of The Prestige server, which decides your price. We store the result of that check and when it was made, along with a refresh token that lets us repeat it later without asking you again. We never see your Discord password, email address or messages.

2. Sessions and cookies

Signing in on the website sets one cookie, cb_session. It is HttpOnly, sent only over HTTPS, and holds a signed token that identifies your account for up to 90 days; logging out clears it. The apps and the Discord bot use the same kind of signed token, kept on your device. The website has no analytics, advertising cookies or third-party trackers.

3. Account and payment records

For each account we keep when it was created and last signed in, when your subscription started and ends, whether your access is complimentary, revoked or administrative, your clip credit balance and the clip ids it was spent on, your one-time trial's start and end, and the total you have paid. For each payment we keep the amount, status, creation and payment times, and the OxaPay tracking id and order id that match it to your account. Payments happen on OxaPay's pages from your own wallet; we never receive or store wallet keys, card numbers or bank details. OxaPay's own privacy policy covers what it collects.

4. What the apps report

Whenever the desktop or iPhone app checks your licence (at start-up and about once a minute while open) it sends your session token, the app version, the operating system and a random install id created on that device; we keep the version, platform and last-seen time per install, so we can see which app versions are in use and help when an update fails. The desktop app also sends its activity log to us automatically so a reported problem can be looked at directly; the logs describe what the app did (channels buffered, clips cut, errors) and may include file paths on your computer. Sending a report from the app is noted on your account. The iPhone app saves clips to your own Photos library and may register a push notification token with us so we can tell your phone when a clip is ready; each phone has its own device id, so several phones can share one account.

5. The clip server

When you add a channel in the iPhone app or through Discord, our clip server buffers that stream and keeps only the last few minutes of it. When you cut a clip, the server stores the file for a limited period, currently about a week, then deletes it. It also stores the watermark image you upload, any layout settings you save, and the list of channels you follow. Clips are available to you and, where you choose, posted to the Discord channel or direct message you selected.

6. How we use it

Only to run the service: signing you in, deciding what your account may use and what it costs, processing and matching payments, delivering clips, keeping the apps updated, answering support questions and stopping abuse. We do not sell personal data, show ads, build advertising profiles or share your data beyond the providers below.

7. Who else is involved

• Discord, for sign-in, the bot, and the clips you send to Discord.
• OxaPay, for payments.
• Apple, for distributing the iPhone app through TestFlight and, if you allow notifications, delivering them.
• Kick and Twitch, whose public streams the service buffers; the service connects to them the way a viewer would.
• The infrastructure that hosts the website, the clip server and our storage.

Account data lives in our own private storage, accessible only to the people who run ClipBuffer. We do not give your data to advertisers or data brokers, and disclose it only when the law requires.

8. Administrators

A few administrators can see the records above and can extend, revoke or comp an account or adjust its credits; each such action is logged with who made it.

9. How long we keep it

Account and payment records are kept for as long as your account exists. Buffered stream data lives for minutes, clips for about a week, and diagnostic logs are trimmed as they grow.

10. Your choices

• The dashboard shows your plan, payments and credits.
• Log out, or clear the cookie, to end a website session.
• You can remove ClipBuffer from your Discord authorized apps at any time; we then cannot refresh your membership check, and you will need to sign in again to use the service.
• You can ask us on Discord to delete your account. We then remove your account record, clips, watermark, diagnostics and the personal details on your payment records, keeping at most bare payment amounts and dates for accounting, with nothing that identifies you. Deleting the account forfeits remaining time and credits.

If the law where you live gives you rights to access, correct, export or delete your data, ask us on Discord and we will honour them.

11. Children

The service is not directed at children under 13 and we do not knowingly collect data from them; Discord itself requires users to be at least 13. If you believe a child has an account, tell us and we will delete it.

12. Security

Session tokens are signed, the cookie is HttpOnly and HTTPS-only, payment notifications are signature-checked, and our storage is private. No system is perfectly secure, so tell us on Discord right away if you suspect a problem.

13. Changes and contact

We may update this policy; the new version is posted here with a new "Last updated" date, and significant changes will be announced on the website or Discord. Questions go to us on Discord at discord.gg/clipbuffer. The Terms of Service cover the rules of using the service.