Last updated October 20, 2026

Privacy Policy

Blipit is run by Louward Labs FZC LLC. This page says exactly what we hold, why we hold it, who else touches it, and how long it stays. It is written to be read, not to be survived.

Two kinds of data

Your account data is about you: it is ours to look after. Your event data is what your applications send us when they break: it is yours, and we process it on your instructions. If your errors contain other people's personal data, you are the controller of it and we are your processor.

What we collect

When you create an account

Your email address. If you sign in with Google, GitHub or Microsoft, we also receive the account identifier they give us, your name and, if they provide one, your profile picture, and we check with them that the email is verified. We never receive your password from them, and we never ask you for one.

We record sign-in activity to keep the account safe: the IP address and browser user agent of each session, when it was last used, and the IP that requested each sign-in link.

When your applications report an error

Whatever the report contains. Typically: the error type and message, the stack trace and the lines of your code around it, the URL or job that was running, the release and environment, the browser or server version, the breadcrumbs leading up to it, and any context your application chose to attach. We do not store the IP address an error report came from. Login-attempt reports for security monitoring carry the username, IP address and country your application sends.

Before anything is stored, we blank out values that look like secrets: fields named like passwords, tokens, keys, cookies or sessions, Authorization headers, bearer tokens, and card numbers. This is a safety net, not a filter for personal data: if your application puts a customer's name, email or address into an error message, it still arrives here. Scrub personal data before it leaves your systems.

Other data your applications send

Your applications can also send logs, performance traces, user feedback (the name, email and message the person typed), release health sessions and web vitals if you use them. Websites with the browser SDK send session replays (recordings of page changes) according to each project's Session replay setting: by default the browser keeps only the last minute and uploads it with an error or a bug report; a project owner can instead record a share of all visits or turn replay off. Typed values, page text and media are masked in the browser before anything is sent; field names, column headers, tabs, menus and buttons stay readable unless the project owner turns that off, so the recording shows which screen and button were used without showing what was typed or the records on screen. For web vitals we derive the visitor's country from the IP address and do not keep the address.

Session replay in mobile apps

Android apps with the Blipit Android SDK can also send session replays, but only after the app has asked the person and they agreed: until the app records that consent nothing is captured, and withdrawing it stops recording at once and discards what was kept on the device. A recording is about one frame per second of the app's own screens, masked on the device before anything is stored, so text, images, typed input and web content become solid blocks; it also contains taps, screen changes, the device model, operating system and app version. It never captures other apps, the system screens or anything while the app is in the background, and it does not use accessibility services or system screen capture. The video segments are stored in Cloudflare R2 in the Asia-Pacific region, follow the project's Session replay setting and the plan's replay retention of 7 to 30 days, and are deleted with the replay. For these recordings, as for all data your applications send, you are the controller and we act as your processor.

When you connect an Odoo instance

A one-way hash of your database identifier. It is not reversible and tells us nothing about your database contents. It exists so one key cannot be used by two installations, and so we can tell your production instance from your staging one.

If you use Odoo Workflows, the module also sends counts of the business steps your users run and, when a step fails, business document identifiers (record ids of the Odoo documents a failed step touched), the Odoo user id and the company id. Workflow data never includes names, and includes amounts only if you turn on Value on hold: then a failed step sends the total and currency of the document it was working on. The message Odoo showed the user stays in your Odoo database; the occasional sample of a blocked step is sent like an error report, with numbers and quoted values removed. If you use Odoo performance, the module sends how long your users' actions take, how many database queries they run, the text of those queries with every value removed, and the file and line of code that runs them; it never sends record values.

If you joined the waitlist

Before sign-up opened, we kept your email address and which part of the site you signed up from. Nothing else.

If you subscribe to product updates

We keep your email address, the language of the site you signed up from, where on the site you signed up, a one-way hash of your IP address, when you signed up, when you confirmed and, if you leave, when you unsubscribed. You are only subscribed after you click the confirmation link we email you (double opt-in). Every newsletter email has a one-click unsubscribe link, and you can also write to privacy@blipit.io. We use the address only to send these updates.

If you have a Blipit account, we also send these product updates to your account email, in your account's language. Turn off Product updates in Settings or use the unsubscribe link in any update; your choice is kept with your account and we do not email you again until you turn it back on.

When you visit our website

We count page views on blipit.io and our dashboard ourselves, with no third-party analytics: the page, the referring site, your browser's user agent and your country. Your country is looked up from your IP address, which is not stored. To count unique visitors without storing anything in your browser, we combine your IP address and user agent with a random value that changes every day and keep only the resulting one-way hash; the day's value is then deleted, so visits on different days cannot be linked. Nothing is shared with anyone else.

What we do with it

We use account data to sign you in, to show you your workspace, to send the alerts you asked for, and to contact you about the service. We use event data to group errors into issues, to symbolicate stack traces, to count usage against your plan, and to put the alert in your inbox. We use logs and IP addresses to keep the service up and to stop abuse.

We do not sell your data. We do not share it with advertisers. We do not use your event data to train models, and we do not read it except when you ask us to help with a support request or when we must to keep the service running.

Where it lives

Blipit runs in Singapore. Our database is Neon on AWS Singapore, our ingestion and processing run on Fly.io in Singapore, and our queue is Upstash. The website and dashboard are served by Vercel, DNS goes through Cloudflare, and alert email is sent through Microsoft 365. Google, GitHub and Microsoft receive a sign-in request only when you choose to sign in with them. Payments are handled by Stripe, which receives your workspace name and the owner's email. When someone in your workspace runs an AI fix on an issue, that issue's details (the error, stack trace, breadcrumbs and request address, without the query string, after secrets are blanked out) are sent to Anthropic's API in the United States to write the analysis. If the project is connected to a GitHub repository through the Blipit.io GitHub App, the source files named in the stack trace and the files they import are read from GitHub at that moment and sent with it; files that look like secrets are never read, secret-looking values are removed, and Blipit keeps only the file paths and the commit. Opening a pull request from an AI fix sends the proposed change to GitHub. Nothing is sent to Anthropic unless an AI fix is run. When SMS or phone-call alerts are switched on for on-call, Twilio in the United States receives the phone numbers and the incident title. If you connect a GitHub repository for release commits, we call GitHub's API with your token and keep the commit authors' names and emails it returns. The sign-up and product-updates forms are checked by Cloudflare Turnstile, which sees your IP address and browser details to tell people from bots; on blipit.io it only loads when you start typing your email.

Bug reports: screenshots, screen recordings (with microphone audio when the reporter turns it on) and attached images or videos are stored in Cloudflare R2 in the Asia-Pacific region. They follow your plan's retention and storage limits and are deleted from R2 when the report is deleted.

Those companies are our processors. They hold data only to provide their part of the service and are not allowed to use it for anything else. This means your data may be transferred outside the country you are in, including from the UAE to Singapore and the United States. Those transfers rely on the safeguards the UAE PDPL allows (contractual commitments from these processors, and transfers needed to provide the service you asked for), and for the EU and UK on standard contractual clauses with the providers named above.

When you connect Slack, Microsoft Teams, Jira, Linear or a webhook, we send issue details to the destination you set up: the title, project, environment, release and level, plus stack frames for Jira and Linear tickets and, for security alerts, the username, IP address and country. You choose those services, and they act under your own agreements with them.

How long we keep it

• Error events: for your plan's retention period — 7 or 30 days — then deleted.
• Issue summaries (the grouped record, its counts and its status) for as long as your workspace is open, so history and regressions still make sense after the raw events expire.
• Logs, traces, replays and other telemetry: logs 3 to 14 days, traces 7 or 14 days and session replays 7 to 30 days depending on your plan, web vitals 30 days, release health sessions 90 days, and user feedback for your plan's retention period, then deleted.
• Security monitoring: login-attempt usernames and their IP history follow your plan's retention period, but a security issue keeps the last username, IP address and country it saw for as long as your workspace is open.
• Account and workspace data: while your workspace or account is open. You can delete either yourself in Settings, Danger zone, or write to privacy@blipit.io and we do it within 30 days. A deleted workspace is switched off at once and can be restored by an owner for 30 days, then it is permanently erased with everything in it. A deleted account is switched off at once and can be recovered by signing in for 14 days, then it is permanently erased.
• Sessions: 30 days, or until you sign out.
• Sign-in links: 60 minutes, single use. Sign-in requests from addresses that never create an account are deleted after 30 days.
• Action links in alert emails: 48 hours, single use.
• Waitlist emails: until you ask us to remove them.
• Product update subscriptions: until you unsubscribe; the address is then deleted within 30 days. Sign-ups that are never confirmed are deleted after 30 days.
• Website page views: the record is deleted after 400 days. IP addresses are not stored.
• Audit log: 365 days, including the IP address and browser of each recorded action.
• Backups: deleted data, including permanently erased workspaces and accounts, can stay in our database provider's backups until they roll over, within our backup retention period and never more than 30 days after it is erased.

Cookies

Only the ones the service needs: a signed-in session cookie, a short-lived cookie that protects the sign-in round trip to Google, GitHub or Microsoft, a short-lived cookie that protects the round trip to GitHub when you connect a repository, a short-lived cookie that records that you agreed to the Terms while signing up, and a one-time cookie that carries a newly created secret key to the page that shows it to you. These are set for blipit.io only and marked HttpOnly and Secure. A language cookie remembers the language you chose; it holds only the language code. Counting visits to our website stores nothing in your browser. There are no advertising or cross-site tracking cookies, and none of them follow you anywhere else. If you follow a bug report you sent, the tracking page first emails you a 6-digit code and then keeps a cookie for that report, or for your reports with that team, for 7 days; it is HttpOnly and Secure and is used for nothing else.

How we protect it

Everything travels over TLS. Session tokens, sign-in links and API keys are stored only as SHA-256 hashes, so a copy of our database does not hand anyone a working key. Two-factor authentication is required on every account; authenticator secrets are stored encrypted, and backup codes only as keyed hashes. Secret keys are shown to you once, at creation, and never again. Links that act on your account from an email are signed, expire, and work only once. Access to production is limited to the people who run the service.

If we ever have a breach that puts your data at risk, we will tell affected customers by email without undue delay and within 72 hours of becoming aware, with what we know and what we are doing.

Your rights

You can ask us for a copy of your data, to correct it, to delete it, or to stop processing it. Write to privacy@blipit.io and we will answer within 30 days. A deleted workspace can be restored for 30 days; after that its events are erased for good and we cannot recover them, so export first if you need them.

Depending on where you live, you may also have the right to complain to a data protection authority. We process personal data under the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (PDPL), and the authority in the United Arab Emirates is the UAE Data Office.

Children

Blipit is a tool for developers and is not intended for anyone under 16. We do not knowingly collect their data.

Changes

If we change this policy in a way that matters, we will email the address on your account before it takes effect. The date at the top always tells you the version you are reading.

Contact

Louward Labs FZC LLC, for Blipit — privacy@blipit.io.

Registered address: BC-8936582, 6th Floor, Amber Gem Tower, Ajman, United Arab Emirates