Privacy policy

For your account, your workspace and the videos you record, Blip decides how your information is used.

When a business uses Blip to ask its customers questions (Blip Reply), to collect bug reports, or to share videos with viewers, that business decides what it collects and why. Blip handles it for them. Their own privacy policy covers you too, and their Reply and support pages link to it.

• Your account: your name, email address, the workspaces you belong to and your role in them. You sign in with a code we email you; we don't keep a password.
• What you record: video, sound, screen recordings, titles, and the transcript, summary and chapters made from the sound.
• When someone watches: that a video was viewed, how much of it, roughly when, the kind of device and browser, and the country and city from the network address. We keep a one-way code made from the address and browser, not the address itself, so repeat views count once.
• Reply answers: the person's video or written answers, their name, email and mobile number if the business has them or the person gives them, the consent words they agreed to and when, and their city only if they say it may be shown.
• Bug reports and support tickets: what the person writes, their name and email address, any screenshots or recording they add, the page they were on, their browser and screen size, the page's recent errors, and any replies they write on their ticket's page.
• Failed requests, only where the business has turned this on for its site: with a report, the last few requests the page made that failed. For each one, Blip gets the method, the web address without anything after its question mark, the status code and how long it took. Blip never collects what a request sent or what came back, and never its headers, cookies or sign-in details: the support button's script doesn't read them, and Blip's server keeps only those four facts. Nothing is recorded in the background and nothing is kept in your browser for this: the list is held in the page's memory and sent only when you send a report.
• Who you are, where the business's site says so: if you're signed in to the business's own site, it can tell Blip your name and email (and its own id for you) so you don't type them, signed so Blip can check it really came from that business. Blip shows the business's team that the report came from a verified customer.
• Problems: when something breaks in Blip, the error, the page or app version, and the device. Apps send this to us so we can fix it.
• Billing: your plan and what you've bought. Card details go to our payment processor, not to Blip.
• Reports: when someone reports something on Blip, what they tell us, and their email if they give it.

To learn which parts of Blip work and where people get stuck, we keep page, click and session analytics:

• In the Blip app, for signed-in people: which pages you open and in what order, your sessions and how long they last, and where on a page you click and how far you scroll. A click is kept as a position and a label for what was clicked, never what you type. It's tied to your account and workspace.
• On sendablip.com, for visitors: the same page, click and session analytics, without your name. It stores nothing in your browser (no cookies, no browser storage) and we don't keep your network address: a code that changes every day counts visits.
• If your browser sends Global Privacy Control or Do Not Track, none of this analytics is collected, in the app or on the site. The account log below is different: it's kept for security and support whatever your browser sends.
• Never on the pages businesses share (share pages, embeds, walls and Reply pages). How those are watched is reported to the business that shared them, as described above.

Clicks and scrolls are kept 90 days; sessions and page views 13 months.

Blip also keeps a log of what signed-in accounts do (pages opened and actions taken, never the content of what's typed) for security, support and improving the beta, for 13 months. It's kept even when your browser asks not to be tracked, because it's how we keep accounts safe and answer you when something goes wrong.

When a Blip's link first goes public, and whenever one is reported, an AI model checks its title, description, transcript, the link on its button and a few still frames, and we check its links against a link-safety service's list of phishing and malware sites. A result can hide a link until a person on our team reviews it. Only a person removes a Blip, and its owner can ask for another look.

When we take a Blip down, we keep its file and a record of it as evidence rather than deleting it, so an identical copy can be refused. We report apparent child sexual exploitation to the National Center for Missing & Exploited Children, as US law requires, and keep that material for a year. We share information with law enforcement when valid legal process requires it.

• To run Blip: store and play your videos, make transcripts and summaries, show you who watched, send sign-in codes and the emails you ask for.
• To keep it working and safe: find and fix errors, stop abuse, and keep records of who did what in a workspace.
• To bill you, once paid plans start.

We don't sell personal information, and we don't use your videos or answers to train AI models. The AI services we use to make transcripts and summaries process the sound and text for that job only.

These companies process information for us, only to provide Blip. We name them here by what they do; email support@sendablip.com for the current list of the companies themselves.

• Our database and sign-in provider: our database, sign-in and file storage, including the downloads of Blip's desktop apps.
• Our hosting provider: hosts the website and app.
• Our video hosting and delivery provider (a company in Slovenia, in the EU): stores video and plays it to viewers.
• Our storage provider for clips: stores published clips.
• The AI providers that turn sound into transcripts, summaries and chapters, and screen Blips for safety. Where one passes the work to others, we ask it to use only providers that don't keep it.
• A link-safety service: checks the links on Blips for phishing and malware.
• Our email provider: sends email.
• Our payment processor: takes card payments and keeps the card on file that a plan or monthly block charges. The card form on Blip's billing page is the payment processor's own, so your card number goes to our payment processor, never to Blip; Blip keeps only the card's brand, last four digits and expiry, to show you.

When a business connects its own app to Blip, Blip sends that app what the business set up: for example, a link to send, or that someone finished their answers.

When you report a problem to a business through its support button, Blip itself sends you no email about it. You get a link to your ticket's own page, where you read the business's answers and write back; anyone who has that link can read and answer that ticket, so keep it to yourself. If the business wants you emailed, its own email tool sends those emails, from the business's own address. To make that possible, when a ticket is filed, answered, closed, reopened or left unanswered, Blip's server tells the address the business chose (its own app, or a webhook to a tool such as GoHighLevel, Zapier, Make or n8n) and passes it your name and email address, your report, the message that was just added, and the link to your ticket's page. That tool writes and sends the email under the business's own agreement with it; Blip doesn't see whether it was sent or opened. Blip does email the business's own team (its owners, admins and staff) when a ticket comes in or you reply.

Where a business has written guides, its support form may show you some: the ones it set for the page you're on, and ones that match what you type in "What happened". To find those, the form sends Blip the page's address and the first 200 characters of what you've typed so far. Blip looks them up and keeps neither. For the business, Blip counts that guides were shown, which guide you opened, your answer to "Did this solve it?", and whether a report came from the same browser on the same site in the next 72 hours. It tells one visitor from another by a scrambled mark made from your network address and your browser's name, never by your name, your email or the address itself, and the key that mark is made with is thrown away each month, so it can't be traced back to you after that. Nothing is stored in your browser for any of this. If you send your report and what you typed matched none of the business's guides, Blip keeps the first 200 characters of it for the business, which receives your whole report anyway, with email addresses, links and long numbers taken out, so the business can see what to write a guide about. If you don't send a report, nothing you typed is kept. These counts are kept for 13 months, and after that only as monthly totals with no visitor in them.

A business can also publish its guides on a page of their own, at Blip's address or on the business's own domain. Reading it needs no account and stores nothing in your browser, and the page loads nothing from any company but Blip; a guide's video loads from our video provider only when you press play. For the business, Blip counts how many times each guide was opened each day, and how many readers answered "Did this help?" with yes or no. Those counts hold nothing about who you are. To keep one reader from being counted over and over, Blip briefly uses the same scrambled mark described above, which it doesn't keep with the count. A search on that page is looked up and not kept. If you press "Report a problem" there, the business's support form opens and everything above about that form applies.

A business can also have its Reply invites sent as text messages, through its own provider: its GoHighLevel account, or a webhook address it chooses (such as Zapier, Make, n8n or its own app). Blip has no texting provider of its own. To send each text, Blip's server passes that provider the person's mobile number, name, email and their link, and for GoHighLevel finds or saves them as a contact in the business's account. The business's provider sends the text under the business's own agreement with it, and the business must have the person's permission to text them. A reply of STOP to a GoHighLevel text is handled by GoHighLevel, and Blip doesn't text anyone GoHighLevel has marked as not to be texted.

A business can ask Blip to read its own website and make guides from it: short help pages its visitors can read. Blip reads only a site the business has already set up with Blip (a site on one of its support buttons, or its own Blip domain), and only that site's public pages, the ones anyone can open.

• Blip's server does the reading, as a robot that says who it is: its requests carry the name BlipBot. No visitor's browser is involved.
• It follows the site's robots.txt, asks for one page a second at most, and reads a few hundred pages at most. It doesn't sign in, fill in forms or run a page's scripts.
• Blip keeps each page's words, headings, lists and links as plain text, with the page's address, for that business's guides. It doesn't copy the site's design or code, and pictures stay links to the site.
• The business chooses which pages become guides, can read the site again when it changes, and can remove what was read at any time.

If you run a site and want BlipBot to leave it alone, add a rule for BlipBot to your robots.txt, or email support@sendablip.com.

Any server your browser contacts sees your network address and basic browser details. Here is every company other than Blip that your browser contacts when you use Blip, and when:

• sendablip.com and the sign-in page: none. Blip serves its own fonts and scripts.
• A shared video (its link, an embed, or a Blip inside a business's site), a wall of clips, or one clip: only Blip until you press play. Before that, the page shows a picture of the video from Blip. When you press play, our video delivery provider's player loads from its servers with its own font, fetches the video, and reports to that provider how quickly it loads. The provider also sees the address of the site the video is on.
• A business's logo, and any picture it adds to its Reply pages, walls or share pages: stored by Blip and shown from Blip's own address, not from the business's website. When a business gives Blip a web address for a picture, Blip's server fetches it once to make that copy.
• Recording, answering a Reply or reporting a problem on video: the recording uploads from your browser straight to our video hosting provider.
• Your support ticket's page (the link you get after reporting a problem): only Blip. The screenshots you sent are shown from Blip's own address. If you sent a recording, it's as with a shared video: nothing loads from our video delivery provider until you press play.
• Signed in to Blip: your videos' pictures, previews and player come from our video hosting provider.
• Paying, in Settings, Billing: nothing from our payment processor loads until you open the card form. Then its card fields load from its servers inside the page, so it can take the card, run its fraud checks and, if your bank asks for one, show the bank's check that it's you.
• Blip for Mac downloads its speech model from Blip the first time you edit a recording; your recordings stay on your Mac for that. The Windows installer includes the runtime it needs, so it downloads nothing. (Blip for Mac 1.4.0 and earlier downloads the model from an outside model library, and the Windows installer 0.3.0 and earlier downloads the runtime from its maker, until they update.)
• Emails from Blip show Blip's icon, and a business's logo, from Blip's own address. They have no tracking pixel and their links aren't rewritten, so neither Blip nor our email provider learns whether you opened an email or clicked a link in it.

There are no advertising pixels, social media buttons, outside analytics or captchas on Blip's pages.

The picture a shared link shows in a chat or social post is drawn on Blip's own servers, with fonts and emoji that ship with Blip: no font or emoji service is contacted, even for a title in another script or with emoji. (Noto fonts under the SIL Open Font License; emoji graphics by Twemoji, © Twitter, Inc and other contributors, under CC-BY 4.0.)

If you're signed in, we use cookies to keep you signed in and to remember the workspace you last used, and your browser's storage to remember small choices such as light or dark mode.

If you're visiting sendablip.com or watching a shared video, Blip stores nothing in your browser: no cookies and no browser storage. The usage analytics above keep their count in the page's memory only, so it's gone when you close or reload the page. The video player sets no cookies as Blip uses it.

One exception: if you open a Blip member's referral link (sendablip.com/join/...), Blip keeps one cookie, blip_ref, for 60 days, so the member gets credit if you join. It holds only which link you came from. See Referrals below.

Something is stored only when you do something that needs it. For example: after you give your name and email to watch a video that asks for them, or enter a video's password (a cookie, so you aren't asked again); when you type your name to watch or comment, or your details in a support form (your browser's storage, so you don't type them again); after you send a report through a support form, the link to that report's page and its number (your browser's storage, so the form can list it under Your reports and tell you when it's been answered; clearing your browser's storage for the site forgets them); and the recorder's settings once you use it.

We don't use advertising cookies.

When someone opens a Blip member's referral link, Blip records that the link was opened, with a scrambled code made from the visitor's network address and browser that can't be turned back into either, and the name of the website they came from (never the full address). It keeps the blip_ref cookie described above for 60 days.

If they join the waitlist or sign up, Blip records which member referred them, their name, their email address (to count each person only once), and whether they've joined or paid for a plan. The member who referred them sees only their first name and last initial and how far they've got, never their email address or anything they record.

Blip uses this to run the referral program and to stop it being misused, for example someone referring themselves. Where the law asks for a reason, it's Blip's legitimate interest in running the program fairly.

• Your videos stay until you delete them. A deleted video can be restored for 30 days, then its files are erased for good.
• A video nobody has watched for 6 months keeps one standard-quality (720p) version and its original upload, and its larger sizes are removed, after at least 14 days' notice. It isn't deleted and keeps playing. The Terms explain this.
• Reply answers and their consent stay until the business deletes them or asks us to erase a person.
• Support tickets and their messages stay until the business that received them deletes them or asks us to. A ticket's link shows the whole conversation while the ticket is open and for 90 days after it closes; after that it shows only where the ticket stands.
• Records of errors are kept for 90 days.
• Records of who watched a video through its link or an embed are kept for 13 months. Records of who opened, shared or changed a video, read its transcript or signed in are kept for up to 6 years, so a business can show what happened.
• Your account stays until you ask us to close it.

You can ask to see, correct, export or delete the information Blip holds about you. Email support@sendablip.com from the address you use with Blip. If a business collected it through Blip, we may pass your request to them, since they decide what happens to it.

Someone who answered a Reply can ask to have their answers taken down at any time, as the consent they agreed to says.

Blip isn't for children. People answering a Reply confirm they're 18 or older.

If we change this page in a way that matters, we'll tell signed-in people in Blip or by email before it applies.