FOOD PRODUCTION · LOCAL RECORDS

BatchNest
made for every batch.

Keep recipes, ingredient lots, expiry dates and stock records together on your Android device.

Privacy Policy
01 / ABOUT THE APP

Built for the records behind every food batch

BatchNest is a local recordkeeping application for home food producers and small food businesses. The app brings recipe details, ingredient lots, batch quantities and stock entries into one place on an Android device. It is designed for the practical notes that accompany food production, rather than for an online account or a cloud dashboard. Its scope includes both what goes into a batch and what happens to it afterward.

Product recipes

Create and manage recipes alongside ingredient names and their quantities. These entries give context to a production batch without sending that information to a BatchNest server.

Ingredient origins

Record ingredient lot identifiers, supplier details and costs. The identifiers help keep your own local record of which materials you entered.

Production activity

Keep production dates, batch quantities, storage locations and packaging checklist entries. The details remain in the app’s local database.

Stock and wastage

Follow stock movements, selling prices, wastage and spoilage records. Some movement history may remain to support local stock accounting.

The intended audience

BatchNest is a business recordkeeping tool for home producers and small food businesses. It is not specifically designed for children and does not provide child-directed accounts.

02 / THE WORKFLOW

The data you decide to work with

The app is shaped around records that you enter and manage yourself. Ingredient quantities and supplier costs belong alongside recipes; dates and storage locations belong alongside batches. Presentation settings are also kept locally on your device. Its core operations do not depend on an active internet connection.

Recipes & ingredients

Recipe details include product names, ingredients and quantities. You control the information entered, and the app stores it in its private local database.

Lots & batches

Lot identifiers, batch sizes and production dates connect the information you enter. Linked records may affect which entries can be deleted first.

Shelf-life entries

You provide expiry dates and storage information yourself. The app does not verify that a date represents a scientifically safe shelf life.

Inventory records

Stock movements, packaging checklists, prices and waste entries support local tracking. Stock movement history may need to be retained after another record changes.

Preferences

Onboarding status, currency display, expiry warnings and online-photo settings are stored in local app preferences. These preferences are distinct from exported PDF files.

03 / DATA HANDLING

Where each record goes—and where it does not

BatchNest keeps its core business records in an app-private Room/SQLite database on the Android device. There is no developer-operated server automatically receiving those records. The app also provides optional online food photographs, which are a separate kind of network activity. Saving or sharing a PDF is a separate action initiated by the user.

01 · Enter

You add recipes, quantities, lot identifiers, dates, stock records and other details. Account registration is not required for the core features.

02 · Keep locally

The app stores business records in private app storage, while interface preferences are kept in local settings. Initial example records, if present, are local too.

03 · Optional photographs

Online food images can load from images.unsplash.com over HTTPS. Unsplash may receive an IP address, a requested image URL and ordinary connection metadata.

04 · Export deliberately

PDF batch and stock reports are created on the device. You choose whether to save them locally, use an available storage provider or share them.

05 · Remove

You can edit or delete entries subject to linked-record rules, or clear app data and uninstall. Separately exported PDFs require separate deletion.

04 / QUICK REFERENCE

A clearer picture of privacy

The distinction is simple: your operational records are local, while optional decorative food images may use an external image service. Reports leave the app only when you choose a destination or recipient. The inspected version has no advertising SDK, Firebase Analytics or in-app payment service. External recipients and providers maintain their own separate practices.

No account required

Core tools do not ask you to register with a name, email address or phone number. Your saved business information is not automatically synchronized to the developer.

No advertising SDK

The inspected version does not include an advertising SDK or Firebase Analytics. Local business records are not sold for targeted advertising.

Optional web images

Online food photographs are on by default and may be disabled in Settings. Disabling them switches the app to bundled illustrations.

HTTPS image delivery

Optional image requests use HTTPS and fixed developer-provided photo URLs. Recipe content and PDF contents are not appended to those URLs.

Export depends on choice

A saved or shared report may become accessible to the storage provider, app or person you selected. BatchNest does not automatically upload it to its own server.

05 / YOUR CHOICES

You decide what stays, changes or leaves

BatchNest gives users control over the details they enter and how they choose to export reports. You can turn off online photographs, use the app’s core tools without connectivity, and remove locally stored information. Some linked records require an ordered deletion process. Reports you have already saved outside the app require separate attention.

01 · Switch photographs off

Settings > Online food photographs disables new remote photo requests and uses local illustrations. Previously cached files may remain temporarily.

02 · Change saved records

Records can remain until you edit or delete them. Linked batches or ingredient lots may require related entries to be removed first.

03 · Clear app storage

Clearing app data or uninstalling deletes the local database and preferences. Android automatic app backup is disabled in the inspected version.

04 · Check exported files

A PDF saved to cloud storage or shared with another person remains outside the app’s database. You need to remove it from that destination or ask the recipient.

05 · Ask about practices

Privacy questions can be directed to SUFI AUTO CORPORATION using the email address listed in the policy. The policy may be revised when practices change.

06 / RESPONSIBILITY

Useful records, with important boundaries

Food production notes can support a clearer working history, but they are not proof of product safety. BatchNest relies on the dates and storage details entered by its users. Android’s private app storage provides operating-system protections, yet shared devices and exported reports introduce other risks. The policy sets out those limitations alongside the app’s recordkeeping purpose.

Local security

App-private storage is protected under Android operating-system controls. The security of the device itself still matters.

Shared reports

When information is passed to a selected recipient or storage service, that party’s privacy practices apply. An exported copy is outside the app’s local record deletion process.

Expiry is user-defined

The app does not test products or establish scientifically safe shelf lives. An expiry date is a user-entered record, not a safety certification.

Compliance remains yours

BatchNest does not certify food regulatory compliance or guarantee that products are safe to sell or consume. Applicable handling and labeling requirements remain the user’s responsibility.

Policies evolve

If features, providers, permissions or data practices change, the published policy may change too. Its effective and last-updated dates identify the version displayed.

Know what BatchNest stores, when optional photos connect, and how exports work.

Read the Privacy Policy