Privacy Policy – Baskivo
Last updated: 16 August 2026
This privacy policy explains which personal data is processed when you use the Baskivo app. Baskivo uses no advertising, no analytics SDKs and no profiling.
1. Controller
Juri Bolotko Malzstr. 1 42119 Wuppertal Germany
E-mail: kontakt@dayvela.app
2. Local processing on the device
Baskivo first stores shopping lists, items, quantities, units, notes, prices, budgets, categories, favourite shops, optional shop assignments, freely chosen household profiles, person assignments, self-defined restock intervals, purchase and due dates as well as settings in a local SQLite database on the device. Optionally scanned or manually entered product codes, cached product names, brands, packaging details, source metadata and the product names you have confirmed are added to this. This local processing makes it possible to use the app without an internet connection.
Recipe or ingredient text you paste is evaluated locally in an editable preview. The raw text is not transmitted to any recipe service or to the Baskivo backend, and it is not stored permanently. Only the ingredients you confirm are saved as ordinary items with the selected quantities, units and notes, and — if household sync is switched on — synchronised as described below.
The purchase details named in section 12 are likewise stored only locally, after a purchase.
Local data remains stored until it is removed inside the app or until the app data is deleted through the Android settings or by uninstalling the app.
The local product cache can additionally be removed in the product scanner via “Clear the local product cache” after a confirmation prompt. Items already added to a list are kept.
3. Product scanner and Open Food Facts
You may voluntarily read an EAN/UPC product code printed on packaging with the camera, or enter it by hand. The camera permission is only requested after an explanation and an explicit tap on “Open the camera”. Recognition takes place on the device, in the live camera image. Baskivo does not record any photo, video or audio in the process, and it neither stores nor transmits any camera image. Manual entry remains usable without the permission.
After a successful local check-digit test, Baskivo queries the individual product code directly via the public product API of Open Food Facts. In doing so, the following data is transmitted to, or technically processed by, Association Open Food Facts, a non-profit organisation based in France:
- the requested EAN/UPC/GTIN code as part of the API path,
- IP address, time of the request and the HTTP connection data technically required,
- the identifying user agent
Baskivo/1.0.3 (kontakt@dayvela.app).
List names, household identifiers, other shopping content and any later corrections you make are not sent to Open Food Facts. Only the product name, brand, packaging details, source modification time and code are requested. The purpose and legal basis are the product search and display that you have explicitly triggered, Article 6(1)(b) GDPR. The privacy policy and terms of use of Open Food Facts are available at Privacy and Terms of use.
Results are cached locally for 30 days. Names you have confirmed remain stored locally until the product cache is cleared, the app data is deleted or the app is uninstalled. Corrections are not written back to Open Food Facts. The product data comes from an open community database and may be incorrect, incomplete or out of date; the packaging remains authoritative. Baskivo does not download any product images in this process.
4. Live synchronisation
The published app is connected to the self-operated Baskivo backend. When it first connects, after you have agreed to the rules for shared households, it automatically creates a random anonymous user identifier and a household. No e-mail address, real name or access to your address book is required for this. Without your agreement the app remains usable locally and transmits no shopping content to the household sync.
The following data is processed for synchronisation:
- anonymous user, session and household identifiers,
- invitation code and household membership,
- lists, items, optional product codes, categories, quantities, units, notes, prices, budgets, favourite shops and optional shop assignments,
- freely chosen profile names, profile colours, optional profile symbols and assignments of items to those profiles,
- optional restock intervals, the last purchase or consumption you entered, calculated due dates and active status,
- modification and deletion times as well as technical synchronisation information.
The purpose is to secure changes from the local queue, to transmit them after a period offline and to keep shopping data up to date with the household members you have invited. The legal basis is Article 6(1)(b) GDPR, in so far as the processing is necessary to provide the synchronisation you have requested.
Baskivo does not examine shopping content for advertising, analytics or profiling purposes. Even so, you should not enter information in free-text fields that the shopping list does not need.
Household profiles are shared organisational labels, not user accounts. Profile names may contain real names or nicknames and are visible to invited members of the same household. You should only enter names or labels that are intended to be used jointly within the household.
The local product cache with its provider source, brand, packaging details and your correction is not transmitted via household sync. If a confirmed product is saved as a list item, only its item name and optional product code are synchronised, like any other list content.
5. Shared households and invitation codes
Anyone holding a valid eight-character invitation code can join the corresponding household and read and change its synchronised shopping data. The code should therefore only be shared with the household members you intend. Members of a household are themselves responsible for not passing the code on publicly. The code can be renewed in the app, which invalidates the previous one. Members who have joined can leave the current household. The current list is then kept as a local copy and assigned to a new private household.
The native share function passes the text you have selected to the Android share menu. Baskivo receives no access to your contacts or to the target app you choose.
6. Reports and moderation
Offensive content, members or households can be reported directly in the app. The following data is transmitted to the self-operated backend in the process:
- the anonymous identifier of the reporting person and the household identifier,
- the chosen subject of the report and the reason given,
- the description entered by the reporting person,
- rules version, processing status and time stamps.
Other household members cannot list or read reports. Access is granted only to the reporting person for their own report entry, and to the operator for review and processing. The purpose is to enforce the rules for shared households, to protect users and to counter unlawful or abusive content. The legal basis is Article 6(1)(f) GDPR; the legitimate interest lies in operating the household sync safely and in line with the applicable policies.
7. Server access and technical logs
When the backend is accessed, connection data that is technically required is processed. This may include the IP address, the time, the path called, the HTTP status, device or client information and technical session identifiers. Request content such as item names is not stored in the Nginx access logs.
The logs serve to provide the service securely, to analyse faults and to counter abusive access. The legal basis is Article 6(1)(f) GDPR. The legitimate interest lies in the security and stability of the service.
- Nginx access and error logs are kept for no longer than 14 days.
- Technical Appwrite execution and audit data is normally kept for no longer than 14 days.
- Internal aggregated resource and usage statistics may be stored for up to 100 days.
- No external error-analysis or tracking service is connected.
8. Hosting and recipients
The backend is not operated in Appwrite Cloud. The Appwrite software runs on a dedicated server at the Hetzner site in Nuremberg, Germany.
The following processor is used for server hosting:
Hetzner Online GmbH Industriestr. 25 91710 Gunzenhausen Germany
No transfer of Baskivo sync data to a third country is envisaged for the backend operation described here. In addition, the people to whom you pass your household invitation code gain access to shared shopping data. Where you explicitly trigger a product search, Association Open Food Facts, based in France, receives the product code and connection data named in section 3 as an independent recipient; no household sync data is transmitted in the process.
9. Retention and deletion of synchronised data
Synchronised household data is stored for as long as the household is used for Baskivo, or until its deletion is requested. Anonymous sessions and technical assignments are deleted together with the associated data, unless legal obligations or compelling security reasons stand in the way. Data already contained in routine backups may persist until the end of the respective backup cycle and is not put back into productive use.
Deletion can be triggered directly in the app: Settings → My data → *Delete all data*. The process deletes all local data on the device and ends the anonymous sync identifier. If you are the only person in the household, the synchronised household data on the server is deleted in full as well. If there are other people in the household, that data belongs to them too; in that case only your device's access ends, and the shared lists remain in place for the other members. The process is final and cannot be undone.
Deletion can also be requested by e-mail to kontakt@dayvela.app — for example if the server was unreachable at the time of deletion or if the device is no longer available. The household invitation code shown in the app may be needed in order to identify the data unambiguously. The code should be sent to this contact address only.
Completed moderation reports are deleted no later than twelve months after they are closed. They are kept for longer only in so far as this is necessary to counter repeated abuse, to establish or defend legal claims, or because of legal obligations. Reports found to be unfounded may be deleted earlier.
10. Security
Transmission to the backend is encrypted with HTTPS/TLS. Access to household data is restricted by anonymous Appwrite sessions, household memberships and row-level permissions. Despite appropriate technical and organisational measures, absolute security cannot be guaranteed.
11. Permissions and local notifications
Baskivo needs an internet connection for live sync and for an online product query that you explicitly trigger. Shopping mode can keep the display from switching off automatically while you shop. Baskivo does not request access to contacts, location, microphone or advertising ID. The optional camera permission serves solely the EAN/UPC recognition described in section 3 and can be refused, or withdrawn in the system settings.
You can optionally allow local system notifications for restock reminders you have switched on yourself. The app explains this function when you enable it and requests the notification permission only after you have chosen accordingly. Without that permission, due items remain visible inside the app. Notifications are scheduled on the respective device; no push token is transmitted to Baskivo or to any external push service for this. Item and list names may appear in the text of a system notification you have enabled, including on the lock screen, depending on your personal device settings.
12. Purchase and subscription
Baskivo Pro is sold through the Google Play billing system. Baskivo does not collect payment data such as card numbers, bank details or billing addresses, and does not receive any. The entire payment process takes place between you and Google; Google's privacy policy applies to that processing. Cancellation, payment method and receipts are held in your Google Play account.
After a purchase, Baskivo stores on the device the details needed to check your access: the purchase token issued by Google, the product identifier, the purchase time and any expiry time, and the time of the last confirmation. They are not transmitted via household sync, because a Play purchase is tied to the Google account and not to the household. Deleting the app data also removes these details; the purchase can then be restored through Google Play.
To confirm the purchase, the app transmits the purchase token and the product identifier to the Baskivo server; the server passes both on to Google Play and reports only the result back to the app — valid, invalid or not verifiable, and for a subscription along with the expiry time. The server stores nothing in the process, neither the receipt nor any reference to a user; at most the first eight characters of the token appear in the technical operating log. The check is carried out after a purchase, after a restore and at intervals of several days thereafter.
The legal basis for processing these purchase details — including the transmission for purchase confirmation — is Article 6(1)(b) GDPR, because it is necessary in order to perform the purchase contract for Pro access.
13. Rights of data subjects
Under the GDPR, data subjects have in particular the right of access, and the rights to rectification, erasure, restriction of processing, data portability and objection. They also have the right to lodge a complaint with a data protection supervisory authority.
Enquiries can be sent to kontakt@dayvela.app. As Baskivo does not collect real names or e-mail addresses for registration, additional details from the app may be needed in order to identify an anonymous data record.
14. Changes
This policy is adjusted when functions, recipients or legal requirements change. The current English version is available at https://api.klarkorb.dayvela.app/privacy, the German one at https://api.klarkorb.dayvela.app/datenschutz. Both versions have equal standing and describe the same processing.
The rules for shared households are available in the app and, once the server version is published, at https://api.klarkorb.dayvela.app/terms.