Last updated 28 September 2026

Terms of Service

These terms are the agreement between you and Louward Labs for Blipit, the error monitoring service at blipit.io. Using Blipit means you accept them. If you are agreeing on behalf of a company, you confirm you can bind that company.

1. What Blipit does

Blipit receives error reports from applications you connect, groups them into issues, keeps them for the retention period of your plan, and notifies you. You control what you send. Blipit is a monitoring tool, not a backup service and not a system of record.

2. Your account

You need an account to use Blipit. Keep your sign-in method secure and tell us at support@blipit.io if you think someone else has access. You are responsible for what happens under your account, including what your team members do.

Your API keys identify your projects. A secret key can read the errors in your project, so treat it like a password: keep it on your server, never in a browser, and rotate it from the dashboard if it leaks.

3. What you may not send

Do not send Blipit anything you are not allowed to hold or share: payment card numbers, government identifiers, health records, passwords, or the personal data of people who have not been told about it. Error payloads are visible to everyone on your workspace and to our operators when we investigate a support request. Scrub sensitive values before they leave your application.

Do not use Blipit to attack, overload or probe our systems or anyone else's, to break the law, or to resell the service as your own.

4. Plans, limits and billing

Every plan has a monthly event limit. When you reach it, Blipit samples further events instead of dropping them silently, and tells you. We do not bill you past your plan for going over: a bad deploy will not multiply your invoice. That is a deliberate product promise, and it is part of this agreement.

The Free plan costs nothing and needs no card. Paid plans are billed in advance, monthly or yearly, are not refundable for partial periods, and can be cancelled at any time with effect from the end of the period you have paid for. If we change a plan's price, we will tell you before it applies to your next period.

5. The Odoo module and other clients

Our Odoo module and SDKs are licensed to you to use with Blipit. Each installation binds to one Blipit project using an identifier derived from your database, so one key cannot be shared across instances. You may install a client on systems you operate or administer. You may not remove the parts that identify the installation, or use the clients to reach Blipit without a valid key.

The Odoo module is proprietary software under the Odoo Proprietary License v1.0. You may not publish, redistribute, sublicense or sell it, modified or not, rename or rebrand it, or connect it or any part of it to a service other than Blipit. Your keys may only be used with the clients we publish. Limits that come with your plan, such as seats and events, are enforced by the service, and working around them in a client is a breach of these terms.

6. Availability

We publish live status at status.blipit.io. We aim to keep Blipit up and to warn you when it is not, but there is no service level agreement and no credits for downtime. Ingestion is designed to accept events even when other parts of the service are degraded; that is an intention, not a guarantee.

7. Who owns what

You own your data: the events you send, the issues built from them, and your account content. You give us the permission we need to store, process, display and transmit that data so the service can work, including sending it in alert emails you have configured.

We own Blipit itself: the software, the site, the name and the marks. Nothing here transfers that to you. Feedback you send us we may use freely.

8. Ending the agreement

You can close your workspace at any time from the dashboard or by writing to us. We can suspend or close an account that breaks these terms, that is used to harm others, or that has not been paid for. Where the situation allows it, we will tell you first. When an account closes, its events are deleted on our normal deletion schedule and cannot be recovered afterwards, so export anything you need first.

9. No warranty

Blipit is provided as it is. We do not promise that it will catch every error, that alerts will always arrive, or that it will be uninterrupted or fault free. You should not rely on Blipit alone for anything safety critical.

10. Limit of liability

To the extent the law allows, Louward Labs is not liable for indirect or consequential loss, lost profits, lost revenue, or lost or corrupted data. Our total liability for any claim is limited to what you paid us for Blipit in the twelve months before the claim, or one hundred US dollars if that is greater. Nothing here limits liability that cannot be limited by law.

11. Changes

We may change these terms. If a change materially affects you, we will email the address on your account at least thirty days before it takes effect. Continuing to use Blipit after that date means you accept the new terms.

12. Law and disputes

These terms are governed by the laws of the Republic of the Philippines, and disputes belong to the courts there. If any part of these terms is unenforceable, the rest stays in force.

13. Contact

Louward Labs, for Blipit — support@blipit.io.