Privacy Policy
Effective 10 November 2026 · Frox Labs
PingAgain is operated by Dilip Kumar Chellaboina under the Frox Labs brand. This notice explains how we handle information for sign-in, monitoring and notifications. The proposed company, Frox Labs Private Limited, is not yet incorporated.
Privacy questions and requests
Email [email protected] to request access, correction or deletion, or ask about this notice. Describe your request and the account concerned, but do not send passwords or API keys. We may verify your identity.
GitHub and Microsoft sign-in
If you choose GitHub or Microsoft sign-in, the provider authenticates you and sends the identity and email information needed for that sign-in. PingAgain uses provider identifiers, verified identity information and authentication records to manage access and protect against conflicting account links. We do not receive your provider password. These sign-in methods do not request access to your repositories, mailboxes or cloud resources.
Your chosen provider processes sign-in under its own privacy notice. Magic Link remains an email-based alternative. Linking or disconnecting an identity does not by itself delete your PingAgain account.
Lighthouse performance audits
For explicitly eligible Websites, PingAgain operates isolated browser audits of your authorised public HTTPS URL. The browser loads the page and permitted public resources to measure Mobile or Desktop lab performance. The target website and its permitted resource providers receive the requests needed for that audit. Do not submit private URLs, credentials or unnecessary personal information.
We retain device strategy, audit time, engine version, category scores, selected performance measurements, bounded finding identifiers and operational status for reports and history. New audits may also retain the original Lighthouse HTML report privately for authorised account members. That report can include public resource URLs, page excerpts and images used in audit diagnostics; it is not a copy of the target site’s raw HTML. Reports are encrypted at rest, size limited and subject to account retention and cleanup. Browser traces and temporary browser profiles are not retained. Downloaded copies are under your control; share them carefully. Measurements are lab observations, not measurements of your visitors.
These audits use PingAgain-operated Lighthouse and Chromium. Audits require account and Website eligibility and are rate limited. Mobile and Desktop observations are stored separately.
Google sign-in
Google sign-in requests openid, email and profile permissions. Google may include your name and profile image in its authentication response. PingAgain uses your Google account identifier, issuer, email address, email-verification status and authentication security claims. This sign-in flow does not persist your Google profile name or image. It does not request Gmail messages, Drive files, contacts or calendars, and PingAgain does not receive your Google password.
We use these details to verify sign-in, create or restore account access, and associate your Google identity with your PingAgain identity. A Google-verified Gmail address or qualifying Google Workspace address can be associated with an existing matching PingAgain email identity. Other addresses may require additional email confirmation. Explicit provider linking requires a recent sign-in and checks for conflicting identity links.
We store the provider identifier, email and verification information, and authentication timestamps. The current flow does not store Google access or refresh tokens for ongoing access to Google services. Google processes your interaction with its sign-in service under its own privacy policy.
Email authentication and account information
Magic Link uses your email address to send and verify a single-use sign-in link, which expires after 15 minutes. We process account and membership identifiers, preferences, consent records, sessions, and authentication and security events to operate and protect your account.
Email-delivery records include recipient and provider delivery information to handle failures, retries, bounces and complaints. Monitoring alerts and optional reports use your notification preferences. Support correspondence contains the information you choose to send us.
Monitoring data and your configuration
We process monitor names, target URLs and domains, schedules, configuration and notification destinations. Checks produce availability and timing measurements, HTTP, TLS, DNS and domain-registration observations, crawl and sitemap findings, heartbeat events, incidents and reports.
Fetching targets and crawling pages processes the responses needed for those checks. API monitoring may process configured request bodies, headers, authentication secrets and response content needed to evaluate assertions. Configured API secrets are encrypted for storage. Only monitor targets you are authorised to monitor, and avoid submitting unnecessary personal information or placing secrets in names or ordinary URL fields.
We use this information to run your checks, show results and history, detect incidents and recovery, and deliver configured notifications. Publishing a status page exposes the selected status information to visitors. Integrations send relevant notification data to the destinations you choose.
Cookies, browser storage and security records
The necessary __Host-sitepulse_session cookie maintains sign-in. It is host-only, Secure, HttpOnly and SameSite=Lax. Sessions have a 30-day maximum lifetime and expire after 14 days of inactivity; logout or revocation can end them sooner. Blocking this cookie prevents authenticated use. Browser storage also remembers interface preferences such as your theme.
Authentication uses hashed security signals and coarse browser/device labels. Cloudflare and our hosting systems process IP addresses, request metadata and security/access logs. Hashing a signal does not make every associated record anonymous. The current application does not implement advertising cookies or Google Analytics tracking.
Service providers and sharing
Amazon Web Services hosts the current application and account data in Mumbai and provides storage, encrypted backups and transactional email through Amazon SES. Cloudflare provides DNS, HTTPS delivery and network/security services. Google, GitHub and Microsoft provide their respective sign-in services. Providers receive information needed for their services, and global delivery and support operations may involve processing outside your country. We do not claim that all processing stays in India.
Google identity information is used for account authentication and related security, not to request access to unrelated Google products. Your configured recipients receive alert or report content. Membership permissions control access within an account; published status pages are public. Integration providers separately process the information sent to destinations you enable.
Retention and deletion
Account configuration and linked sign-in identities are retained to operate your account until changed, disconnected or removed through the applicable account process. Monitoring history is subject to account retention settings and periodic cleanup. Monitoring, delivery and security records have different retention rules; there is no single retention period for all information.
Deleting an account disables access and notifications and starts removal of its data from the live service. If a removal step fails, the service can retry it. Sign-in details may remain if they are still needed for membership in another account. Encrypted backup copies expire according to their retention settings rather than being edited immediately. Restoring a backup must take recorded deletion requests into account. Deleting an account therefore does not immediately remove its information from every backup.
Your choices and data controls
Account settings let you change notification preferences, manage sign-in methods and sign out active sessions. Data & privacy lets you export account information or request deletion. The export includes the account records supported by that feature; it does not include every security log or historical backup.
To disconnect a sign-in provider, you must have signed in recently and keep at least one working way to access your account. You can also manage PingAgain access in your Google Account. Removing Google access does not delete your PingAgain account or sign you out of an existing PingAgain session. Use PingAgain’s logout, session controls or account deletion for those actions.
Contact us about access, correction, deletion or questions about your information. We may need to verify that a request concerns your account before disclosing or changing account information.
Changes to this notice
Updates to this notice are published at this same address, with the effective date shown at the top. You can return here to review the current notice or contact us with questions about a change.