Tiny Bit Studio

Privacy

Last updated

In short

This page covers this website and our three apps, Michi, Lark and Kozeni. We don’t collect your data. None of them needs an account, and none has analytics, ads or tracking of our own. What you keep in the apps stays on your device and in your own iCloud, apart from the trips you share in Michi and the households you share in Kozeni, which go to the people you invite, and what Lark and Michi send to the services they use, such as YouTube and Apple Maps. Nothing that identifies you reaches us unless you write to us.

Each has its own section below: this website, Michi, Lark and Kozeni.

Privacy

This website

In short

We collect nothing through this website. It sets no cookies and has no analytics, ads or tracking. Everything a page loads, fonts and images included, comes from this site, so your browser contacts no one else.

GitHub

The site is a set of static pages hosted by GitHub Pages. GitHub logs and stores visitors’ IP addresses for security, whether or not they’re signed in to GitHub. The GitHub General Privacy Statement covers that.

Email

If you write to us, at hello@tinybit.studio or from one of the apps, we use your message and your address to reply, and to fix what you report. We don’t share them, and we don’t add you to any list. We keep them only as long as we need them for that, and we’ll delete them, with your address, whenever you ask.

Links to the App Store and other sites take you to services with privacy policies of their own.

Privacy

Michi

In short

There’s no account, no server of ours, and no analytics, ads or tracking. Your trips are kept on your device and in your own iCloud, and go to no one but the people you invite to them. Everything else Michi sends goes to Apple: to Apple Maps, for places, maps and routes, and, when you plan with Michi, to Apple Intelligence, which may run on Apple’s Private Cloud Compute. The one exception is a stop you open in Google Maps, which goes to Google.

You

The paths below start on Michi’s You page: tap the person button at the end of the album’s bar, after New Trip and the filter. A trip’s own options are in its brochure, under Trip Options, the … button.

On your device

Michi keeps your trips in its own storage on your device: each trip’s title, dates and ink (its stamp’s color); its stops, with each one’s name, town, place on the map, day, how long you’ll spend there, how you get there, notes and when you visited it; and its photos. For a shared trip, it also keeps who’s on it (see Sharing) and whether you can make changes. Where you’ve moved your stamps in the album, whether the full map shows satellite imagery, and your Daily Plan setting are kept on the device too, and so is each trip’s history (see Trip History). Michi has no networking code of its own; it goes online only through Apple’s iCloud, Apple Maps, Apple Intelligence and App Store, as described below. Backups of your device include all of this, apart from photos iCloud already has, which Michi downloads again if they’re missing.

iCloud

When your device is signed in to iCloud, Michi syncs your trips, their stops and their photos between your devices through Apple’s CloudKit, in your iCloud account’s private database. It keeps what they hold in CloudKit’s encrypted fields, and photos as files CloudKit encrypts. Where your stamps sit in the album, the satellite setting, Daily Plan, each trip’s history and conversations with Michi stay on each device, and Michi Pro doesn’t sync through iCloud at all: each device asks the App Store (see Michi Pro). iCloud wakes Michi silently when a trip changes on another device, so it can fetch the change; the only notifications Michi shows are the daily plans you ask for (see Notifications).

Michi has no sync switch of its own: it follows iCloud, which you can turn off for Michi in the Settings app, under your name → iCloud. Without iCloud, Michi works on the device alone, and syncs what you made there once you sign in. Signing out of iCloud, or switching to another account, removes every trip and photo from the device, with their histories and the maps, routes and places kept for them; what iCloud has comes back when you sign in again, and anything it hadn’t received yet is lost. Apple’s privacy policy covers iCloud.

Sharing

Invite, in the brochure of a trip you made, shares it through iCloud with the people you choose, by whichever app you send the invitation with, such as Messages or Mail. Only the people you invite can join: Michi never offers a link that anyone can open. You choose whether they can make changes or only view the trip. The share iCloud keeps, and the invitation, can’t be encrypted, so Michi never puts the trip’s title there: both say “A trip on Michi”, with Michi’s icon.

Everyone on a trip sees all of it: its title, dates, stops, notes and photos, whoever added them, and who’s on it, by the names iCloud gives or, where it gives none, by email address or phone number. Anyone who can make changes can add stops and photos, change or delete any of them, and bring back an earlier version of the trip (see Trip History). A shared trip is kept in the iCloud of its owner, the person who made it, and counts toward their iCloud storage. Travelers, in the brochure, opens Apple’s sharing sheet, where the owner can invite or remove people and stop sharing, and the others can leave. If you leave a trip, or are removed from it, what you added stays on it, and so do the versions on others’ devices that name you.

Trip History

Trip History, in Trip Options, lists earlier versions of a trip, so you can bring one back. Michi keeps a version each time the trip’s plan changes, whether you change it, apply changes from Michi, or someone’s change arrives through iCloud; changes a few minutes apart make one version. Each holds the trip’s title, dates and ink; its stops, with everything set for each, notes included, and when each was visited; and who made the change, by the name they have on the trip (see Sharing). It holds no photos. Versions are kept on the device that saw the changes, up to a trip’s last 40, and never sync: each of your devices keeps its own, and on a shared trip, so does each device of everyone on it. Only people who can make changes see Trip History. Restoring a version changes the trip for everyone on it (see Deleting).

Apple Maps

Michi finds places, draws maps and works out routes with Apple Maps, through Apple’s MapKit. It never uses your location, and never asks for it. Apple’s privacy policy applies to what Apple Maps receives.

  • Add Stop. What you type is sent to Apple Maps as you type it, with the area your trip’s stops are in, so places near them come first. Picking a result looks it up. Choose on Map, in Add Stop, opens Apple’s map around your trip’s stops: tapping a place the map marks, such as a café, looks that place up, and tapping anywhere else drops a pin and sends where it is to Apple Maps, for the spot’s name. Either way, Michi keeps the place’s name, town and place on the map.
  • Planning. When you plan with Michi, it searches Apple Maps for the places, towns and destinations the model names, and for what the model looks for, such as “ramen”, mostly in the area of the trip’s stops or its destination.
  • Maps. A brochure’s map, the full map, Add Stop’s map and each stamp’s print show Apple’s map of where the trip’s stops are, loaded from Apple Maps. Stamps’ prints are kept on your device.
  • Routes. When you open a brochure, its full map or a stop, or look over a plan from Michi, Michi asks Apple Maps for the route, or the travel time, from each stop to the next: where the two stops are and how you get there, without their names. Michi keeps routes on your device and asks for them again after 60 days, or 14 for travel times. A leg’s route goes once no trip has that leg.
  • Passport. When you open You or the passport, Michi asks Apple Maps which country and city each stop is in, from where the stop is and nothing else. The answers are kept on your device until no stop is there.

Apple Intelligence

Plan with Michi, in New Trip, and Ask Michi, in Add Stop, plan with Apple Intelligence, and only when you send them a message. On iOS 27, Michi asks Apple’s Private Cloud Compute first and, whenever it can’t answer, Apple’s on-device model; on iOS 26, it uses the on-device model alone. Private Cloud Compute runs Apple’s models on Apple’s servers, and Apple says what it’s sent is used only to answer, never stored, and can’t be seen by anyone, Apple included. The planner says when your messages may go there. For each message, the model is given:

  • your message, and the last three exchanges before it
  • the trip’s title and dates, or what you’ve filled in of New Trip
  • each stop’s name, town and day, how long you’ll spend there and how you get there, and the first line of its notes, up to 110 characters, whoever wrote them
  • the names and towns of the places Apple Maps finds for it, and the language to answer in

It isn’t given where the stops are on the map, the trip’s photos, who’s on it, anything from your other trips, or your location. Conversations and drafts are kept in memory only, and are gone once you close the planner. Nothing Michi drafts is saved until you tap Create Trip or Apply Changes; after that, its stops and notes are saved, and sync, like any you add yourself.

Photos

Add Photos, on a stop you’ve visited, opens the system’s photo picker. Michi can’t see your photo library: it gets only the photos you pick, which the picker may first download from iCloud Photos. It keeps a copy of each at full size, without its location, camera details or other metadata, apart from the date it was taken, which it uses to sort them and, for a stop’s first photo, as the day you visited. The copies sync through iCloud, and on a shared trip go to everyone on it.

Save All Photos, in Trip Options, adds every photo of the trip that’s on your device to your photo library, other travelers’ included, without their location or camera details. It asks only to add to your library, never to see it. The share button in the photo viewer shares one photo, and Share as Image, in Trip Options, makes one picture of the brochure, with each stop, the first line of its notes and its photos, but not who’s on the trip; where they go is up to you. Anyone on a trip can use all three, even if they can only view it.

Passport

The passport, at the top of You, is worked out on your device from your trips each time you open it, and isn’t stored or synced. Its countries and cities are Apple Maps’ (see Apple Maps), and the name on it is yours as iCloud gives it on a shared trip. While it’s open, Michi reads the device’s tilt for the hologram, unless Reduce Motion is on, and keeps nothing of it.

Notifications

Daily Plan, in You → Notifications, is off until you turn it on, and Michi asks to send notifications only when you do. Then, on each day of a trip with dates that has stops planned, trips shared with you included, it sends you that day’s plan at the time you choose, wherever you are: the trip’s title, which day of the trip it is and how long its stops come to, and the stops’ names. Michi schedules them on your device and the system shows them, so nothing comes from a server; they appear wherever your notification settings allow, such as the Lock Screen. Whether Daily Plan is on, and its time, are kept on each device. Turning it off takes back the plans still to come, and a trip that leaves the device takes its plans with it, those already sent too.

Michi Pro

Michi Pro, in You → Support, is one purchase through Apple’s App Store, not a subscription. It unlocks every ink, and Michi on every trip. Apple handles the payment, and we never see your payment details. Michi asks the App Store whether your Apple Account has Michi Pro, bought on any of your devices or shared with you through Family Sharing, and keeps only the answer, on your device. It keeps no receipt, amount or date.

Without Michi Pro, Michi is free on three trips: the first three a plan or changes from Michi are saved to. To count them, it keeps those trips’ IDs on your device only, even once a trip is deleted.

Feedback

You → Support → Send Feedback opens a draft email to support@tinybit.studio in your mail app, with the subject “Michi feedback”. Below the space for your message, under “Info”, it fills in Michi’s version, your system’s name and version, and your device’s model identifier, such as iPhone17,1. It adds nothing else. You can change any of it, and nothing is sent unless you send it. We use your message only to reply and to fix what you report, and we don’t share it.

Other apps

Apple Maps, on a stop, hands the stop’s name and place to the Maps app. Google Maps, beside it, hands the stop’s name, town and place to the Google Maps app or, where it isn’t installed, opens Google Maps’ website in your browser with the stop’s name and town; Google’s privacy policy applies there. The links to this website, at the foot of You, open in your browser. What happens in those apps and sites is up to them and their policies.

Deleting

  • A photo. Delete Photo, when you touch and hold a photo or in the viewer, deletes it from your devices and from iCloud, and, on a shared trip, for everyone on it.
  • A stop. Deleting a stop deletes its photos with it, for everyone on a shared trip. The trip’s earlier versions keep the stop, without its photos, until later versions take their place (see Trip History).
  • A version. Restore This Version, in Trip History, deletes the stops added since, with their photos, for everyone on the trip.
  • A trip. Delete Trip, in Trip Options or the stamp’s menu, deletes the trip, its stops and its photos from your devices and from iCloud, and for everyone you’ve shared it with, and each device it was on deletes its history. It can’t be undone. On a trip someone else shared with you, Leave Trip takes it, and its history, off your devices instead, and what you added stays on it.
  • The app. Deleting Michi deletes what it keeps on that device. Backups of your device keep a copy until they’re replaced or deleted.
  • iCloud. Your trips stay in iCloud, and on your other devices, until you delete them in Michi. You can also delete Michi’s data from iCloud storage in the Settings app, which deletes the trips you made for everyone you’ve shared them with too.

Photos you’ve saved to your library, and pictures you’ve shared, stay where they went. There’s no Recently deleted, though Trip History can bring back a deleted stop, without its photos, while a version that has it is kept. Apart from a trip’s oldest versions, which give way past 40, nothing expires on its own: Michi keeps your trips until you delete them.

Analytics

Michi contains no analytics, crash reporting, advertising or tracking code, and no third-party libraries. It doesn’t use the advertising identifier or ask to track you. It writes notes about what failed to the device’s own system log, never what you wrote or planned, and doesn’t collect them. If you’ve turned on Share With App Developers, in the Settings app under Privacy & Security → Analytics & Improvements, Apple may give us anonymous crash reports and aggregated statistics about how Michi is used. Those come from Apple, under Apple’s privacy policy, not from anything in Michi.

Children

Michi collects no data from anyone, children included.

Privacy

Lark

In short

There’s no account, no server of ours, and no analytics, ads or tracking. Lark transcribes, translates and explains on your device. Data leaves the device only for the services you use through Lark, listed below, and for your own iCloud.

Going online

Apart from syncing with your iCloud, and loading the artwork of what’s on screen, Lark goes online only to do something you’ve asked of it. Below is every place it connects to, and what it sends. Each request also carries your IP address, as any request does, and the service that receives it handles it under its own policy. Lark sets and reads no cookies of its own; as in any app, iOS keeps the ones a server sets and sends them back to that server.

When you search, Lark sends what you’ve typed to Apple’s podcast directory (the iTunes Search API), shortly after you stop typing or when you press Search. Opening a show sends the show’s ID, to list its episodes. Artwork, in results and on your library’s cards, loads from the addresses the directory returns whenever it’s shown. Apple’s privacy policy applies. Your last ten searches are kept on your device until you clear them.

Podcasts

Episodes stream from their publishers’ servers, often by way of services that count downloads for the publisher. When you make an AI transcript of an episode, Lark downloads the whole episode from the same address and keeps it on your device, so the transcript matches what you hear. When it makes a transcript of an episode whose language is set to Automatic, or takes subtitles you import for one, it also reads the start of the podcast’s feed to find out the language. Publishers, and the services they use, see these requests as they would from any podcast app.

YouTube

YouTube is Google’s, and Google’s privacy policy applies to everything YouTube receives through Lark.

  • Adding a video. Lark sends the video’s link to YouTube for its title, channel and thumbnail, and the thumbnail loads from YouTube whenever its card is shown.
  • Captions and audio. When Lark fetches a video’s captions (by default, as soon as you add it) or makes an AI transcript of it, it asks YouTube for the video’s caption tracks and audio streams, then downloads the captions in the material’s language, or the audio. Lark’s part of each request is the video’s ID, with a fixed language (English), region (US) and time zone in place of yours, and nothing about your device; iOS adds its usual headers, as it does for any app. Downloaded audio is deleted as soon as the transcript is done, or if it fails or you cancel it.
  • Playing. Videos play in YouTube’s own embedded player, inside Lark. It runs YouTube’s scripts, which can store cookies and similar data on your device and collect information as YouTube’s player does anywhere. That data is stored on your device, and Lark never reads it.

Speech models

The first time you make an AI transcript in a language, Lark asks iOS for Apple’s speech model for that language, and iOS downloads it from Apple.

iCloud

When your device is signed in to iCloud, Lark syncs a small record between your devices through iCloud key-value storage, in your own iCloud account. For each card, it holds:

  • its ID, title and author
  • its kind and source: a YouTube video ID, a podcast episode’s address, or a note that the file is on one device only
  • its language, level and length
  • how many sentences it has and how many you’ve practiced, where you left off, how long you’ve practiced it and whether it’s done
  • when you added it, last practiced it and last changed it
  • the addresses of its artwork (if it’s online), source page and podcast feed

It also holds the days you practiced and when you last reset them, and the ID and date of each material you delete, kept for 180 days so it’s deleted on your other devices too. Files you import don’t sync, but their cards’ titles and authors do. A video from Files is titled with its file name; an audio file takes its title and artist (or album) from its own tags, or its file name if it has none. A renamed card syncs under its new name.

Media files, transcripts, card stills, recordings, explanations, settings, recent searches and the weekly count of AI transcripts never sync. Lark has no switch for this; without an iCloud account, it works on the device alone.

Lark Pro

Lark Pro, in You → Support, is one purchase through Apple’s App Store, not a subscription. It takes the limit off AI transcripts and unlocks every accent color. Apple handles the payment, and we never see your payment details. Lark asks the App Store whether your Apple Account has Lark Pro, bought on any of your devices or shared with you through Family Sharing, and keeps only the answer, on your device. It keeps no receipt, amount or date.

Without Lark Pro, Lark makes three AI transcripts a week. To count them, it keeps a note of each one it makes (the material’s ID and when you asked for it), up to the last 500, and when it started counting and the latest time your device’s clock has shown, on your device only, even once a material is deleted.

Feedback

You → Support → Send Feedback opens a draft email to support@tinybit.studio in your mail app, with the subject “Lark feedback”. Below the space for your message, under “Info”, it fills in Lark’s version, your system’s name and version, and your device’s model identifier, such as iPhone17,1. It adds nothing else. You can change any of it, and nothing is sent unless you send it. We use your message only to reply and to fix what you report, and we don’t share it.

Other apps

“Open in YouTube”, “Open in Podcasts” and “Open source page” hand the link to that app, or to Safari. What happens there is up to that app and its policy.

Microphone

Lark uses the microphone only if you turn on Record Attempts, which is off by default, and it asks your permission the first time. It records only during your turn: one file per sentence, replaced each time you try again, in Lark’s temporary folder. Each recording plays back once, after your turn. All of them are deleted when the drill ends, and they’re never uploaded or synced. If you don’t allow the microphone, drills work without recording. If Lark is stopped in the middle of a drill, its recordings are left in the temporary folder until iOS clears it.

On your device

Apple’s Speech framework makes the AI transcripts. Apple’s Translation framework makes the translations, using only languages already on your device. Apple’s on-device model writes the explanations. Language detection runs on the device too. Lark makes no network request of its own for any of them. To explain a sentence, the model is given the sentence, its translation (when there is one), the names of the language you’re studying and of your own language, and your device’s locale. When it has to write the meaning itself, it also gets the lines before and after. Explanations are kept in memory only, until Lark quits.

Storage

Lark keeps your library on your device: each material’s details and transcripts, your progress, the video and audio files you import from Photos or Files (copied in), the podcast episodes it downloads for transcripts, and card stills, including an audio file’s own cover art. A subtitle file you import from Files isn’t copied in: Lark keeps the lines it reads from it, and their times, as that material’s transcript. Your settings, practice days and recent searches are kept there too, and so is whatever YouTube’s player stores. Temporary audio made while transcribing is deleted when Lark is done with it. Lark doesn’t keep its files out of your device’s backups, so a backup to iCloud or a computer includes them.

Lark can’t see your photo library or your files. It gets only the item you pick, through the system’s picker, which may first download it from iCloud Photos.

Deleting

  • A material. Deleting one removes its card, its transcripts, your progress in it, and the file it played from, unless another material uses the same file. The deletion syncs, so it goes from your other devices too. Marking a material Done deletes nothing.
  • Your practice record. You → Reset Practice Record forgets every day you’ve practiced, on this device and your other devices. Your library and progress stay.
  • Leftover files. You → Storage → Clear Out Unused Files deletes files no material uses, such as a canceled transcript’s audio.
  • Recent searches. Clear, on the search page, removes them.
  • The app. Deleting Lark deletes everything it keeps on the device, including YouTube’s player data. Backups of your device keep a copy until they’re replaced or deleted.
  • iCloud. Lark doesn’t erase what it has synced to iCloud key-value storage, so that may stay in your iCloud account after you delete the app. To leave as little as possible there, delete your materials and reset your practice record first: then only the IDs and dates of what you deleted, and the date of the reset, remain.

Analytics

Lark contains no analytics, crash reporting, advertising or tracking code, and no third-party libraries. It doesn’t use the advertising identifier or ask to track you. It writes a few notes to the device’s own system log, such as a material’s title when its transcript is done, and doesn’t collect them. If you’ve turned on Share With App Developers, in the Settings app under Privacy & Security → Analytics & Improvements, Apple may give us anonymous crash reports and aggregated statistics about how Lark is used. Those come from Apple, under Apple’s privacy policy, not from anything in Lark.

Children

Lark collects no data from anyone, children included. YouTube and the other services you use through it have policies of their own.

Privacy

Kozeni

In short

Kozeni collects no data. What you enter stays on your device and, if you use iCloud, in your own iCloud, where we can’t see it, apart from a household, which you share with the people you invite to it. There’s no account, no server of ours, and no analytics, ads or tracking.

Settings

The paths below start in Kozeni’s Settings. On iPhone, tap the four‑squares button at the bottom of the screen, then Settings; on iPad, Settings is in the sidebar.

On your device

Kozeni keeps your entries (amount, expense or income, category, note, date and how it repeats), categories, recurring items and budgets in a database on your device, along with your settings and the highlights Insights has picked. In a household, it keeps the household’s entries, categories, recurring items and budgets in a second database on your device, with who’s in it (see Household). For the Home Screen widget, it writes a short summary to storage it shares only with the widget: your totals for the week, month and year, and your latest entries with their notes and amounts, from your household while you’re in one. The widget makes no network requests. Kozeni has no networking code of its own; it goes online only through Apple’s iCloud and App Store, as described below.

iCloud

If iCloud is on for Kozeni, your entries, categories, recurring items and budgets sync between your devices through Apple’s CloudKit, in your iCloud account’s private database. Entries in Recently deleted sync too, until they’re removed. Your settings, the widget’s summary and the saved highlights stay on each device, and Kozeni Pro doesn’t sync through iCloud at all: each device asks the App Store (see Kozeni Pro). Kozeni has no sync switch of its own: it follows iCloud, which you can turn off for Kozeni in the Settings app, under your name → iCloud. A household syncs on its own, through its owner’s iCloud (see Household). Apple’s privacy policy covers iCloud.

Household

Settings → Sharing → Household lets you keep one ledger with the people you live with. Creating a household needs Kozeni Pro; joining one doesn’t. You can be in one household at a time.

  • Where it’s kept. A household is kept in the iCloud of its owner, the person who created it, through Apple’s CloudKit, in a part of their private database of its own, and counts toward their iCloud storage. The people in it reach it through iCloud sharing. Everything anyone writes in it, amounts, notes and categories included, is kept in CloudKit’s encrypted fields. The share iCloud keeps, and the invitation, can’t be encrypted, so Kozeni puts nothing of the household there: both say “A household on Kozeni”, with Kozeni’s icon.
  • Inviting. Only the owner invites people, with the invite button on the Household page, by whichever app they send the invitation with, such as Messages or Mail. Only the people the owner invites can join: Kozeni never offers a link that anyone can open, and nobody can ask to join.
  • What everyone sees. Everyone in a household sees all of it: its entries, categories, recurring items and budgets, who logged each entry and who set up each recurring item, and who’s in it, by the names iCloud gives or, where it gives none, by the email address or phone number they were invited at. Kozeni learns your name only from iCloud, through the household’s share; it never reads your contacts or looks anyone up. Everyone can change their own entries; the owner chooses, under Permissions, whether the others can change everyone’s entries, categories and budgets too.
  • Joining. When you create or join a household, your entries and recurring items move into it, Recently deleted included, and your categories are matched to the household’s. The owner’s budgets are copied in; a member’s stay where they were. While you’re in a household, everything you log goes to it, from Shortcuts and Siri too, and your own ledger is hidden until you leave.
  • Leaving. A member can leave, and the owner can remove someone or delete the household, on the Household page. Whoever leaves or is removed keeps a copy of their own entries, and the household keeps them too unless the person leaving, or the owner removing them, chooses otherwise. Deleting the household removes it, and everything in it, from the owner’s iCloud; everyone keeps a copy of their own entries, and the owner can keep everyone’s. Once you’re out of a household, by any of these or by signing out of iCloud, Kozeni removes it from your devices, with its highlights, its widget summary and the reminders for its recurring items.

Shortcuts and Siri

Kozeni can log Apple Pay purchases for you through a shortcut. Settings → Preferences → Shortcuts → Add automation opens a ready-made shortcut from iCloud; you add it, then turn it on in the Shortcuts app, and iOS asks your permission the first time it runs. Each time, the shortcut hands Kozeni a note (the merchant’s name, for example), an amount, a date, whether it’s an expense or income, and, optionally, a category name. Kozeni saves them as an entry, which syncs like any other. Clean up notes, on by default in the same place, first takes store numbers such as “#1234” off the note, on your device. Kozeni never reads Wallet or your cards itself; it gets only what the shortcut passes in.

Kozeni’s actions in Siri and Shortcuts can also log a transaction, find entries, change or delete one, total your spending, check your budgets and log a receipt. Siri gets what an action returns, such as the entries it found, with their notes and amounts, or the totals, and Apple’s privacy policy covers what Siri does with it. Every action but Log Transaction asks you to unlock your device first. Log Transaction can run on a locked device, so the Apple Pay shortcut works, and there its result shows only what it was given, the note, the amount and the time, not the category Kozeni chose.

Log Receipt reads a receipt, an image or a PDF that Siri or a shortcut hands it, on your device, with Apple’s Vision framework, and asks you before it saves. It keeps only the entry: the merchant as its note, the total, the date and a category. The file and the text read from it are never saved.

Apple Intelligence

Where Apple Intelligence is available and turned on, Kozeni uses Apple’s on-device model in three places. It makes no network request for either, and the results stay on your device.

  • Highlights. Kozeni writes the Insights highlights itself, from the period’s figures. The model is given those lines, which can include amounts, percentages, category names, weekdays or months, and the note of the period’s largest expense or income, cut to 40 characters, and in a household the name of whoever logged it. It only chooses which lines to show. Without Apple Intelligence, Kozeni shows its top-ranked lines instead. Settings → Reset → Reset AI analysis clears the saved ones.
  • Categories for logged purchases. When Log Transaction is given no category name, or Log Receipt reads a receipt, Kozeni looks for an earlier entry with the same note, then for your default category. If it finds neither, the model is given the entry’s type, amount and note, the names of your categories of that type, and up to eight recent notes with their categories, which in a household can be anyone’s in it. It answers with one of your categories, or none. This happens only while Smart category is on and no default category is set, both in Settings → Preferences → Shortcuts.
  • Receipts. When Log Receipt has read a receipt’s text, the model is given that text, or the first 2,500 and the last 1,500 characters of a longer one, and answers with the merchant, the total, its currency and the date. Without Apple Intelligence, Kozeni finds them in the text itself.

Notifications

If you turn them on in Settings → Preferences → Notifications, Kozeni schedules its reminders on your device: a daily reminder to log, and a reminder when a recurring item is due, which shows the item’s note or category, its amount and how often it repeats. In a household, When others log, on the same page and off until you turn it on, shows a notification when iCloud brings in an entry someone else logged: their name, the amount and the entry’s note or category. Kozeni makes each of these on your device, and none is sent from a server. In a household, Kozeni also receives iCloud’s silent notifications, which show nothing and only tell it to fetch what’s changed. Notifications appear wherever your notification settings allow, such as the Lock Screen.

Kozeni Pro

Kozeni Pro, in Settings → Support, is one purchase through Apple’s App Store, not a subscription. It unlocks the extra Theme colors and creating a household. Apple handles the payment, and we never see your payment details. Kozeni asks the App Store whether your Apple Account has Kozeni Pro, bought on any of your devices or shared with you through Family Sharing, and keeps only the answer: on your device, and in the storage it shares with the widget, so the widget can use the colors Pro unlocks. It keeps no receipt, amount or date.

Ratings

After your first ten entries or three days, whichever comes first, Kozeni asks iOS a single time to show Apple’s rating prompt. It isn’t told what you choose.

Feedback

Settings → Support → Feedback opens a draft email to support@tinybit.studio in your mail app, with the subject “Kozeni feedback”. Below the space for your message, under “Info”, it fills in Kozeni’s version and build, your system’s name and version (iOS or iPadOS), and your device’s model identifier, such as iPhone17,1. It adds nothing else. You can change any of it, and nothing is sent unless you send it. We use your message only to reply and to fix what you report, and we don’t share it.

Export and import

Settings → Backup → Export data makes three CSV files, of your entries, categories and budgets, and hands them to the share sheet; where they go next is up to you. They leave out Recently deleted, your settings and the saved highlights. In a household, they’re the household’s, and the entries file names who logged each entry. Kozeni writes them to its temporary folder on your device, where they stay until iOS clears it. Import data reads one CSV file that you pick and adds its rows to Kozeni; in a household, it asks first, since everyone in it will see the entries. Kozeni can’t open any file you haven’t picked.

Deleting

  • An entry. Deleting an entry moves it to Settings → Library → Recently deleted, where you can swipe left on it to restore it within seven days. After that, it’s removed for good the next time Kozeni opens. The bin button at the top right clears everything there at once.
  • Everything. Settings → Reset → Erase all data deletes every entry (Recently deleted included), category, recurring item and budget, and the saved highlights. It offers to export first. With iCloud on, the deletion syncs, so it all goes from your other devices and from iCloud too. It isn’t offered while you’re in a household: leaving one, or deleting it, is on the Household page (see Household). Your settings and Kozeni Pro stay, and the widget’s summary is replaced the next time you return to Kozeni.
  • The app. Deleting Kozeni deletes its data from that device. Backups of your device keep a copy until they’re replaced or deleted.
  • iCloud. Your data stays in iCloud, and on your other devices, until you delete it there. To remove it everywhere, use Erase all data before you delete the app. You can also delete Kozeni’s iCloud data from iCloud storage in the Settings app.

Apart from Recently deleted, nothing expires on its own: Kozeni keeps your data until you delete it.

Analytics

Kozeni contains no analytics, crash reporting, advertising or tracking code, and no third-party libraries. It doesn’t use the advertising identifier or ask to track you. If you’ve turned on Share With App Developers, in the Settings app under Privacy & Security → Analytics & Improvements, Apple may give us anonymous crash reports and aggregated statistics about how Kozeni is used. Those come from Apple, under Apple’s privacy policy, not from anything in Kozeni.

Children

Kozeni collects no data from anyone, children included.

Changes to this policy

If what this website or any of the apps does with your data changes, we’ll update this page and the date at the top.

Contact

Write to hello@tinybit.studio with any question about privacy, or about this page.

Credits

Lark’s App Store screenshots show stills from these videos, and lines of the first one’s narration, transcribed and translated by Lark. All three are licensed under CC BY 3.0.

Their creators aren’t connected with Tiny Bit Studio and don’t endorse Lark.

Michi’s seal is Wu Ju’s 道, adapted from Modelbooks of the Three Rarities Hall, Vol. 17: Transcription of Six Poems, Including “A Tamed Flying Deity Being Saddled”. The National Palace Museum, Taipei, CC BY 4.0 @ www.npm.gov.tw. The museum doesn’t endorse Michi.