Privacy Policy

KitchenLog (the "System" or "Service") is a digital platform for managing, documenting, and tracking the operations of professional kitchens, catering businesses, and food-service institutions. The System assists with documentation, monitoring, and process management for operational and regulatory purposes, including temperature logging, barcode scanning, recurring checklists, pest control records, supplier and customer management, and report generation.

Website: kitchenlog.app
Email: info@kitchenlog.app

We collect and process the following categories of information to operate the System:

2.1 Account and Identification Data:

• Full name and email address of users (owners, managers, employees).
• Role within the account (owner / manager / employee) and associated branches.
• A notification email address configured per branch (editable by the account owner).

2.2 Kitchen Operations Data:

• Barcode scans of products, including scan count, scan timestamps, and measured temperatures.
• Temperature records for various states: prepared, leaving warmer, delivered, defrosted.
• Temperature records per refrigerator and warming unit.
• Dish status (planned, prepared, leaving warmer, delivered, defrosted).
• Checklists and recurring tasks (daily, weekly, monthly, yearly), including completion status, who completed them, and when.
• Chlorine concentration readings in water (PPM).
• Pest control records (including uploaded images).
• Critical point logs — temperature deviation documentation and actions taken (destruction, alternative use, etc.).
• Audit records (self-audits or health ministry audits).

2.3 Management Data:

• Branch details: name, address, phone, active status, subscription plan (Basic / Pro / Premium).
• Customer details: name, contact person, phone, email, address.
• Supplier details: name, phone numbers, email, address, license image, notes.
• Products, refrigerators, warming units, defrost products.
• Allowed temperature ranges per status (min/max) per branch.
• Print jobs (barcode labels) per branch, including printer identifier.

2.4 Images:

• Images uploaded to the System by users (e.g., pest control documentation, supplier licenses).

2.5 Google Account Data:

• When signing in with Google: the email address associated with your Google account, as well as basic profile information from your Google account, such as your name, as provided by Google.

2.6 Google Sheets Export Data:

• When exporting reports to Google Sheets, the System creates a dedicated spreadsheet in the user's Google Drive account and writes report data to it (see Section 4 for details).

The System allows users to sign in using their Google account. When you sign in:

• The System receives the email address associated with your Google account, as well as basic profile information such as your name, as provided by Google. The OAuth scopes requested are openid, https://www.googleapis.com/auth/userinfo.email, and https://www.googleapis.com/auth/userinfo.profile.
• This information is used solely for identification, registration, and authentication within the System.
• The System does not access your Gmail inbox contents, Google Contacts, Google Calendar, or any other data in your Google account beyond the email address and basic profile information described above.
• Google Sign-In is implemented through a Custom OAuth integration registered by KitchenLog, and is used exclusively for user authentication — it is separate from the Google Sheets integration described in Section 4.

The System allows each user to connect their own Google Sheets account to export operational reports and audit reports to a personal spreadsheet. The connection is made with the user's consent via OAuth, and the user can disconnect it at any time.

The Google Sheets connection is established through a dedicated OAuth connector provided by the Base44 platform (the hosting platform of the System). This connector is separate from the Custom OAuth integration that KitchenLog uses for Google Sign-In, which is used exclusively for authentication and does not grant access to Google Sheets.

4.1 Google Permissions (Scopes):

• The Google Sheets connection is established through a dedicated OAuth connector provided by the Base44 platform.
• The permissions requested are for reading and writing Google Sheets spreadsheets (Google Sheets API).

4.2 What the System Does with Google Sheets:

• Creates a new spreadsheet — if no existing spreadsheet is found, the System creates a new spreadsheet named "KitchenLog - Reports - [User Name]" in the user's Google Drive account.
• Creates tabs — a dedicated tab is created for each report type within the spreadsheet (e.g., scans, temperatures, checklists, audits, etc.).
• Writes data — the System writes report data (column headers and data rows) to the appropriate tab. New rows are appended below existing data.
• Updates formatting — the System sets the tab to RTL (right-to-left) format and configures cell text to clip within cell boundaries.
• Prevents duplicates — the System tracks which records have already been exported and skips them on subsequent exports to avoid writing duplicate rows.

4.3 What the System Does Not Do:

• It does not read or access other spreadsheets in your Google Sheets account beyond the one created by the System.
• It does not delete or modify other spreadsheets.
• It does not share the contents of your spreadsheets with third parties.
• It does not use Google Sheets access for advertising or marketing purposes.

The use of data received from Google is limited solely to providing the functionality the user requested:

• Google Sign-In: identification, registration, and authentication within the System.
• Google Sheets: creating a personal reports spreadsheet and writing report data to it.

We do not use this data for marketing, advertising, monetization, or developing advertising profiles. We do not transfer this data to third parties for these purposes.

Limited Use Statement: In accordance with the Google API Services User Data Policy, the use of data obtained from Google is limited to the purposes described above. We do not transfer this data to any party for advertising, sale, or rental purposes. We do not use it to develop advertising profiles or for competing services. Our use complies with the Limited Use requirements of Google.

The information we collect is used solely for:

• Providing the System's documentation and operational tracking capabilities (scans, temperatures, dish status).
• Managing checklists and recurring tasks, including recording completion status and scheduling the next recurring task.
• Sending automated email alerts for temperature deviations and critical events (to the email address configured for the branch).
• Generating operational reports and audit reports for regulatory and inspection purposes.
• Exporting reports to the user's personal Google Sheets, upon request.
• Managing users, branches, permissions, and subscriptions within the account.
• Maintaining, improving, and troubleshooting the System.

KitchenLog does not sell, rent, or trade users' personal information — including data received from Google. The information is used solely to provide the Service as described in this policy.

Information is accessible to users within the same account (owners, managers, and employees) according to their configured permissions. We do not share information with third parties except in the following cases:

• Data export by the user: When exporting to Google Sheets, data is transferred via the authorized integration to the user's Google account.
• Legal obligations: Where required by law or pursuant to a court order.
• Service providers: External service providers that assist in operating the System (such as the Base44 hosting platform, email delivery services, and the PrintNode label printing service) — but only to the extent necessary to provide the Service, and subject to confidentiality agreements and the privacy policies of those providers.

Information is stored in the database of the Base44 platform, which hosts the System. The retention period depends on the type of data and applicable requirements:

• Operational data (scans, temperatures, checklists, audits) is retained for as long as the account is active, in accordance with documentation requirements applicable to food-service institutions.
• Google sign-in data (email address) is retained for as long as the account is active.
• The original operational data remains stored in KitchenLog in accordance with this policy. However, KitchenLog does not store a separate copy of the Google Spreadsheet file itself — only the spreadsheet identifier (spreadsheet ID) and a record of which records have been exported, to prevent duplicates.
• Backup copies of the database may be retained by the hosting platform for a period of time in accordance with the platform's backup policies.

We do not retain your data longer than is necessary for the purposes described in this policy, except where retention is required by applicable law.

We take reasonable measures to protect the information stored in the System:

• Encryption in transit: All communication with the System is encrypted using TLS.
• Role-based access control (RBAC): Read, write, and delete permissions are defined for each data type and are limited to relevant users and branches only. An employee sees only the data of their branch; a manager sees all branches assigned to them; an owner sees all branches in the account.
• User authentication: All access to account data and KitchenLog operational data requires authenticated sign-in. Public information pages, such as the home page, privacy policy, and terms of service, are available without sign-in.

However, no security system is perfect, and we cannot guarantee absolute protection against unauthorized access.

• A user may request deletion of active information stored about them in the System.
• Deletion of operational data (scans, temperatures, checklists, audits) may be subject to legal documentation requirements applicable to food-service institutions — some data may need to be retained for an additional period as required by law.
• Upon account deletion, all data associated with the account, including branches, users, and operational data, will be deleted, subject to applicable legal retention requirements.
• Google Sheets: The personal spreadsheet in the user's Google Drive is not deleted by the System upon disconnecting — it remains in the user's ownership. To delete it, the user should remove it directly from Google Drive.
• Backup copies may be retained temporarily until the hosting platform's backup cycle completes.

• Google Sign-In: You can revoke Google sign-in authorization at any time through your account settings in the System or through Google Account Security → "Apps with access to your account".
• Google Sheets: You can disconnect the Google Sheets connection from the System at any time through the System's user interface. After disconnection, the System will no longer be able to read from or write to your spreadsheet. The spreadsheet itself remains in your Google account.
• You can also revoke all permissions granted to KitchenLog through Google Account Permissions.

Disconnecting the connection within KitchenLog causes KitchenLog to stop using the connection. To fully revoke Google's authorization, you can do so through Google Account Permissions.

At any time, you may request to:

• Receive a copy of the information stored about you in the System.
• Update incorrect or outdated information.
• Delete active information stored about you in the System (subject to Section 11).
• Disconnect the Google Sheets connection from the System at any time.
• Revoke Google sign-in authorization at any time.

To exercise these rights, contact us at info@kitchenlog.app.

We may update this policy from time to time. The updated version will be published on this page, and the last updated date will appear at the top of the page. We recommend reviewing this page periodically.

For any question or request regarding your privacy or your data, you can contact us:

• Email: info@kitchenlog.app