Draft, under legal reviewLast updated 15 November 2026

Privacy Policy

Bwip answers comments on a creator’s Instagram posts with a private message, and lets creators make small pages to share. This policy says what we keep about each person involved, why, for how long, and how to have it removed.

Who we are

Bwip is a service of XUSLABS LTD, a company registered in the United Kingdom, company number 16706799, registered address 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. In this policy “we” and “us” mean XUSLABS LTD.

For privacy questions and requests, write to privacy@bwip.app.

The short version

  • Bwip deals with three groups of people: creators who have an account, visitors who open a creator’s page, and people who comment or message on a creator’s Instagram account.
  • About visitors we count what happens on a page, per day, without telling visitors apart. The only thing we store about a visitor is an email address they choose to type in to open a locked part of a page.
  • About people who receive a private message from a creator’s Instagram account we keep their Instagram id, username and name, and how far they got in the creator’s campaign, so the creator can see who received it. We keep no message text. To avoid messaging someone twice we also keep scrambled ids (keyed hashes) that delete themselves within 8 days.
  • We do not sell personal data, we do not show advertising, and Bwip has no analytics or advertising trackers.
  • Instagram access tokens are stored encrypted. Files are kept in a private store and reach visitors only through Bwip.

Creators with a Bwip account

What we collect

  • Account: your email address, your name if you give one, whether you have confirmed your email address, and when the account was made. Your password is stored only as a one-way hash (scrypt), never as you typed it.
  • Google sign-in, where offered: if you sign in with Google, Google sends us your name, email address and profile picture, and sign-in tokens that we keep with your account.
  • Sessions: for each signed-in device, a session record with the IP address and browser description (user agent) it was opened from.
  • Workspaces and team: the workspaces you belong to, your role in each, its name and time zone, and invitation links you create (we store only a hash of each link’s secret).
  • Connected Instagram account: its Instagram id, username, display name, a copy of its profile picture, and an access token that lets Bwip act for the account (stored encrypted). Also your campaigns: keywords, which posts they apply to, links, and the messages you wrote.
  • Pages and files: what you put on your pages, and the files you upload (pictures, videos, audio, PDF, ZIP and text files), with their names, types and sizes.
  • Usage counts: how many people your workspace reached and how many emails it collected each month, which is what plan limits are counted from.
  • Email we send you: to confirm your address and to reset your password. We do not send marketing email.

Why, and on what legal basis

  • To provide the service you signed up for: your account, sign-in, pages, files, campaigns, and sending messages from your Instagram account. Basis: performance of our contract with you.
  • To keep the service secure and stop abuse: session records, rate limits, checking passwords against a list of common ones, confirming email addresses before pages can be published, files uploaded, people invited or Instagram connected. Basis: our legitimate interest in a safe service.
  • To meet legal obligations, such as keeping records we are required to keep. Basis: legal obligation.

How long we keep it

  • Your account, workspaces, pages, files, campaigns and connected Instagram accounts: until you delete them or delete your account.
  • A confirm-your-address link works for 24 hours, a password-reset link for one hour, an invitation link for 7 days.
  • A session lasts 7 days from your last visit, and ends when you sign out. Records of sessions that ran out on their own are not yet cleaned up automatically; they are removed when your account is deleted.
  • Monthly usage counts and the daily numbers on your pages: until your workspace is deleted.
  • A file you remove from a page but do not delete stays in storage, and counts against your plan, until you delete it or your workspace. Uploads that never finished are cleared after an hour.
  • Backups held by our database provider: [BACKUP RETENTION].

Visitors of a creator’s page

A creator’s page lives at an address such as bwip.app/p/name. You do not need an account to open it.

What we collect

  • Anonymous counts. We add up, per page and per day, how many times it was opened, whether an open came from a link sent in a direct message or elsewhere, how many prompts were copied and files downloaded, how far people got through its steps, and how often the email request was shown. These are totals. No visitor is identified, and no IP address, device id or cookie is stored with them.
  • An email address, only if you type one in. A creator can lock parts of a page until a visitor leaves their email address. If you do, we store that address with the page’s title, when you left it, whether you arrived from a direct-message link, and whether you went on to take a file or a prompt from the page. If the creator’s plan has no room left for emails that month, you still get in, and your address is kept on hold: the creator does not see it, and it is not exported, until there is room again (a new month or a bigger plan). Each workspace can hold up to five times its monthly allowance of emails; past that you still get in, but your address is not stored and your browser is given a pass with no email behind it.
  • Your IP address, briefly, to stop abuse. To limit how often one address can submit the email form or send page events, we count tries per address (an IPv6 address is counted on its first 64 bits, its /64, since one household has a whole range of them). The address itself is not stored: we keep a keyed hash of it, and delete those counters about a day after their time window ends. When the challenge described below is switched on, Cloudflare also receives your address and signals from your browser. Our hosting provider also sees your IP address when it delivers the page, as any web host does, and may keep it in its own logs.

Why, and on what legal basis

  • The counts show the creator how their page is doing. Basis: the creator’s legitimate interest, with Bwip processing on the creator’s behalf; nothing in the counts identifies you.
  • The email address is collected for the creator, who decides what to do with it. The creator is responsible for telling you why they want it and for having a lawful basis, and Bwip stores it for them. The form says the address goes to that creator only.
  • The hashed rate-limit counters protect pages from being flooded. Basis: our legitimate interest in a safe service.
  • Where the challenge is switched on, Cloudflare Turnstile checks that a request comes from a person and not a robot. Basis: our legitimate interest in a safe service.

How long we keep it

  • Anonymous daily counts: until the creator deletes the page or their workspace.
  • Your email address: until the creator removes it, the creator’s workspace is deleted, or you ask for it to be removed (see How to delete data). If the creator deletes the page, the address stays in the creator’s list with the page’s title until it is removed.
  • An address on hold: until it is released to the creator’s list, or dropped if it was never released, which happens when the second calendar month after the one you left it in begins (so one to two months, about a month and a half on average).
  • Rate-limit counters: about a day.
  • On your own device: see Cookies and browser storage.

People who comment or message on Instagram

When you comment on a post of a creator who uses Bwip, and your comment contains a word the creator chose, Bwip sends you one private message from the creator’s account. If you then write back or tap a button in that conversation, Bwip answers you there. Bwip only ever messages people who commented or wrote first.

What we receive and what we keep

  • What Instagram sends us: the comment or message (its id, its text, the time) and your Instagram user id and username. To answer you, Bwip may also ask Instagram for your name and whether you follow the creator’s account, when the creator only gives the link to followers.
  • What we do with it: we check the text for the creator’s keyword, greet you by your name or username, and decide which message to send. This happens in the moment. We do not store the text of your comment or messages.
  • What we keep, per connected account: once Bwip has sent you a message, we keep a contact record for you under the creator’s Instagram account: your Instagram-scoped id, your username and your name (when Instagram gave them to us), which campaign you are in, how far you got (asked to follow, waiting for the follow, or done), whether you follow the account (when it was checked), and the first and last time Bwip dealt with you. The creator sees this list in Bwip.
  • To avoid messaging you twice, we also keep the id of your comment, of your messages and of your Instagram account, each only as a keyed hash that cannot be turned back into the id without our secret key, together with which campaign you are in and which step you reached. These records delete themselves: the step you reached after 7 days, the rest after 8 days (just longer than the 7 days Instagram allows for a reply to a comment).
  • To count people per month, we keep one keyed hash per person per month, made for the creator’s workspace, so you are counted once however many times you write. It cannot be linked to you without our secret key, or across workspaces. It is kept until the workspace is deleted.
  • Counts: the creator sees totals per campaign (comments answered, people asked to follow, links sent, messages that could not be delivered) and how many people the workspace reached each month. These totals do not identify anyone; per-campaign totals are kept for 400 days.
  • The conversation itself stays in Instagram, in the creator’s inbox, under Instagram’s rules. When the creator looks at conversations in Bwip, they are read from Instagram at that moment, not copied into our database.

Why, and on what legal basis

Bwip does this for the creator, who decides which comments are answered and what the messages say. The creator is the controller of this processing and Bwip is their processor. The creator relies on their own legitimate interest in answering people who asked for something under their post. We keep the contact record so the creator can see who received a message and how far they got, and the monthly hash so that people can be counted against the plan.

How long we keep it

The contact record: until the creator disconnects the Instagram account or deletes their Bwip account, or until you ask for it to be removed (see How to delete data). The hashed de-duplication records: at most 8 days. The monthly counting hash: until the creator’s workspace is deleted. Per-campaign totals: 400 days. We do not keep the text of your comments or messages.

Information we receive from Instagram (Meta)

Bwip uses Instagram’s official API. When a creator connects their professional Instagram account, Meta asks them to grant Bwip three permissions. This is what each one is for:

  • Instagram basic (instagram_basic): to read the connected account’s id, username, name and profile picture, and its list of posts, so the creator can see which account is connected and choose the posts a keyword applies to.
  • Instagram manage comments (instagram_manage_comments): to read new comments on the creator’s posts, check the campaign’s comment trigger, and, if the creator turns it on, post a short public reply under a matching comment.
  • Instagram manage messages (instagram_manage_messages): to send the private reply to the person who commented, to read and answer their replies and button taps in that conversation, to check whether they follow the account when the creator asks for that, and to show the creator their conversations inside Bwip.

Instagram also tells Bwip, as they happen, about new comments and messages on connected accounts (webhooks), so answers go out in seconds.

Data obtained through Meta’s platform is used only to provide the features above to the creator who connected the account. It is not sold, not used for advertising or to build advertising profiles, and not shared with anyone except the providers listed in Providers we use, who process it only to run Bwip.

Who decides what happens to the data

  • Creator accounts (account, sign-in, workspace, billing when it exists): XUSLABS LTD is the controller.
  • Emails left on a creator’s page (including those on hold), the contact list and Instagram conversations handled by Bwip for a creator: the creator is the controller and XUSLABS LTD processes the data on their behalf, following their settings. Questions about how a creator uses your data are best sent to that creator; we will help them answer.
  • Security records (hashed rate-limit counters, session records, the challenge check): XUSLABS LTD is the controller.

Providers we use and where data is

ProviderWhat it does for BwipWhere
Vercel Inc.Runs the Bwip website and app, and stores uploaded files in a private file store (Vercel Blob).Functions and the file store in Frankfurt, Germany. Pages are delivered through Vercel’s worldwide network.
Supabase Inc.Hosts our Postgres database: accounts, pages, collected emails (including those on hold), Instagram contacts and the Instagram engine’s working data, counts.Frankfurt, Germany.
ResendSends our emails to creators (confirm your address, reset your password). It receives the recipient’s address and the email.Sending region: Tokyo, Japan.
Meta Platforms (Instagram)The Instagram API through which Bwip reads comments and sends messages for connected accounts.Under Meta’s own terms and privacy policy.
GoogleOnly if you choose to sign in with Google, where offered.Under Google’s own terms and privacy policy.
Cloudflare, Inc. (Turnstile)Used when the challenge is switched on: a check that a request comes from a person, on sign-up, password reset, sign-in after failed tries, and pages that ask for an email. Cloudflare’s script runs in your browser and reads signals from it; our server sends Cloudflare the challenge answer and your IP address to check it.Under Cloudflare’s own terms and privacy policy; its network is worldwide.

Payments are not taken today: every account is on the Free plan. When paid plans open, payments will be handled by a payment provider, and this policy will name it before then.

International transfers

Our database and file store are in Germany. Some providers (Vercel, Supabase, Cloudflare) are companies based in the United States, and email is sent from Japan, so personal data can be reached from or sent to countries outside the UK and the European Economic Area. Where that happens we rely on [TRANSFER SAFEGUARDS].

Cookies and browser storage

Bwip sets only the cookies it needs to work, and keeps a few preferences in your browser. There are no analytics, advertising or social-media cookies or trackers.

Cookies

NamePurposeLifetime
__Secure-better-auth.session_tokenKeeps a creator signed in. Holds a random session code.7 days from your last visit; removed when you sign out.
bwip.wsRemembers which of your workspaces you last chose.1 year.
bwip_u_<page>Set on a visitor’s browser after they leave an email on a page, so the page opens again without asking. Holds a signed code for that one page, not the email address.1 year. It stops working if the creator removes the email. It works the same when the address is on hold. If no address could be stored (the creator’s held emails are at their limit), it is a pass for that page with no email behind it.

Cloudflare Turnstile, when the challenge is switched on. The check loads a script from Cloudflare (challenges.cloudflare.com) on sign-up, password reset, sign-in after failed tries, and pages that ask for an email. Cloudflare decides what that script stores or reads in your browser to tell people from robots; Bwip does not read it. See Cloudflare’s own policy.

Browser storage

These stay on your device and are not sent to us.

NamePurposeLifetime
bwip.themeYour choice of day or night colours.Until you clear it.
bwip.sideWhether the app’s sidebar is open or closed.Until you clear it.
bwip.p.<page>.doneThe steps you ticked on a page, so they stay ticked when you come back.Until you clear it.
bwip.p.<page>.seen, bwip.p.<page>.askedSo one visit counts once in the page’s numbers, even if you reload.Until the tab is closed (session storage).

How we protect data

  • Instagram access tokens are encrypted with AES-256-GCM before they are stored, so the database never holds a usable token.
  • The ids used to avoid messaging someone twice (comment, message and account ids) are kept only as keyed hashes (HMAC-SHA-256), and expire within 8 days. People are counted per month only as keyed hashes.
  • Passwords are stored as scrypt hashes. A new password is checked on our own server against a built-in list of common passwords, and never sent to another service. Invitation links and rate-limit keys (addresses and emails) are stored only as hashes.
  • Uploaded files sit in a private store with no public address. Every download goes through Bwip, which checks whether the visitor may have it (for example, that they unlocked that part of the page). Uploaded files are checked against their declared type and are never run as web pages.
  • Every table in our database has row level security switched on with no access rules, which closes it to the database provider’s public data API; only Bwip’s server can read it.
  • Connections use HTTPS, sign-in cookies cannot be read by page scripts, and sign-in, sign-up, password reset, uploads and page forms are rate limited. Failed sign-in attempts are counted by address and by email.

No system is perfectly secure. If a breach puts your data at risk, we will tell you and the regulator where the law requires it.

How to delete data

If you have a Bwip account

  • Delete single pages, files, campaigns and collected emails in the app at any time.
  • Delete your whole account in Settings → Delete account. This removes your account, sign-in records, the workspaces you own with everything in them (pages, files and their stored bytes, collected emails, campaigns, connected Instagram accounts and their tokens), and your place in other workspaces. If a workspace you own still has other members, they must leave or take it over first.
  • Or write to privacy@bwip.app from the address on your account.

If you connected an Instagram account

You can disconnect the account in Bwip, which removes it and everything kept for it, including its contact list. You can also remove Bwip in Instagram’s settings, where Instagram lists the apps and websites you have connected. Bwip then stops sending from that account. If you also ask Instagram to delete your data, Meta passes the request to us, we delete the connected account, its token, its campaigns and its contact list, and you get a confirmation code you can check at bwip.app/deletion/<code>.

If you left your email on a creator’s page

Ask the creator: they can remove it from their list in Bwip at once, and removing it also closes the parts of the page it opened. Or write to privacy@bwip.app with the address and, if you know it, the page; we will pass the request to the creator and help them carry it out.

If you commented or wrote to a creator on Instagram

If Bwip sent you a message, the creator’s contact list holds your Instagram id, username and name. Ask the creator to remove you, or write to privacy@bwip.app with your Instagram username and the account you wrote to; we will pass it to the creator and help them carry it out. The hashed de-duplication records delete themselves within 8 days. The messages are in Instagram and the creator’s inbox; ask the creator or Instagram about those.

Your rights

Under UK and EU data protection law you can ask us to:

  • give you a copy of the personal data we hold about you (access);
  • correct data that is wrong (correction);
  • delete it (erasure);
  • stop or limit using it, where we rely on legitimate interests (objection, restriction);
  • give you data you gave us in a machine-readable form (portability).

Write to privacy@bwip.app. We may need to confirm it is you. We answer within one month. Where a creator is the controller (emails on their page, their Instagram conversations), we will pass your request to them and help them answer it.

You can complain to the UK Information Commissioner’s Office (ico.org.uk), or to the data protection authority where you live or work. We would like the chance to sort it out first.

Children

Bwip is not for anyone under 16. Do not create an account if you are under 16. Instagram’s own age rules also apply to anyone using Instagram. If you believe a child has given us personal data, write to us and we will delete it.

Changes to this policy

When we change what we collect or how we use it, we update this page and the date at the top. If a change matters for creators, we will also tell them by email or in the app before it takes effect.

Contact

XUSLABS LTD, 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. Privacy questions and requests: privacy@bwip.app. Everything else: legal@bwip.app. See also our Terms of Service.