Skip to content

Privacy

Last updated October 28, 2026

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

What this covers

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

Your account

In the app, 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.

Your plan answers on the web

If you build a plan at getkinra.app/start, we ask for your first name, goal, an optional reason in your own words (up to 200 characters), how you have tracked food before, what support you want, how you handle off-plan days, tone, food style, allergies, date of birth, sex, height, weight, activity, goal weight, pace, an optional event date, a habit and your email. Some of this is health related. We use your answers to build and save your plan and to move it to the app. If you choose to log a first meal on the web, relevant profile answers are also used as described below. Your email and first name are also sent, hashed, for ad measurement (see Advertising measurement).

The plan builder is open only to visitors in the United States. By continuing past the first question you agree to our Terms and this policy, and we use these answers only for the purposes above. You can ask us to delete them at any time by emailing hello@getkinra.app. We use your email and billing details to perform our contract with you.

We do not store anything for people under 16. If you are 16 or 17, we do not collect weight, height or goal numbers on the web.

Until you save, your answers stay in your browser’s local storage. After you save, they are stored on Kinra’s backend (Convex, United States) with a random claim token. We delete an unclaimed web session 30 days after its last update, or sooner if you ask at hello@getkinra.app.

When you open the iPhone app and claim your session, the app imports your answers only after you confirm. Once claimed, they are app data under this policy, and “Delete account & data” removes them.

Your first meal on the web

Before paying, you can choose to log a first meal on the web. We store your meal text and corrections, the assistant’s replies, nutrition estimates and any generated illustration in a temporary journal linked to your saved web session.

When you send a meal, its text and relevant profile answers are sent for AI processing. The page says so before your first send; there is no separate permission step on the web. This uses the AI services described below to answer, estimate the meal and generate its illustration.

When you restore your web purchase in the app and our server verifies the purchase and its link to your saved session, Kinra transfers the original journal into your app account instead of creating another copy. If it is not transferred, it is scheduled for deletion when the web session expires, 30 days after its last update. Once transferred, the app’s account and data deletion controls apply to it.

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. Session recordings, described under Analytics, show the screen as it was drawn, so figures read from Apple Health can appear in them. You can change access at any time in the Health app.

Subscriptions

In the app, 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.

If you subscribe on getkinra.app (sold in the US for now), billing runs through RevenueCat Web Billing, and Stripe processes the payment. Stripe collects and handles your card or wallet details; Kinra never sees or stores them. RevenueCat receives an anonymous customer identifier, your email, the product you chose and purchase status. Stripe receives your email, payment details, billing country and the amount, and acts as an independent controller for fraud prevention and its legal duties. We do not send your plan answers to either. We keep purchase records as needed for accounting, tax, refunds and fraud prevention.

If you ask Apple for a refund of a Kinra subscription bought in the app, Apple may ask us about it. When it does, we, through our subscription provider RevenueCat, tell Apple whether the subscription was delivered and working, whether you could learn about or try Kinra before buying, and our refund preference. We don’t send your journal, meal photos, messages, health data, name or email. Apple uses this only to decide the refund request. By subscribing, you agree to this.

Analytics

We use PostHog for product analytics, so we can see which features help and where people get stuck. The events we send describe what happened in the app, such as a step completed or a meal saved. They do not carry food text, photos, chat prompts or responses, or exact body measurements.

Separately, the app records sessions of its own screens through PostHog, so we can see where people get stuck. A recording shows what was on the screen at the time. That can include your meals and meal photos, your messages and the coach’s replies, and body figures such as your weight. Recordings are kept for 30 days and are not used for advertising.

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. PostHog also receives the app’s crash reports (the error type, stack trace, app version and the same pseudonymous identifier), with numbers and email addresses removed from error messages, and errors and clicks that did nothing from this website’s pages.

This marketing site also uses PostHog product analytics for every visitor, without a consent banner. It sets a cookie and uses browser storage to recognise a returning visit. 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); your plan answers are never included. The plan builder at /start is described under Your plan answers on the web. The rest of the site has no accounts and shows no ads.

On the plan builder at /start we also keep an anonymous count of how far each visit gets: the steps reached (by name, never your answers), plan saved, the offer shown, checkout started, a checkout that ends without a purchase, purchase completed and opening the app, with the ad campaign’s name, the language, whether the device is an iPhone, the kind of browser (for example Instagram’s) and the country. Outside the EU, the EEA, the UK and Switzerland it also carries Meta’s click identifier from the ad link, so a step can be matched to an ad. It uses a random number that lasts only while the page is open, no cookies or browser storage, and no IP address or profile.

Advertising measurement

In the app, 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.

On getkinra.app/start, we use the Meta Pixel and Meta’s Conversions API to measure our ads, for visitors outside the EU, the EEA, the UK and Switzerland, without a consent step. They do not load for visitors there, or where we cannot tell the country. We send: page views, which steps of the plan builder you reach (by name, never your answers), plan saved, the offer you see, checkout started, trial started and subscribe (with the plan, price and currency), a random event identifier so nothing is counted twice, a hashed random identifier for this browser, and the usual browser data (IP address, browser, Meta’s click identifier). Once you have entered them, we also send your email and first name in hashed form to Meta to measure our ads and find people like our members. We never send your answers, weight, goal or health details. We do not send your email or name for visitors in Washington, Nevada or Connecticut, or where we cannot tell the state. Meta acts as a controller for its own use of this data under its terms.

In the iPhone app, 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. Session recordings are not removed by “Delete account & data”; they expire after 30 days. 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.

A plan saved on the web and never claimed in the app is deleted 30 days after its last update; email hello@getkinra.app to have it deleted sooner. Deleting Kinra data does not cancel a web subscription; cancel it from the link in your receipt email.

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. Unclaimed web plan sessions are deleted 30 days after their last update. 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, and the plan builder does not store answers from anyone 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.