Legal

Privacy Policy for KrypAlert

This policy explains how Krypzon processes information when authorized users access the KrypAlert mobile application, website and related incident-monitoring services.

Last updated July 30, 2026

1. Scope and service model

KrypAlert is a private operational tool used to receive sanitized diagnostic events from participating Krypzon applications and make those events available to authorized response teams. It is not intended for public account registration or advertising.

2. Account and access information

We process an operator’s name, email address, protected authentication credentials, platform role, application memberships, account status and session-security information. Accounts are created or invited by authorized administrators.

3. Incident and diagnostic information

Participating applications may submit sanitized exception type and message, bounded stack frames and context, application name, source, environment, release, route, correlation identifier, severity and timestamps. KrypAlert groups matching events and retains a limited number of recent samples.

Reporters are designed to remove or reject common credentials and unnecessary personal data. Users and product teams must not intentionally submit passwords, access tokens, cookies, private keys, payment information, user documents or unrestricted request bodies.

4. Operational activity

We process incident status changes, assignments, comments, application and notification-rule administration, ingestion-key lifecycle metadata and audit records. These records support accountability, security review and incident response.

5. Device, notification and technical information

When an operator enables mobile notifications, KrypAlert processes the device platform and an encrypted Firebase Cloud Messaging registration token linked to that operator. We also process security logs, IP address, request timestamps, application version, delivery outcomes and limited reliability diagnostics needed to operate and protect the service.

6. How information is used

We use this information to operate and protect KrypAlert.

  • authenticate operators and enforce application memberships and roles;
  • receive, sanitize, group, display and retain operational incidents;
  • send configured email and mobile alerts;
  • support acknowledgement, assignment, commenting and resolution workflows;
  • prevent abuse, investigate failures and maintain an operator audit trail; and
  • provide support and improve service security and reliability.

7. Service providers and disclosure

KrypAlert relies on infrastructure, database, email, monitoring and notification providers. Firebase Cloud Messaging and Apple Push Notification service process device-routing information for push delivery. Providers receive only the information needed to perform their function under their own terms and applicable agreements.

We may disclose information when required by law, to protect users or the service, or as part of an authorized corporate transaction. Krypzon does not sell personal information and KrypAlert does not use third-party advertising.

8. Retention and deletion

Diagnostic samples, groups, notification history and audit records are retained according to operational and security policies. Some records may be deleted on a schedule, while a limited audit or security record may be retained longer to preserve incident integrity, investigate abuse or meet legal obligations.

After a verified deletion request, we delete or anonymize account information where appropriate. Shared comments, audit entries or security records may be retained or de-identified when needed to preserve shared operational records.

9. Security and choices

We use encrypted network transport, access controls, membership checks, protected session handling, encrypted mobile tokens, audit logging and server-side validation. No online system can guarantee absolute security.

Operators can decline notification permission, log out to revoke the current mobile registration, request access correction through an administrator and contact us about their account or privacy rights.

10. Changes and contact

We may update this policy as the service, providers or applicable requirements change. The revision date identifies the current published version.

Privacy questions can be sent to krypalertteam@gmail.com.