PANTRISORA

Privacy Policy

Updated 9 November 2026. This policy explains how PANTRISORA handles kitchen records, backups and page requests in the current application.

Kitchen records in your browser

The tools use an IndexedDB database named menuliva, version 2, within your browser profile and this website’s origin. Records include inventory batches and events, purchase and opening dates, meal plans and serving counts, shopping lists and entered prices, custom recipes, waste records and costs, saved preferences, recipe favourites and recent recommendations. The recommendation history keeps up to ten recipe identifiers; it is not a record of every page you visit. Recipe and ingredient catalogues and application metadata are also stored locally.

The current application code does not upload these kitchen records or provide account synchronisation. Local storage is not an application-level encrypted vault. Someone using your unlocked browser profile may be able to access it. Blocking IndexedDB prevents features that require saved records from working.

JSON backup and restore

The Grocery List Maker and Food Waste Tracker offer complete JSON kitchen backups. Downloads contain readable user records, including favourites, preferences and history. They do not contain a copy of every site asset. Keep the file private and share it only intentionally.

Restoring reads your selected file locally. After your replacement confirmation, the application validates the supported format and record references before replacing the saved user records in one database transaction. It does not merge two households’ records. A failed validation or transaction leaves existing data in place. The interface accepts nonempty backups up to 10 MB (10,000,000 UTF-8 bytes). Keep a current backup before restoring another one.

Cookies, other storage and third-party services

The current source does not set cookies or use localStorage or sessionStorage. It has no analytics, advertising scripts, AdSense, third-party embeds or remote font service. JavaScript requests the recipe and ingredient JSON files from this same site. The browser can cache normal page and asset responses according to its own behaviour and server headers; that cache is separate from your kitchen database.

Images and external links

Stylesheets, scripts, recipe photographs and original topic illustrations are served from this site. Displaying them does not require a request to the original photographer’s website. Source credits, licences and food-safety references are ordinary external links. Following one connects you to the destination under its own privacy practices; the browser may send referrer information according to its policy. These sites are not embedded tracking services in the current build.

Advertising and your choices

Google AdSense is not currently enabled on PANTRISORA. No Google ad request, advertising cookie or advertising web beacon is loaded by the current application. If advertising is introduced, Google and other participating vendors may use cookies, web beacons, IP addresses and advertising identifiers to deliver, personalize and measure ads. The policy and choices offered here will be updated to describe the services actually used before that processing starts.

Read Google’s guide to ad personalization and partner-site settings, or see YourAdChoices control options for participating vendors. These are external resources, not consent controls already operating on this site. Personalized Google ads for users in the EEA, the UK and Switzerland require an applicable Google-certified consent platform integrated with the IAB Transparency and Consent Framework. No claim is made that a consent platform is currently installed or that these links replace the choices required before advertising begins.

Page requests and hosting

A server receives network requests needed to serve pages and assets, including connection information such as an IP address and request metadata. The bundled preview server has no application request-log or kitchen-data collection handler and accepts only GET and HEAD requests. This does not establish the logging, retention or access practices of an operating system, network provider or future production host. Production hosting and any infrastructure logging remain unconfirmed.

Manage and delete your data

  1. Use the relevant tool to edit individual records. Archiving an empty batch or correcting an entry does not erase all related history.
  2. Download a backup first if you want to keep your records.
  3. Close other PANTRISORA tabs. In your browser’s site settings, find this exact website address and clear its stored site data. You can also remove the menuliva IndexedDB database through browser developer tools.
  4. Reloading a tool can create a fresh database. Delete downloaded JSON backups separately; clearing browser data does not remove files or copies you shared.

There is no fixed automatic retention period for kitchen records. They persist until changed or removed, but browser eviction, private browsing or clearing a profile can remove them sooner. A different device, profile, hostname, port or protocol has separate storage. The site cannot recover a lost local database without a usable backup.

Questions and future changes

No account or contact submission form is provided. For privacy questions, email nicemao29@gmail.com. Your email provider and the receiving email service process messages under their own practices. Include only the information needed for your enquiry; do not attach a complete kitchen backup unless necessary. See Contact Us for reporting guidance. If analytics, AdSense, another external service or production logging is introduced, this policy and any required choices must be updated to describe the actual configuration before that processing begins.