How OpsProbe handles monitoring and account data.

Application purpose

OpsProbe helps individuals, small businesses, agencies, and SaaS teams monitor verified websites. The product checks public website availability and related health signals such as HTTP responses, DNS resolution, SSL certificates, TCP ports, Ping, Keyword, Heartbeat, incidents, alerts, reports, and public status pages.

Information we collect

Depending on how you use OpsProbe, we may collect the following categories of information:

• Account information: email address, display name, Google account identifier, and session identifiers.
• Workspace information: workspace name, members, roles, plan state, audit events, and ownership records.
• Website monitoring data: configured URLs, hostnames, ownership verification tokens, monitor settings, check intervals, port numbers, keywords, DNS records, SSL certificate metadata, response status, response timing, incidents, alerts, reports, and status-page configuration.
• Diagnostic data: anonymous or signed-in instant probe targets, DNS/TCP/TLS/HTTP results, timing evidence, redirects, safe response summaries, and temporary shared-report metadata.
• Contact and early-access data: email address, website count range, submitted message context, and related server-side request metadata.
• Operational and security data: IP address, User-Agent, request path, timestamps, authentication events, abuse-prevention state, rate-limit state, error logs, and service health events.
• Product analytics: server-side page views, unique visitor estimates, feature events, sign-in steps, probe submissions, and aggregate usage trends. OpsProbe does not currently use third-party browser tracking scripts for this analytics surface.

Google sign-in and Google API data

OpsProbe uses Google OAuth/OpenID Connect only for authentication. The requested Google scopes are openid, email, and profile. These scopes let OpsProbe confirm your identity, read your email address and basic profile information, create or find your OpsProbe user account, and maintain your signed-in session.

OpsProbe does not request access to Gmail, Google Drive, Google Calendar, YouTube, contacts, photos, files, or other Google product data. OpsProbe does not post to your Google account, read private Google content, or use Google user data for advertising profiles.

OpsProbe's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How we use information

We use collected information to:

• Authenticate users and maintain secure sessions.
• Create workspaces and enforce workspace membership, roles, and plan limits.
• Run website diagnostics, recurring monitors, incident detection, alerts, and status pages.
• Show check history, reports, SSL expiration information, DNS evidence, domain profile evidence, and operational timelines.
• Send transactional alerts, controlled test alerts, product updates requested by the user, and account-related messages.
• Protect the service from abuse, automated noise, private-network probing, invalid targets, and unauthorized access.
• Understand aggregate product usage so we can improve onboarding, reliability, pricing, documentation, and standard monitor profiles.
• Meet legal, security, accounting, and service-administration obligations.

What we do not do

• We do not sell user data.
• We do not use Google user data for advertising profiles.
• We do not use Google APIs to develop, improve, or train generalized artificial intelligence or machine learning models.
• We do not use Google APIs or Google user data for AI-generated non-consensual intimate imagery or any related AI NCII purpose.
• We do not monitor websites unless a user submits a target or configures a monitor, and recurring monitoring requires account access and ownership verification where applicable.

Sharing and subprocessors

OpsProbe shares data only with service providers needed to operate the product, such as hosting, database, email delivery, logging, security, and infrastructure providers. These providers process data for OpsProbe service purposes and are not permitted to use it for their own advertising. Current subprocessor information is listed on the Subprocessors page.

We may disclose information if required by law, to protect users or the service, to investigate abuse, or in connection with a business transfer such as a merger, acquisition, or asset sale.

Retention

Retention depends on the data type and workspace plan. Monitoring results, incidents, and reports are kept only as long as needed for the product and the active retention policy. Temporary shared reports expire after a limited period. Server logs, analytics, rate-limit state, and security records are kept for operational, abuse-prevention, and troubleshooting needs. More detail is available on the Data Retention page.

Security

OpsProbe uses server-side sessions, HTTPS, hashed tokens where appropriate, workspace authorization checks, bounded probes, target validation, and access controls to protect account and monitoring data. Additional security notes are available on the Security page.

User choices and deletion

Users can choose not to sign in, can run a limited anonymous diagnostic from the homepage, and can remove configured website monitors from their workspace. A workspace owner can request account, workspace, monitor, or early-access contact deletion. Some records may be retained where required for security, abuse prevention, legal obligations, backup integrity, or financial records.

International processing

OpsProbe may process data in countries where its hosting, infrastructure, email, and operational providers run services. By using OpsProbe, you understand that data may be processed outside your country of residence subject to the safeguards used by the relevant service providers.

Contact

For privacy requests or Google OAuth verification questions, contact the OpsProbe operator at ken@shfanxi.com. Include the email address used to sign in and the workspace or website involved so we can locate the relevant records.