Kiwi Kiwi Notifications Notice
Last updated: September 26, 2026
1. Notification choices
Kiwi Kiwi provides six separate preferences for visible push alerts: Tokens received, Tokens returned, Tokens ready to revoke, New matches, New messages, and Account & service alerts. Each preference controls its category rather than all notifications. Account & service alerts include supported account events such as a confirmed refund.
Your phone’s operating-system permission separately controls whether visible notifications can appear on that device. The app shows the device permission state and lets you open device settings or request permission when available. Disabling device permission preserves your saved account choices; it does not replace them with different choices.
2. What disabling alerts does not change
Turning a category off suppresses its optional visible push alerts. It does not stop tokens being received or returned, prevent a match or refund, delete a message, or remove account history. Required information may still appear inside the app, and the app may still synchronize state, unread indicators, or badges.
You can use Kiwi Kiwi without granting visible push permission. However, you may not promptly learn about an event unless you open the app. Re-enabling notifications does not promise delivery of every earlier missed alert.
3. Device and delivery information
We process push-registration identifiers, platform, app version/build, limited device information, active/inactive status, and delivery or cleanup records needed to send and route notifications, maintain registrations, and diagnose errors. A registration identifier is not an advertising permission.
We use notification service providers as described in the Privacy Policy. Account access and the current interaction’s permissions still determine what a notification tap can open; receiving a notification does not grant access to otherwise unavailable content.
4. Lock-screen privacy
Depending on your device settings, alerts can appear on a lock screen. Notification copy may identify an event and, for supported notices, another member’s displayed name. Keep device previews private when appropriate.
We limit payloads and do not intentionally include raw message text, private notes, precise coordinates, detailed verification results, private report details, secret credentials, or detailed payment proofs. A brief alert does not contain the entire underlying account record.
5. Delivery limits
Alerts can be delayed, dropped, duplicated, or suppressed by network conditions, operating-system behavior, battery settings, permissions, service outages, or technical interruptions. Delivery and correct tap routing are not guaranteed.
Do not rely on push alerts for emergencies or as the sole way to learn about a time-sensitive legal or account matter. An alert’s absence does not prove that the underlying event did not occur.
6. Sign-out and deletion
On sign-out, the app attempts to unregister or deactivate its notification registration. A network interruption can delay that step. Account deletion removes the account’s notification eligibility and cleans up registrations through the deletion lifecycle. A notification already sent to a device may remain there until dismissed or removed by the device.
7. Service communications
A disabled push preference is not permission to bypass that choice with the same visible push category. Necessary legal, account, privacy, support, or transactional information may still be shown in the app or delivered through another channel when lawful and required or appropriate.
This version does not introduce a marketing-push category. Future marketing communications must use the notices, permissions, and opt-out methods that apply to them; ordinary token or service permissions are not a blanket marketing consent.
Questions may be sent to support@kiwikiwi.dating.