InkBatch Privacy Policy

Document version: 1.3 · Applies to application version: 1.0.0
Effective: 7 October 2026

1. The publisher and how to reach us

The InkBatch app is published by Dominik Trojanowski Vertias. The publisher’s address is on the Publisher and contact page.

Privacy contact: kontakt.vertias@gmail.com.

The data you enter in the application stays on your device and never reaches the publisher, so the publisher is not its controller. The publisher becomes a controller of personal data only for the correspondence you choose to send (section 10).

2. The shortest honest answer

InkBatch collects nothing and sends nothing by itself. The published build does not even hold the internet permission, so it cannot transmit at all. Everything you type stays in the application's private storage on your own device. The only things that leave the device are those you export or share yourself (section 7).

3. What data exists, where it lives and what it is used for

All of it is data you create by typing it in:

ingredients: names, codes, prices and stock levels,
recipes and their compositions,
mixing sessions, batch history and historical costs,
stock movements,
leftovers,
notes and per-component instructions,
a batch's job reference and notes, if you enter them,
a recipe's target colour, if you set one,
application settings: language, theme, the resolution of your weighing scale, default currency, the time a backup was last saved or shared (and which of the two it was), and the record that you acknowledged the legal notices.

All of it is written to the application's private SQLite database on this device. There is no account, no sign-in, no server and no synchronisation. All processing happens locally, on your own device.

The application uses this data only for what you ask of it: recording recipes, scaling, running a mix, batch history, stock and cost. For nothing else.

The descriptive fields — names, codes, notes, instructions, job reference — accept any text. If you type a person's details into one of them, for example a customer's name, you decide about that data and you control it; it never reaches us in any form and we cannot access it.

4. What does not exist

No accounts, no sign-in.
No server and no publisher-operated cloud of any kind.
No synchronisation.
No adverts, no advertising identifier.
No analytics.
No crash reporting and no telemetry.
No tracking, no profiling.
No INTERNET permission in the published build.
No camera permission.
No storage or photo permissions.
No access to location, contacts or calendar.

We do not sell or share data from the application with anyone — we never receive it.

5. The picture you read a colour from

If you ask InkBatch to read a colour out of a picture, you choose that picture in Android's own system picker. That choice is the entire access granted — the application requests no photo permission and cannot see your gallery.

The picture is read where it already is, and processed entirely on the device. It is never copied into the application, never stored as workshop data, never shown to anyone, and never transmitted. The only thing kept is a number describing the colour you accept, held as a recipe's target colour. The reading is approximate and serves as your own reference note.

A picture larger than the application can decode without risking the process being stopped is refused with a message, before it is read.

6. Backups: creating, exporting and importing

A backup is created when you ask for one, and automatically immediately before a restore, so that the data you currently hold is protected.

The copy is written to the application's private documents directory on this device.
You may deliberately export or share it to a destination you choose, using Android's own save dialog or share sheet. From that moment the file is managed by the destination you picked. InkBatch does not know where it went and cannot delete it from there.
Importing, and the temporary file. When restoring, the file you select is copied into the application's private cache for the duration of the read, because it can be tens of megabytes. That working copy is deleted as soon as the import ends — whether the file was accepted or refused. A temporary file left behind by an interrupted import, or by an earlier version of the application, is removed automatically at the next start.
Android's automatic backup is disabled (allowBackup="false"). The application's database is never copied to your Google Drive.

7. What you can send yourself — and what it contains

The application sends nothing by itself. There are, however, three places where you can pass something on, through the system save dialog, the system share sheet or the clipboard. It is worth knowing what each one carries:

a backup — your whole database, including every descriptive field and every price, as a plain, unencrypted JSON file;
a single batch summary as text — including that batch's job reference and notes, if you entered them;
a report from the feedback screen — your own description plus a technical block: application version, operating system and its version, language, theme, the screen the report was started from, and a timestamp. No device identifier, no advertising identifier, no account.

The application fills in no recipient — you alone choose where it goes. What happens to a message you send to us is described in section 10.

8. Deleting your data, and how long it is kept

Data in the application stays on the device until you delete it yourself; the application removes nothing after any set period.

Delete all data inside the application erases the workshop records and every recognised backup InkBatch created in its private directory. It deliberately does not write a new recovery copy — if you want to keep anything, export it first.
Clearing the application's storage in system settings, or uninstalling it, removes everything, settings included.
Files you exported or shared outside the application cannot be deleted by InkBatch. Delete them at their destination.
We receive nothing from the application, so there is nothing for us to erase on request. The one exception is anything you send us yourself (section 10).

9. The store you download the application from

You download the application from an app store — Google Play or Samsung Galaxy Store. The store processes your account and download data under its own privacy policy. In the store's console the publisher sees aggregate statistics, such as the number of downloads, and the reviews users choose to publish in the store. None of it contains data entered in the application.

10. Writing to the publisher

If you write to us — for example by sending a report from the feedback screen to the contact address — we receive your e-mail address and the content of the message. The controller of that data is Dominik Trojanowski Vertias (details in section 1).

Purpose and legal basis: answering the message and dealing with the matter it concerns — Article 6(1)(f) GDPR, the legitimate interest of handling correspondence.
Recipients: the e-mail provider we use (Gmail, a Google service). It may process data outside the European Economic Area as well, and relies on the mechanisms the GDPR provides when it does. We pass messages on to nobody else.
Retention: for as long as handling the matter takes; the message is then deleted, unless a legal provision requires it to be kept.
Voluntary: writing to us is voluntary; without a return address we cannot reply.
We make no automated decisions on the basis of correspondence and we profile nobody.

11. Your rights

You manage the data in the application yourself: you can view, change, export and delete it without any involvement of ours.

For data from correspondence (section 10) you have the right of access, rectification, erasure, restriction of processing and the right to object to the processing — writing to the contact address is enough. You also have the right to lodge a complaint with a supervisory authority; in Poland that is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych).

12. Children

This is a professional tool intended for adults working in a workshop. It is not directed at children, and it collects data from nobody.

13. Permissions the published build declares

The release build declares one permission, pl.vertias.inkbatch.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, at signature level. AndroidX adds it automatically for the application's own broadcast receivers. It grants access to nothing outside the application itself.

(For completeness: the developer builds — debug and profile — do hold the INTERNET permission, because Flutter's development tooling requires it. Those variants never reach users; only the release build is published.)

14. The website carrying this policy

This policy is also published on the publisher's website. The application does not connect to that website or to any other. Visits to the website are served by a hosting provider: like any web server, it may record the IP address and technical browser details of people who visit the site in its logs. That concerns visits to the website only, not use of the application.

The website is served by Cloudflare. How visitors’ data is processed is described in Privacy on this website.

15. Changes to this policy

Any change to how data is handled requires this policy, the data declarations filed with the stores the application is available in, and the in-application text to be updated together. A new version of the policy is published on the publisher's website under a new version number. In the application the changed text arrives with an update, and the application then asks you to read the legal information again. As long as the application has no network access, no accounts and no external component, the answers above do not change.

16. Questions

kontakt.vertias@gmail.com