Privacy Policy

Last updated: 13 November 2026

Kozica is an Android app for hiking in the Polish mountains: an offline map of the trails, drawn in their signpost colours. This policy describes what the app does with information about you. It is short because the app does very little.

The app collects nothing

Kozica has no account, no sign-in and no server. The app has no permission to use the internet, so it cannot send anything anywhere.

What it keeps (your settings, including where you left the map; the routes you save, each a name and the points you chose; and the hikes you record, with their notes and photos) is stored only in the app’s private storage on your own phone, and is readable only by the app.

There is no analytics, no crash reporting, no advertising, and no third-party SDK that phones home.

Backup files. Settings has Backup and restore, which writes your routes, hikes, notes and settings, and your photos if you choose, to a single file. The file leaves the phone only when you share it or save it to a folder you choose yourself; the app sends it nowhere.

GPX files. A hike or a saved route can be exported as a GPX file, for another map app or a watch. A hike’s file holds its track with the times you walked it, its name, its note, and where its photos were taken, with their captions but not the photos.

Sharing a file. Some phones’ share screens only hand a file over if every app that can receive one may read it before you choose, so the app allows that when you share a backup or a GPX file. Once you pick an app, the others lose that access, and if you close the share screen without picking, all of them lose it as soon as you are back in the app (or, if the phone closed the app meanwhile, when you next share that kind of file). The one you picked keeps it until you next export or share that kind of file, or restart the phone. The app itself sends the file nowhere.

What the app can access, and why

Your location, only once you tap the position button and allow it, to draw where you are on the map. It is read on the phone and used there, never sent anywhere, and the app keeps no record of it. The map does remember where you left it, in the app’s settings: if you last used the position button to centre it, that spot is where you were. The settings go into Android’s backup below with the rest of the app’s data. You can allow only an approximate location, or none, and the map works without it.
Your location while you record a hike, only once you tap Record and allow precise location. The app then keeps the hike’s track, where you walked and when, in its private storage on the phone, for as long as you keep the hike. It is never sent anywhere by the app. While a hike records, a notification says so, and the app reads your location with the screen off until you stop it. Recording asks for notifications once, for that notification; you can say no and still record.
Your location while you follow a Route, only once you tap Follow and allow precise location. While the app is on screen it reads your location to show how far along the Route you are. So that it can pick up where you were if Android closes it, the app keeps the Route you follow and how far along it you are in its settings on the phone, until following ends, or the next time you open the app once 24 hours have passed. It is never sent anywhere by the app, and goes into Android’s backup below with the rest of the app’s data.
Photos you add to a hike, only the ones you take with your camera app from the recording bar or pick yourself with Android’s photo picker, which shows the app nothing else. Neither needs a permission. The app keeps its own smaller copy in its private storage, with the photo’s location and all its other metadata removed. It reads only when the photo was taken, before removing it, to place the photo on the hike’s track.

When you write to the developer

The Help and feedback screen in Settings has a row to report a problem and one to suggest a feature, and Settings’ Language section has Something read wrong?. Each opens your own email app with a draft addressed to the developer. The draft carries the app’s version, your Android version, your phone’s make and model, and the language you are reading the app in, so a report can be acted on. You see every line before sending, can change or delete any of it, and nothing is sent unless you send it yourself.

The screen’s other rows send nothing. One shows the developer’s address and copies it when tapped, and another copies the app’s version; both stay on your phone until you paste them somewhere. Rating the app opens Google Play, and the app’s web page, this privacy policy and More MaksForge apps open in your web browser, which then works under its own privacy policy. Credits stays inside the app.

The two things that happen outside the app

These are done by the operating system or by Google, not by Kozica, but they are the honest answer to “where could my data be”:

Android’s automatic backup. If it is enabled on your phone, Android backs up the app’s database, which holds your saved routes and your recorded hikes with their tracks and notes, its settings, and as many of its small photo previews as fit, not the photos themselves, to your own Google Drive, in a space that does not count against your storage quota and that Google states apps cannot read. When you move to a new phone with Android’s own phone-to-phone transfer, the photos go too, straight to the new phone. You can turn backup off in your phone’s settings.
Google Play. Installing and updating an app is a transaction between your phone and Google, with its own privacy policy. The developer of this app receives aggregate, anonymous statistics — install counts, crash rates, country-level breakdowns — and no information about individuals. The map data is downloaded by the Play Store app too, under Google’s terms, after Kozica is installed; Kozica itself opens no connection.

Children

The app is not directed at children and collects nothing from anyone.

Deleting your data

Uninstalling the app removes everything it stored on the phone. A copy can be in three other places:

A backup file or a GPX file you exported, wherever you shared or saved it.
Android’s backup in your Google Drive, if backup is on. It outlives an uninstall, which is how a reinstall gets your data back. Delete it under Backups in Google Drive, or manage it in your phone’s backup settings.
A mail you sent the developer. It is kept in the developer’s mailbox, with your email address and what the draft carried, until you ask for it to be deleted. Write to the address below and it will be, including a mail sent to the developer’s earlier address.

Changes

If this policy changes, the date at the top changes with it, and the history of this file is public in the repository.

Contact

kozica.support@maksforge.com