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.
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. 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.
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 PostHog for limited, aggregate measurement of the public website. Each event contains only a random browser identifier, the measurement schema version, website surface and platform, a general page category, and predefined categorical values—for example whether a search returned results or the general placement of a sign-up link. We do not call identify or alias and do not link the random identifier to a Uni.Kitchen account.
Events exclude names, email addresses, usernames, account, kitchen, recipe and publication identifiers, search terms, page URLs and parameters, referrers, recipe content, comments, drafts, payment details and sign-in details. Automatic capture, screen recording, performance measurement and console error capture are disabled. As with any network request, the measurement provider receives connection information needed for delivery and security; location enrichment is disabled on the events we send.
You can turn measurement off or on for this browser using the control below. Turning it off stops future events and replaces the local identifier. Events already sent are anonymous and are not linked to an account, so they cannot be located by account for deletion.
The measurement preference is unavailable in this browser, so measurement is not sent.
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.