Corntree Studio Privacy Policy
Last updated: 23 October 2026.
1. About this policy
Corntree Studio operates the eleven applications identified in Appendix A — Application differences below. This policy and the appendix should be read together. The appendix explains differences in content, connected services and deletion between applications.
Privacy and deletion requests for all eleven applications can be sent to xiaoaojianghu001007@gmail.com for manual handling by Corntree Studio.
2. Information handled by the applications
Depending on the application and its enabled features, information handled includes:
Content you work with: calculations and history, notes and tasks, documents and scans, photos and edited images, or microphone recordings and related file information.
Diet, exercise, water, weight, profile and activity information in Calorie and Step, including precise route information when Step's route-tracking feature is used.
Nearby TV information and local-network requests in Roku Remote.
App-account identifiers, backup content, device associations and encryption-recovery material for relevant account and recovery features.
App interactions, diagnostics, app/device information, installation identifiers, support communications, notification tokens and purchase or entitlement information where the relevant service is used.
Local content and online service records are separate. A feature that processes a document, image or recording on your device does not mean that every item handled by that application stays on the device. In particular, operation logs, error reports, account backups, recovery material, conditional image samples, usage measurement and support services can involve information leaving your device. The appendix describes these differences.
3. Purposes and recipients
Information supports the relevant app functions, saving or restoring content, account or recovery features, diagnosing failures, usage measurement, feature configuration, advertising where enabled, purchase entitlements and support. The categories and triggers differ by application. Health, location, private content, diagnostics and advertising data are separate categories; one general description of analytics does not describe every use.
The services named in the appendix include Google/Firebase, Google Play, advertising services where enabled, Corntree support services, Worktile purchase notifications, an exchange-rate service and optional external forms. Sharing or exporting content at your direction creates copies with the destination you choose. Online service data and copies held by those destinations are distinct from an application's local content.
4. Permissions and choices
Android permissions control access to restricted functions such as media, files, camera, microphone, location, activity recognition and notifications where applicable. Refusing a permission can prevent the related function. Selected-photo or selected-file access differs from access to a wider media or file collection.
An Android permission choice does not necessarily control every online service. For example, support registration and reply synchronisation can occur separately from submitting a feedback message. This policy does not describe a universal switch for all service processing or treat a region setting as a user choice.
5. Accounts, purchases and subscriptions
PicSafe and Step have account-linked features using Google sign-in and Firebase Authentication. An application's account is different from the underlying Google Account. An installation identifier is not by itself a user-created account.
Google Play handles purchases for the relevant subscription features in Calorie and PicSafe. Purchase state and app entitlements differ from payment-card information held by the payment provider. Manage Google Play subscriptions through Google Play.
Signing out, revoking Google access, deleting an app account, deleting local content, uninstalling, cancelling a subscription and requesting a refund are separate actions. A privacy or deletion request does not automatically cancel a subscription or produce a refund.
6. Local protection and connected services
PicSafe's local vault-media encryption and encrypted image-sample transfers are specific protections; they do not mean that every database, preference, backup or service record is encrypted in the same way. Recovery material can be held separately from encrypted local media. Encryption must not be interpreted as all keys staying on the device or as a guarantee that the operator cannot access recovery material.
Roku's local TV control can use an unencrypted local-network connection. This differs from connections to online services. No statement in this policy guarantees universal encryption or secure erasure of every copy.
7. Retention and deletion
Local saved content is managed through the relevant app's file, history, record or trash controls. Removing an index or a recent-file entry is different from deleting the underlying file. Files outside the app, exported files, sharing destinations, other devices and system backups are separate copies.
Account records, backups, encryption-recovery material, support communications, usage records and supplier records have separate lifecycles. Local deletion, signing out or uninstalling does not by itself establish deletion of these records. The local trash feature is not a cloud-retention rule, and removing a cloud key is not a remote wipe of local or exported media.
For privacy or deletion requests, email xiaoaojianghu001007@gmail.com. Identify the application and the relevant account or data concern. Do not send passwords, PINs, verification codes, encryption keys, private media or payment-card details.
This is a manual request channel. It is not a guarantee that an email immediately erases every record or copy. The request's scope is distinct from app-account deletion, local file removal, supplier-held records and backup handling. This policy makes no fixed cloud-deletion deadline or universal remote-wipe promise.
8. Health information and children
Calorie and Step handle the health and activity information described in the appendix. Route information, dietary records and profile information require their own treatment and should not be confused with general app-usage data.
The applications have different functions and audiences. This policy does not assign a single minimum age or claim a parental-consent process across all eleven applications. Contact Corntree Studio with concerns about a child's information and identify the relevant application.
9. Changes and contact
This policy can change as app functions or connected services change. Read it together with the information for the application you use.
Corntree Studio Privacy and deletion requests for all eleven applications: xiaoaojianghu001007@gmail.com.
Appendix A — Application differences
Read with the Corntree Studio Privacy Policy above.
Corntree Studio operates all applications below. The manual privacy/deletion request email for each is xiaoaojianghu001007@gmail.com. Features and connected services differ by application; the descriptions below must not be read as a promise that all content remains local or that every online service is controlled by one local deletion action.
EZ Calculator
com.sevegame.calculator
EZ Calorie Counter
com.sevegame.calorie
Notepad - Colorful Notes (ColorNote)
com.sevegame.colornote
PDF Reader: Viewer
com.sevegame.pdf
Collage Maker - Photo Editor (PhotoCollage)
com.sevegame.collage
PicSafe - Private Photo Vault
com.sevegame.vault
Remote Control for Roku
com.sevegame.roku
Step Counter - Pedometer
com.sevegame.step
PDF - Reader, Viewer, Scanner
com.sevegame.pdfscanner
Photo resizer image compressor
com.sevegame.resizer
Voice Recorder
com.sevegame.voicerecorder
1. EZ Calculator
Calculations, results and history are handled on your device. A calculation-error reporting path can send the original expression to Firebase Realtime Database. Diagnostics can also contain information about the calculation editor or result; performance and installation-related services are separate from calculation history.
Exchange-rate requests go to an external exchange-rate service. External forms, if offered and opened, handle the information you choose to submit. Clearing local history does not itself remove error reports, supplier records, form responses or system backups.
2. EZ Calorie Counter
Profile and health information includes age, sex, height, weight, dietary records, exercise, water and goals. Local records and an app-operation logging service are separate. Operation logs can include food, exercise or water actions, searches, barcodes, custom-food information, age, sex and BMI, and can be sent to Firebase Storage. Clearing the local diary does not by itself remove those service logs.
Diagnostics, usage measurement, advertising where enabled and purchase processing are additional paths. Purchase notifications can send subscription type, offer information and app information to Worktile. A cleanup rule for local operation logs does not establish a retention or deletion rule for uploaded logs or other services.
3. ColorNote
Notes, tasks, colours, timestamps and trash records are handled in the app's local storage. Trash and permanent-deletion controls concern those local records. Support communications, diagnostics and notification services are separate from note storage, and support synchronisation can occur separately from writing a feedback message.
Removing a note is different from removing external copies, backups or service records. Promotion links to other apps are also separate from processing the note itself.
4. PDF Reader
Reading, scanning, annotations, forms and recent-file functions work with documents and file information on the device. A document, its file index and its recent-file entry are different items. A file may also originate from an external provider or be shared to another destination at your direction.
Diagnostics, notification, support and advertising services where enabled are separate from these document functions. Deleting an index entry does not necessarily delete the original document, scan image, exported copy or feedback attachment.
5. PhotoCollage
Selected photos are used to create edited images and collages; exported results are saved as separate image copies. Where image-sample collection is enabled, an encrypted reduced image and associated metadata can be sent to Firebase Storage. Metadata can include an installation-related identifier, use count, language, country, timezone and template or edit information.
Saving an image and sending an image sample are different paths. An encrypted sample is not necessarily anonymous. Removing a gallery result or local app data does not itself remove an uploaded sample, its associated records, support attachments or other supplier records.
6. PicSafe
Imported media and thumbnails are handled in the local vault together with names, paths, album information and other media metadata. Local media encryption is separate from recovery services. Device-associated encryption keys and recovery material can be sent to Firestore when the vault's PIN/recovery setup is initialised, including a setup that skips sign-in. Signing in can associate an app-account identifier with device records.
PIN-recovery requests, verification data, diagnostics and subscription entitlements are separate from the encrypted media files. A local vault, an original gallery file, an exported file and a copy on another device are different copies.
Local trash or permanent deletion, deleting an app account, removing cloud recovery material and managing a Google Play subscription are separate actions. Removing cloud recovery material can affect recovery; it must not be described as automatically erasing every media copy. Email contact is a request route, not proof that all account, recovery, supplier and backup records have already been deleted.
7. Roku Remote
The app discovers local Roku devices and uses device names, addresses and control requests to provide remote-control functions. Local TV control can use an unencrypted local-network connection. The TV and its records are separate from the app's saved device list.
Usage measurement, diagnostics and advertising where enabled are separate online services. Removing a TV from the app's list does not establish deletion of TV-side records or supplier data.
8. Step Counter
Profile, step, workout and route features handle fitness information and, when route tracking is used, precise location records. Local preferences, activity records and route files are separate from account-linked backup. Google sign-in and Firebase Authentication support the backup and restore features, which can send those records and device/account associations to Firebase Storage.
Signing out and revoking Google access are different from deleting the app account and all related cloud data. Removing a current backup does not establish deletion of historical backup copies or supplier records. Local routes, other-device copies, map services, diagnostics, support and notification data require separate treatment.
9. PDF Scanner
Scanning, rendering and recent-document functions handle documents, scan outputs and file information on the device. Removing a recent-document entry and deleting the document are different operations. Saved scans, originals, exported files and external-provider files are separate copies.
Diagnostics, app interactions, installation-source information and advertising where enabled are separate service paths. A promotion for another app is also different from document processing. Local file deletion does not remove those service records or copies held elsewhere.
10. Photo Resizer
Selection, compression, resizing and saving work with images on the device. Where image-sample collection is enabled, a reduced image and associated metadata can be encrypted and sent to Firebase Storage. Metadata can include an installation-related user identifier, use count, time, timezone, country, source dimensions or size and target dimensions or size.
Sample collection is separate from saving the image. A region check is not a user consent control, and encryption does not by itself mean a sample is anonymous or inaccessible to the operator. Original images, exported images, app data, uploaded sample components and supplier records are separate when considering deletion.
11. Voice Recorder
Recording, playback and editing work with audio files and a local list containing recording names, paths, categories, duration, timestamps and size. Microphone permission supports recording. Local recording files, trash, exported audio and user-directed sharing create different copies or records.
Usage measurement, diagnostics, advertising where enabled, notifications and feedback are separate from local audio processing. A feedback service can register an installation identifier and notification token and synchronise replies at startup or in the background. These actions can occur before you compose a feedback message. A feedback submission can include text, app information, timestamp, notification token and device/platform information.
Deleting a local recording, clearing trash, resetting an installation identifier or marking a support message read does not itself establish deletion of cloud feedback, notification, measurement or supplier records. Local trash does not define cloud retention, and an export or shared copy requires separate handling.