About the app
This policy covers the Creality Helper mobile app, also named Creality Helper Script, and its website. The app works with compatible printers on a local network. The current release does not offer separate user registration with a name, email or password.
Data on your device and printer
The phone stores the chosen model, printer address, SSH username, language and app settings. New SSH passwords use Android or iOS secure storage. Original fields from the previous Flutter app may remain for migration compatibility.
The SSH password is sent to the printer you select to establish a connection. It is not sent to Creality Helper server functions, Firebase or the Expo update service. Terminal commands and output are used when working with your printer. Compatible RFID tag data is processed on the device and sent to the selected tag when writing.
If you configure Telegram on a printer, the token and chat settings you enter are sent to that printer. Its subsequent requests to Telegram depend on the installed script and your configuration.
Data in cloud services
For activation and notification requests, the app creates a random installation credential in secure storage. The server receives it over HTTPS and uses its hash as an identifier for this installation.
When you enable notifications, the server stores the installation identifier, Expo push token, Android or iOS platform, language, build channel and technical timestamps. Test sends process a notification identifier, provider receipt and delivery result.
When you use a promo code, the server processes the code and stores its hash, redemption information, activation expiry and attempt counters. Payments are not enabled in the current release.
For updates, Expo processes the network request and the technical information needed to deliver a compatible package: platform, channel and app runtime version. Cloud providers may also process IP addresses, request times and technical logs to operate and protect their services.
Services and recipients
Firebase and Google Cloud provide server functions, activation records and notification registration. Expo/EAS provides updates and push sending. Push delivery uses Firebase Cloud Messaging on Android and Apple Push Notification service on iOS. These services may process technical data in different countries under their own terms.
The website is hosted through Sites (OpenAI), using Cloudflare infrastructure. These providers deliver pages and may process technical network request information.
Support email uses Resend. When you contact support, the service processes the sender address, subject, message and attachments. We use this information to reply and handle your request. Do not send printer passwords or secret keys.
If you choose to contact Telegram or support by email, the selected service receives your message content. Do not attach secrets or unchecked full logs.
The current implementation does not use data for advertising profiling or sell it. This website has no first-party advertising trackers or analytics counters. Hosting may process technical requests and use necessary protection or authorization mechanisms.
Retention
Phone settings remain until you change them or remove app data. Removing the app on iOS does not always remove Keychain data. Removing the app does not automatically delete cloud records.
Disabling notifications in the app deletes this installation's server push registration. An unfinished removal request is retried at the next launch. Pending receipt records are removed after processing; if a receipt is unavailable, checks are retried until the waiting window expires.
Activation, redeemed promo and rate-limit records have no configured automatic deletion deadline. They are retained to support activation and prevent repeated use. You may request deletion through the private support contact. Third-party technical log retention follows provider settings and policies.
Support messages are processed in Resend; their availability depends on the service plan settings. This website does not create a separate support database. Use the support email to request deletion of correspondence.
Your choices and enquiries
You can revoke notification permission in your phone settings and disable registration on the app's notifications screen. Local printer features remain available without notifications.
You may request information, correction or deletion of server data relating to you. Deleting activation records may end the access associated with them. Data on the printer you select, Telegram and third-party services is managed separately.
Transfer and protection
Requests from the app to our cloud functions use HTTPS. Passwords and the installation credential use operating system secure storage; the server represents the credential with a hash.
SSH connections use the SSH library's encryption. Local Moonraker requests may use HTTP without TLS, depending on the printer configuration. These local connections should not be treated as protected cloud HTTPS.
Policy changes and contact
When data handling changes, we will update this page and its date. The support page lists the support channel and private contact for data enquiries.