Privacy

The short version: your data is yours. We don’t sell personal information for money, we keep sensitive journal content out of advertising and product analytics, and you can export or delete your Kinra account from inside the app.

What this covers

This policy covers both the Kinra app for iOS and our marketing site at getkinra.app. Where a practice applies to only one of them, we say so.

Your account

Kinra does not require an email or sign-in to get started. Onboarding asks for an optional first name for greetings. When you first open the app, we generate a random device identifier and store it in your device’s Keychain. That identifier is what links you to your journal.

After you subscribe, you can use Sign in with Apple so you can recover your account and subscription on a new device. When you do, Apple shares your first name and email with Kinra and we store them: your first name so the assistant can greet you, and your email so we can reach you about your account. Apple may give you a private relay address instead of your real email, and either one works. We also store the stable Apple user identifier that ties the account to you. Signing in is optional, and you can still use Kinra without it.

Kinra stores the Apple authorization credential needed to keep account recovery working. If you delete your Kinra account, we ask Apple to revoke that credential before removing the account link.

What the app stores

Your journal lives on Kinra’s backend, hosted in the United States. It includes:

• Food and drink entries, with the nutrition estimates for each.
• Meal photos you choose to send.
• Weight logs, including any Apple Health data you authorize us to import.
• Your chat messages with the assistant.
• Assistant memories: the corrections and preferences Kinra saves so you don’t repeat yourself.
• Your plan and goal settings.
• Reminder preferences, time zone, and an APNs device token when push notifications are enabled.

How AI processing works

To power the assistant, food recognition, and meal illustrations, we send the information needed for the request through OpenRouter, which routes the request to the model provider selected for Kinra. That can include your message or meal photo, recent journal context, profile and goals, plan, weight trend, and saved preferences or corrections. We use that context to answer, estimate a meal, or make a meal illustration; we do not send it for advertising. We require these third-party providers to protect personal information to the same or an equivalent standard as this policy.

For nutrition lookups, we query providers such as USDA FoodData Central, Open Food Facts, and, when configured, FatSecret using food, product, or barcode information rather than your account profile.

Voice logging

Voice logging starts only when you tap the microphone. Kinra asks iOS for microphone and speech-recognition permission and requires on-device recognition. Raw microphone audio is not uploaded to Kinra or stored by Kinra. The resulting text remains editable and is sent to the Kinra service only if you choose to submit it.

Apple Health

Kinra reads from and writes to Apple Health only with your explicit permission. It can read body weight, water, steps, and active energy. It can write calories, protein, carbohydrates, fat, water, and caffeine. Health data is used for your journal, habits, and adaptive plan; it is not used for advertising. You can change access at any time in the Health app.

Subscriptions

Subscriptions are processed by Apple. We use RevenueCat to present subscription offers and keep track of whether your subscription is active. RevenueCat receives a pseudonymous app identifier and purchase information. When available, your account name and email help us find your subscription for support. We do not send your journal, meal photos, chats, or raw body measurements as subscription analytics or targeting attributes.

Kinra personalizes the subscription screen with the name you provided and a formatted summary of your plan or selected goal. An estimated arrival is approximate. These display values are supplied to RevenueCat’s paywall view separately from analytics and targeting attributes. Coarse preferences, such as your onboarding version, may be used to choose an offer.

Analytics

We use PostHog for product analytics, so we can see which features help and where people get stuck. We deliberately keep sensitive content out of analytics: no food text, no photos, no chat prompts or responses, or exact body measurements. If you use Sign in with Apple, we may add the name and email Apple provides as profile properties in PostHog so support can match your Kinra account. The app's PostHog event identifier remains a pseudonymous Kinra user identifier.

When configured for a release build, Firebase Crashlytics receives crash and reliability diagnostics, such as device and app-version information, stack traces, and a pseudonymous Kinra identifier. We do not intentionally attach journal text, photos, chats, email, or exact health measurements to crash reports.

This marketing site also uses PostHog product analytics. That covers pageviews and interaction events like tapping the App Store button, plus the coarse context PostHog derives from a request (rough location, device type). The site has no sign-up, no accounts, no email capture, and no ads.

Advertising measurement

If you allow tracking in Apple’s permission prompt, Kinra uses Meta and Tenjin measurement tools to understand whether an ad led to an install or subscription. We may share an advertising or device identifier, a pseudonymous app identifier, and campaign or click information. Meta receives app-activation events and one event when you save your first food entry, and may receive eligible subscription-attribution events through our RevenueCat integration. Tenjin receives install and session attribution plus limited events for onboarding completion, the first food entry, and trial start.

We do not send advertisers your name, email, journal, food entries, photos, chats, weight, health data, goals, or nutrition plan. If you decline Apple’s tracking permission, Kinra does not connect its Meta or Tenjin individual-level measurement paths or send individual-level advertising events. Apple may still send privacy-preserving aggregate attribution reports to measurement partners.

What we don’t do

• We don’t sell your personal information for money.
• We don’t show ads inside Kinra.
• We don’t use your journal, photos, or chats to train our own models.

Your choices

You can change access to Apple Health, notifications, microphone, speech recognition, photos, camera, and tracking in iOS Settings. Turning a permission off stops future access through that permission but does not remove information you already chose to submit. You can remove submitted Kinra account data with the in-app deletion control.

Deleting and exporting your data

In the app, “Delete account & data” permanently removes the account-linked journal, profile, plan, chat history, memories, Health imports, reminders, device tokens, and account-linked stored media from our backend. If you contributed a nutrition-label scan, the product facts and label image may remain in the shared product catalog as deidentified evidence; Kinra removes the contributor link. Shared food and render catalogs otherwise are not account records. Limited subscription and attribution ledger entries may be retained for financial reconciliation, fraud prevention, and webhook deduplication without your journal content. You can export a JSON copy of your core account, profile, plan, food journal, summaries, weights, memories, and conversation messages from inside the app first.

Deleting Kinra data does not cancel an Apple subscription. Manage or cancel the subscription separately in Apple’s subscription settings. If a Kinra subscription is active, Apple may continue billing until it is cancelled there.

Retention and security

We keep account data while your account is active and until it is deleted or no longer needed to provide Kinra. Financial and operational records are retained only as needed for legitimate accounting, security, fraud-prevention, and legal obligations. We use access controls and encryption in transit, but no online service can promise absolute security.

Age and location

Kinra is intended for people age 16 and older. It is not directed to children under 16. Kinra’s backend is hosted in the United States, so information may be processed in the United States and in the locations where the service providers described above operate.

Contact

Questions about your privacy? Email hello@getkinra.app. We’ll keep this page updated as Kinra grows.