Legal

Privacy Policy

Last updated: May 23, 2026

Published by raadtech.co · Applies to the Push Tools desktop application for macOS.

Privacy at a glance

✓No personal data is collected

✓No accounts, no sign-in, no cloud sync

✓Credentials stored in macOS Keychain — never transmitted to us

✓Network requests go only to the push provider you choose

✓No analytics, no crash reporters, no telemetry of any kind

Overview

Push Tools is a native desktop application published by raadtech.co that helps developers send, test, and debug push notifications to Expo, Firebase Cloud Messaging (FCM), Apple Push Notification service (APNs), and Live Activity endpoints. This Privacy Policy explains our data practices. The short version: Push Tools does not collect, transmit, or store any personal data on our servers — because we have no servers involved in normal app usage.

Information We Collect

We collect nothing. Push Tools has no analytics SDK, no crash reporter, no usage telemetry, and no backend of its own. The app does not create an account, require sign-in, or communicate with any raadtech.co server.

The only network requests made by Push Tools are the ones you explicitly trigger: push notification dispatches sent directly from your machine to the provider endpoint you selected (Expo, FCM, APNs, or Live Activity). These requests go your device → provider. raadtech.co is not a party to those requests.

Credential Storage

Push Tools stores sensitive credentials — APNs .p8 private keys, FCM service account JSON, and Expo access tokens — in the macOS Keychain via the OS keyring API:

Credentials are stored by the security subsystem inside the macOS Keychain, protected by your device login.

These credentials are never written to unencrypted files, never logged, and never transmitted to raadtech.co. They are read back on demand solely to authenticate outbound push requests to the respective provider API.

File access (for importing .p8 keys or service-account JSON) is restricted to files in Desktop, Documents, Downloads, or the system temp directory, and capped at 1 MiB per file. No other filesystem paths are accessible.

Device Book (Local Storage)

The Device Book feature stores named device tokens in a local file (device-book.json) managed by the Tauri store plugin on your device. This file never leaves your machine. You can delete it at any time by clearing the app's data or uninstalling Push Tools.

Third-Party Services

When you send a push notification, your request goes directly to one of these provider endpoints:

https://exp.host — Expo push API
https://fcm.googleapis.com and https://oauth2.googleapis.com — Firebase Cloud Messaging (Google)
https://api.push.apple.com / https://api.sandbox.push.apple.com — Apple Push Notification service

Each provider governs the token, payload, and credentials you supply under their own privacy policy:

Children's Privacy

Push Tools is a developer utility not directed at children. We do not knowingly collect information from anyone under 13 (or the applicable age in your jurisdiction). If you believe a child has provided personal information through this app, please contact us and we will address it promptly.

Changes to This Policy

We may update this Privacy Policy occasionally. The “Last Updated” date at the top reflects when it was last revised. Continued use of Push Tools after any changes constitutes your acceptance of the revised policy. Significant changes will be noted in the app release notes.

Contact

Questions or concerns about this Privacy Policy? Contact us at support@raadtech.co. We respond to all privacy inquiries.

support@raadtech.co