NanoPush Privacy Policy
Last updated: 2026-11-12
NanoPush is designed around local-first notification handling with an official APNs gateway that we operate. You do not need to deploy a server, provide Apple Developer credentials, or handle APNs provider keys. The app connects only to that gateway; it does not offer self-hosting or connecting to other servers.
Data Processed
- Notification content entered by the user.
- APNs device token used only for push routing.
- Device key and encryption key.
- Local notification history.
- StoreKit purchase and entitlement state.
- Diagnostic exports explicitly created by the user.
Storage
NanoPush stores app settings and history locally. Device keys and encryption keys are stored through the app's secret storage path where available. Notification extension history may use the configured App Group container so the main app can import messages processed by the extension. The APNs device token is not shown as the normal user-facing push credential.
Official Gateway
In the default product path, the app registers its APNs device token with the official gateway. The gateway uses this registration only to forward pushes to Apple Push Notification service.
Messages sent by the app, by Shortcuts and by the exported script are end-to-end encrypted by default. The app encrypts the whole message (title, body, URL, group, copy text and other fields) before it leaves the device; the gateway and Apple see only a fixed placeholder ("NanoPush" / "Encrypted message") and ciphertext. Plaintext is sent only when you turn it on explicitly.
What the gateway stores, for as long as the device is registered:
- A random device identifier and the push address alias shown in the app.
- The APNs device token, encrypted at rest.
- The public half of the device's send-signing key. The gateway can check that a send request is genuine but cannot create one.
- Platform (iOS or macOS), APNs environment, app version, and the dates the registration was created and rotated.
- The last day the device was active: the app was opened, or a notification was accepted for delivery. It is recorded at most once a day and is used only for the 12-month rule below.
What the gateway keeps after a registration is deleted: the push address alias and a hash of the device's management key. They hold no device token, key or message. They let the same device get its own address back and make sure no other device can ever be given that address.
What the gateway never stores:
- Message content, in any form.
- A record of sends: no list of who sent what to which device, or when. The result of each send is returned to the sender and then discarded.
- Sender IP addresses. Push and registration requests are not written to access logs. Short-lived abuse counters use a keyed hash of the IP address that changes every day, and expire automatically.
Gateway operators see only aggregate counts (for example, how many devices are registered). There is no list of devices. An operator can look at a single device's routing information only after you share the support code (your push address) with them, and each lookup is recorded.
User Controls
Your push address changes only when you ask for it. If it ever changes for another reason, for example after moving to a new phone, the app shows a notice so you can update your scripts.
You can regenerate your push address if it may have been shared with someone you do not trust. This deletes the previous registration immediately and creates a new one with new keys. The old address stops working for good.
You can pause receiving. Pausing stops deliveries but keeps your registration, however long it lasts. When you resume, your push address and scripts work again.
You can delete your data on the server (Settings). This deletes the registration immediately, replaces every local routing credential and leaves receiving off. Messages stored on your device are not affected.
Retention
Local history stays on your device under the retention you choose in the app. On the free plan the list shows the most recent messages; older messages are not deleted.
On the gateway:
- When you delete your data on the server or regenerate your address, the registration is deleted immediately. Copies in backups are removed as backups rotate, within 7 days.
- A paused registration is kept until you resume or delete it.
- A device that has neither opened the app nor received a notification for 12 months has its registration deleted. If it is used again, it gets the same push address back.
- Operator audit records are kept for 90 days.
The gateway database is backed up on the gateway server every 6 hours and before each update. Each backup is kept for 7 days and is not copied anywhere else. Backups hold the same registration data listed above and never message content. If the gateway ever has to be restored from a backup, every device registers again before it receives anything; the app does this the next time it opens, and push addresses stay the same. This makes sure credentials you replaced after the backup cannot be used again.
Abuse Prevention
The official gateway uses request signing, replay protection, rate limits, blocklists and emergency switches to reduce abuse. These controls work on short-lived counters and do not create a send history.
Apple Services
NanoPush uses Apple Push Notification service for notification delivery and StoreKit for purchases. Apple may process data required for those platform services.
Diagnostics
Diagnostic exports are user initiated. They include operational summaries such as whether a device key, API token, or encryption key exists, but should not include the full device key, API token, encryption key, APNs device token, notification body, or full server URL path. Users should review exported files before sharing them.
Contact
Support: support@nsorz.com