Privacy Policy

Scope

This Privacy Policy explains how OpsBlip collects, uses, stores, and discloses information when you use the public website, the Org portal, and related support workflows. It is written for the current MVP and free-tier product shape, including domain verification, endpoint monitoring, alerts, flows, and support.

Information we collect

• Account data such as full name, email address, timezone, and authentication settings.
• Organization data such as workspace name, timezone, domain mode, and domain verification state.
• Operational records you add, including objects, endpoints, findings, alerts, support tickets, and flows.
• Usage and diagnostic data needed to operate the service, such as error events, page-level analytics, and audit-style activity history.
• Communication data when you contact support or receive product emails.

How we use information

• Authenticate users, maintain sessions, and enforce onboarding or security requirements.
• Store and display tracked operational assets, monitoring results, and runbook progress.
• Send alerts, reminders, weekly digests, account verification messages, and support replies.
• Protect the platform, troubleshoot issues, and improve stability, abuse prevention, and usability.
• Meet legal obligations and keep accurate operational and support records.

What you should not store

OpsBlip is not designed for secrets management. Do not store passwords, API keys, private keys, tokens, or similar credentials in objects, notes, flows, support tickets, or imports. If that information is submitted anyway, you remain responsible for the data and should remove it immediately.

Cookies, local storage, and similar technologies

We use authentication cookies to keep you signed in. The product also uses browser-side storage for items such as theme preference and reminder-read state. Additional details are in the Cookie Policy.

Third-party processors

• Cloudflare as the CDN, DDoS mitigation, and TLS termination layer in front of the service. Cloudflare sees request metadata (IP address, user agent, request path) and may set bot-management cookies such as __cf_bm and cf_clearance.
• Sentry for error and performance diagnostics. Error events may include technical request metadata; cookies and request bodies are stripped before upload.
• Google Analytics 4 for aggregate traffic and usage analysis. IP addresses are anonymized and no advertising signals are enabled.
• Google Search Console for indexing diagnostics of the public marketing pages. Verification is performed via a site-level meta tag only.
• Infrastructure and email providers that host the service or deliver required account and alert messages (for example, Azure Communication Services for transactional email).

Retention and deletion

We keep information for as long as it is needed to provide the service, enforce limits, maintain audit history, resolve support issues, and satisfy legal obligations. Deleting an item in the UI may remove it from active views while some operational history remains in timeline, alert, or support records where required for product integrity and abuse prevention.

Your choices and rights

Depending on your jurisdiction, you may have rights to access, correct, export, or delete personal data. Many profile and workspace settings are self-service inside the portal. For additional privacy requests, contact support using the address below.

Contact

For privacy questions, contact support@opsblip.io or use /app/support.