At a glance
The Kuluka iPhone app works without an account. MN Booth LLC does not receive your daily prompts, relationship preferences, people and their details, optional contact links, message drafts, selected reviewed wording, feedback, saved prompts, completion history, or private notes. Optional Apple Intelligence selection runs on the iPhone and makes no request to a Kuluka server. The Kuluka website is a static information site and does not use analytics, advertising trackers, cookies, or contact forms. This website publishes support@kuluka.app for voluntary support messages. Email routing forwards those messages to MN Booth LLC's verified support mailbox. Replies currently come from Phia N Vang at pnvang@gmail.com, rather than from support@kuluka.app.
Information stored by the app
The app stores the following information locally on your device:
- Relationship preferences used to select appropriate prompts
- Your reminder choice and preferred reminder time
- Daily prompt selections and prompts already tried, used to keep the current choice steady and reduce repetition
- Saved prompts and prompt completion history
- Optional private notes and optional locally entered names or nicknames
- People you add for personalization, including names, relationships, pronouns, and the details you choose to write
- An optional, narrow link from one Kuluka person to one phone contact you explicitly select
- Your personalization choice, selected person, and tone
- A terminal personalization attempt with the exact attempted setup and local failure category, so Kuluka does not silently retry it
- Selected reviewed wording and current thumbs-down exclusions; legacy archive files can contain older feedback
- Appearance, haptic, onboarding, and other app preferences
- Minimal widget presentation state for a neutral prompt-free pending state or the current prompt, plus completion state
This information supports app features on your device. It is not sent to MN Booth LLC and is not used for advertising or profiling.
Optional contact linking
Kuluka can ask Apple’s system Contacts interface to let you link one Kuluka person to one phone contact you choose. This is optional. Kuluka does not scan, bulk-import, or build a copy of your address book. Apple’s one-time picker returns the contact property you select. Kuluka checks that it is a phone entry, reads only its phone-number value, and does not use or persist the associated contact, identifier, or label. The picker gives Kuluka no ongoing access to the contact store. Kuluka stores only the selected phone-number snapshot, selection time, and picker source in its private archive so it can prefill the recipient when you ask to review a message. You can choose a different contact or unlink the person without disabling daily prompts or personalization.
A link is a saved snapshot, not a synchronized contact. Kuluka cannot observe a later edit or deletion in Contacts because it does not retain contact-store access. The draft screen masks the saved number and tells you to cancel and relink if it changed; Apple’s composer also lets you remove or replace the recipient before sending. The selected phone-number snapshot and all other Contacts fields are never included in either Apple Intelligence model request.
Apple Intelligence personalization
On iOS 26 devices where Apple Intelligence is available or may become available after a settings, readiness, or language change, personalization is introduced during onboarding but remains optional and skippable. Earlier iOS versions and ineligible hardware skip that setup page. On an eligible Apple Intelligence-capable iPhone running iOS 26 or later, Kuluka can use Apple’s Foundation Models framework and the system language model to choose a daily prompt for one person from a bounded set of human-reviewed ideas. The model runs on the iPhone. Kuluka does not use Private Cloud Compute, a server-hosted model, or an app-owned network request for personalization.
For one selection, Kuluka can provide the on-device model with filtered notes about the selected person, their relationship, your chosen tone, and the reviewed text for a bounded list of choices. Kuluka does not serialize the person’s separately stored name or pronoun fields, completion notes, separately stored details for another person, support messages, or linked Contacts fields. It removes stored-name tokens from notes and excludes a whole note when it looks like an email address, web link, or phone-like number. Free-form notes may still contain pronoun words, postal addresses, location text, references to other people, or other personal details. Sensitivity and relationship compatibility are checked locally before any model call. A current thumbs-down excludes that reviewed idea from later choices for the same person. A legacy archive or export can contain thumbs-up feedback for compatibility, but thumbs-up data is not sent to the model and does not influence selection. Upgrading or importing an archive from the former free-form personalization format clears its active and retired generated wording, failed-attempt state, and legacy prompt feedback. Kuluka restores each completion to the current reviewed base prompt, or to This prompt is no longer available. if that prompt retired, while preserving the completion identity, date, private note, relationship, and nickname. Feedback is not model training, analytics, or a relationship score.
Apple Intelligence returns only an opaque token that exists for that request. Kuluka resolves the token to human-reviewed wording, then applies the selected person’s name or pronouns deterministically on the iPhone only when the sentence supports naming and the value is one letter-based name component with optional internal apostrophes or hyphens. Otherwise Kuluka keeps the exact unnamed reviewed wording. The model never authors the daily prompt shown on screen, and there is no generated-wording critic or safety-rejection loop. Each selection uses a fresh model session so one person’s details are not carried into another request. If Apple Intelligence is unavailable and no compatible selection is already stored, Kuluka keeps the exact original reviewed prompt and starts no new model work. A compatible reviewed selection already stored for the day remains visible if availability later changes. If an available model times out, declines a request, or returns no valid choice, Kuluka can keep deterministic reviewed fallback wording available. Selected wording is stored in the local archive for the day and may appear in completion history, sharing, the Home Screen widget, exports, recovery copies, and iOS backups according to the choices and system features described in this policy.
User-reviewed message drafts
Message drafting is separate from daily-prompt selection and uses its own constrained request and safeguards. Message model work starts only while Personalize prompts is enabled, the current prompt is not consent-sensitive, Apple Intelligence is available, and a nonempty render-safe recipient is available. On a supported iPhone, Kuluka provides only the underlying reviewed prompt text, before Kuluka applies a name locally, when the on-device model selects an action-matched human-reviewed variant. The app renders the selected wording deterministically. A separate on-device review receives that underlying reviewed prompt and the proposed starter, which begins with a locally entered Kuluka name. When no person is saved, that name can be the default nickname. Kuluka accepts only one letter-based name component with optional internal apostrophes or hyphens; an unsafe or empty value uses unnamed reviewed wording and starts no message model work. Neither request receives the selected relationship, tone, pronouns, free-form person details, completion notes, feedback, prior wording, phone numbers, contact identifiers, or other Contacts fields. When the model cannot help, or any model trigger is absent, Kuluka provides the deterministic default reviewed starter instead without starting model work.
Kuluka shows the result in an editable review step. You decide what it says, choose or confirm the recipient, and decide whether to open Apple’s message composer. The composer remains editable and sends only if you tap Send. You may cancel instead. Kuluka never sends a message automatically or in the background, and a composer result does not guarantee delivery. After you hand content to Messages or another destination, that provider’s privacy practices apply.
Notifications
Daily reminders are optional local notifications scheduled by your iPhone. Kuluka asks for notification permission only after you choose to enable reminders. You can change or revoke permission in iOS Settings at any time. Notification text is written to avoid exposing private relationship details on your Lock Screen.
Exports and sharing
If you export your Kuluka data, the app creates readable JSON on your device and presents Apple’s system file exporter. If you share a prompt, the app presents Apple’s share sheet with either the prompt text or a branded image card. If you approve a message draft, Apple’s message composer receives the editable body and the recipient you chose. You choose each destination. The privacy practices of that destination are governed by its provider, not by Kuluka.
Website information
This website does not run analytics, set cookies, use advertising pixels, or collect data through forms. As with any website, Cloudflare and your network provider may process limited technical information, such as an IP address and security request data, to deliver and protect the site. MN Booth LLC does not use that information to build personal profiles.
Support communications
You can email support@kuluka.app for support. MN Booth LLC and the email routing and mailbox providers used to deliver the message may receive your email address, message, email headers, and anything you choose to attach or describe. This may include your iPhone model, iOS version, and Kuluka version when you provide them for troubleshooting. Please do not send private notes or other information you do not want us to receive.
Replies currently come from Phia N Vang at pnvang@gmail.com, rather than from support@kuluka.app. Keep the original conversation so you can verify the reply context.
We will use support messages to answer you, troubleshoot the issue you reported, protect the service from abuse, and meet legal obligations. We keep them only as long as reasonably needed for those purposes, then delete them under our support-mailbox practices. You may ask us to delete a support conversation, subject to security, legal, and recordkeeping needs.
Data deletion and retention
You can edit or clear the default nickname, delete individual history items, or choose Delete all local data under Your data in Kuluka Settings. Removing a person from the active archive also removes their optional contact link, selected and retired wording, and feedback attributed to them, and restores an attributed completion snapshot to its curated wording. It also removes terminal personalization attempts for that person. Before a valid import replaces your current archive, Kuluka keeps one local pre-import recovery copy. That copy can include earlier people, personalization details, feedback, selected wording, nicknames, notes, and history even after you change the current archive. Choose Delete pre-import recovery copy to remove it without changing current data. A later valid import replaces it. Delete all local data removes both personal information from the active archive and the pre-import recovery copy, clears pending reminder state, and leaves non-personal archive and widget defaults so Kuluka can open normally. Use these in-app controls before uninstalling when you need certainty. Kuluka is designed to keep its data only in local app and App Group storage, but iOS manages extension container cleanup and device backups. Because MN Booth LLC does not receive your local app data, we cannot view, retrieve, or delete it for you.
If completed history refers to a prompt that the current Kuluka catalog no longer includes, Kuluka keeps the completion identity, date, private note, relationship, and nickname. It replaces the unverifiable prompt wording with This prompt is no longer available. and clears personalization provenance. The history moment itself is not silently deleted.
Children’s privacy
Kuluka does not knowingly collect personal information from children. The app does not require an account, contact linking, or personal profile. The one-time contact picker is presented only when someone explicitly chooses to link a Kuluka person and grants no ongoing Contacts access.
Changes to this policy
We may update this policy if Kuluka’s features or legal obligations change. The effective date at the top of this page will identify the current version. We will describe material privacy changes in the app or on this website when appropriate.
Contact
Email support@kuluka.app for privacy questions. Replies currently come from Phia N Vang at pnvang@gmail.com, rather than from support@kuluka.app.
MN Booth LLC
Minnesota, United States