Privacy Policy
1. Scope and responsible company
Product name: MEMOORB. Brand: FLYOKAY. Models: TSM028-BP and TSM028-BG. Both models have the same functions and data processing described in this document.
This policy describes FLYOKAY used with MEMOORB (TSM028-BP / TSM028-BG). The responsible company is Dongguan Tesimai Electronic Technology Co., Ltd.. Address: Room 1801, Building 1, No. 4, Headquarters 2nd Road, Songshan Lake Park, Dongguan, Guangdong Province, China. Privacy and data requests: tesimai01@163.com.
The app edits content and controls the product locally through Bluetooth. It has no cloud account, cloud content storage, advertising tracking, usage analytics or remote crash-reporting service in this operating model. Local data is not automatically uploaded to our company. This does not mean that no data is processed: the phone and product process the data described below.
2. Data processed and purposes
Bluetooth/device data: device name and Bluetooth identifier, signal strength, connection state, model and firmware version. These enable discovery, connection, reconnection and communication. Available operating data includes battery value, motor-speed setting, display position and, on supported firmware, rotation speed.
User content: selected images, text, animations and locally captured media are processed to edit or preview content and create LED display frames. Only content selected for transmission is sent to the product. Where the installed version offers portrait effects, face regions/landmarks and segmentation are processed on the phone for image effects, not to identify a person or build an identity database.
App settings, privacy acknowledgement, drafts, history, cached device content and diagnostic logs support local operation, recovery and troubleshooting. Logs can include timestamps, device identifiers, status values and errors. Technical values can be personal data when associated with an identifiable person.
We do not use IMEI or advertising identifiers for tracking. No user account or contact-list access is required. We do not use the local operating data for advertising profiles, sale of data or decisions with legal or similarly significant effects.
3. Permissions and user choices
Bluetooth/nearby-device permission is used to scan and connect. On Android 11 and earlier, Bluetooth scanning may require the system location permission; the app does not use that permission to obtain geographic coordinates.
Photos/files permission or a system picker is used to import selected media and save creations. Camera permission is requested for capture. Where video recording with sound is available and selected, microphone permission is used for that recording; silent capture does not require audio recording. Permission availability depends on the operating system and installed features.
Optional permissions are requested for the relevant feature and can be withdrawn in phone settings. Refusing one may prevent that feature from working. Reading or accepting these documents is not blanket consent to unrelated processing.
4. Storage, retention and deletion
Settings, drafts, history, cached files and logs are stored in the phone’s app storage. Settings, drafts and caches have no fixed automatic time expiry; they persist until replaced, deleted or app data is removed. The history cleanup routine keeps the latest 50 binary history files; associated files may have a separate lifecycle. The log buffer retains up to 500 entries, with older entries replaced by new ones.
Display content transferred to the product stays in device memory until deleted or overwritten through supported controls. Current status values are refreshed rather than kept as a complete continuous history. Uninstalling the app does not delete content stored on the product.
Delete saved works through app history and device content through its delete action while connected. Phone app data can be removed through the operating system’s app-data/uninstall controls. Exported files and system backups must be managed separately; their retention depends on your settings and the relevant provider. We cannot remotely erase copies held only on your phone or product.
Support correspondence and attachments are retained while needed to handle and follow up the request. Any further retention is limited to what is necessary for applicable legal duties or the establishment, exercise or defence of claims. When those purposes cease, the information is deleted or anonymised. There is no fixed day-based retention promise; the determining criteria are request completion, necessary follow-up, and applicable legal/claims periods.
5. Support email, webpages and recipients
If you contact tesimai01@163.com, we receive your email address, message and any attachments you choose to send. We use them to respond to enquiries, provide after-sales assistance and handle data requests. Providing only the necessary information is sufficient; please avoid sending unrelated personal data. Without the information needed to understand a request, we may be unable to resolve it.
Our company handles support in China. The 163 mailbox is supplied by NetEase; email delivery and storage involve the mailbox providers. Online legal pages hosted on GitHub Pages involve GitHub and may process connection data such as IP addresses and request information under the host’s own privacy notice. These are separate from automatic product telemetry. The bundled legal pages can be read without opening the online site.
Access to correspondence is limited to personnel and service providers who need it for the stated purpose, and authorities where disclosure is legally required. We do not automatically share local device content with these providers. Sending support email is not treated as a waiver of data-protection rights. For information on applicable international-transfer arrangements for a particular request, contact us before sending attachments.
6. Legal grounds where the GDPR applies
Processing necessary to deliver a requested service or handle a contractual/pre-contractual support request is based on Article 6(1)(b). Compliance with applicable legal obligations, including applicable data-rights duties, is based on Article 6(1)(c). Necessary general enquiry handling, service security and defence of claims may rely on Article 6(1)(f); our interests are responding to users, protecting the service and managing claims, subject to their rights and interests. Where processing relies on consent, Article 6(1)(a) applies and consent can be withdrawn without affecting prior lawful processing.
7. Your rights and contact
Subject to the applicable conditions, you may request access, correction, erasure, restriction, portability, or object to processing based on legitimate interests. Contact tesimai01@163.com and identify the product and request; do not send identity documents unless a proportionate identity check is necessary and requested. You may complain to the competent data-protection supervisory authority, including in the EU country of your habitual residence, work or the alleged infringement.
Data Act access and sharing requests may use the same contact. We will explain available local access options and address requests for data we hold or can lawfully make available. No complete one-click self-service export is currently provided. The absence of a cloud copy does not remove statutory rights.
8. Children, security and changes
A child’s use should follow the product’s applicable age/safety instructions and parental supervision where required. We do not operate child accounts or advertising profiles. If a child has sent personal information through support, a parent or guardian can contact us about its removal, subject to lawful retention requirements.
Phone permissions and application storage controls help limit access. Bluetooth operation should take place in a trusted setting; we do not claim that every local file is encrypted or that Bluetooth uses website TLS encryption. Keep the phone and app secure and remove personal display content before transferring the product to another person.
This policy may be revised when functionality or processing changes. The revision date identifies this text. Material changes will be brought to users’ attention through an appropriate notice; any legally required consent will be obtained separately.