Owlet Recipe Saver Privacy Policy
    



    

OWLET RECIPE SAVER PRIVACY POLICY

Effective date: September 17, 2026

Owlet Recipe Saver (“Owlet”) is an independent browser extension that captures structured recipe information from a webpage the user chooses and allows the user to review, edit, print, and export it without connecting to an Owlet server. KitchenOwl is an optional server-storage destination selected by the user. Owlet is not affiliated with, endorsed by, or sponsored by KitchenOwl.

INFORMATION OWLET HANDLES

Owlet may handle:

  • The KitchenOwl username or email entered by the user
  • Authentication access and refresh tokens returned by the selected KitchenOwl server
  • Recipe title, ingredients, instructions, times, servings, user-entered tags, and source URL
  • Recipe images
  • The selected KitchenOwl household
  • Import/export files selected by the user
  • Minimal diagnostic information

Recipe information is read only when the user clicks “Read/Refresh Recipe” in Owlet’s side panel. Clicking the toolbar icon only opens or focuses that panel. Owlet does not monitor navigation or inspect pages automatically.

The current recipe remains visible until another read, a successful server save, or another explicit clearing action replaces it.

The source URL is retained as recipe metadata only when the user chooses to save or export the recipe. Before use, Owlet removes URL credentials, query strings, and fragments.

Recipe images may load during review and may be included in printouts. An image is downloaded and sent to the selected KitchenOwl server only when the user chooses Save for a recipe containing an image. Owlet does not persist image bytes.

Optional description/notes and nutrition information are local review, print, and export fields and are not sent to KitchenOwl.

HOW INFORMATION IS USED AND SHARED

Owlet uses this information solely to provide its recipe capture, review, printing, import/export, and KitchenOwl-saving functions.

When the user chooses Save, recipe data and any recipe image are sent directly to the KitchenOwl server selected by the user.

Authentication credentials are used solely to authenticate to that selected server. Owlet does not operate a service that receives recipe data or images.

Owlet does not:

  • Sell user data
  • Use user data for advertising or marketing
  • Use browsing history for advertising or profiling
  • Use recipe information for personalized recommendations
  • Operate analytics or tracking services
  • Automatically inspect pages as the user browses

KitchenOwl servers, including self-hosted servers, are controlled by their respective operators. Their privacy and security practices are separate from Owlet’s.

LOCAL STORAGE AND SECURITY

Owlet persistently stores the selected KitchenOwl server address and username, print-option preferences, interface visibility/font/theme preferences, print handoff data, and a limited diagnostic log in extension-local storage.

Owlet does not store the KitchenOwl password.

Access and refresh tokens are held in browser session storage rather than persistent local storage and are intended to disappear when the browser/extension session ends.

Disconnecting or a failed connection removes those session credentials.

On the first Read/Refresh Recipe action, Owlet requests optional access to HTTP and HTTPS sites from that direct user gesture. This access allows the action to read the active page and allows recipe images to load for review and printing.

Connecting KitchenOwl may request access to the selected server origin if access has not already been granted.

Owlet does not revoke previously granted permissions when the user disconnects. Permissions can be managed by the user through Chrome or Microsoft Edge.

DIAGNOSTIC INFORMATION

Owlet provides an optional diagnostic log that the user may download from the extension menu.

The diagnostic log is designed to contain only limited operational information such as:

  • Timestamps
  • Operation names
  • Counts
  • Response status
  • Data format
  • Generic error categories

The diagnostic log is not intended to contain:

  • Passwords
  • Authentication tokens
  • Authorization headers
  • Cookies
  • Session identifiers
  • Recipe contents
  • Recipe titles
  • Source URLs
  • Image URLs

The user can clear diagnostic information by removing extension data or uninstalling the extension.

PERMISSIONS

Owlet uses the following Chrome extension permissions:

  • activeTab — to access the active webpage following an explicit user action
  • scripting — to extract recipe information from the selected webpage
  • sidePanel — to provide the Owlet user interface
  • storage — to store the limited information described in this policy

Owlet may request optional HTTP and HTTPS host access when the user explicitly chooses to read a recipe. Owlet may also request access to a selected KitchenOwl server when the user explicitly connects that service.

These permissions are used to support user-initiated recipe capture and saving. They do not cause Owlet to automatically monitor or inspect webpages as the user browses.

CHROME WEB STORE LIMITED USE

Owlet’s use of information received from Chrome extension APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

User data is used only to provide Owlet’s single purpose and related operational functionality.

CONTACT AND CHANGES

For privacy questions, contact:

Support@Keniem.com

This policy may be updated when Owlet’s functionality or data practices change. The current version of this policy should be published at the privacy-policy URL associated with the Chrome Web Store listing before submission.