Made for bakery work
CrumbPilot is for home bakers, cake designers, and small bakeries. It brings customer orders and production details into the same offline planning space.
Bakery orders, recipes, schedules, and costs—organized offline on your device.
Privacy PolicyCrumbPilot is an offline bakery order and production planning tool. It is designed for home bakers, cake designers, and small bakeries who need a place for the details of a job. The current version keeps the bakery records you enter on your device. You can organize your work without creating an online account.
CrumbPilot is for home bakers, cake designers, and small bakeries. It brings customer orders and production details into the same offline planning space.
Customer names, phone numbers, dates, quantities, status, and pickup or delivery instructions are fields you may enter. Those records help you follow a job from the initial request to its planned handoff.
Record flavors, sizes, fillings, frosting, decoration notes, and reference images. The purpose is to keep chosen details near the related bakery order.
Ingredient expense, labor, packaging, deposits, estimated prices, and balances can be used in the app. This information helps organize the costs associated with bakery work.
The current release does not require an account or the Android INTERNET permission. Your bakery records are managed in application storage on the device.
Bakery work involves more than writing down a cake name. Orders, reference choices, quantities, and preparation stages all contribute to the record. CrumbPilot lets you enter these details in the current offline release. Scroll through the areas of information the app is designed to help you manage.
Order records may contain a customer name, phone number, quantity, date, and status. Pickup or delivery directions are entered by you for the order you are organizing.
Keep custom specifications such as flavors, filling, frosting, size, and decorations. Reference photos come from files you explicitly select using the Android picker.
Manage product catalog records, recipes, ingredient units, and serving quantities. Shopping checklist information can also form part of your locally kept records.
Use baking schedules and preparation checklist progress to organize the work ahead. Favorites and preferences help the app remember your own selections.
Store estimated prices alongside ingredient, labor, and packaging costs. Deposits and balances are part of the bakery records you choose to enter.
Create PDF order summaries or manual ZIP backups when you choose. Files may contain customer and recipe information, and ZIP backups are not encrypted by CrumbPilot.
Swipe or scroll sideways to see the different record types.
CrumbPilot uses records that you deliberately enter or select. Core bakery information lives in app storage, not a developer-operated account. Exporting or sharing is a separate choice that can move a copy beyond the app. Understanding each stage makes it easier to decide where your information belongs.
Information starts with the records you choose to create: orders, recipes, notes, costs, and optional images. The app does not ask you to register for an account.
CrumbPilot uses local application storage, including SQLite databases and preferences. The current release does not automatically upload bakery data to developer servers.
For photos, you pick a specific item through the system interface. For exports, you decide when to generate a PDF or ZIP file and where to save it.
If you share a PDF or save an export to cloud-synced storage, that app or storage provider may process the file. Its privacy practices are separate from CrumbPilot.
You can edit or delete records, or clear app storage to remove local data. Files saved outside the app and files already shared need to be handled separately.
The current release is built around local bakery planning. It does not include in-app ads or analytics SDKs, and it does not request internet access. You can still decide to save or share documents using Android’s system interfaces. The most important points are gathered below, with the complete wording available in the Privacy Policy.
The app does not require registration, a username, or a login to use its bakery planning functions.
The current release does not include advertising, analytics SDKs, Firebase, or third-party tracking.
CrumbPilot does not request Android’s INTERNET permission and does not automatically upload your bakery records.
The app accesses reference images only when you explicitly choose them through the Android picker.
PDFs may contain customer details, and manual ZIP backup files are not encrypted by the app.
App data can remain until you delete it, clear storage, or uninstall. Separate exports must be deleted separately.
You decide what bakery information to enter and which photos to select. You also decide when to produce files outside the app and how to handle them after export. Deleting an app record is not the same as deleting a file already saved or shared elsewhere. These distinctions matter when customer details are involved.
Enter only the information needed for your bakery workflow. If you enter someone else’s phone number or contact details, you are responsible for having a lawful basis to use them.
The system picker lets you select individual files rather than granting the app unrestricted photo access. Removing or revoking access to a file can make its image unavailable in the app.
A PDF summary or ZIP backup is created by your choice. Think about the customer information inside it before saving to a synced folder or sharing through messaging.
Orders and certain products can be deleted in the app. Products in use by active records may require you to update or remove the related records first.
Android Settings allows you to clear the app’s storage, or you may uninstall it. These actions can permanently erase records that have not been exported.
A PDF or ZIP saved elsewhere can remain after uninstallation. Files already passed to others can also remain with recipients, so manage those copies independently.
Bakery records can include customer contact details, pricing notes, and photos of requested designs. The policy explains both the local safeguards supplied by Android and the limits of those safeguards. It also clarifies that external exports need separate care. Clear boundaries help you manage sensitive material without assuming every copy is protected in the same way.
Android’s app sandbox restricts access by other apps to private app data under normal conditions. A device screen lock adds an important practical safeguard.
CrumbPilot does not promise end-to-end or at-rest encryption for its database or exported files. Be deliberate about where customer-related documents are stored.
Automatic Android app backup is disabled, while manual ZIP backup remains optional. CrumbPilot cannot remotely retrieve or delete files that exist only on your device or with external providers.
The app is intended for bakery work and is not specifically directed at children. It does not knowingly collect children’s information on developer-operated servers.
If features or data-handling practices change, the publisher may update the policy and its effective date. The current version is intended to be available in the app and on its public listing.