Privacy Policy

Effective October 11, 2026. Last updated October 11, 2026.

  • October 11, second update: Blipzy looks for words about serious topics in reviews, comments and messages so it can hold its reply for the business to read, and for a health practice it writes public replies without mentioning a visit or treatment and does not send its direct messages to AI. Before it posts a reply to a Google review on its own, it reads that review on Google to check for a reply from the business, and does not keep that reply's words. Text you paste in to teach Blipzy is now listed with what we collect: it is sent to AI, and we keep only the notes made from it.
  • October 11: when Blipzy reads your Google reviews, it notes whether your business has already replied, and does not keep the words of your reply. Your public Google reviews are read through SerpApi while Google has not granted Business Profile access; this page had said all Google data came through Google's own APIs. What our team is emailed when a deletion needs a person to check its billing, that Stripe keeps its billing records after a deletion, and that our record of a refund we owe you is kept after a deletion.
  • October 6: before a review request is sent, we leave out you, your team and your own website's email domain. A notice about a payment on your account is sent to the owner even if you switched alert emails off. What we keep from Stripe: reference numbers, never card details.
  • October 5: a business can be registered on Blipzy once. We keep a record of which Google listing each business is registered to, so nobody can register it twice. If someone asks to join a business that is already on Blipzy, we email its owner that person's name and email address, and keep the request for 30 days. We also use the free-trial record to recognize a business with no Google listing being signed up a second time, and your time zone and the country in your address to ask about public holidays where you are.
  • October 5: a clarification that the button in the Search room is the only way Blipzy changes your listing details, and that replies to your reviews also go to Google, when you send or approve them, or automatically if you switch on automatic replies. Nothing about what we collect, how we use it or who receives it changed.
  • September 30: that we record when you pause and resume, and when each message arrives, so messages from a pause are drafted rather than sent. The line that ends anything Blipzy sends or posts on its own, which line says AI, and that you choose between two wordings of it, neither of which names Blipzy. The daily Google Ads totals we now keep, and for how long. What the summary email says about your Google Ads, and the setup steps email. That search terms from your ads are shown to your team. That we no longer send tracked search terms to our search data providers. The plans are now called the Search pack and the Social pack.
  • September 29: exactly what the Google Ads script sends us, who can see it, that it is never sent to an AI service, and how to stop it (there is no disconnect button: you delete the script in Google Ads). The Pause Blipzy switch. The screen names now match the app.
  • September 27: which search terms reach our search data providers, and that some of them come from your Google Business Profile. That Google may use the questions sent to Gemini to improve its products. How long we keep the record that stops a business claiming a second free trial. What your browser stores. A plain statement of how we treat data from Google APIs, and that we do not train AI models on it. What a deletion request forwarded by Instagram or Facebook now removes. Google Ads readings are now kept for 14 days, apart from the most recent one. That review invitations show your account email as the reply address. That we keep which Instagram or Facebook account was connected after a disconnect, so a deletion request can still reach it.
  • September 26: the ads audit is now part of the Google pack (renamed the Search pack on September 30).
  • September 14: Google Ads readings, if you connect an ads account.
  • August 7: a correction, and it matters more than an addition. This page said that disconnecting a platform deleted the content Blipzy had imported from it. That was never what the software did: disconnecting stops the flow and deletes the access token, and the imported content goes when you delete the business or your account. Corrected everywhere it appeared: three times on this page and once on the data deletion page.
  • August 7: three things Blipzy holds that this page had not named. The postal address you give us for your marketing emails, required by anti-spam law. The platform id of somebody who tells one of our businesses to stop messaging them, kept so we can refuse to message them again. And a record of a deletion request forwarded to us by Instagram or Facebook. The last two are kept indefinitely and on purpose, for the same reason as the email unsubscribe list.
  • August 4: Smart Answers, which let you point Blipzy at one of your own systems to answer a DM, has been removed. The paragraph that described it is replaced below by the webhook address you can still give Blipzy.
  • August 4: booking. If you turn it on, Blipzy asks Google when your calendar is busy, and only that. It also reads your own Instagram description, follower count and recent captions, if you connect Instagram, to learn how you write.
  • August 3: the one-tap changes Blipzy can make to your Google Business Profile when you press the button.
  • Earlier: reading your own website, review invitations, scorecard leads, the AI assistants used for visibility checks, and where connection tokens are actually stored.

Get Blipzy ("Blipzy") is a product of The Buddy Labs AI Inc. ("we", "us").

Who we are

Blipzy is operated by The Buddy Labs AI Inc., a company based in Ontario, Canada. For the data you and your business give us to run Blipzy, we act as the data controller. For the messages and content that other people send to your connected accounts, we act as a processor on behalf of your business, which is the controller of its own customer data. You can reach us about privacy at privacy@thebuddylabs.com.

What Blipzy does

Blipzy brings a business's own Google reviews into one inbox with replies drafted in that business's voice (Instagram and Facebook comments and messages join once Meta approves Blipzy), and reports on how visible the business is on Google and in AI search. If the business runs Google Ads, Blipzy can also read that account and say what it found. We only process data for the account that connected it, and only from platforms that account connected itself.

Information we collect

  • Account details from your sign-in provider: name and email address.
  • Business details you enter: business name, category, address, website, phone number and brand voice.
  • A postal address for your marketing emails, if you send any through Blipzy. Anti-spam law in Canada and the United States requires a real sender address on commercial email, so it is printed in the footer of emails we send on your behalf. You give it to us; we never guess it.
  • When somebody messaging one of our businesses on Instagram or Facebook asks to stop being contacted, we record the platform id that sent that message so we can refuse to message them again. That id and nothing else. The same applies to a deletion request forwarded to us by Instagram or Facebook, where we keep a record that it arrived and was carried out.
  • What is published on your own website. If you give us its address, our servers fetch up to six pages from it and read what is printed there. We save your services and their prices, your opening hours, any email addresses and phone numbers on the page, your postal address, links to your social accounts, any booking links, the page title and description, and which booking or website software the page appears to use. We identify ourselves as BlipzyBot when we ask, we never sign in and we never fill in a form, and the only pages we ask for are the address you gave us, whatever it redirects to, and pages linked from it on that same site (plus wherever those redirect to, though we keep nothing from a page that turns out to be somewhere else). We save it so Blipzy can answer questions about your business without you retyping it, it is replaced every time we read the site again, and you can clear it at any time from your Playbook.
  • Content from platforms you connect (Google, Facebook, Instagram): public reviews of your business, and, once you authorize those platforms, comments and direct messages sent to your business accounts. Where the platform identifies the sender, we store that identifier so a reply can reach them.
  • When Blipzy reads your Google reviews, it also notes whether your business has already replied to each one, so it does not show an answered review as waiting or post a reply in place of yours. Google has not given Blipzy access to Business Profiles, so these are read from your public Google Maps listing through SerpApi. Blipzy uses only whether a reply exists and, just before it posts a reply on its own, whether the reply on Google is the one Blipzy posted. It does not store the text of replies you post on Google yourself.
  • Your own Instagram profile, if you connect it: the account name, the description you have written on it, your follower and post counts, and the captions of your recent posts. Blipzy reads these to learn how you write and what you are known for, so replies sound like you rather than like a bot. It keeps a weekly record of the follower and post counts so it can show you whether the account is growing. This is your own account, never anybody else's.
  • When your calendar is busy, if you turn on booking, Blipzy asks Google only for BUSY AND FREE TIME RANGES, using a permission that returns nothing else: no event titles, no descriptions, no guests, no locations. It does this so it can answer a customer who asks whether you have space. If you point Blipzy at a calendar that belongs to somebody else, or that you share with another business, the same limit applies: Blipzy can tell that a time is taken and can never tell what it is taken for or by whom. None of it is stored. The busy ranges are read to work out free slots for that one reply, and neither the busy ranges nor the times we offered are kept afterwards.
  • The email address of somebody you refer, if you use a referral link. We store it so the reward can be credited when they sign up, and for nothing else. We never message them because you entered them.
  • The time zone your browser reports when you sign up. Blipzy uses it, together with the country in your address, to tell which day is today for you: so a Monday night post is not reported as a Tuesday one, so we can ask about the public holidays where you are, and so a holiday notice ends when your day does.
  • A counter of how many messages we have sent to each recipient, so the anti spam cap in our terms is real. The recipient is not stored: the counter is keyed on a one way hash of your business together with the recipient, so the table holds an unreadable string and a number and cannot be turned back into a list of people.
  • Customer contact details you give us for review requests: the names and email addresses you upload or enter so Blipzy can send review invitations on your behalf. You are responsible for having permission to contact them. We keep a record of who has been invited and who has unsubscribed, so nobody is invited twice and an unsubscribe is honored permanently. Each invitation shows your business name as the sender and your account email as the reply address, so a customer who answers it reaches you rather than us. If we cannot look up the account owner's email, it is the email of the team member who sent the invitation. Before a review request goes out, Blipzy leaves out the email addresses of the account owner, your team members and people you have invited to your team, and any address at your own website's domain (the website on any of your locations, unless it is a shared website platform or an email provider such as Gmail), because Google does not allow reviews from a business's own people. Those addresses are only compared with your list. We do not email them and do not store them with the invitation. Nobody is left out because of what they might say in a review.
  • If you run a free scorecard on our website without an account, and choose to enter your email to get the result: that email, the business you searched for, the score we produced, and the country the search was for, which comes from your connection and is country level only.
  • Your Google Business Profile data, once you verify with Google and confirm which listing is yours: the listing details Google holds (categories, description, hours, photos count, attributes), its Google Maps link, which tells us which listing it is, its performance statistics (how often it was seen, calls and clicks it received, and the search terms people used to find it), and, where your site is set up in Google Search Console, the search queries that bring people to your website. We use this to report on your own visibility, and to change your listing when you ask us to: from the Search room you can tap to put your website address, your phone number or a description onto the listing, or mark the listing open again. Blipzy changes none of those details unless you press that button, and we keep a record of what was sent and what Google answered. Replies to your reviews are separate: they go to Google when you or your team send or approve one, or on their own if you switch on automatic replies.
  • Files you choose to upload, such as a menu or price list. The file is sent to Anthropic to read the text out of it, and we keep only that text, attached to your business and deleted with it. We do not store the file itself.
  • Text you paste in to teach Blipzy, such as past reviews, messages or a document. It is sent to Anthropic, which turns it into short notes about your business (common questions, what customers like, or plain facts). We keep those notes, which can include a few short phrases quoted from it, not the text you pasted, and they are deleted with the business.
  • If you connect a Google Ads account: the account number you type in, and what a script running inside that account sends us each time it runs. That is:
    • the account's number, name, currency and time zone;
    • your campaigns, ad groups and conversion settings, including each campaign's name, status, daily budget, networks, targeting radius, whether it has an ad schedule, whether it runs dynamic search ads, and the website addresses (the domain only) its ads send people to, and how many ads, keywords and negative keywords each ad group holds;
    • spend, click, impression and conversion totals for the last 30 days, for the account, for each campaign and ad group, and split by network (Search, search partners, Display, YouTube);
    • the search terms that triggered your ads, as Google reports them, with their spend, clicks and conversions;
    • your keywords and their quality scores, with their clicks and spend, and how many negative keywords you have;
    • how your bidding is set, and how often your ads lost the auction on rank or on budget;
    • your call, sitelink and callout extras, with how often each was shown and used;
    • how many of your ads Google has disapproved;
    • daily totals for the last seven days: spend, clicks, conversions, taps on a call button and conversions from phone calls.
    It contains no click identifiers, no contact details and no link to any person who saw or clicked an ad. Search terms are what people typed into Google, as Google reports them in aggregate, and are not linked to anyone. Anyone on your business's Blipzy team can see what Blipzy found, including the search terms themselves, on your Ads page; only owners and managers can connect an account. It is not sent to any AI service. A short summary also goes in your summary email, through our email provider (Resend): the headline of what Blipzy found, whether it is the same as a week earlier, the first steps to fix it, how many settings changed between two readings, and the date of the reading, or that no reading has arrived. It never includes spend, search terms, campaign or keyword names, or account numbers, and it goes to the owner's email or to the report address set for that location. Blipzy only ever READS an ads account. Nothing in it can change a budget, place a bid, start a campaign or spend a penny.
    If the account you connect belongs to a client rather than to you, you are responsible for having their permission to share it with us, and we handle it as their information as well as yours.
  • Which Google listing your business is registered to. A business can be registered on Blipzy once, so when you sign up with a Google listing, or confirm one later, we record that listing's Google id against your business. If somebody else then tries to register the same business, they are told it is already on Blipzy, and nothing else about you or your business is shown to them.
  • If you ask to join a business that is already on Blipzy, we email its owner your name and email address (as your sign-in provider gives them to us), so they can decide whether to invite you. We do not tell you who the owner is, and you only hear more if they invite you or write back to you. We keep a record of the request (who asked, which business, and when) for 30 days.
  • Usage records needed to run the service, such as counts of AI requests for rate limiting.
  • Product analytics: how the app itself is used (pages visited, features clicked), collected via PostHog to improve Blipzy. We do not use advertising trackers.
  • If you subscribe to a paid plan, payments are processed by Stripe. We never see or store your card details. We keep your plan status and Stripe's reference numbers for your customer record, your subscriptions and your checkouts, so each payment is matched to your account. If a payment needs a person to look at it, such as a payment for a location that was already on your account, we keep a record of it with those reference numbers and email it to our team. That record is deleted with the business, except a refund we still owe you when you delete it, or a payment that reached us after you deleted it: that record, with the deleted business's id, Stripe's reference numbers and the amount, is kept with our billing records. When you delete a business or your account, we tell Stripe to stop its billing first; if that needs a person to check, our team is emailed the business's id and Stripe's reference numbers. Stripe keeps its own record of your subscriptions, invoices and payments, including the name and email on them, after the deletion, because tax law requires it. Blipzy can no longer show them to you, so keep the receipts Stripe emails you, or ask us for a copy.

How we use it

  • To show your reviews, comments and messages in one inbox.
  • To draft and, where you enable it, post replies in your brand voice.
  • To measure your visibility on search and AI engines and suggest improvements.
  • To make sure a business is registered on Blipzy only once. The record of which Google listing your business is registered to is used for three things: to refuse a second registration of the same business, to stop another account linking your listing or bringing in its reviews, and to find whose business it is when someone asks to join it, so their request reaches you as described below.
  • To tell which day it is where you are, from the time zone your browser reported at signup together with the country in your address: so your posts are counted on the day you made them, so we can ask about the public holidays where you are, and so a holiday notice ends when your day does.
  • To pass on a request to join a business. When someone asks to join yours, we email you their name and email address so you can decide whether to invite them. We use the request for nothing else, and inviting them is always your choice.
  • If you connect a Google Ads account, to check how that account measures results and where its money goes, and to show you what we found and what to fix first. You make any change yourself, in Google Ads. If your Google Ads account's average cost per click can be worked out from what it sends, Blipzy may offer it as the rate on the Business You Didn't Pay For screen. It is only used if you tap to fill it in and then save it. Blipzy keeps a daily record of your ad account's totals so it can show you the days before and after a change you make.
  • To send what you have switched on in your name: automatic replies, your automation rules and review request reminders. One switch, Pause Blipzy in Settings, then Automations, stops all of it, along with the drafts Blipzy writes on its own and the daily work it picks for you, until you resume. New reviews and messages still arrive while it is paused, and anything you send yourself still goes out. We record when you pause and resume, and when each message arrives, so that reviews, messages and comments that came in while Blipzy was paused are never answered automatically: after you resume, any reply Blipzy writes for one of them waits in your inbox as a draft for you to send.
  • To email you the reports you asked for, and instant alerts for anything that needs you. Alerts go to the owner's email, or to the report address set for that location, and you can switch alert emails off in Settings, then Automations. A notice about a payment on your account, such as a payment for a location that was already on your account, is still sent, to the owner's account email, when alert emails are off, because it is about your money and not your inbox. If you ask for the Google Ads setup steps by email, Blipzy sends them to your own account email; that email holds no script and no key. Browser notifications are sent only if you turn them on, and you can turn them off in your browser at any time. When you turn them on, your browser gives us a delivery address for that browser, which we store so we can reach it. Sending a notification means handing it to whoever runs that address, which is Apple, Google or Mozilla depending on the browser you use. We delete the address when you turn notifications off.
  • To learn your reply style: replies you post or approve are analyzed to build a private, per-business style profile so future drafts sound like you. This profile is used only for your business and is deleted with it.
  • To publish your public profile page: if you share your Blipzy page, it displays your business details and customer reviews that are already public on the platforms they were posted to. It never shows private messages.
  • To get in touch about Blipzy if you ran a free scorecard and left your email. The report itself is shown on the page straight away, not emailed. Tell us and we will remove your address.
We do not sell personal information, and we do not use your data to advertise to anyone.

Why we are allowed to use it

Where privacy laws such as the GDPR ask for a legal basis, we rely on: performing our contract with you (to provide the features you signed up for); your consent (for optional things like product analytics, which you can decline); our legitimate interests (to keep Blipzy secure, prevent abuse, and improve the product), kept in balance with your rights; and, where it applies, meeting a legal obligation. You can withdraw a consent at any time without affecting what we did before.

AI processing

Review, comment and message text is processed by Anthropic's Claude models to analyze sentiment and draft replies, except direct messages to a business Blipzy treats as a health practice, which Blipzy does not send to Anthropic. Text you paste in yourself to teach Blipzy is sent to Anthropic too, so a health practice should not paste patient messages there. Content sent through the Anthropic API is not used by Anthropic to train models.

Separately, the visibility tools ask public AI assistants what they recommend, so we can report on how you show up in AI search. Those questions go to Perplexity and Google Gemini, and to OpenAI when that check is switched on. Each question is either built from your category or specialty and your city ("What are the best bakeries in Guelph?"), or is one you type yourself in the AI answer tester, which may name your business. They never contain a customer's review, message or contact details. Each of those assistants applies its own terms and its own retention to what it receives, which may differ from Anthropic's.

Our Gemini access is on Google's free tier. Under Google's terms for that tier, Google may use the questions we send and the answers it gives to improve its products, and human reviewers at Google may read them. That is why those questions carry only the wording above and never anything about your customers.

AI drafts are suggestions, not automated decisions

Blipzy uses AI to draft and score content, not to make decisions that have a legal or similarly significant effect on any person. You control whether a reply posts automatically or waits for your approval, and you can keep any topic in human hands. Blipzy also looks, with its own software and no extra AI call, for words suggesting that a review, comment or message is about an injury or illness, a legal threat, discrimination or harassment, the police or an inspector, or a payment dispute. When it finds them, it does not reply on its own: any reply it writes waits for the business to read first. It records only that the reply was held for a serious topic, not which one. Because it reads words, it can miss a message or hold a harmless one. For a business that looks like a health practice, Blipzy tells its AI not to mention a visit, treatment or appointment in a public reply, and holds one in which it finds such a mention for the business to change. Blipzy does not send direct messages to a health practice to AI: they are stored and wait for the business to read. Text the business pastes in itself to teach Blipzy does go to AI, so it should not paste patient messages. We do not use AI to profile the people who contact you, whether for advertising or for eligibility decisions. When Blipzy sends a message or posts a reply on its own, without you pressing send, it ends with a line saying so. A reply written by Blipzy's AI ends with a line that says it was written by AI and sent automatically. A message from an automation rule you set up, which sends your own words as you wrote them, with the customer's name or your business name filled in where you used them, ends with a line that says it was sent automatically. You choose the wording: "Written and sent automatically with AI" and "Sent automatically", or "Automated reply, written by AI" and "Automated reply". The first pair is used until you choose. The line cannot be removed. This covers Instagram and Facebook direct messages, private replies to comments, public replies to comments and Google review replies. For each automatic reply we record whether AI or one of your rules wrote it, and which wording its line went out in, so your inbox can show it. Replies you write, or approve and send yourself from the inbox, carry no line. The line is added as the message is sent, so it is not part of the reply saved in your inbox. Your inbox shows it under an automatic reply when we recorded which line that reply carried, starting with replies sent on October 1, 2026.

Service providers

We use a small set of processors to run Blipzy: Supabase (database and authentication), Vercel (hosting), Anthropic (AI drafting and analysis), Perplexity, Google Gemini and, when that check is switched on, OpenAI (AI visibility checks only, as described above), Resend (email delivery), Stripe (payments), PostHog (product analytics), Sentry (error monitoring, so we can find and fix problems), UptimeRobot (checking the site is up), and search data providers (Serper, SerpApi) for public listing data. Those two receive your business name, its category and its area, to find your listing and the businesses near you. SerpApi also receives your listing's Google id, to read the public reviews on it and whether your business has replied to them. Blipzy does not track your ranking for search terms, so it sends them no search terms of yours. Data we read from Google and Meta accounts you connect is accessed through their official APIs under their terms, which for booking means Google Calendar's free and busy service and nothing else on your calendar.

If you give Blipzy a webhook address of your own (in Settings, under Connections), Blipzy posts each Instagram and Facebook DM and comment to that address as it arrives, and posts the reply again when Blipzy answers one by itself. Each post carries the sender's name and the text they wrote. Reviews are not sent to it. That destination is chosen by you, it is not one of our processors, and whatever happens to the data once it arrives there is governed by whoever runs it. Remove the address and the posts stop immediately.

A small weather touch

The app can tint its background to match your local sky. To do that it uses the approximate, city-level location our hosting provider derives from your connection (never GPS, never a browser permission prompt) to look up the current weather from Open-Meteo, a public weather service. We do not store your location or send anything that identifies you to the weather service, and if the lookup fails the app simply uses its default look.

Cookies and Do Not Track

Blipzy sets a small number of cookies: to keep you signed in, to remember which of your businesses is active, and, during sign-in to a platform, to protect that connection from being hijacked. If you arrive through someone's referral link we also set a cookie for 30 days so their referral is credited if you sign up; you can clear it in your browser at any time. Product analytics stays off until you accept it, and you can decline. We do not use third-party advertising cookies.

Once you are signed in, your business name, your email and your account's id are also kept in your own browser's local storage so the sign-in screen can greet you next time. That stays on your device. We clear it when you delete your account, when you delete the business it names, when you press "Not you?" on the sign-in screen, and whenever we check and find the account no longer exists. Clearing your browser data removes it too.

Your browser also keeps a few small settings of ours in local storage, on your device only: your answer to the analytics question, and interface preferences such as which cards on Home you have already seen or put off today (the "bz-today" entry, which holds names of cards, never content, and resets each day), whether you chose light or dark in this browser ("bz-theme"), and whether you have finished the connection walkthrough. None of it is sent to us.

Because there is no common standard for browser Do Not Track signals, we do not respond to them, but our analytics choice above gives you the same control.

Security

Data is encrypted in transit and encrypted at rest by our database provider, and access is scoped per business at the database level (row-level security). The access tokens Blipzy holds for the platforms you connect are stored in our database, in tables that no browser session can read: they are reachable only by our server. Our own service keys are held in our hosting provider's encrypted configuration and are never in the code. Replies can only be sent for the business that connected the account.

Where your data is processed

Blipzy runs on providers located in the United States and Canada, so your data is processed and stored there. When information moves across borders, we rely on our providers' safeguards for international transfers (such as standard contractual clauses where they apply) to keep it protected to the standard of this policy.

How long we keep it

  • Account and business information: while your account is active, then deleted when you close it.
  • Reviews, messages and drafts: while the related business exists, and deleted when you delete the business or close your account. Disconnecting a platform stops us receiving anything further from it and deletes the access token, but it does not delete what was already imported. That is deliberate: a disconnection is often temporary, and Instagram does not let us re-read messages from before a reconnection, so deleting them would lose them for good. If you want the imported content gone, delete the business or your account, which does remove all of it. A deletion request you make through Instagram or Facebook also removes what was imported from that account.
  • Your private voice profile: only for your business, and deleted with it.
  • Which Instagram or Facebook account was connected to a business (the account id, never a token): kept after you disconnect it, so a deletion request you make through Instagram or Facebook can still find and remove what was imported. Removed once that request is carried out, or with the business.
  • Google Ads readings: kept for 14 days, except the most recent one, which is kept while the business exists so the ads check still has something to show. All of them, and the account number you gave us, are deleted when you delete the business or close your account. To stop new readings, delete the script inside Google Ads (Tools, then Bulk actions, then Scripts): nothing further reaches us from that moment. Connecting again in Blipzy issues a new script, and the old one stops working.
  • Google Ads daily totals (spend, clicks, conversions, taps on a call button and conversions from phone calls, one line per day): kept for 400 days and deleted with your business.
  • What we read from your website: kept while the business exists, replaced whenever we read the site again, and cleared straight away when you press Forget what we read in your Playbook.
  • Review invitation records: kept while the business exists, so an invitation is not sent twice. Unsubscribe records are kept even after the rest is deleted, in a separate list with no link to the business or the account, because forgetting an unsubscribe would mean contacting someone who asked us not to. That list holds the address and nothing else about you.
  • Requests to stop being messaged on Instagram or Facebook: kept indefinitely and on purpose, for the same reason as the unsubscribe list above. When somebody tells a business to stop, we keep the platform id that sent that message so we can refuse to message them again. It is that id and nothing else, it is not linked to any other record about them, and it survives the business being deleted, because an opt-out that a deletion can erase is not an opt-out.
  • Deletion requests received from Instagram or Facebook: we keep a record of the request and the platform id it names, so we can show the platform that it was carried out. Kept indefinitely for the same reason.
  • The postal address a business gives us for its marketing emails: kept while the business exists and deleted with it. Anti-spam law in Canada and the United States requires a real sender address on commercial email, so it appears in the footer of emails sent on that business's behalf.
  • A record that a business has had its free trial: a marker for the business (its Google listing id, or its name and address) and the id of the account that claimed it. Kept after the account is deleted, so that one business gets one free trial. While a business with no Google listing is on Blipzy, the same record is also how we recognize someone else signing up that business again, and how we find its owner when that person asks to join. It holds nothing else about you.
  • Which Google listing a business is registered to: kept while the business exists, and deleted with it, which frees the listing to be registered again.
  • A request to join a business (the name and email address of the person who asked, which business, and when): kept for 30 days, then deleted. Deleted sooner if that person closes their account or the business is deleted.
  • Scorecard leads (an email entered on our website without an account): kept for up to 24 months, then deleted. To have one removed sooner, email us at the address below.
  • Billing records (your subscriptions, invoices and payments, held by Stripe, and our own record of a refund we owe you after a business is deleted, with its id and Stripe's reference numbers): kept after you delete a business or your account for as long as tax law requires, which in Canada is six years after the end of the tax year they relate to.
  • Other limited records we must keep for legal or security reasons: for as long as the law requires, then deleted.
  • Routine backups: cycled out on a rolling basis after deletion.

Retention and deletion

You can delete individual businesses, or your whole account and its data, at any time from inside Blipzy; see data deletion instructions. Disconnecting a platform stops the flow of new data and deletes our access token; deleting the business or your account is what removes the content already imported.

Your privacy rights

Depending on where you live, you may have the right to access the personal information we hold about you, to correct it, to delete it, to receive a copy in a portable form, to limit or object to certain processing, and to withdraw a consent. Much of this you can do yourself in the app; for anything else, email privacy@thebuddylabs.com and we will respond within the time the law allows. You do not need a Blipzy account to exercise any of this. If a business you dealt with uses Blipzy and we hold your review, your comment, your message or your email address, write to the same address with the name of the business and roughly when you contacted them. How to ask. We will not treat you differently for exercising these rights. If you are in Canada you may also contact the Office of the Privacy Commissioner, and in the UK or EU your local data protection authority, if you are not satisfied with our response.

For California residents

In the past year we have collected the categories described under "Information we collect" above (identifiers, business and contact details, connected-platform content, and usage and analytics data). We do not sell or share your personal information as those terms are used under California law, and we have not in the past year. You have the right to know what we collect, to delete it, to correct it, and to opt out of sale or sharing (which we do not do), and we will not discriminate against you for exercising them. You may use an authorized agent to make a request. To exercise these rights, email privacy@thebuddylabs.com.

Meta and Google platform data

Data received from Meta (Facebook and Instagram) and Google is used only to provide the features above for the business that connected it, and is never sold. Disconnecting stops the flow and deletes our access token, so we can neither receive nor send anything more. Content already imported is deleted when the business or the account is deleted. If you ask Instagram or Facebook to delete your data, they forward the request to us, and we delete the connection, its access token and the messages and comments imported from that account, then give you a code to check that it finished. All of this is in line with the Meta Platform Terms.

Blipzy's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to train AI models.

Children

Blipzy is a tool for businesses and is not directed at children under 16. We do not knowingly collect data from children.

If there is a data breach

We work to protect your data, but if a breach happens that affects your personal information, we will notify you and the relevant authorities as required by the laws that apply, without undue delay, and tell you what we know and what we are doing about it.

Changes to this policy

If this policy changes in a way that matters, we will update the date above and note the change on this page before it takes effect.

Who we are

Blipzy is a product of The Buddy Labs AI Inc., incorporated in Ontario, Canada. Reach us by email at the address below; we will give you a postal address on request.

Contact

Questions or requests: privacy@thebuddylabs.com.