FeiEgg App Privacy Policy
Application name: FeiEgg Operating entity: Chengdu Lanchuang Wisdom Technology Co., Ltd (hereinafter referred to as "we", "us" or "our") Date of update: July 24, 2026 Date of effectiveness: July 24, 2026
Special notice: Please read this Policy carefully before using the FeiEgg App (hereinafter referred to as "this Application"). By clicking to agree or by commencing use, you indicate that you have understood and agreed that we may process personal information in accordance with this Policy.
This Policy describes only the capabilities actually provided as of the current date by this Application's client and its supporting backend (the app service). Sensitive system permissions are all requested when you use the corresponding function and are not enabled by default. Before your first launch of the Application and your agreement to this Policy, the client will not initialise any third-party business SDK, nor will it initiate any business-type network request (except for the loading of pages for the purpose of displaying this Policy / the User Agreement). You may review this Policy, the List of Personal Information Collected and the List of Third-Party Information Sharing again under "Settings" and "About".
I. How We Collect and Use Personal Information
All of the collection items set out below correspond to existing business functions such as registration and login, profile, conversation, payment and hardware control; you may refuse to provide non-essential information, but you may then be unable to use the corresponding functions.
1.1 Account Registration and Login (Essential)
- Mobile phone number: used for registration, login, password retrieval/reset and security verification. The verification code is delivered through an SMS service.
- SMS verification code / login password: used for identity verification. The password is stored and transmitted in a secure manner and is not retained in plain text.
- Login session credential (Session / Access Token): used to maintain login status and for interface authentication.
- Network and client information at login: IP address, User-Agent (browser/client identifier), used for session security and protection against anomalous logins.
Currently supported by the client: registration/login by "mobile phone number + SMS verification code", login by "mobile phone number + password", and forgotten password (reset via SMS verification code). Currently not provided by the client: carrier one-click login and third-party account login such as WeChat/Google/Facebook.
1.2 Personal Profile (Non-essential, Where You Voluntarily Provide It)
The backend user profile fields include: nickname, gender, sexual orientation, avatar URL, personal bio, date of birth, etc. These are used for the personal homepage and interactive display. Failure to complete them does not affect basic login. The nickname, avatar and similar items may be subject to content security review.
1.3 AI Conversation, Characters, Scenarios and Content Generation
- When you use functions such as AI conversation, character interaction and scenarios/theatre, we will submit the text you actively input, as well as voice content generated after you authorise the microphone (the recognised text or the audio stream), to AI / voice-related services, in order to generate replies, complete the interaction and carry out necessary security processing.
- Function usage, error logs and session-related identifiers may be recorded, for purposes such as stability and billing (for example, voice is charged in points per minute).
- AI output is generated by algorithms and may be inaccurate; it does not represent our position. Please do not input the sensitive personal information of others.
1.4 Smart Hardware Bluetooth Control
Device scanning, binding, remote control and synchronised control are carried out on the client via Bluetooth. Technical information such as device name, connection status and control commands may be processed. This is not used for map navigation, trajectory tracking, or annotating the geographical location of published content. The Android system may require location permission when scanning for Bluetooth devices; that permission is used solely to discover nearby Bluetooth devices.
1.5 Real-Time Voice Calls and Speech Recognition / Synthesis
When you use functions such as voice calls, voice control and voice messages, after you authorise the microphone, the audio stream will be transmitted through a real-time audio and video service, and speech recognition (ASR) and speech synthesis (TTS) capabilities may be invoked. No continuous background recording takes place after you stop using the function.
1.6 Camera, Photo Album and Local Media
- Camera: scanning device QR codes, taking avatars, etc.
- Photo album/storage (where you actively make a selection): selecting an avatar or images, or selecting local video/audio for local linkage control, etc.
- Files such as avatars are uploaded to object storage, which returns an access URL; the upload process may include content security review.
- The current version does not provide a system screen recording / screen sharing business function.
1.7 Payments and Virtual Goods
When you purchase points, memberships, etc., we process: the order number, product/package information, amount, payment method, payment status, and the necessary identifiers returned by the payment channel. The Android client currently connects to Alipay and WeChat Pay; the iOS client may connect to Apple In-App Purchase. The payment password and bank card number are processed by the payment institution; we do not collect complete bank card numbers or payment passwords.
1.8 Community and Social Features (Where You Use the Relevant Functions)
If you use community posting/commenting/liking/favouriting/reporting, or social/instant messaging-related functions, we will process the content you actively publish or send, your interaction relationships and conversation messages, in order to implement the corresponding functions. The instant messaging capability is provided by the instant messaging SDK integrated into the client.
1.9 Device and Operating Logs
- Device model, operating system version, application version number;
- Network status (whether connected to the network, network type, etc.);
- Device identifiers within the range permitted by the system (such as Android ID; iOS identifierForVendor, etc.), used for security and compatibility;
- Operation logs, crash/error logs, interface request status, etc.
The current version does not proactively request READ_PHONE_STATE and does not collect information for the purpose of reading call content; it does not request the permission to read the full list of installed applications for business purposes.
1.10 Message Notifications
After you authorise the notification permission, the client may display system notification-type reminders. On the business side, events may also be delivered to the client through the server-side push channel of the logged-in session (such as SSE). You may turn off notifications in the system settings.
II. Description of Operating System Permissions
The following are the permissions that the client may currently request or that may be merged in by plugins. Capabilities not listed here (such as reading phone state to obtain the IMEI, background location, system floating windows, screen recording via MediaProjection, reading the full list of installed applications, etc.) are not requested in this version or are not used for business purposes.
2.1 Android
| Permission | Purpose and scenario of use |
|---|---|
| INTERNET / ACCESS_NETWORK_STATE / ACCESS_WIFI_STATE / CHANGE_NETWORK_STATE, etc. | Accessing the backend and third-party services, and determining network status. |
| BLUETOOTH / BLUETOOTH_ADMIN (lower versions) BLUETOOTH_SCAN / CONNECT / ADVERTISE | Searching for and connecting to smart hardware; advertising is used for discovery related to synchronisation/remote control. Not used for location tracking. |
| ACCESS_COARSE_LOCATION / ACCESS_FINE_LOCATION | Used solely for Android Bluetooth scanning to discover nearby devices; not used for LBS posting, maps or trajectories. |
| RECORD_AUDIO / MODIFY_AUDIO_SETTINGS | Voice calls, voice control, voice messages; audio settings related to calls. |
| CAMERA | Scanning codes, taking avatars, etc. |
| READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE (and the system photo picker capability) | Where you actively select images/local media; caching or saving necessary files. |
| POST_NOTIFICATIONS | Notification reminders on Android 13+. |
| FOREGROUND_SERVICE / WAKE_LOCK / VIBRATE, etc. | Basic operation and alerts for calls, playback, connections, etc.; excludes screen-recording-type MediaProjection. |
2.2 iOS (Privacy Usage)
| Permission key | Purpose and scenario of use |
|---|---|
| NSBluetoothAlwaysUsageDescription / NSBluetoothPeripheralUsageDescription | Connecting to and controlling smart hardware. |
| NSMicrophoneUsageDescription | Voice calls, voice control and voice interaction. |
| NSCameraUsageDescription | Taking avatars, scanning codes, etc. |
| NSPhotoLibraryUsageDescription / NSPhotoLibraryAddUsageDescription | Selecting or saving images, etc. |
III. Cookies and Local Storage
In order to maintain login status, cache necessary data and ensure security, the client may use SharedPreferences, a local database, secure storage, etc. These are not used for any purpose other than those stated in this Policy. After clearing the application data, you may need to log in again.
IV. How We Share and Entrust the Processing of Personal Information
4.1 Principles
- We will not sell your personal information.
- We entrust or share necessary information only where this is essential to implement a function, to perform a statutory obligation, or where your consent has been obtained.
- Each of the third parties listed below corresponds to a service currently configured on the backend or already integrated into the client; the specific processing rules are governed by their published policies.
4.2 List of Third-Party Services
Apart from the display of agreement pages, the following services are invoked only after you have agreed to this Policy, or when you actively use the corresponding function.
| Service | Purpose (consistent with the live environment) | Information that may be involved | Notes / Policy |
|---|---|---|---|
| Volcengine SMS | Registration/login/password reset verification codes | Mobile phone number, logs related to verification code delivery | Volcengine privacy statements |
| Large models such as Volcengine / Doubao (Ark) | AI conversation, character and content generation | The text you input and the context necessary to implement the conversation | Volcengine |
| Volcengine RTC | Real-time voice calls, audio transmission | Device and network information, audio stream, room/session identifiers | Volcengine RTC statements |
| Volcengine ASR | Speech-to-text | Audio or audio URL, recognition results | Volcengine ASR statements |
| TTS services such as MiniMax | Speech synthesis and playback | Text to be synthesised, technical data related to the synthesised audio | Governed by the service provider's published policy |
| Agora RTC (Shengwang Agora) | Real-time audio in certain voice call scenarios | Device and network information, audio stream, channel identifiers | Agora Privacy Policy |
| Microsoft Azure Speech | Speech recognition on the client, etc. | Audio clips captured while you use the function, device and network technical information | Microsoft Privacy Statement; may involve overseas processing — please do not use this function if you do not consent |
| Alipay | In-app payment | Order and payment result, device/network information (SDK) | Alipay statements |
| WeChat Pay | In-app payment | Order and payment result, device/network information (SDK) | WeChat Privacy |
| Apple In-App Purchase | iOS in-app purchase and receipt verification | Transaction identifiers, receipts and other payment verification information | Governed by Apple's rules |
| Qiniu Cloud Object Storage (S3-compatible) | Storage of and access to files such as avatars and images | Uploaded files, access URLs, device/network and access logs | Qiniu Privacy Policy |
| Alibaba Cloud Content Moderation | Content review of nicknames, avatars, comments, etc. | The text/images awaiting review, etc. | Alibaba Cloud privacy and product statements |
| Tencent Cloud Instant Messaging IM | Social/private messaging and other instant messaging (if you use this module) | Account identifiers, messages, device and network information | Tencent Cloud IM statements |
In addition: basic components such as the Flutter engine, networking libraries and local databases are used solely for application operation and local caching.
4.3 Transfer and Public Disclosure
We will not transfer or publicly disclose your personal information, except where this is required by law in cases such as merger or acquisition and a level of protection no lower than that of this Policy is ensured, or where your consent has been obtained, or where laws and regulations provide otherwise.
4.4 Circumstances in Which Consent Is Not Required Under Law
Where this relates to circumstances provided for by laws and regulations such as national security, public security, criminal justice, emergency rescue, information you have made public yourself, or legally public sources of information, the relevant information may be processed in accordance with law.
V. Storage Location and Duration
- Storage: accounts, orders and business data are processed by services we deploy within the territory; object storage uses a Qiniu Cloud domestic region. When services of overseas entities such as Azure Speech are used, the relevant audio may be processed overseas in accordance with their rules, as detailed in 4.2.
- Duration: information is retained for the period necessary to achieve the purposes of this Policy; after account cancellation, the relevant information will be deleted or anonymised (unless laws and regulations provide otherwise). Session information (including IP and User-Agent) is managed according to the session lifecycle.
VI. Security Protection
We adopt reasonable technical and organisational measures (access control, transmission and storage security, security incident handling, etc.). Please keep your mobile phone verification codes and passwords properly. If a personal information security incident occurs, we will promptly notify you and handle it in accordance with law.
VII. Your Rights
- Access and correction: you may view and edit your personal profile within the application.
- Withdrawal of authorisation: you may turn off permissions such as Bluetooth, location, microphone, camera, photo album and notifications in the system settings.
- Account cancellation: you may apply under "Settings → Cancel Account" (or the cancellation entry in the personal centre). The backend will cancel/soft-delete the account; after cancellation the relevant information will be deleted or anonymised (unless otherwise provided by law).
- Complaints: please provide feedback through the contact details in Chapter XI; we will reply as soon as possible after verifying your identity (generally within fifteen working days).
VIII. Minors
This Application is primarily intended for adults with full civil capacity. Minors should use it with the consent of a guardian. We do not proactively collect children's personal information; if we discover that it has been collected in error, we will delete it as soon as possible.
IX. Policy Updates
We may revise this Policy and publish it within the application. Where material changes are involved, we will obtain your consent again by means such as a pop-up dialog. If you do not agree, please stop using the Application and cancel your account.
X. Scope of Application
This Policy applies to the services provided by Chengdu Lanchuang Wisdom Technology Co., Ltd through the FeiEgg mobile application and its supporting backend. Where a particular service has separate terms, those terms apply together with this Policy; in the event of any inconsistency, the separate terms shall prevail (without lowering the level of protection afforded to you).
XI. Contact Us
Operating entity: Chengdu Lanchuang Wisdom Technology Co., Ltd
Personal information protection contact email: tom@feiegg.com
We will respond promptly after verifying your user identity.