Data and privacy

Blipit stores whatever your application sends when it breaks, on your instructions. This page says what that is in practice, what the SDKs strip before sending, where the data lives, and what you can delete. The full policy is at blipit.io/legal/privacy.

1What an event contains

Typically the error type and message, the stack trace with a few lines of your code around each frame, the URL or job, release and environment, browser or server version, breadcrumbs, the user id or email you attached, and tags. The IP address a report came from is not stored. Personal data in your messages is not filtered: if your code puts a customer's name in an error message, it arrives.

2What is scrubbed

Before storage, Blipit blanks out values that look like secrets in events, traces and logs: fields named like passwords, tokens, keys, cookies or sessions, Authorization headers, bearer tokens and card numbers become [Filtered]. On top of that, the browser SDK redacts query parameters whose name contains token, key, password, secret, auth, session, passwd or api in URLs and breadcrumbs, and masks typed values and page text in replays, keeping only labels and buttons readable unless the project turns that off. The Odoo module never sends query strings, request bodies, passwords, hashes, session tokens or cookies. Use beforeSend in the browser SDK (before_send or BeforeSend in the other Blipit SDKs) to drop or edit anything else before it leaves.

3Where it lives

Singapore: the database is Neon on AWS Singapore, ingestion and processing run on Fly.io in Singapore, the queue is Upstash. The dashboard is served by Vercel, DNS by Cloudflare, alert email by Microsoft 365, payments by Stripe. Anthropic (United States) receives an issue's details, and the source files AI fix reads from a connected GitHub repository, only when someone runs an AI fix; Twilio (United States) receives phone numbers and the incident title only when SMS or call alerts are on. Slack, Teams, Jira, Linear and webhooks you connect receive issue details.

4How long

Raw events for your plan's retention (7 or 30 days), issue summaries while the workspace exists, logs 3 to 14 days, spans 7 or 14 days, replays 7 to 30 days, web vitals 30 days, sessions 90 days, audit rows 365 days, feedback for your plan's retention. Website page views lose their IP after 30 days and are deleted after 400 days. Deleting a workspace or account in Settings, Danger zone switches it off at once; a workspace is permanently erased after 30 days and an account after 14, and either can be restored until then.

5Terms and deletion

You accept the Terms (version dated 28 September 2026) on sign-up and again if they change; the acceptance is recorded with time and IP and appears in the audit log. The Odoo module records the same acceptance on Connect. Remove a project to delete all its data at once. Settings, Danger zone schedules the deletion of the whole workspace (owners only; an active subscription is cancelled at once, without refund; any owner can restore it for 30 days, then everything is erased) or of your own account (once no live workspace has you as its only owner; signing in within 14 days cancels it); each step sends an email, with a reminder 3 days before the final erase. For a copy of your data, write to privacy@blipit.io; answers within 30 days.

6Odoo, dependency and server data

Odoo performance sends durations, query counts, the text of queries with every value removed, the file and line of code, and the Odoo user id and company id; never record values. Odoo Workflows sends counts of business steps and, when a step fails, the record ids of the documents it touched, the Odoo user id and the company id; with Value on hold turned on (Scale), it also sends the total and currency of the document whose step failed. Dependencies record the host of each service your servers call with its timings and failures, and Server health records CPU, memory, event-loop delay and database connections. Odoo performance data is kept 1, 7 or 30 days depending on the plan, workflow data 7 days on Free and 30 days on paid plans, and dependency and server data as long as spans: 7 days on Free and Solo, 14 days on Team and Scale.

Good to know

  • API keys, session tokens and sign-in links are stored only as SHA-256 hashes. Tracker tokens, GitHub tokens and TOTP secrets are encrypted with AES-256-GCM.
  • If a breach puts your data at risk, affected customers are emailed within 72 hours of Blipit becoming aware.
  • Blipit does not sell data, share it with advertisers or use event data to train models.

Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.