Pipemason — Privacy Policy

Last updated: June 24, 2026

CrashBytes ("we", "our", or "us") operates the Pipemason mobile application, a tool for monitoring CI/CD pipeline runs available on the Apple App Store (iOS) and Google Play Store (Android). This policy explains what data Pipemason collects, how it is used, and what choices you have.

The Privacy Promise

  • We do not sell, lease, share, or rent your data to anyone for marketing, advertising, or cross-context behavioral profiling.
  • We do not train AI models on your data, ever. No exceptions.
  • We do not run advertising in Pipemason. There are no ads, no ad SDKs, and no advertising identifiers collected.
  • We do not bundle advertising, marketing, or attribution SDKs. No Facebook SDK, no AdMob, no Mixpanel, no Amplitude, no Branch, no AppsFlyer.
  • We use Google Firebase (Analytics, Crashlytics, and Performance Monitoring) for first-party product analytics and stability only. It is configured for privacy: no advertising identifier is collected, analytics events carry no free-text or personal data (only screen names, counts, durations, and run status values), and the only identifier attached is your opaque Pipemason/Clerk user ID. We do not use it to track you across other apps or websites. See Analytics, Crash, and Performance Data and Sub-processors below.

What We Collect

The following is everything Pipemason collects, and the lawful basis for each:

  • Account identity — When you sign in, our authentication provider Clerk (see Sub-processors below) issues a user identifier and stores the basic profile data Pipemason needs to associate runs with your account: your email address, your display name (if provided by the chosen sign-in method), and the authentication method you used (Google, Apple, or email). If you sign in with Apple, we use Apple's "Hide My Email" option and receive only an Apple-issued relay address unless you choose to share your real address. Lawful basis: contract / performance.
  • Authentication tokens — Pipemason stores short-lived session tokens issued by Clerk in your device's secure keychain (iOS Keychain / Android Keystore via expo-secure-store). These tokens are never written to disk in plaintext and never leave your device except to authenticate API requests to our servers.
  • Pipeline run data — When you view pipelines, runs, programs, stories, or notifications in Pipemason, our backend at api.pipemason.com serves the run records your account is authorized to see. These records describe CI/CD pipeline activity (run IDs, statuses, branches, tickets, phase timelines, log events) that you or your organization have produced through normal use of the Pipemason platform. We store this data so the mobile app can show it to you in real time. Lawful basis: contract / performance.
  • Push notification token — If you enable push notifications, your device's operating system issues a push token (via Apple Push Notification service on iOS or Firebase Cloud Messaging on Android), which Expo packages as an Expo push token. Pipemason sends this token to api.pipemason.com and stores it so we can notify you when one of your runs or programs changes state (started, needs input, paused, cancelled, completed, or failed). The token is a delivery address for notifications, not a tracking identifier; it is removed when you sign out or when the device is no longer registered. You control which events notify you from Settings → Notifications in the app, and you can revoke push permission at any time in your device settings. Lawful basis: consent. See Push Notifications below.
  • Analytics, crash, and performance data — Pipemason includes Google Firebase Analytics, Crashlytics, and Performance Monitoring to understand how the app is used in aggregate and to detect crashes and performance problems. This collects: anonymous product-usage events (which screens you open and run/program status changes, as counts and durations — never free text or pipeline content), a Firebase app-instance identifier, crash stack traces and device/app state at the time of a crash, and performance traces (app start time, screen render time, and network request timings to non-identifying route templates). These records are linked only to a Firebase app-instance ID and to your opaque Pipemason user ID — never to your email, name, or pipeline data, and never to an advertising identifier. Collection is disabled entirely in development and test builds. Lawful basis: legitimate interest in app stability and improvement.
  • Platform crash diagnostics — Separately, Apple (iOS) and Google (Android) may collect a crash report through their platform-level diagnostics, subject to your device-level Share With Developers preference. CrashBytes receives only the aggregated reports Apple and Google make available through App Store Connect and Play Console.

What We Do NOT Collect

  • Your location (precise or approximate)
  • Your contacts, calendar, photos, camera, or microphone
  • Your real name, phone number, or mailing address (unless you provide them to support)
  • Health, fitness, biometric, or sensor data
  • Browsing history outside Pipemason
  • Advertising identifiers (IDFA, GAID) — Pipemason does not request the IDFA prompt
  • Keystrokes, screen recordings, or session replays
  • Any biometric authentication data (Face ID, Touch ID, Android Biometric) — these are processed entirely on-device by the operating system and never transmitted

Authentication via Clerk

Pipemason uses Clerk for sign-up and sign-in. Clerk handles three flows on our behalf:

  • Sign in with Google — uses Google's native One Tap / Sign-In API on Android and Apple's ASWebAuthenticationSession-equivalent on iOS. Google returns an ID token to Clerk; Clerk verifies it and issues a Pipemason session. CrashBytes receives the email address and name from your Google account.
  • Sign in with Apple — uses Apple's native AuthenticationServices framework. Apple issues an identity token to Clerk; CrashBytes receives the Apple-issued user identifier and the email address you choose to share (real or relay).
  • Email sign-in — Clerk sends a one-time code or magic link to the address you provide. CrashBytes receives the verified email address.

Clerk's own privacy policy at clerk.com/legal/privacy governs what Clerk does as a sub-processor on our behalf.

Pipeline Data and Organizations

Pipemason is designed to work alongside the Pipemason CI/CD platform. The data shown in the mobile app — pipeline runs, programs, stories, notifications — is the same data the platform already holds about your account or your organization. The mobile app does not introduce any new data collection; it is a window onto data your account has already authorized us to process under the separate Pipemason platform terms. If you do not have an account or organization on the Pipemason platform, the mobile app will sign you in and show an empty state — we do not collect anything beyond your account identity.

Push Notifications

Pipemason can send push notifications when your runs or programs change state. Delivery works as follows: your device registers an Expo push token (backed by Apple Push Notification service on iOS or Firebase Cloud Messaging on Android), which we store against your account. When a relevant event occurs, our backend sends the notification — its title, a short body, and the associated run or program ID for deep-linking — to Expo's push service, which relays it to Apple or Google for delivery to your device. We honor the per-event preferences you set in Settings → Notifications: a notification is only sent for an event type you have left enabled, and not at all if you turn the master switch off or deny push permission at the OS level. We do not use push notifications for advertising or marketing.

Sub-processors

The following third parties process limited data on our behalf, each bound by a Data Processing Agreement:

  • Apple Inc. — App Store distribution, Sign in with Apple, platform-level crash reporting (subject to your device Share With Developers preference).
  • Google LLC — Google Play distribution, Sign in with Google, platform-level crash reporting (subject to your device Share With Developers preference), and Firebase (Analytics, Crashlytics, and Performance Monitoring) as our first-party analytics and stability processor. Firebase receives the anonymous usage, crash, and performance data described in Analytics, crash, and performance data above, plus the Firebase Cloud Messaging token used for push delivery.
  • Clerk, Inc. — Authentication and user identity. Receives the data described in Authentication via Clerk above.
  • Expo (650 Industries, Inc.) — Push notification delivery. Receives your Expo push token and the contents of each notification (title, short body, and the run or program ID) solely to relay it to Apple Push Notification service or Firebase Cloud Messaging. See Push Notifications above.

Aside from Google Firebase (used as our first-party analytics and stability processor, as described above), we do not use Facebook SDK, AdMob, Mixpanel, Amplitude, Branch, AppsFlyer, Sentry, or any marketing-attribution, advertising, or cross-app tracking SDK inside the Pipemason mobile app.

How Data is Transmitted and Stored

  • All network traffic between the Pipemason mobile app and api.pipemason.com is transmitted over HTTPS (TLS 1.2+). The realtime WebSocket connection at wss://api.pipemason.com uses the same TLS protections.
  • Authentication tokens are stored in the operating system's secure keychain (iOS Keychain / Android Keystore), accessed via Expo's expo-secure-storemodule. Tokens are never written to plaintext storage and are scoped to the Pipemason app sandbox.
  • Pipeline run data is held on the Pipemason backend, hosted in commercial cloud infrastructure in the United States. Access is restricted to the CrashBytes engineering team for operational purposes only.

Children's Privacy

Pipemason is rated 4+ on the App Store but is designed for and marketed to professional software developers, DevOps engineers, and platform teams. It is not directed at children under 13 and we do not knowingly collect personal information from children under 13. If a parent or guardian believes a child under 13 has used Pipemason and provided personal information, please contact us and we will delete the associated account.

Your Rights

You can:

  • View, export, or delete your Pipemason account and all associated data by emailing [email protected]
  • Sign out of Pipemason at any time, which clears the session token from your device
  • If you are in the EU/UK, exercise your rights under GDPR including access, rectification, erasure, portability, and objection
  • If you are in California or another US state with comprehensive privacy law (CO, CT, VA, UT, IA, IN, TN, TX, OR, MT, DE, MD, NH, NJ, RI, KY, MN), exercise the analogous rights to access, delete, and correct your personal information

We do not sell your personal information. We do not share your personal information for cross-context behavioral advertising. We have no "Do Not Sell or Share" link because there is nothing to opt out of.

Data Retention

Pipeline run data is retained for as long as your account or your organization's account is active on the Pipemason platform, subject to the separate retention policy of the platform terms. When you delete your account, all account-identity data is removed from Clerk within 30 days and from the Pipemason backend within 90 days. Backups containing your data are purged within the standard backup rotation (typically 90 days).

Changes to This Policy

We may update this privacy policy from time to time. Material changes will be announced in-app and the updated date at the top of this page will be revised. Past versions are available on request from [email protected].

Contact Us

If you have questions about this privacy policy, or to exercise any of your rights:

Email: [email protected]
Website: crashbytes.com