Privacy Policy
BakeCostDee is a recipe-costing app for bakery sellers. Recipes, ingredients, prices, costs, quotes, and sales are designed to stay on your device. The app does not require an account and has no BakeCostDee backend that receives this business data.
Miti Khumhvan, the developer and provider shown on the Store pages, is the data controller for the limited off-device processing described below. Privacy requests can be sent to nerubians@gmail.com.
Data stored on your device
The app stores menus and recipes, ingredients, quantities, units, purchase prices, labor and overhead costs, selling prices, quotes, cake-design details, and sales entries in an app-owned JSON store. It also stores language, onboarding, entitlement, draft, recovery, and local analytics de-duplication state in the app area.
Images are processed only after you choose them from the camera or photo library. The app resizes the image, creates a thumbnail, and removes EXIF data such as GPS coordinates before storing a local JPEG. It does not scan your whole photo library or upload images to a BakeCostDee server.
The JSON store and recovery files are stored in the app area. No additional app-level encryption of the JSON files was verified. Android and iOS sandbox protections apply, and the operating system or account-level backup policy may apply separately.
Sharing and backup
- “Export complete backup” creates a versioned portable file containing customer records and the actual bytes of every saved recipe and cake-design image referenced by those records. The app verifies the package before opening the operating-system Share Sheet. You choose the destination. Pro entitlement is not included or changed.
- The older “Copy backup data” flow places JSON on the system clipboard. It can contain recipes, ingredients, prices, costs, quote and design details, and sales entries, but not image files. It is separate from Complete Backup.
- “Open Share Sheet” for a customer quote shares an editable customer-facing message. The generated message is intended to omit internal costs, profit, margin, and recipe details.
- Cake-design sharing sends an editable message and the selected local image only after you open the Share Sheet and choose a destination.
- “Restore complete backup” validates the selected file and stages images before replacing customer records after confirmation. A cancelled, invalid, wrong-app, incomplete, or unsafe package leaves current data unchanged.
- The older JSON import reads pasted text and replaces local records only after confirmation.
BakeCostDee does not automatically upload backup data. Clipboard, Share Sheet, and operating-system backup destinations are outside the app’s control.
Analytics and technical data
The currently distributed Store version 1.0.34 was built with usage analytics enabled and does not include an in-app analytics switch. A later consent-enabled source update will keep analytics off by default and will let you choose whether to enable it in Settings > Privacy and analytics; that behavior does not apply until that update is distributed. Ordinary development and test builds keep collection off.
The app sends an allowlisted set of product-usage events, such as app and session start, opening the recipe editor, using costing features, recording a sale, creating a quote, viewing Pro, opening ingredient watch, and purchase or restore outcomes. For recipe completion, the app may send only a bounded ordinal from 1 to 4.
The app does not send recipe names, recipe IDs, ingredient names or IDs, quantities, costs, prices, profit, margin, sales values, quote text, customer data, image names, image bytes, or backup payloads through its custom analytics API.
Firebase may also collect provider-defined technical or session data, such as an app-instance identifier, device model, operating-system version, and approximate location inferred from network information. Google Play may provide purchase-event metadata to Firebase through native SDK behavior, such as a product name, product ID, or price. BakeCostDee does not receive card or bank details.
BakeCostDee does not use advertising, advertising ID for ads, Firebase Auth, Firestore, Firebase Storage, Crashlytics, Messaging, or another analytics vendor in the audited app source. Analytics transport uses the provider’s encrypted network transport.
Purposes and lawful bases
- Local business-data processing and Store-entitlement checks are necessary to provide the app functions you request and to perform the app purchase contract where applicable.
- Firebase Analytics is used to understand feature use and improve reliability and product decisions. Store version 1.0.34 does not provide an in-app consent control. In the later consent-enabled update, analytics will rely on your saved consent; declining or withdrawing consent will not block core costing, recipe, sales, report, or backup workflows.
- Support information that you choose to send is used to answer your request and resolve the reported issue.
Recipients and international transfers
Apple or Google processes Store downloads, purchases, and entitlement status under its own platform terms. When analytics is enabled by the distributed build or by your choice in a later consent-enabled update, Google acts as the Firebase/Google Analytics service provider and may process technical and usage data outside Thailand under its contractual and security safeguards. Files or messages shared through the operating-system Share Sheet go only to the destination you select. BakeCostDee does not sell business data and does not use it for cross-app advertising.
In-app purchases
Pro Lifetime purchases are processed by Apple App Store or Google Play. The app uses Store product and status information to unlock the entitlement on the device; it has no BakeCostDee receipt server and does not access payment-card or bank information.
Retention, deletion, rights, and contact
You can delete records in the app. Local records, preferences, and recovery copies remain until you delete or replace them, clear app data, or uninstall, subject to operating-system backup behavior. Export a complete backup to a location you control before uninstalling if you need to keep customer records and images. Portable backup files remain wherever you chose to save them until you delete them.
When analytics is enabled by the distributed build or by your choice in a later consent-enabled update, event-level data is retained under the Firebase/Google Analytics property setting selected by the controller; the supported standard retention choices are currently 2 or 14 months, while aggregated reporting may remain longer. In the later update, withdrawing consent stops future collection but does not itself erase data already received by Google.
You may contact the controller to ask for access, correction, deletion, restriction, objection, withdrawal of consent, or data portability where applicable, or to complain to the relevant data-protection authority. Some requests may be limited where the controller cannot reliably identify a particular analytics record. Contact nerubians@gmail.com.
BakeCostDee does not automatically upload business data to its own backend. User-selected clipboard, Share Sheet, and operating-system backup destinations are separate from automatic BakeCostDee collection.