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.
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
- “Copy backup data” places JSON on the system clipboard. It can contain recipes, ingredients, prices, costs, quote and design details, and sales entries, but not image files. The data leaves the app only when you choose to use it with another destination.
- “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.
- Import reads pasted JSON 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
Store or approved QA builds may enable Firebase Analytics automatically. There is no in-app analytics switch; ordinary development and test builds keep it 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.
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.
Deletion and contact
You can delete records in the app. Uninstalling normally removes app-area data according to the operating system. Export a backup first if you need to keep it. Deletion of provider-held analytics data is subject to that provider’s settings and processes.
For privacy questions or support, 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.