Privacy policy

Blurp finds burps and farts in the videos you give it. This policy covers the Blurp website, its API, and Blurp for YouTube, the Chrome extension. It says what we collect, what we do with it, and how to get rid of it. We do not sell personal data, and we do not show ads.

What we collect

Your account

Your email address, whether you have verified it, and a display name if you give one. Signing in is handled by our authentication provider, which stores your password (hashed) or sends you one-time codes; we never see your password.

Your scans

The links you submit, the video and audio fetched from them, what the detector found, the clips cut from it, and the keep or reject decisions you make while reviewing. We also record how many minutes of video each scan processed, which is how plan allowances and billing are counted.

Payments

Paid plans are billed by Stripe. Your card details go to Stripe and never reach us. We keep the Stripe customer and subscription ids, your plan, the subscription's status and when it renews.

Saved site logins

On plans that include them, you can paste a cookies.txt for a site that requires signing in. It is encrypted before it is stored, used only to fetch links from that site for your own scans, and never shown back to anyone. Delete it from your account page at any time.

Problem reports

If you file a report, we keep what you wrote, an email address if you gave one, the page you were on, and your browser's user agent. We also keep a one-way hash of your IP address to limit how many reports one address can send; the address itself is not stored.

Analytics and cookies

We count page views with Vercel Web Analytics, which does not use cookies and does not identify you. The site sets one cookie, to keep you signed in, and remembers your light or dark theme in your browser's local storage. There are no advertising or tracking cookies.

Blurp for YouTube

Blurp for YouTube lets Blurp fetch YouTube videos you ask it to scan using your own YouTube sign-in, because YouTube often refuses to hand videos to a server that is not signed in. To do that, it handles your YouTube cookies. This is exactly what it does with them:

• It reads the cookies Chrome holds for youtube.com, which include your YouTube sign-in. It reads no other site's cookies, and it does not read your browsing history or the contents of any page.
• It sends those cookies, over HTTPS, to your Blurp account and nowhere else: when you connect it, every 30 minutes after that, just before Blurp starts a YouTube scan for you, and when you press Sync now.
• Blurp stores them encrypted, as your account's YouTube login, and uses them only to fetch the YouTube videos you ask it to scan. They are not shared, not used for anything else, and not shown to anyone, including you.
• When you open its popup on a YouTube video, it reads that tab's address to offer Scan this video. The address is not stored or sent anywhere unless you press the button, which opens Blurp with that link filled in.
• In your browser it keeps a Blurp sign-in token and the time of the last sync, in the extension's own storage. The token expires after 90 days without use.

To delete the stored copy, press Sign out in the extension's popup, or Disconnect next to that browser on your account page. When the last connected browser is disconnected, the stored YouTube login is deleted at once. Uninstalling the extension stops it syncing; disconnect it on your account page as well to delete the copy.

Worth knowing: while it is connected, YouTube sees your account used from Blurp's servers as well as from your browser. If you would rather not, use a separate YouTube account in that browser.

What we use it for

• Running your scans and showing you their results.
• Counting usage against your plan, and billing for paid plans.
• Answering problem reports, and fixing what they describe.
• Keeping the service working and stopping abuse of it.

Nothing else. We do not sell personal data, use it for advertising, or share it with anyone except the providers below, who handle it only to run Blurp for us.

Who handles it for us

• Vercel: hosts the site, runs the processing, stores scan files, and counts page views.
• Neon: the database, sign-in, and the verification emails sign-in sends.
• Stripe: payments, for paid plans.

To process a link, Blurp's servers request it from the site it points to, as any visitor would. That site sees the request come from Blurp, along with a login if one is saved for it.

How long we keep it

Source video and the audio taken from it are deleted 24 hours after they are fetched. Everything else about a scan -- its clips, previews, detections and your decisions -- is deleted 7 days after the scan was created. You can delete a scan sooner from your history.

A saved login or synced YouTube login is kept until you delete it or disconnect, or until its cookies expire, after which it is no longer used. Your account, and the usage and billing records attached to it, are kept while the account exists. Billing records may be kept longer where tax law requires it.

Your choices

You can see and delete your scans, saved logins and connected browsers yourself. To get a copy of your account data, correct it, or delete your account and everything attached to it, use the report form linked at the bottom of every page (leave an email address if you want a reply). We will do it within 30 days.

Blurp is not meant for children under 13, and we do not knowingly collect their data.

Changes

If this policy changes in a way that matters, we will update the date at the top of this page, and tell account holders by email before a change that collects more or uses it differently takes effect.

Contact

Questions about any of this: use the report form linked at the bottom of every page (leave an email address if you want a reply).