通知君隐私政策

1. Information and purposes

We process an app-generated installation ID, a service-generated Push Code, a management credential hash and registration/update/sync state. After you enable system alerts and the app obtains an APNs token from Apple, the app also binds that token to the current installation for system notification delivery. Device registration and fetching messages in the app do not require a token. These data support identification, authorization, message sync and delivery, are linked to the installation and are not used for advertising identification.

You or scripts, CI/CD and automation tools holding your link submit notification titles, bodies, tags and reminder settings. An optional mail parameter may provide one recipient address for a copy of the same notification. We process message identifiers, timestamps and delivery/read/deletion state for sending, sync, display and management. Sender-provided request identifiers may be used for deduplication. Content and the optional address are linked to the receiving device identity.

If you contact support, we receive your email address, message and chosen attachments solely to respond, troubleshoot and handle privacy requests. The app does not automatically attach full codes, tokens, credentials or notification bodies; please do not send them. Local copies, preferences and credentials stay in app storage or Keychain. Credentials are sent over HTTPS for registration and authentication; the server persists only a hash, not the plaintext credential.

We do not actively read contacts, photos, microphone recordings, precise location, health information or clipboard content for analytics. Copy actions you initiate write selected content to the clipboard. Do not submit personal information you have no authority to process.

2. Use and tracking

We use information only for notification delivery, sync after reconnecting, message/device management, necessary security and support you request. We do not sell or rent personal information, advertise, create marketing profiles, or train AI models with notification content. These public pages use no advertising, third-party analytics scripts or analytics cookies. We do not use IDFA or combine app data with other companies' app or website data for targeted advertising or ad measurement.

3. Service providers and sharing

When sending system notifications to a device with an APNs binding, Apple APNs receives the token, title, body preview and necessary notification settings; payloads may also include message identifiers, badge or sound settings. Messages received without a token binding are available in the app without scheduling APNs delivery. See Apple's Privacy Policy. In-flight notifications may still arrive after permission is disabled, messages or the device are deleted, or the link is revoked, and cannot be guaranteed to be recalled.

Cloud hosting and email providers process necessary information for infrastructure, mail delivery and security. We use Alibaba Cloud Direct Mail to send a notification copy only when a mail parameter is supplied; it processes the recipient address, title, full body and necessary delivery metadata. We require entrusted providers with access to user information to offer equivalent protection under this policy and applicable law, limit purposes and access, and refrain from independent marketing. Apart from these services, your separate authorization or legal obligations, we do not disclose your personal information to third parties. Legally required disclosure is limited to necessity.

Apple, your chosen automation platforms or email providers may process information outside your country or region; also review their privacy notices. We will meet applicable requirements for separate consent or other safeguards where required.

4. Retention and deletion

Device identity remains for continued service until its deletion is completed. Updating or invalidating an APNs token does not delete the entire identity. Normal server message reading and delivery are available for 3 days from creation. An optional recipient address and its mail claim/completion/result state are stored with the message and removed in the same cleanup window. Mail is attempted once; an ambiguous SMTP result is not retried automatically, and a copy already submitted to the provider cannot be recalled. Deleted message content and sync state may remain briefly to prevent deleted messages from reappearing and to support undo. Expired messages and deletion records are removed by a task running every 10 minutes; failures or downtime may delay physical removal until recovery. This is not a promise that every physical copy is deleted at exactly 72 hours.

Local copies remain until you delete them, clear them or remove app data. Uninstalling normally removes app storage, but Keychain or system backups may retain information according to system behavior and device settings. Uninstalling does not delete server data.

Message-associated caller IP addresses and request headers use the same 3-day business-access window as the message and are deleted by the same scheduled cleanup; failures, downtime and backups have the same limitations described above for server messages. Separate rate-limit counters expire after a 60-second window. Redacted diagnostic logs are grouped by date and deleted by scheduled retention controls within a maximum of 30 days; they may be removed sooner when no longer needed. Diagnostics are not used for unrelated purposes.

Support correspondence is retained while needed to respond, verify and execute requests and resolve necessary disputes. You may request email deletion; we explain any legally required retention. Necessary recovery backups are access-restricted, not used for routine queries, marketing or notification replay, and cleaned up when no longer required. Deletion requests also examine relevant copies; deletion in the business database does not mean simultaneous removal of all backup or third-party copies.

5. Choices and privacy rights

Use iPhone Settings → Notifications → NotifyMe to disable notifications or adjust previews, sound and Lock Screen display. Successful device registration provides your private link without notification permission or an APNs token. With system alerts off, open the app, return to the foreground, enter Messages or refresh manually to retrieve messages from the last three days; automatic background retrieval and real-time alerts are not promised. If you later enable notifications and bind a token successfully, newly received messages can also trigger APNs alerts. Messages received without a binding are not pushed later. Permission changes do not replace your installation identity or private link. Disabling permission does not stop external scripts or delete cloud data.

You can delete or clear messages in the app. Deleted message content and sync records may remain for sync or undo until cleanup; undo does not restart stopped reminders. Clearing messages does not delete device identity or disable the link. Resetting the Push Code prevents new pushes to the old link but keeps existing messages; update your scripts.

For complete deletion, open Settings → Reconfigure Push in the app and confirm. This deletes the current device identity and associated cloud messages and reminders, and clears the local identity and messages. Once the operation succeeds, the previous push link stops working immediately. Notifications already submitted to Apple may still arrive. Rely on the app's success result; uninstalling, reinstalling or a failed network request is not confirmation of deletion.

For access, correction, a copy, or help with a lost credential or failed deletion, use Contact Support in the app or email mail@yeyeye.vip. We verify ownership only as necessary and explain the outcome or inability to fulfill a request. Normal complete deletion in the app does not require contacting support first.

You may withdraw notification permission, stop scripts, request deletion, or exercise applicable rights to restriction or complaint. Withdrawal does not undo completed processing; in-flight notifications, information needed for privacy requests and legally required retention remain subject to this policy. Never send passwords, full credentials or APNs tokens. After credential loss, a new identity cannot establish ownership of old data or guarantee old-code revocation; contact us for feasible verification. We will not request unrelated information.

6. Security, children and updates

We use HTTPS, access controls and credential hashes. Notifications are not end-to-end encrypted: the service and APNs process their content, and no network service can guarantee absolute security. Anyone holding your private link may send notifications. Keep it private and reset it if exposed. Notifications may appear on the Lock Screen or in Notification Center; do not send passwords, verification codes, keys, health information or other sensitive or confidential content.

The app is for developers and automation users, is not directed at children and does not knowingly seek children's personal information. Guardians may contact us for appropriate deletion or protection after verification.

We update this policy and its effective date when practices change, prominently notify material changes in the app or on this page and obtain separate consent when required. A policy update alone does not authorize unrelated new uses of existing information. Contact mail@yeyeye.vip. This policy and the support page are public without login, notification permission or a Push Code.