Summary
Rebot is an interactive AI robot companion. It uses your camera and microphone only when you enable related features. On-device face detection may briefly read momentary expression cues so the robot can visually mimic your emotions; body pose detection may estimate your movements for motion mini-games. Face and pose signals are processed only on your device, are not recorded or retained, and are never shared with third parties (see Camera). Speech input may be processed by the operating system’s speech recognizer on-device or according to your platform’s rules. The App may show ads through Google Mobile Ads; those networks may use identifiers described below. We use Firebase Analytics for limited, aggregate usage signals (such as app opens and session activity) primarily to support ad delivery — not to collect the content of your voice, chat, or camera. ReBot Friends and ReBot Links let mutually accepted friends send encrypted in-app messages; message contents are not permanently stored on our servers (see Data Retention). We do not sell your personal information.
Controller
The publisher identified on the App Store and Google Play listing is responsible for this Policy and for answering privacy inquiries submitted through the contact channels listed in those stores.
Permissions & how they work
The App requests access only where needed for features you use. Denying a permission may disable specific functions but does not necessarily block the entire App.
Camera · iOS (NSCameraUsageDescription) & Android (android.permission.CAMERA)
Purpose. The live camera preview powers on-device face detection, full-body pose detection, reactive robot animations, optional selfie or video flows you start yourself, and related vision features described below. Camera access is used only while you actively use those features.
Operation. Video frames are analyzed on your device. The App does not upload your camera feed to our servers for face or pose features. Optional media you deliberately capture (for example a selfie) stays on your device unless you choose to share it outside the App yourself.
Control. You can grant or revoke camera access in system Settings at any time. Revoking camera permission immediately stops face detection, body pose detection, and other camera-based features.
Face detection (face data)
Collection & intended use. When you enable mimic or other face-reactive modes, the App runs on-device face detection on the live camera stream. It reads only momentary, frame-by-frame signals such as facial landmarks and expression cues so the on-screen robot can visually mimic your emotions and head movements in real time. This is not facial recognition, biometric identity matching, face templates for login, or user identification of any kind. Face data is not used for advertising, analytics profiling, Friends messaging, AI chat prompts, or any other purpose beyond driving the robot’s live visual reaction while the feature is on.
Sharing. Face data is never shared with third parties, affiliates, cloud AI providers, advertising networks, analytics services, or other users. Because face data is not shared with any third party, no third-party transfer of face data occurs under this Policy.
Retention. Face data is processed ephemerally in device memory for the current frame (or a short in-memory buffer needed for the live animation). The App does not record, save, archive, or upload face images, face scans, expression histories, or biometric face templates to disk, our servers, or any external service.
Deletion & revoking consent. Because face data is not stored, there is no separate face-data archive to delete after a session ends. You revoke consent for collection or use of face data by turning off the mimic / face-reactive feature and/or denying or revoking Camera permission in system Settings. Closing the feature or leaving the related screen stops processing immediately. Uninstalling the App removes any remaining local App data from the device; no face data remains on our servers because none was ever uploaded.
Body pose detection
Collection & intended use. In motion and camera mini-games, the App may run on-device body pose detection to estimate skeletal keypoints (for example limbs and torso) from the live camera stream. This is used only to determine your in-game movements and gestures so gameplay and robot reactions can respond in real time. Pose detection is not used to identify you or to build a biometric profile.
Sharing. Pose data is never shared with third parties, cloud services, advertising networks, analytics providers, or other users.
Retention. Pose data is processed ephemerally on the device for the live game or feature session and is not recorded, saved, or uploaded.
Deletion & revoking consent. Stop the game or feature and/or revoke Camera permission in system Settings to end pose processing. No stored pose archive exists on our servers to delete.
Microphone · iOS (NSMicrophoneUsageDescription) & Android (RECORD_AUDIO)
Purpose. Captures your voice for speech recognition, spoken commands, robot voice interaction, and other audio-driven features you activate.
Operation. Audio is used while you use voice features. Recording does not run continuously in the background unless you explicitly start a recording-related command supported by the App.
Control. Revoke microphone access in system Settings to disable voice capture.
Speech recognition · iOS only
Purpose. Converts spoken words to text so hands-free commands and assistant chat can work.
Operation. On supported devices, Apple’s speech recognition may process audio according to Apple’s privacy policies. The App uses this capability only when you invoke voice input.
Control. Manage Speech Recognition under iOS Settings for this App.
Location when in use · iOS (NSLocationWhenInUseUsageDescription)
Purpose. Some bundled camera or media SDKs may request approximate location metadata when optional tagging features are enabled.
Operation. If requested, location is read only while you use the App and only when a relevant library prompts for it. Core chat and most robot features do not require location.
Control. You can deny location; remaining features continue where possible.
Notifications · iOS & Android
Purpose. On both platforms, the App can show local reminders or alerts (for example alarms or reminders you configure) and, if you use ReBot Friends, deliver friend-request and message alerts through Firebase Cloud Messaging (FCM).
Operation. On iOS, you are prompted for notification permission in system Settings; remote alerts use Apple Push Notification service (APNs) via FCM (remote-notification background mode). On Android, Android 13 and newer require the POST_NOTIFICATIONS runtime permission; notifications use the system notification channel after you grant it. Friend-related push details are in Push Notifications below.
Control. Disable notifications for Rebot in iOS or Android Settings. You can also turn off incoming friend requests inside the App.
Network · Android (INTERNET) / iOS networking
Purpose. Enables AI chat, weather and web-backed commands, ad delivery, and optional cloud APIs you trigger.
Operation. Data sent over the network depends on the feature used (for example a chat message to an AI provider). Use features only if you agree to those providers’ terms.
On-device storage & Apple-declared APIs
The App stores preferences and session-related data locally (for example via platform storage APIs) so commands, UI language, and companion behavior persist between launches.
Taught commands. When you use the teach feature (brain icon), trigger phrases, linked tasks, and optional custom voice replies are saved only on your device (up to 30 entries per install). This data is not uploaded to our servers by default.
The iOS privacy manifest (PrivacyInfo.xcprivacy) declares reasons for accessing restricted APIs such as User Defaults, system boot time, disk space, and file timestamps. These are used for normal app operation—for example configuration persistence, diagnostics/time handling, and cache management—and not for tracking users across other companies’ apps or websites.
Firebase Analytics
The App integrates Google Firebase Analytics on iOS and Android (via the Firebase SDK configured with google-services.json / GoogleService-Info.plist).
What we use it for. We collect limited analytics and usage data — for example when the App is opened, how long a session runs, and similar aggregate load/activity signals. We use this information primarily to support ad delivery through Google Mobile Ads (AdMob), such as measuring impressions and keeping the ad experience functional. We do not use Firebase Analytics to read or store the text of your messages, voice recordings, camera video, or taught command phrases.
What we do not do. Analytics is not used to build a marketing profile of you beyond what Google’s ad and measurement stack requires for serving ads. We do not sell analytics data to third parties.
Third-party processing. Data processed by Firebase is subject to Google’s Firebase Privacy and Security documentation and Google’s privacy policies. You can limit ad personalization or reset advertising identifiers in your device settings (where your platform provides those controls).
Advertising
Rebot may display advertisements through Google Mobile Ads (AdMob). Ad networks may use advertising identifiers and collect usage signals subject to Google’s policies. Firebase Analytics (above) helps provide session and launch-related measurement that supports this ad stack. The App’s AdMob configuration is tuned toward family-friendly content ratings and limited ad personalization where applicable; review Google’s disclosures for details.
AI providers
When you use AI chat or related cloud features, your prompts and responses may be transmitted to third-party AI services configured in the App (for example OpenAI or Google). Those transmissions are governed by the respective provider’s privacy policy. Do not submit secrets or highly sensitive personal data through chat.
Friends
ReBot Friends is an optional, in-app social layer that lets you connect with other ReBot users you know. Friendship requires mutual acceptance — neither side can message the other until both have agreed.
- Each install receives a ReBot ID (for example
RB-…) used to send or receive friend requests. - You may assign a local nickname to a friend. Nicknames you set are stored on your device only and are not uploaded as a separate profile field.
- Your optional settings nickname and public DNA summary (level, title, XP) may be visible to accepted friends when profiles sync — not to the public internet at large.
- ReBot Friends is not a public social network, feed, or open messaging platform. Only people who are already your accepted friends can send you ReBot Links through this system.
Friend Requests
To add a friend, you enter their ReBot ID or open their profile link inside the App. The other person receives a request and must accept before messaging is enabled.
- You can disable incoming friend requests in the Friends screen. When off, new requests are not added to your list (and related push alerts are not processed).
- Request metadata (sender and recipient ReBot IDs, a display label, and request status such as pending, accepted, or declined) may be stored on our backend so requests can sync across reinstalls and devices tied to the same ReBot ID.
- We do not use friend requests to collect message contents, camera data, or AI chat transcripts.
ReBot Links
ReBot Links are encrypted deep links that carry robot actions or short messages (text, voice-style replies, tasks, and similar payloads) from one ReBot user to another.
App-only opening. ReBot Links only open inside the ReBot app. They are designed for universal links / app links on supported platforms. A web preview page may show a generic card image and prompt you to open the App; the payload is decrypted on the device after the App receives the link.
Not public sharing. This is not a public posting or broadcast system like social media. Links are intended for private, friend-to-friend delivery. Only accepted friends can send you ReBot Links through the Friends messaging flow.
Encryption. Link payloads are encrypted before sharing. Our servers and notification relays handle the encrypted URL and limited preview metadata — not readable message bodies stored as plain text in a central inbox.
No cloud backup of your inbox. ReBot Links received in your Friends inbox are kept in local app storage on your device. They are not designed to be restored from a server-side message archive.
Push Notifications
When you enable notifications and use ReBot Friends, the App may receive push messages through Firebase Cloud Messaging (FCM) for:
- Incoming friend requests and accept/decline updates
- New ReBot Link messages from accepted friends
- Optional URL-open actions you trigger through supported push types
Push payloads typically include the sender’s ReBot ID, a short display label, an encrypted ReBot Link URL, and sometimes a brief preview string for the notification banner. Tapping a notification opens the App and plays or displays the linked content locally.
We do not use friend push notifications for advertising. You can turn off notifications in system Settings and can stop new friend requests inside the App.
How Messages Are Delivered
When you send a message to a friend:
- The App builds a ReBot Link with your message or action payload and encrypts it on your device.
- The encrypted link is sent to our backend, which forwards a push notification to your friend’s device (or stores a broadcast entry friends can fetch later, depending on the send path).
- Your friend’s App receives the notification, saves the link reference locally in their Friends inbox, and decrypts the payload only when they open it inside ReBot.
- The robot then speaks or performs the linked action on your friend’s device — still entirely inside the App.
Direct friend messages are not delivered to non-friends. There is no global “anyone can message anyone” directory.
Data Retention
Message Content Retention
ReBot message contents are delivered through automatically encrypted ReBot Links. The contents of these links are not permanently stored on our servers as readable chat history. Users may choose to keep messages locally on their own devices in the Friends inbox until they delete them or remove the app.
Our backend may temporarily retain:
- The encrypted link URL and a short preview snippet (for notifications or friend-profile sync)
- Friend-request records (IDs, status, timestamps) until the request is accepted, declined, or cleared
- Device push tokens and ReBot IDs needed to deliver notifications
When you delete a message from your local inbox, it is removed from your device. Deleting the App removes locally stored friends, nicknames, and inbox entries unless your platform restores app data from its own backup.
Other app data
Preferences, taught commands, companion settings, and charge-session timers remain on-device as described in On-device storage. Firebase Analytics retention follows Google’s policies. Ad-related identifiers follow Google Mobile Ads / AdMob rules. Face data and body pose data from camera features are not retained after real-time processing (see Face detection and Body pose detection).
Blocking & Removing Friends
- Decline or dismiss an incoming friend request to prevent that person from becoming a friend until they send a new request (after you clear a declined entry where applicable).
- Remove a friend from your Friends list to delete the local friendship record and inbox history for that person on your device.
- Turn off incoming requests to stop receiving new friend-request notifications and list entries.
- Removing or declining a friend stops new ReBot Links from that relationship on your device. It does not delete another user’s local copy of messages they already received.
There is no separate public profile page where strangers can comment or message you outside the mutual-friend flow.
Children
The App is not directed to children under 13 (or the minimum age required in your region). Advertising-related flags may indicate heightened protections for younger audiences where configured; parents should supervise minors’ use of cameras, microphones, and network features.
Security
We rely on platform sandboxing, encrypted ReBot Link payloads, and standard secure transport (HTTPS/TLS) for remote calls. Sensitive friend message bodies stay inside encrypted links rather than plain-text server logs. See Data Retention for how long different categories of data are kept.
Your choices
- Use system Settings to grant or revoke Camera, Microphone, Speech Recognition, Location, and Notifications.
- Revoke Camera access (or leave mimic / motion-game screens) to stop all face-data and body-pose processing; see Camera.
- Limit AI features if you prefer not to send text to external providers.
- Disable incoming friend requests or remove friends in the Friends screen.
- Delete individual inbox messages or uninstall the App to remove locally stored app data from your device.
International users
If you use the App outside your home region, information may be processed where servers or providers operate. By using networked features, you acknowledge cross-border processing where applicable.
Changes
We may update this Policy when features or regulations change. The effective date at the top will be revised; continued use after updates means you accept the revised Policy unless applicable law requires additional consent.
Contact
For privacy questions, contact the developer using the support email or form shown on the App Store / Google Play listing.