Local capture first
Voice recordings are saved as encrypted local chunks before any transcript, recipe, or action review workflow runs.
Privacy
Private by default, explicit by design.
lilKiTTY is built for Apple Watch-first voice capture on Apple devices. Recordings are saved locally by default, and generated drafts require review before use.
Effective July 28, 2026
Recovery stays local
Companion-app notes remain recoverable in local Trash for 30 days. Permanent deletion removes their metadata and encrypted source files from that device.
You start capture
lilKiTTY uses the microphone only when you start recording. The app is built for intentional personal notes, ideas, tasks, reminders, and meetings.
No tracking surface
The public lilkitty.app site is a static product and privacy surface. It does not store voice notes and ships without third-party analytics.
Suggestions need review
Transcripts, summaries, tasks, reminders, and documentation updates are assistive outputs. You are responsible for reviewing them before relying on them.
Need help? Visit lilKiTTY Support or email shoutout@lil.business.
Data use
What lilKiTTY does not do.
lilKiTTY does not use the public website as a note or audio storage path. The app does not send voice data to Cloudflare by default, does not run third-party analytics on this site, does not sell personal information, and does not require sign-in for local capture.
Policy
Plain-language privacy details.
Information processed by the app
lilKiTTY can process recordings, transcripts when available, optional anonymous speaker labels and names you assign locally, note titles and their local refinement state, private folder names and membership, optional recurring-folder rules containing a one-way calendar-series identifier, normalized title key, and folder target, reviewed operational mentions and source-note references, private template names, descriptions and section choices, saved-question names, question text and scope, context tags, draft action candidates, meeting recipes, capture status, error messages, and local diagnostics needed to run the app. Local capture does not require sign-in.
Where data is stored
By default, companion capture rotates through bounded temporary audio windows on the recording device. Each completed window is encrypted and verified before it is appended to the note, then that plaintext window is removed. A small recovery record inside the app's local container can reconcile already-encrypted parts after an interrupted save; it may contain the current note metadata needed for recovery and does not contain audio content. Local recordings, transcripts, metadata, and generated outputs remain on that device by default. Companion-app Trash retains a moved note for 30 days unless you permanently delete it sooner. The current Watch app does not transfer recordings or note summaries to its companion app.
Apple Speech recognition
With your permission, supported iPhone, iPad, Mac, and Vision Pro surfaces can ask Apple's Speech framework for on-device transcription during capture and, when needed, after encrypted save. The app requires on-device recognition and does not fall back to Apple's network speech service. If on-device recognition is unavailable for the selected language or device, no transcript is created and the encrypted recording remains saved. Temporary transcription audio is removed when the attempt finishes or times out. Watch-local recordings are not transferred or transcribed in v1.
Pause, transcript search, and copy
On companion development surfaces, pause and resume control the same local recorder and create no network request. Finalized on-device transcript results for encrypted parts may be assembled during capture, but lilKiTTY does not claim volatile word-by-word live transcription until physical microphone, route, interruption, latency, and recovery tests pass. A transcript search query and transient copied marker remain only in the open view and are not persisted, logged, counted, model-processed, included in diagnostics, or transmitted. Copy All and per-turn copy run only when you choose them; copied transcript text is then controlled by the Apple device clipboard and your later paste destination. Apple Watch does not include transcript controls.
Local Vocabulary
On iPhone, iPad, Mac, and Vision Pro development surfaces, you can save up to 100 short words or phrases for Apple Speech to expect in future transcripts. They stay in a protected local primary/backup file and are used only as contextual hints while lilKiTTY continues to require on-device speech recognition. They are not replacement rules or acronym definitions, are not mined from notes, and are not placed in UserDefaults, logs, product counters, Foundation Models prompts, shares, exports, support data, or developer systems. The Watch app does not include Local Vocabulary.
On-device title refinement
lilKiTTY creates a deterministic title locally from available note content. On supported iPhone and iPad systems, Apple Foundation Models may refine it on device. The app does not use Private Cloud Compute, a lilKiTTY server, or another network model for this feature. If the model is unavailable, cancelled, or fails, the deterministic title remains. Your title edit wins over late model output. The Watch app does not refine titles.
On-device enhanced note refresh
Only when you choose Refresh, lilKiTTY creates a bounded snapshot of that note's written notes, finalized transcript, reviewed action plan, context tags, and selected template section labels. Supported systems may use Apple Foundation Models on device to propose refreshed sections. Raw audio and private-template descriptions are excluded, and the request does not use Private Cloud Compute, a lilKiTTY server, or another network model. A deterministic local enhancer remains available when the model cannot run. Edited generated sections require preview acceptance; your written notes and user-owned sections remain authoritative. Accepted sections, local provenance, and bounded revisions stay with the local note. Apple Watch does not include this feature.
Local questions about notes
On iPhone, iPad, and Mac development surfaces, you can explicitly ask about one open note, 2–40 notes you select, or one private local folder. lilKiTTY bounds the question, written notes, and transcript segments before processing them on that device; every multi-note scope is capped to 40 eligible notes and 32,000 source characters. Supported systems may use Apple Foundation Models on device; unavailable, unsupported, timed-out, invalid, or uncited output falls back to deterministic local extraction. Answers reveal one to three exact source excerpts labelled with their source note or say the answer was not found. Selections, questions, answers, and source reveals are temporary, are not saved as chat history or logs, and are not sent to lilKiTTY, Private Cloud Compute, or another model provider. The Watch app does not include folders or note questions.
Private local folders
On iPhone, iPad, and Mac development surfaces, folder names, optional descriptions, system-icon choices, one-level nesting, and note membership stay in the same protected local manifest as note metadata. If you accept the optional prompt to file future instances of a recurring meeting, the manifest also stores a one-way series identifier, normalized exact-title key, and folder target. It does not retain the raw calendar identifier, attendees, location, description, URL, organizer, or event body in that rule. Undoing automatic filing, removing its membership, or deleting the folder removes the rule. A note can belong to more than one folder, and deleting a folder does not delete its notes. There are no folder accounts, team workspaces, permissions, public links, integrations, or developer access to this metadata. The Watch app does not expose folders.
Related Meetings
On iPhone, iPad, Mac, and Vision Pro development surfaces, opening an identified recurring note can reveal earlier active notes whose already-stored one-way series identifier or normalized exact title matches. The list is computed on the device, is not stored as viewing history, requests no new Calendar access, and is not sent to a model or developer system. It does not read attendees, location, description, URL, organizer, event body, Contacts, transcript text, or human-note text. The Watch app does not include Related Meetings.
Local People and systems records
On iPhone, iPad, and Mac development surfaces, lilKiTTY can group reviewed or user-corrected note entities into local records for people, software and services, and systems and places. A record contains only its reviewed name and type, cloud or local scope when known, and links to at most 40 source notes. Equal names with different types remain separate. lilKiTTY does not query Contacts, calendar attendees, employers, directories, social networks, the web, or a developer service and does not invent profiles, job titles, employers, email addresses, avatars, or relationships. Questions are available only when at least two source notes can answer them and reuse the same temporary bounded local answer flow. The Watch app does not expose these records.
Private local templates
On iPhone, iPad, and Mac development surfaces, lilKiTTY can keep up to 24 private templates in a protected local primary/backup file. Each template has a unique bounded name, optional short description, and one to eight fixed section choices. The description is explanatory metadata, not an AI prompt. Applying a template after review deterministically selects existing note sections; it does not regenerate the transcript, title, or review. Sharing remains explicit and excludes raw audio. There is no account, team publishing, public link, sync, or Watch template surface.
Private saved questions
On iPhone, iPad, and Mac development surfaces, lilKiTTY can keep up to 24 private saved questions in a protected local primary/backup file. Each item has a unique bounded name, bounded question text, and a one-note or multiple-note scope. Choosing one only prefills the existing Ask field; nothing runs until you review it and press Ask. The submitted question then uses the same bounded, temporary, cited local-answer flow. There is no automatic run, note selection, chat history, account, team sharing, sync, network provider, or Watch surface.
Meeting recording and consent
lilKiTTY records only after you deliberately start capture. It does not automatically record meetings, detect or capture another app's iPhone or iPad call audio, join a meeting as a bot, or verify that another person consented. You must provide notice and obtain consent required by applicable recording, privacy, workplace, contractual, and confidentiality rules.
Local diagnostics and feature counts
lilKiTTY may keep coarse totals on the device, such as how many captures started or reviewed drafts were confirmed. These totals do not contain note text, audio, titles, people, meeting names, destinations, timestamps, locations, or device/account identifiers. They are not sent automatically to the developer. A future support export may include them only after you choose to preview and share it.
When data leaves the recording device
The current development app does not upload notes, titles, transcripts, recordings, folder names or membership, recurring-folder rules, operational records, private templates, saved questions, note questions, or answers to a lilKiTTY server; does not use network speech recognition, network title refinement, or network note answers; and does not transfer Watch recordings or note summaries to the companion app. Reviewed text leaves only when you choose a destination in the system share sheet or use another operating-system feature. Apple backup or device-sync settings may also copy app data.
Google Keep drafts
lilKiTTY can prepare Google Keep list-item and note draft text locally from phrases such as adding groceries or saving a quick note. The current app uses the Apple system share sheet, so nothing is sent to Google Keep unless you choose Google Keep or another destination yourself.
Calendar, Reminders, and communication drafts
lilKiTTY can separate reviewed tasks, reminders, dated events, list additions, email drafts, and message drafts. Confirmed event creation uses write-only Calendar access. Coming Up requests full Calendar access only when enabled on iPhone, iPad, or Mac, then keeps a bounded upcoming title/time list in memory on that device. When enough related local history exists, a preparation icon can match bounded event-title words against existing notes and reveal two or three source-linked questions, decisions, or follow-ups. If you manually file an identified recurring meeting, lilKiTTY may separately ask whether future matching instances should use that folder. Nothing is enabled until you accept; matching remains local, and Undo or removing the membership removes the rule. Event and brief data is not saved into notes or logs, sent to a model, added to product counters, or sent to developer systems. Calendar descriptions, URLs, locations, attendees, email addresses, and organizer details do not enter that boundary. iPhone/iPad meeting reminders are an independent notification opt-in that schedules generic local prompts from event times. Apple provides no write-only Reminders tier. Items may sync through your configured system account, but lilKiTTY and its developer do not receive them. Email and message text remains unsent until you choose to copy or use a system surface and press Send.
Local playback
When you choose to play a saved recording, lilKiTTY validates and decrypts it into a protected temporary audio file on the recording device. The app removes that temporary copy when playback ends or stops and cleans abandoned temporary audio on a later launch. Playback does not transfer Watch audio to the iPhone companion.
Website data
lilkitty.app is a static public website served through Cloudflare. Cloudflare may process standard request data such as IP address, user agent, request URL, timestamps, and security events to deliver and protect the site. lilKiTTY does not use cookies, advertising, cross-site tracking, or third-party analytics on this site and does not use the website to store recordings or transcripts.
Controller and contact
For developer-held website and support information, the data controller is the Australian lilKiTTY developer identified as the seller on the App Store product page. Contact shoutout@lil.business with “lilKiTTY privacy” in the subject. The developer cannot retrieve app recordings, transcripts, or local note data from your device.
Purposes and lawful bases
Device-local processing is initiated by you to provide the recording, transcription, review, playback, sharing, and deletion features you request. Website request data is processed as necessary for the legitimate interests of securely delivering and defending the site. Messages you send are processed to answer your request, take requested pre-contract steps, provide support, and meet legal obligations. Microphone and speech permissions control device access; they are not consent to advertising, tracking, or unrelated data use.
Recipients and international processing
The developer does not receive app content unless you deliberately include it in a message or share it to a destination you choose. Cloudflare processes website request data on its global network as a hosting and security provider. Apple and any destination chosen in the system share sheet handle information under their own terms. Do not send recordings, transcripts, encryption keys, passwords, or sensitive note content to support.
Retention and deletion
On iPhone, iPad, and Mac, moving a note to Trash keeps it recoverable for 30 days. Permanent deletion removes its local metadata and encrypted source files. Recording-and-transcript retention is off by default. A selected retention age waits seven days before taking effect, then removes both the encrypted recording and transcript when they reach that age while keeping the title, your written notes, and reviewed drafts. Turning it off during the grace period cancels automatic deletion. Watch keeps its confirmed permanent local-deletion flow and does not expose Trash or retention controls. Removing the app removes its local container, subject to Apple backup and device-management behavior. Support and privacy correspondence is kept only while needed to resolve the request, maintain a necessary security or legal record, and meet applicable limitation periods, then deleted or de-identified. Hosting security data is retained according to Cloudflare's documented security and operational retention criteria. Exports, shares, and backups outside lilKiTTY must be managed with the destination provider.
Your privacy rights
Depending on your location, you may request access, correction, deletion, restriction, objection, or portability for personal information the developer holds, and may withdraw consent where consent is the basis used. Email shoutout@lil.business with “lilKiTTY privacy request” and your request. We may need proportionate information to verify the requester and will respond within the period required by applicable law. For device-local app content, use the in-app deletion controls because the developer cannot access or export it for you.
Complaints
Please contact us first so we can investigate. You may also complain to the privacy regulator where you live or work. In Australia this is the Office of the Australian Information Commissioner (oaic.gov.au); in the UK, the Information Commissioner's Office (ico.org.uk); and in the EEA, your national data protection authority. These rights are not limited by contacting us first.
Generated outputs
lilKiTTY may generate transcripts, summaries, person references, tasks, reminders, dates, and documentation candidates. These outputs can be incomplete or wrong. They are not legal, medical, financial, employment, or security advice. lilKiTTY cannot determine whether a recording or proposed action is lawful, authorised, complete, or suitable for your circumstances.
Children and sensitive use
lilKiTTY is a general-audience productivity tool and is not directed to children under 13. The developer does not knowingly collect children's app content. A parent or guardian who believes a child sent personal information to support should contact us for deletion. Do not record anyone without the notice or permission required where you are, and do not store highly sensitive information unless you understand your device, backup, export, and sharing settings.
Automated decisions, sale, and advertising
lilKiTTY does not make solely automated decisions that produce legal or similarly significant effects. The developer does not sell personal information, share it for cross-context behavioral advertising, or use app content for advertising or model training. Local transcripts and draft actions can be wrong and require your review.
Contact and updates
Privacy questions for lilKiTTY can be sent to shoutout@lil.business with lilKiTTY in the subject. This policy may change as the app adds account, sync, or provider features; the effective version is the version published on lilkitty.app.