Last updated:
This policy explains how Uni.Kitchen uses information, what remains private, and how you can manage or delete it. The service is operated by Miri Cohen.
To authenticate accounts, save and restore content, extract and edit recipes, publish when you choose, support community interactions, review professional verification, handle requests and reports, and prevent abuse. Private cloud saving involves transmission to our service; it does not make content public.
Drafts and extraction sources are not shown publicly. Publishing is a separate action: your approved version, media and public kitchen details can appear in the community, on the website and in shared links. Comments and mentions on public posts are also visible to others. Liking a public post is a public action: the public kitchen name, username and avatar you selected may appear beside that post. Saving a post remains private to your account.
Source materials, chef verification documents and unpublished private edits are not part of the public version. Other people may copy or share content that you publish; withdrawing it cannot remove copies made by others.
For support after a request, troubleshooting or a safety review, the platform owner may open content from one account at a time in a read-only view after selecting a reason. The index shows titles; recipe contents open only after an explicit selection. Each list request and recipe opening is recorded in an access audit log scheduled for cleanup after 90 days; cleanup failures or retries can delay completion. Private content is not used for publication, campaigns or marketing targeting.
Camera, photo library and microphone access is used when you choose to capture, attach or record media. Manage permissions in your device settings. Selecting a file or recording is not permission to publish it. Sign-in information and working copies are also stored on your device. The website may store technical information needed for functionality and security.
Saved account content and attached sources remain available until you delete them or the account. For troubleshooting and improving extraction, a failed extraction source is retained privately for up to seven days from the request, with its error code and processing stage and, for a page-recognition failure, a bounded sample of the page response. Only the platform owner can inspect it with a recorded reason and an audit entry. It is not automatically sent for model training, is not public, and is also erased with account deletion. Audio and video references remain subject to deletion of the original file. Temporary extraction results expire after 24 hours; a structured recipe that consumed a credit is retained separately and privately in the account until removed or the account is deleted. Deleting a draft or post does not automatically remove this extraction copy; temporary job records remain for up to 30 days. Separate, limited operation and cost records, including technical identifiers and hashes, remain afterward to prevent duplicate charges and reconcile usage with an unknown outcome. These records currently have no automatic deletion date and do not include recipe content, source files or email addresses. Abandoned sources not attached to saved content become eligible for cleanup after 48 hours.
The activity history shown to the platform owner records server-confirmed actions, timestamps, content type and extraction or publication metadata; it does not include recipe text, source files or email addresses. It is retained while the account exists and deleted as part of account deletion. Collection starts when event tracking is enabled; historical events already expired or deleted will not be restored. Administrative content-access audit records are scheduled for cleanup after 90 days; failures or retries can delay completion.
Professional verification documents attached to an application are retained while it is reviewed. After a final approval, rejection or revocation decision, they are scheduled for cleanup after 90 days, or earlier following deletion. These are cleanup eligibility times; failures and provider retries can delay completion.
A completed-account-deletion record is retained for 30 days for recovery. Limited security, administrative decision and revoked professional invitation records can remain to prevent reusing permissions or address abuse. Service deletion does not erase exports, offline device copies or separate copies retained by providers under their policies. Contact us about remaining information.
You can edit your profile and content, withdraw publication, export cloud content and delete your account in the app. Contact hello@unimi.io to request access, correction or deletion, or ask a privacy question. We require appropriate ownership verification before releasing or deleting data. Do not send passwords or sign-in codes. Additional rights and options depend on applicable law.
The update date appears above. Material changes will be communicated through the service as appropriate for the change and applicable requirements. Contact us for an explanation of this policy or our use of information.
We use Vercel Web Analytics and PostHog to understand website and app usage. Events include page and action categories, platform and distribution cohort (public website, iOS beta or Android beta), and limited values such as extraction method, editing action and save outcome. When recognized, campaign source is reduced to Meta, YouTube, Google or other. Before sign-in, activity is grouped by a random browser-session or app-installation ID. After sign-in, a stable account ID and public username link activity to a PostHog account profile so we can understand user journeys and conversion across devices. The app also sends a first-open-per-install event; a first open is not a download count.
We do not send email addresses, sign-in tokens, kitchen names, recipe or media content, search text, full page URLs, raw UTM parameters or advertising click IDs to PostHog. The username is sent as a profile property; campaign source stays a broad category and is not sent to Meta or Google through conversion APIs. The owner activity report is read separately from Clerk and server-confirmed actions and is used to verify completed operations.
Browser signup replay is optional and only starts when a person separately checks its consent box on the signup screen in the web/PWA workspace. It stops when signup completes or the person leaves the flow, and is used to improve signup. All text and input values are masked before transmission; URL query parameters are removed, the CAPTCHA area is blocked, and network request headers and bodies are not recorded. No replay runs in the iOS/Android apps, on public marketing pages, or on signed-in content screens. PostHog processes and retains recordings according to the retention settings configured for the project there.
Events are sent directly to PostHog, and the browser keeps a temporary delivery queue to retry after network interruptions. Website measurement runs only on the authorized Production domain; app measurement runs in the public app and TestFlight builds marked Production.
When website checkout is available, Cardcom processes payment and YeshInvoice issues the payment document and emails it. This uses your full name, verified email, mobile number and order details. We also retain subscription consent, the terms version, price, billing and cancellation dates, and payment status.
Card details are entered on the secure Cardcom page. Uni.Kitchen does not store a full card number or CVV. A Cardcom token for renewal is encrypted on the server and is not sent to the app or browser. Limited transaction records and references support reconciliation, documents and duplicate-charge prevention. Provider documents remain subject to its policy and applicable requirements.
Account deletion cancels renewals and removes contact details and payment links from our order records. Limited financial grant, consumption, charge and refund records may remain for recovery and duplicate prevention; these currently have no automatic deletion date and contain no recipe content. Contact us about a specific record.
With separate, updated browser permission, Meta Pixel measures creator-page visits and trial clicks. Our server may also report a verified, completed new signup following a campaign visit. A click, submitted form or existing-account sign-in is not a completed new signup.
Meta receives the approved public creator landing URL, bounded campaign parameters such as UTM values and fbclid, advertising-cookie identifiers and technical browser information. Registration reports contain no name, email (including hashed email), account identifier or recipe content. Meta code never loads in account or sign-in screens; registration measurement is sent by our server without the private screen URL. An opaque measurement token in this browser is valid for up to 24 hours to complete reporting and prevent duplicates.
Advertising measurement remains off until you accept. An older grant for visits and clicks does not automatically permit signup measurement. You can decline and keep using the website, and change your preference here. Your choice stays in this browser for up to 180 days. Withdrawal stops future measurement and asks our server to cancel reports not yet sent; a failed cancellation is retried later. Withdrawal does not erase information already delivered to Meta. This choice is separate from anonymous product-usage measurement.
Advertising measurement is off in this browser.