Notifications and Chat Actions
AI72 uses notifications and chat actions to support introduction flows, permanent chats, safety/system status, and user controls. This document explains push notifications, notification previews, foreground/background behavior, notification actions, temporary intro actions, permanent chat actions, and Shared Media behavior.
1. Notification philosophy
Notifications are meant to inform users about important product events when they are away from the app and to provide quick actions inside the app without exposing unnecessary private content. AI72 does not design notifications to manipulate users, create constant interruption, or disclose hidden content.
2. Push notifications
AI72 may send push notifications for permanent chat messages, introduction-cycle/IntroMe updates, safety, account status, and system announcements. AI72 may process push tokens, install id, device/platform data, app version, locale, timezone, notification permission status, match notification preference, general notification preference, and message preview preference.
- Push notifications require operating-system permission and a valid push token.
- If system permission is off, AI72 cannot force it on.
- Delivery depends on Apple, Google, Firebase/FCM, device connectivity, battery restrictions, network conditions, and user settings.
3. Notification preview
Message previews are privacy-first. Message previews may be off/private by default. When previews are off, push notifications may use generic wording and may not show message text or sender profile photo. When previews are enabled, sender name, profile photo, and message content may appear on the lock screen or in the notification center.
4. Foreground notifications
When the app is open, some push alerts may not appear as system notifications. The app may instead use in-app banners, unread badges, navigation intents, or chat state updates. Permanent chat in-app banners may offer quick reply, read, and like actions where supported.
5. Background notifications
When the app is in the background or closed, a push notification may be shown by the device. Tapping the notification may route the user to an IntroMe/introduction surface or the relevant permanent chat. Routing depends on data payload, chat id, message id, and app state.
6. Silent or data notifications
Where platforms allow it, some notifications may be data-only, badge, token-refresh, navigation, or sync related and may not show a visible alert. Behavior may vary by device, operating system, Firebase/FCM, Apple/Google platform rules, and app state.
7. Notification permissions
Notification permission is controlled by the device operating system. AI72 may request permission or show permission state in the app, but final permission depends on device settings and platform rules.
- Users can disable system notification permission in device settings.
- AI72 may provide in-app preferences such as introduction notifications, general notifications, and message previews.
- If device permission is off, push notifications may not arrive even if in-app preferences are on.
8. Notification actions
On supported platforms, permanent chat notifications or in-app notification banners may offer actions such as Open, Dismiss, Reply, Mark as Read, and Like. These actions may not be available on every device, every message type, or every app state.
- Reply may send a text message and attach reply context to the referenced message.
- Mark as Read may update chat read state.
- Like may update message reaction state.
- Open may route to the relevant chat or introduction surface.
- Dismiss may only close the notification; it does not delete the message or chat record.
- Native notification actions may pass through backend authentication, legal consent, chat ownership, and message id checks.
9. Temporary Intro actions
Temporary Intro is a limited, lifecycle-controlled introduction session. User actions or system state may trigger pass, leave, expire, reject, accept, reveal, blur, clear photo access, signed URL access, and timeout behavior.
- Pass or leave may end the session or return the user to the pool.
- Expire or timeout may happen because of network, lifecycle, foreground/background, peer offline, or product-rule conditions.
- Blur/clear photo reveal depends on session state, role, product rules, safety checks, signed URL, and timeout conditions.
- A signed URL provides temporary access; it is not a permanent download, sharing, or archiving right.
10. Permanent Chat actions
Permanent Chat is a longer communication area opened after product rules and offer/acceptance flows. Permanent chat may include typing/activity, delivered/read state, text, translation, TTS, voice, photo, video, media, location, Shared Media, reply, like/reaction, star, copy, report, block, mute, pin, archive, clear/delete for me, delete for everyone/unsend, and end chat actions.
- Delete for me or clear may affect only your view; it does not automatically delete the other user’s view or safety/legal records.
- Delete for everyone/unsend may retract a message where supported, but audit, safety, report, backup, or legal records may not be immediately deleted.
- Report and block are governed by the Moderation and Reporting Policy.
11. Notification privacy
Notifications can contain sensitive information. If message previews are enabled, content may appear on the lock screen, connected devices, or operating-system notification history. Users should keep previews off when they need more privacy.
12. Shared Media behavior
Shared Media is an in-app convenience surface for revisiting eligible photos and videos sent in a permanent chat. Private, deleted, expired, disabled, restricted, report-quarantined, or moderation-removed media may not appear in Shared Media.
- Shared Media does not grant a right to download, save to gallery, screenshot, screen record, or re-share media.
- Media access may depend on signed URL, session state, moderation state, sender action, product rules, and legal/safety retention requirements.
13. Device behavior
Offline, reconnect, retry, failed delivery, and expired notification behavior may vary because of network, device, operating system, Firebase/FCM, Apple/Google services, app state, and backend state. A notification may be delayed, never arrive, expire, or point to content that is no longer accessible when opened.
14. Notification safety
Notifications may be limited to protect safety and privacy. AI72 may use open-only or generic notification text for media, voice, private media, location, or sensitive content. Some notifications may not be sent because of safety, abuse, block, mute, report, moderation, or legal reasons.
15. User controls
Users may control device notification permission, introduction notifications, general notifications, message preview, chat mute/unmute, block/report, permanent chat end/delete/clear, and account deletion. Some controls are managed in the app, while others are managed in device settings.
16. What AI72 does not guarantee
AI72 does not guarantee that notifications will always arrive, arrive on time, appear on the correct device, complete every action successfully, apply preview settings identically in every operating-system context, or prevent external recording of media. AI72 does not present notification generation as an AI decision system and does not claim E2EE, screenshot prevention, or absolute media protection.
17. Linked documents
This document should be read with the Terms of Service, Privacy Policy, Community Guidelines, Safety Center, AI and Automated Processing Disclosure, Moderation and Reporting Policy, Account and Data Deletion, Data Safety and Permissions, and Support documents.