Privacy Policy
Last updated: November 1, 2026
This Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your information when You use the Service and tells You about Your privacy rights and how the law protects You. It applies to Our websites, applications, and related products and services.
We use Your Personal Data to provide and improve the Service as described in this Policy. Where a feature requires consent or separate permission, We request it for that purpose; using the Service or accepting general Terms is not a substitute for that permission.
Interpretation and Definitions
Interpretation
The words whose initial letters are capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in singular or in plural.
Definitions
For the purposes of this Privacy Policy:
- Account means a unique account created for You to access our Service or parts of our Service.
- Affiliate means an entity that controls, is controlled by, or is under common control with a party, where "control" means ownership of 50% or more of the shares, equity interest or other securities entitled to vote for election of directors or other managing authority.
- Application means any software application published or provided by Qutzl LLC, including mobile, desktop, and web applications, and related backend services.
- Business, for the purposes of the CCPA/CPRA and only to the extent that law applies to Qutzl LLC, refers to Qutzl LLC as the entity that determines the purposes and means of processing Consumers' personal information.
- Business Customer means a company or organization that purchases Managed Services, hosting, remote support, or other technology services from Qutzl LLC, together with the employees and other individuals it authorizes to receive those services.
- CCPA and/or CPRA refers to the California Consumer Privacy Act (the "CCPA") as amended by the California Privacy Rights Act of 2020 (the "CPRA").
- Qutzl LLC (also referred to as "the Company", "We", "Us" or "Our" in this Agreement) means Qutzl LLC, PO Box 154, Karthaus, PA 16845, United States of America. Where the GDPR applies, Qutzl LLC is the Data Controller for Personal Data it collects for its own purposes and a Data Processor for data it handles on behalf of Business Customers.
- Consumer, means a natural person who is a California resident. A resident, as defined in the law, includes (1) every individual who is in California for other than a temporary or transitory purpose, and (2) every individual who is domiciled in California who is outside California for a temporary or transitory purpose.
- Cookies are small files that are placed on Your computer, mobile device or any other device by a website, containing the details of Your browsing history on that website among its many uses.
- Data Controller, for the purposes of the GDPR (General Data Protection Regulation), refers to Qutzl LLC as the legal person which alone or jointly with others determines the purposes and means of the processing of Personal Data.
- Device means any device that can access the Service such as a computer, a cell phone or a digital tablet.
- Do Not Track (DNT) is a concept that has been promoted by US regulatory authorities, in particular the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing Internet users to control the tracking of their online activities across websites.
- GDPR refers to the EU General Data Protection Regulation and, where relevant, the UK GDPR.
- Managed Services means the IT support, remote support, server and network management, hosting, email, domain, security, camera and physical security system, consulting, and similar services Qutzl LLC provides to Business Customers under an agreement, quote, or invoice.
- Personal Data is any information that relates to an identified or identifiable individual. For the purposes of GDPR, Personal Data means any information relating to You such as a name, an identification number, location data, online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity. For the purposes of the CCPA/CPRA, Personal Data means any information that identifies, relates to, describes or is capable of being associated with, or could reasonably be linked, directly or indirectly, with You.
- Remote Support Session means a remote-access connection to a Device, started with the Qutzl Support application or otherwise authorized by You or a Business Customer, that lets a Qutzl technician view and control that Device to provide support.
- Service refers to the Website, the Applications, and related products, features, and technology services offered by Qutzl LLC.
- Service Provider means any natural or legal person who processes the data on behalf of Qutzl LLC. It refers to third-party companies or individuals employed by Qutzl LLC to facilitate the Service, to provide the Service on behalf of Qutzl LLC, to perform services related to the Service or to assist Qutzl LLC in analyzing how the Service is used. For the purposes of the GDPR, Service Providers are considered Data Processors. Our current Service Providers are listed in the Service Providers We Use section below.
- Store means an applicable third-party digital distribution platform such as the Apple App Store, Google Play, Amazon Appstore, Samsung Galaxy Store, or similar platforms.
- Third-party Social Media Service means a third-party sign-in service, such as Sign in with Apple or Sign in with Google, through which You can log in or create an Account for the Service.
- Usage Data refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself (for example, the duration of a page visit).
- Website refers to the websites operated by Qutzl LLC, including qutzl.net, qutzl.com, and chefskiss.io, the subdomains of those domains that Qutzl LLC operates, and any other website or application operated by Qutzl LLC.
- You means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable. Under GDPR, You can be referred to as the Data Subject or as the User as you are the individual using the Service.
Collecting and Using Your Personal Data
Types of Data Collected
Personal Data
While using Our Service, We may ask You to provide Us with certain personally identifiable information that can be used to contact or identify You. Personally identifiable information may include, but is not limited to:
- Email address
- First name and last name
- Phone number
- Address, State, Province, ZIP/Postal code, City
- Company name, job title, and billing details when You buy services from Us as or for a Business Customer
- Account credentials, support ticket contents, and other communications You send Us
Usage Data
Usage Data is collected automatically when using the Service.
Usage Data may include information such as Your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, the time spent on those pages, unique device identifiers and other diagnostic data.
When You access the Service by or through a mobile device or Application, We may collect certain information automatically, including, but not limited to, the type of mobile device You use, Your mobile device's unique ID, the IP address of Your mobile device, Your mobile operating system, the type of mobile Internet browser You use, Application version, unique device identifiers, crash logs, performance diagnostics, and other diagnostic data.
We may also collect information that Your browser or Application sends whenever You visit Our Service or when You access the Service by or through a mobile device.
Application Content and Activity Data
When You use an Application, We may collect and process Content and activity You provide or generate while using the Service, which may include:
- Saved content such as recipes, meal plans, notes, documents, preferences, and related materials
- Diet and allergy preferences You choose to enter in Chef's Kiss
- Chat prompts, messages, and other inputs You submit to AI or assistant features, and related outputs needed to provide those features
- Account settings, feature usage events, and similar in-app activity
Some Content may remain stored only on Your Device until You sync, back up, or otherwise transmit it to Our Service. We process Content You send to Us to provide the features You request.
Chef's Kiss
Chef's Kiss, Our recipe import, collection, and cooking Application, has its own Chef's Kiss section below. It describes what the app stores and where, its diet and allergy preferences, how long Chef chat history is kept, public share links and other sharing features, ads, notifications, and what account deletion removes. Diet and allergy preferences can reveal information about Your health or religious beliefs. We use them only to provide the features You request and never for advertising. Our Consumer Health Data Privacy Policy describes Your rights over that information under Washington, Nevada, and similar state laws.
Our Games
Our games, the Quiet Games and Our Mobile Games, use no account or analytics and keep Your progress only on Your Device. They are described in the Our Games section below.
Purchase and Entitlement Information
If You make a purchase or subscribe through a Store, that Store processes Your payment. We do not receive Your full payment card number from the Store. We may receive limited information needed to provide purchased features, such as purchase status, product or subscription identifiers, entitlement or renewal status, and transaction identifiers.
Push Notifications and Device Tokens
If You enable notifications, We may collect a device push token and related delivery status information so We can send the notifications You turn on, such as reminders or tips and offers You opt in to. You can turn off optional notifications in the Application's settings or Your Device settings.
Billing Portal and Payments
Our client portal at billing.qutzl.net collects the account, contact, company, billing, support ticket, and service details needed to provide and invoice Our services. Card and PayPal payments are processed by Stripe and PayPal under their own privacy policies. We do not store full payment card numbers on Our systems; We receive payment confirmations and the limited details needed to manage Your account, such as the card brand, last four digits, and expiry date.
Remote Support Sessions
Our remote support application, Qutzl Support, is available from connect.qutzl.net. It is built from the open-source RustDesk client using the RDGEN build tool and is configured to connect only to rendezvous and relay servers that Qutzl operates on a dedicated server We rent from OVHcloud. When You take part in a Remote Support Session:
- The standard application shows a session ID that You give to Your technician, and a connection is made only after You accept it on Your screen, every session. On request, We can provide a separately configured application that allows unattended access to a Device. It is installed only with the written authorization of the Device's owner or the Business Customer, and that authorization can be withdrawn at any time by uninstalling it or asking Us to disable access.
- We receive the Device's name, operating system, IP address, session ID, and connection times, and We keep a connection log of which technician connected, when, and for how long.
- During the session the technician can see Your screen and, with the permissions You grant in the application, control the keyboard and mouse, transfer files, and use the clipboard. Anything visible on screen, including documents, messages, or passwords You display, can be seen by the technician.
- Session traffic is encrypted end to end between Your Device and the technician's. Our relay servers forward encrypted traffic and cannot read it.
- We do not make video or audio recordings of sessions. Technicians may record written notes about the work performed in Your support ticket.
- You can end a session at any time by closing the application. Close anything You do not want seen before the session starts.
Managed Services Data
When We provide Managed Services, We may access systems, mailboxes, files, backups, logs, and user directories that contain Personal Data about a Business Customer's employees, customers, and contacts. Where We install or manage a camera or physical security system, We may also access video recordings and access-control records while installing, testing, or supporting it; the Business Customer owns those recordings and decides how they are used and how long they are kept. We access that data only as needed to deliver the services requested and under the Business Customer's instructions, as described in the Business Customers and Managed Services section below.
Contact and Request Forms
Some contact and data-request forms for Our Applications, including legacy Chef's Kiss contact links and the account deletion request form, are hosted on Google Forms. Information You submit through them is stored in Our Google Workspace account and processed by Google under its privacy policy. Built-in Chef's Kiss Help & Support is a separate feature described below; older clients may still use external contact links. You can also use Our support desk or contact form.
Information from Third-Party Social Media Services
Qutzl LLC allows You to create an account and log in to use the Service through the following Third-party Social Media Services:
- Sign in with Apple
- Sign in with Google
If You decide to register through or otherwise grant us access to a Third-Party Social Media Service, We may collect Personal data that is already associated with Your Third-Party Social Media Service's account, such as Your name and Your email address. If You use Apple's private email relay feature, We receive the relay address Apple provides instead of Your personal email address.
You may also have the option of sharing additional information with Qutzl LLC through Your Third-Party Social Media Service's account. If You choose to provide such information and Personal Data, during registration or otherwise, You are giving Qutzl LLC permission to use, share, and store it in a manner consistent with this Privacy Policy.
Chef's Kiss accounts, including these sign-in options, run on an authentication service that We operate on Our own servers. Clerk provides sign-in for Our administrative tools and some other Qutzl products. Both are described in the Service Providers We Use section below.
Cookies and Similar Technologies
Our public Qutzl websites, qutzl.net and its public subdomains such as insights.qutzl.net, show a cookie banner on Your first visit. Our client portal at billing.qutzl.net shows no banner because it uses only the essential and security cookies described below. Essential cookies work without Your consent; analytics and advertising cookies are set only after You accept them in the banner, and You can change Your choice at any time through the Cookie settings link in the footer of every page. Cookies and similar storage are used in the following places:
Essential Cookies
Where: Our client portal and sign-in pages, chefskiss.io and its web companion, and the signed-in areas of Our Applications | Administered by: Us
Purpose: Session cookies that keep You signed in, protect forms against cross-site request forgery, and prevent fraudulent use of accounts. They expire when You sign out or after a period of inactivity.
Consent Cookie
Where: all Our public websites | Administered by: Us
Purpose: A first-party cookie named qutzl_consent that records the choice You made in the cookie banner so You are not asked again on any Qutzl site. It holds Your yes-or-no choice for analytics and advertising cookies and the time You made it, nothing that identifies You, and it expires after 180 days.
Preference Storage
Where: insights.qutzl.net | Administered by: Us
Purpose: A browser local-storage value that remembers when You dismiss a Chef's Kiss house advertisement so it is not shown again in that browser. It contains no identifier and is never sent to Us.
Security and Delivery Cookies
Where: any of Our sites served through Cloudflare | Administered by: Cloudflare
Purpose: Cloudflare may set short-lived cookies to tell automated traffic from people and to deliver the site securely. They are not used for advertising.
Advertising Cookies and Identifiers
Where: Our websites where Google AdSense is enabled and ad-supported Applications that use Google AdMob; website advertising on chefskiss.io is currently paused | Administered by: Google and its advertising partners
Purpose: Used to serve, personalize, and measure advertising. On Our websites, personalized advertising cookies are set only after You accept advertising cookies in the banner; declining personalization does not itself establish eligibility to request or serve an ad. See the Analytics and Advertising section below for the services that may show ads and the controls available to You.
Analytics Cookies and Identifiers
Where: Our websites and Applications that use an analytics provider, where enabled | Administered by: that provider (PostHog on Our websites)
Purpose: Measure which pages and features are used so We can improve them. On Our websites, the analytics service and its cookies load only after You accept analytics cookies in the banner. Providers in use are listed in the Service Providers We Use section below.
Emails We send may contain a delivery or open-tracking image from Our email delivery provider; You can block remote images in Your mail client. You can block or delete cookies in Your browser settings, but blocking essential cookies will prevent You from signing in to the client portal or Applications.
Use of Your Personal Data
Qutzl LLC may use Personal Data for the following purposes:
- To provide and maintain our Service: including Application features such as accounts, saved content, planning and organization tools, chat or AI features, and to monitor the usage of our Service.
- To manage Your Account: to manage Your registration as a user of the Service.
- For the performance of a contract: the development, compliance and undertaking of the purchase contract for the products, items or services You have purchased, including verifying Store entitlements.
- To contact You: by email, telephone calls, SMS, push notification, or other equivalent forms of electronic communication about Your Account, services, and support requests. We send marketing text messages only with Your prior express consent.
- To provide You with news and offers: about other goods, services and events similar to those you have already purchased or inquired about. You can opt out of promotional email at any time using the unsubscribe link included in those messages or by contacting Us; transactional and service messages (such as invoices, renewal notices, and security alerts) are not affected.
- To manage Your requests: To attend and manage Your requests to Us.
- To improve the Service: including troubleshooting, analytics, security, and, where applicable, evaluating aggregate usage patterns to improve quality. We do not sell Your Content, and We do not use Your Content to train artificial intelligence models.
- To provide Managed Services: to access, configure, monitor, secure, and repair systems for Business Customers under their instructions.
- To deliver Remote Support Sessions: to connect to a Device You authorize, verify the session, and keep connection records for security and billing.
- For business transfers: We may use Your data to evaluate or conduct a merger, asset sale, or restructuring.
- For other purposes: such as data analysis, identifying usage trends, and security audits.
Sharing Your Personal Information
We may share Your personal information in the following situations:
- With Service Providers: to host infrastructure, provide AI inference, process payments, deliver email, analyze use of our Service, report crashes, or otherwise help Us operate the Service. Our current providers are listed in the Service Providers We Use section below.
- With payment processors: Stripe and PayPal, to take and refund payments on Our client portal and to prevent fraud.
- With Business Customers: if You use the Service as an employee, contractor, or end user of a Business Customer, with that customer and its administrators, including support ticket history and Remote Support Session records for its Devices.
- With Stores: as needed to validate purchases, subscriptions, and entitlements.
- For business transfers: in connection with, or during negotiations of, any merger or sale of Qutzl LLC assets.
- With Affiliates, if any: in which case we will require those affiliates to honor this Privacy Policy.
- With other users: in public areas where information is distributed publicly.
- With Your consent: We may disclose Your personal information for any other purpose.
Service Providers We Use
We rely on third-party companies to run Our websites, Applications, and services. Their roles and applicable privacy terms differ. The list is not exclusive: it describes services behind Our websites, Applications, client portal, and support, and may not include products specific to an individual Business Customer. The Chef's Kiss section gives more specific disclosures, including AI routing and legacy image handling. The main categories and providers are:
- Websites, content delivery, DNS, and file storage: Cloudflare, which serves Our public Qutzl websites, sits in front of Our client portal and the customer websites We host, provides DNS, TLS certificates, and security for those domains, stores the remote support downloads, article images, and house ad images, and runs the Chef's Kiss website, web companion, and API; and QUIC.cloud, which provides content delivery, optimization, and certificates for websites We host.
- Servers and cloud infrastructure: NameHero, which hosts Our client portal at billing.qutzl.net and Our cPanel web and email hosting; OVHcloud, whose dedicated server runs Our remote support rendezvous and relay servers and other Qutzl-managed virtual machines; and Vultr, Amazon Web Services, Google Cloud, and Microsoft Azure for additional servers, storage, backups (including Amazon S3 Glacier long-term archives), and AI platform services.
- Hosting platform software and add-on products: cPanel and WHMCS from WebPros, CloudLinux OS and Imunify360 from CloudLinux, Let's Encrypt certificates, and JetBackup backups, which run on the servers above and send their vendors license, security, and certificate data rather than Your account content, and optional installers and builders in the control panel that run only when You use them; and the providers of add-on products sold through Our client portal, such as Sectigo, DigiCert, CodeGuard, SiteLock, and SocialBee, which receive Your order details and deliver the product under their own terms.
- Domain names: Cloudflare, the registrar with which We register Your domain in a Cloudflare account of Your own, and the registry for each extension, which receive the contact details You enter when You register, transfer, or renew a domain through Our client portal and keep them as the domain's registration record under ICANN and registry rules.
- Application backend and tooling: Convex provides application databases and backends, including synced Chef's Kiss data and built-in support records. Cloudflare R2 is the current runtime store for Chef's Kiss recipe covers. UploadThing is a former cover-storage provider; historical files and references may remain as described in the Chef's Kiss section. RevenueCat manages in-app purchase and subscription entitlements. Expo provides mobile build and push-delivery services; Expo Observe provides performance and crash diagnostics, separately from optional feature-usage analytics or session replay.
- AI inference for Application features: Across Qutzl products, providers include Anthropic, OpenAI, Google through its APIs, xAI (Grok), OpenRouter for routing, and open-weight models We run on Our infrastructure. Chef's Kiss Chef and recipe extraction use OpenRouter and the model providers disclosed for the enabled feature. Current Chef's Kiss cover generation uses Google and OpenAI, directly or through OpenRouter as configured, and may include a title, ingredient names, and up to 120 characters of scrubbed recipe notes. Older images may have other historical provider provenance. Exa receives conversation-derived search terms for optional Pro web search. See the Chef's Kiss section for information sent, separate AI permission, and provider-retention limitations. We do not make a universal guarantee about providers' retention, training use, or processing country.
- Development, source control, and monitoring: Cursor and T3 Code, together with the model providers above, for writing and maintaining Our software; GitHub and a self-hosted GitLab for source code; and Uptime Kuma (self-hosted) and HetrixTools for checking that Our sites and the systems We manage are reachable. These tools process Our source code, configuration, hostnames, and availability data, not Your Content or Account data, apart from log excerpts We may share while diagnosing a problem.
- Payments: Stripe and PayPal for client portal invoices, and the Apple, Google, Amazon, and Samsung Stores for Application purchases.
- Email and productivity: Mailgun, which delivers account, notification, and support email, and Google Workspace, which hosts Our mailboxes and forms.
- Sign-in and account security: an authentication service We operate on Our own servers for Chef's Kiss accounts; Clerk, for sign-in to Our administrative tools and some other Qutzl products; and Apple and Google for the optional social sign-in options.
- Remote support: the open-source RustDesk client, built for Us with RDGEN and configured to connect only to servers We operate. The RustDesk project does not receive Your session data.
- Advertising and analytics: Google AdSense on Our websites where ads are enabled (website advertising on chefskiss.io is currently paused), Google AdMob in ad-supported Applications, PostHog on Our websites and in Applications where enabled, and Google Analytics where enabled in an Application.
We review this list at least quarterly and update it when a provider changes. You can request more information about a provider's role, the data it handles, its processing locations, or its privacy policy through the contact methods below.
Business Customers and Managed Services
When We provide Managed Services or remote support to a Business Customer, We act as a service provider (a "processor" under the GDPR) for Personal Data in that customer's systems, such as its employee directory, mailboxes, files, backups, and customer records. In that role:
- We access and use that data only as needed to deliver the services the Business Customer requested and under its instructions, Our agreement with it, and this Privacy Policy.
- The Business Customer is responsible for having the right to give Us access, for notifying its own users as its laws require, and for approving Remote Support Sessions on its Devices.
- We do not use Business Customer data for advertising, do not sell it, and do not disclose it except to Service Providers that help Us deliver the service or as required by law.
- If You are an employee or end user of a Business Customer and want to exercise privacy rights over data in that customer's systems, please contact the Business Customer. We will support its response.
- When an engagement ends, We return or delete the Business Customer's data and remove Our access and credentials, except for backup copies, which expire within 90 days, or within 180 days where held in long-term archive storage, and records We must keep by law.
Business Customers that need a written data processing agreement, or a list of the Service Providers involved in their services, can request one through the contact methods below.
Chef's Kiss
Chef's Kiss is Qutzl LLC's recipe import, collection, and cooking Application for iOS, Android, and the web, including app.chefskiss.io and chefskiss.io. Chef chat is a secondary assistant. The Service is intended for adults aged 18 and older. An age declaration does not mean We independently verify every user's age.
This section supplements the rest of this Privacy Policy and controls where it gives more specific information about Chef's Kiss. Our Consumer Health Data Privacy Policy also describes applicable rights over diet, allergy, and other consumer health information.
At a Glance
We use information to import and organize Your recipes, support cooking features, and provide the AI features You request. Current clients ask for separate AI permission, which You can withdraw in Settings. We do not routinely send Your entire library to an AI provider. Diet and allergy preferences, recipes, and Chef conversations are not advertising targeting data. Help & Support requests, user-submitted content reports, and automatic safety-review records are separate records with different purposes and retention periods. Account deletion does not cancel an Apple or Google subscription.
Version 4.0 and Feature Rollout
The descriptions below include changes prepared for the 4.0 release. Availability and enforcement depend on the app version and deployed backend. Older clients and backends may continue to behave differently until updated; in particular, dietary-context formatting, AI-permission enforcement, report-expiry handling, and diagnostics settings may differ. Automatic harmful-bypass holds are initially disabled. The conditional descriptions of automatic review and holds apply only if those features are enabled. Publishing this Policy does not activate a feature, update a client or backend, or enable enforcement.
Accounts and Guest Use
Guest use. You can use the mobile app without an Account. Guest recipes and pantry data stay on Your Device unless You send them through a feature such as an import, AI request, share, or support submission. Guest Chef requests carry a random device identifier used for usage limits and abuse prevention.
Accounts. You can create an Account with an email address and password, an emailed sign-in code, Sign in with Apple, or Sign in with Google. Accounts run on an authentication service We operate on Our own servers. Passwords are stored as salted hashes. Clerk provides sign-in for administrative tools and some other Qutzl products, rather than Chef's Kiss consumer accounts.
Names and age confirmation. You can set a first name for Chef's greeting and a name visible to people on Your shared shopping lists and libraries; if the shared name is blank, they see a short code instead. The app records Your confirmation that You meet the age requirement and when You gave it, rather than collecting Your birth date for that confirmation.
Account email. Mailgun delivers sign-in codes, verification, password recovery, and account deletion messages, with open and click tracking turned off for those messages.
Library, Kitchen, and Settings
Chef's Kiss stores recipes You import, create, or save from Discover, with folders, tags, favorites, notes, version history, and cover references. Kitchen information can include pantry items and expiry dates, meal plans, shopping lists, events, and Kitchen Level progress. Settings include diet and allergy preferences, appearance, language, notifications, ad preferences, usage limits, and referral details.
Convex provides the application database and backend for account data and features that sync. Sync depends on Your plan and feature: Local Unlock keeps Your recipe library on Your Device, and some planning and shopping features also remain local unless Your plan includes sync. A local library does not mean that AI requests, support submissions, or other online features never send data to Our servers. We cannot recover information held only on Your Device. Use export tools to keep a copy of important local information.
AI Permission and Information Sent
Current clients request explicit permission before sharing information for AI processing and let You withdraw that permission in Settings. Accepting general Terms or this Privacy Policy does not by itself grant AI permission. Withdrawal controls future AI use; it does not recall requests already processed or automatically delete records kept under the retention rules below. Older-client and backend enforcement may differ during rollout.
For the enabled feature, requests use OpenRouter and the model providers disclosed for that feature. Current recipe-cover generation uses Google and OpenAI, directly or through OpenRouter as configured. Other Qutzl products may use the additional providers listed in Service Providers We Use. Older cover images may have been generated by other providers; their presence does not identify a current Chef's Kiss image provider.
We do not add Your account name, email address, or account ID to normal OpenRouter model requests. Request text or attachments may themselves contain identifying information. We send information relevant to the feature You request:
- Recipe extraction and import: text from the link, video description or captions, recipe text, or photo You select, together with relevant dietary preferences and ingredient exclusions used for the requested feature. OpenRouter routes extraction requests to the disclosed model provider. Source links are saved with imported recipes.
- Chef chat: Your request, relevant conversation context, attachments You choose to submit, the recipe opened with Chef where relevant, and relevant dietary preferences and ingredient exclusions. This is not routine transmission of Your entire library.
- Recipe covers: the recipe title, ingredient names, and up to 120 characters of scrubbed recipe notes used as styling context. Scrubbing does not make recipe notes anonymous; avoid including private information You do not want processed for this purpose.
- Optional Pro web search: search terms derived from the conversation are sent to Exa to retrieve web results. A derived search term can itself reveal information from Your conversation.
- Optional support AI: the support conversation is sent after AI permission, as described under Help & Support. That assistant does not automatically receive diagnostics, screenshots, Your library, or Chef history.
Qutzl does not use Your Content to train AI models. This Policy does not promise zero retention by an AI or search provider, that every provider excludes all training uses, or processing in any particular country. Provider handling depends on the provider, the enabled service, and applicable terms and settings. Withdrawing AI permission does not replace a request to delete data already held by Us or a provider.
Pantry barcodes. For a pantry product lookup, Our servers send the barcode to Open Food Facts to retrieve the product's name and picture.
Diet and Allergy Preferences
Diet styles, common or custom allergies, and notes about foods You prefer or avoid are optional. Chef's Kiss works without them. Previously saved medical presets such as Diabetic, GERD, Low FODMAP, DASH, and Heart-healthy, as well as allergies and other condition-related preferences, can reveal health information; Kosher and Halal can reveal religious beliefs. We treat preferences that reveal health information or religious beliefs as sensitive information.
With the updated dietary-context handling, the five medical presets listed above remain readable in existing saved settings but are currently withheld from automatic AI context while We clarify data requirements with upstream providers. Updated clients no longer offer those presets as new selections. We do not infer replacement food goals from a saved medical preset. You can explicitly choose ordinary food preferences such as Less added sugar, Mild flavors, and Less acidic ingredients. These changes take effect as the relevant client and backend updates roll out; older request paths may still include the earlier medical classifications.
Relevant remaining preferences may accompany an Import or Chef request to the AI providers described above. Where the updated backend handling is deployed, ingredients from saved allergies and other avoidances are combined into an ingredients-to-avoid instruction without identifying which ingredients came from an allergy entry. Other selected diet names, including Kosher or Halal, custom diet descriptions, and preference text can still be sent. Older backends may explicitly label allergy context. Food instructions can themselves reveal sensitive information. Messages, earlier conversation context, recipes, notes, attachments, and derived search terms can also contain personal or health information; the medical-preset change does not automatically remove that information or anonymize a request.
This change to AI request formatting does not change how Your saved preferences are stored or synced. Synced preferences are stored with Your Account; guest preferences remain on Your Device except when included in a request You make. We do not sell these preferences, use them for advertising or ad targeting, supply them to Google AdMob or AdSense, or publish them to other users.
You can change or clear preferences in Settings under Diet & Allergies on mobile or Dietary preferences on the web, and request deletion through the contact methods below. Account deletion includes account-stored preferences, subject to the limited record and backup exceptions described below. Where explicit consent is required for sensitive information, it must be obtained separately; entering preferences or accepting general Terms is not a substitute for the required consent. AI permission and permission to store sensitive preferences are separate choices.
Chef History and Usage Limits
The retention periods for visible Chef history differ from security records and reports:
| Plan or use | Visible history on Your Device | Signed-in server history |
|---|---|---|
| Free, Essentials, and Local Unlock | Seven days | 30 days |
| Guest | Seven days | No signed-in history; separate abuse-review copies described below |
| Plus and Pro | One year | One year |
Guest abuse-review copies are separate from visible chat history. They can contain a bounded copy of a guest question and reply and the recipe Chef generated, associated with a device identifier rather than an Account, for a 30-day abuse-review window. They are not the content-free refusal receipts described below.
We count Chef and import requests per Account or device to apply plan limits. A history item disappearing from the app does not mean that every server, security, or backup copy has been physically erased at that moment. The current implementation allows a seven-day grace period for physical cleanup of soft-deleted chat rows and uses scheduled server cleanup. If plan-entitlement evidence is unavailable, plan-based server cleanup can be deferred rather than incorrectly shortening paid history, subject to the one-year server ceiling. Cleanup schedules and deployed versions can affect physical removal; the periods for separate records below still apply. Review of a safety receipt or resolution of a report does not start a new retention period.
Sharing and Cover Images
Public links. Creating a public share link stores a copy of that recipe that anyone with the link can read without signing in. You can update or revoke the link in the app. Other people can retain copies they have already received.
Shared libraries and shopping lists. Members can see the content shared there and Your chosen shared name. Discover recipes are published by Our team; saving one copies it into Your library. Your own recipes are not automatically published to Discover.
Referrals. When a friend applies Your code, We record the referral to award bonus slots. Custom codes are reviewed by Our team. Deleting either Account removes the identifying link between the Accounts, while the other person keeps the bonus.
Storage and access. Current runtime recipe-cover storage uses Cloudflare R2. Published catalog covers are publicly accessible through the content delivery network. Personal and pending covers have restricted access. UploadThing is no longer used for new runtime cover storage or signing. Historical files and references may remain from the prior service and for older-client compatibility; removal of that integration does not establish that every legacy file has been erased.
Deletion and reuse. Generated, catalog, and community images may be reused and may remain after Account deletion, with the deleted Account's ownership associations removed. This does not mean that private uploads, recipe-extraction photos, or support screenshots become part of a public or reusable image collection. Those inputs are handled for their respective features and deletion purposes. Contact Us to request deletion of a private upload or a legacy file. Account deletion includes signed-in support requests. Removal of every image from legacy storage, caches, provider systems, and backups is not necessarily immediate; the precise behavior for those copies depends on the storage and feature involved.
Help & Support
Built-in Help & Support requests can contain a subject, description, replies, optional contact email, and screenshots You select. Optional diagnostics are limited to app version, build number, platform, OS version, device type, and selected language. Review what You submit, including any personal information visible in a screenshot.
Support records expire 90 days after creation and are removed through scheduled cleanup. Replies do not restart that period. Signed-in support requests are included in Account deletion. Guest requests use a separate private access credential and are not automatically transferred to an Account when You sign in. Replies are available in the app; this feature does not currently send automatic support emails. An optional contact email is part of Your submission, not a promise of automatic email delivery.
If You choose the optional support AI assistant and give AI permission, it receives its support conversation. It does not automatically receive diagnostics, screenshots, Your library, or Chef history. AI can propose a report, but You must review and submit it Yourself. Direct support remains available during a provisional AI hold, although the support AI assistant can be restricted as an AI feature.
User-Submitted AI and Content Reports
When You submit an AI or content report, We retain bounded reported content, Your explanation, and relevant Account, device, request, or content identifiers to investigate. These are separate from Help & Support requests and automatic refusal receipts. Current report handling gives a report an original 90-day deadline; resolving it does not restart that deadline. An administrative listing limit, including a screen showing up to 200 reports, is not a retention rule.
Account deletion does not necessarily immediately remove every abuse or security report. Legacy reports, backup copies, or records retained for a legally required purpose may require separate handling. The 90-day rule describes current report handling, rather than a guarantee that every historical or backup copy is physically erased by that deadline.
Safety Reviews and Account Standing
Valid safety-refusal receipts can contain request and Account identifiers, the request time, a refusal reason or category, the model, request length, and a request hash. Ordinary refusal receipts do not contain the message text. They do not copy a whole conversation, library, image, or attachment.
When automatic harmful-bypass review is enabled, a candidate for that review may additionally retain a verbatim evidence excerpt of up to 400 characters. An independent corroborating AI assessment receives the latest request text through the disclosed Chef provider chain; it does not receive the whole conversation or library. These receipts expire 30 days after the original request, and reviewing them does not restart that period. Account deletion removes the provisional Account hold, but limited security receipts can remain until their original expiry.
Minimal restriction and decision metadata is separate from the receipts. A provisional hold is bounded to its original 30-day window. A cleared decision can leave a content-free fence for up to 15 additional minutes, to prevent a delayed action from reapplying the cleared decision. Scheduled cleanup can be delayed, but expired restrictions cease applying. Independently imposed manual restrictions are separate from provisional holds and their expiry.
Access to review records is limited to authorized review personnel. Account-standing responses do not disclose private evidence or operator notes. A model flag can be mistaken; manual review and appeals through Help & Support are described in Our Acceptable Use Policy. The current automated process does not send reports to law enforcement or other outside authorities. Lawful disclosure obligations are addressed separately in this Policy.
Purchases and Advertising
Plans include Free, Essentials, Local Unlock, Plus, and Pro. Purchases offered through Apple or Google are processed by that Store. We do not receive Your payment card details. RevenueCat manages purchase and subscription entitlements, including Account, product, and transaction identifiers and purchase and renewal information. Store and RevenueCat purchase records can remain as needed for accounting, tax, refunds, and fraud prevention. The web companion reads Your plan and does not take payments.
Deleting Your Account does not cancel an Apple or Google subscription. Manage cancellation through the relevant Store's subscription settings. Deleting the app also does not cancel a subscription or delete Your Account.
Free and Local Unlock may display automatic banner or feed ads through Google advertising services. Essentials, Plus, and Pro remove those automatic placements. Optional rewarded ads may be offered on every mobile plan when eligible and voluntarily chosen. Removing automatic ads does not rule out an optional rewarded ad You choose. Rewarded Ad Offers can be turned off in Settings under Ads.
Google's User Messaging Platform (UMP) determines whether an ad request is eligible under the applicable consent state. Request eligibility and ad personalization are separate: declining consent does not guarantee that non-personalized ads will be served, and some consent states do not permit a request. On iOS, App Tracking Transparency separately controls tracking permission. Non-personalized or limited ads, where eligible, can still involve device information and IP addresses for delivery, measurement, frequency control, or fraud prevention.
Website advertising on chefskiss.io is currently paused; the help wiki is ad-free. If website advertising resumes, its applicable disclosure and consent controls must accompany it. Dietary preferences, allergies, recipes, and chat content are not supplied as advertising targeting data. Advertising providers' other collection is described in Analytics and Advertising below.
Notifications
Pantry expiry reminders and cook timers are scheduled on Your Device; those reminders and timers are not sent to Us. Promo & Tips is off until You turn it on. If You enable it while signed in, We register a push token for delivery through Expo and Apple's or Google's notification service. You can turn it off in Settings under Notifications. Account deletion includes that token.
Diagnostics and Other Security Records
Expo Observe is used for performance and crash diagnostics, including app and device information. It is not optional feature-usage analytics or session replay. The corrected app configuration disables automatic navigation and query-parameter collection and network tracing. Older diagnostic payloads may differ; We do not claim that no historical diagnostic payload could ever have included content.
Our API runs on Cloudflare. Separate operational records include sampled request logs, usage events associated with Account or device identifiers, and failed or blocked requests. The existing operational periods are up to seven days for request logs, about three months for usage events, and 30 days for failed or blocked requests. Refusal receipts, reported content, and restriction decisions have the more specific handling described above. Other device or IP security blocks can survive Account deletion until reviewed and lifted; they are not provisional harmful-bypass holds.
Registered-account counts come from Our authentication backend. They are not counts of active installations or daily users. Chef's Kiss does not currently use optional third-party feature-usage analytics or session replay. Expo Observe diagnostics and advertising services are separate from that statement. If We add optional analytics, We will identify the provider and update the relevant disclosure; diet and allergy preferences will not be sent to analytics providers.
Retention and Account Deletion
Library, kitchen, planning, and preference data are retained for the features You use until You delete the data or Your Account, except for shorter periods described above. Chef history, guest abuse-review copies, refusal receipts, support requests, and submitted reports each have their own periods. Our cached plan status expires within 45 days after it last changed. We keep the existing content-free deleted-Account identifier record to prevent old sessions or delayed requests from recreating deleted data; it contains no name, email, or Content.
You can request Account deletion under Settings, then Account, on mobile or the web. If You cannot sign in, use the account deletion request form linked from the app or any Contact Us method below. Deletion starts the removal process and cannot be undone. It includes account-stored library, pantry, planning data, dietary preferences, Chef history, public share links, push tokens, sign-in details, and signed-in support requests. Local-only copies must be removed on the Device separately.
Limited security receipts may remain until their original expiry; generated, catalog, or community images may remain with ownership associations removed; and some reports, purchase records, operational logs, deleted-Account identifiers, and backup or legacy copies may remain as described above. Removing ownership associations does not establish that an image or record is anonymous. Guest support records are separate from Your Account.
Expiry and physical cleanup are not always simultaneous. This section does not promise immediate erasure of every image, private upload, support screenshot, legacy report, provider copy, or backup. The company-wide backup periods below are not a verified physical-deletion deadline for every Chef's Kiss copy. You can ask Us about deletion of a specific record through Help & Support or the Contact Us methods below. Applicable consumer health data deletion rights are described in Our Consumer Health Data Privacy Policy and are not overridden by the operational retention exceptions above.
Our Games
This section covers the games We publish: the Quiet Games (Quiet Find, Quiet Match, and Quiet Bingo, calm large-type puzzle apps designed for older adults) and Our Mobile Games (Offline Arcade, Pocket Puzzles, and other game collections We release under the Qutzl name). The rest of this Privacy Policy also applies to them; where this section is more specific, it controls. None of these games uses an account, analytics, AI features, chat, or a Qutzl server for Your play.
What Stays on Your Device
- Progress and settings. Your boards, cards, levels, scores, streaks, coins and cosmetic items earned in play, favorites, display and voice settings, and, in the Quiet Games, the caregiver PIN and recovery code and the local play statistics shown in the caregiver menu, are stored only on Your Device. We cannot see, back up, or recover them. They remain until You change them in the app or delete the app, and Your Device's own backup may keep copies according to its settings.
- Backups You export. Each game can export a backup file through Your Device's share sheet to a place You choose. The file contains Your progress and settings, in the Quiet Games including the caregiver PIN and recovery code, and the game does not encrypt it. Share it only with people and services You trust; You control the copies You make, and importing a backup replaces the progress in that app. Backups never contain purchase receipts or entitlements.
- Voice features. The Quiet Games can read words aloud using Your Device's own speech output, and Quiet Bingo plays bundled voice recordings. No game records microphone audio or sends Your voice to Us.
Ads
- Quiet Games. An optional banner served by Google AdMob can appear. The apps ask Google for non-personalized ads only, after Google's consent check where it applies, and limit ads to general-audience content. Google's advertising SDK may still process Your IP address and approximate location, device and advertising identifiers, ad impressions and interactions, and diagnostics, as described in Google's data disclosure and privacy policy. You can turn the banner off for free under Show banner ad in Settings, revisit Google's consent choices under Ad privacy choices where they are offered, and report an ad from Settings or through its AdChoices control. Turning the banner off stops new ad requests; it does not erase what Google has already processed.
- Mobile Games. Offline Arcade and Pocket Puzzles may show a banner and offer optional rewarded ads, for example to continue a round, through Google AdMob where live ads are enabled. Until then their ads are labelled demonstrations that load nothing from the internet. When live ads are enabled We will name the app in this section, Google's consent message will ask where it applies, and the Google AdMob section below will apply. Declining an ad never prevents a new game.
Purchases
The Quiet Games have no purchases or subscriptions. Offline Arcade and Pocket Puzzles may offer in-app purchases through the App Store or Google Play where they are shown in the app, such as removing banners or buying coins, managed with RevenueCat as described in the Purchase and Entitlement Information section above. Coins and cosmetic items earned by playing are stored only on Your Device.
Diagnostics and Deletion
The games send Us no crash reports, usage events, or analytics. Google receives the information described above when an ad is requested, and Apple or Google may collect diagnostics under their own policies and Your Device settings. Because We hold no data about Your play, deleting the app from Your Device deletes everything the game stored; Google's own privacy controls apply to the information it holds.
Analytics and Advertising
Our public Qutzl websites may show Google AdSense ads and may use PostHog analytics. Website advertising on chefskiss.io is currently paused. The cookie banner on Our websites asks for Your consent before analytics cookies are set and before advertising is personalized, and the Cookie settings link in every footer lets You change that choice. The providers below apply to Our websites and Applications where enabled. Each provider processes data under its own privacy policy in addition to this one.
Google AdSense (Website Advertising)
Where We enable website ads, Google AdSense and its advertising partners may use cookies, device identifiers, IP address, and browsing activity to serve and measure advertising. Website advertising on chefskiss.io is currently paused. If You decline advertising cookies or send Global Privacy Control, We do not request personalized treatment for that browser. This does not by itself mean Google can serve a non-personalized ad: request eligibility depends on the applicable consent state and requirements. Eligible non-personalized or limited ads can still involve IP address and device information for delivery, measurement, frequency control, and fraud prevention. Google's consent tools and Google Ads Settings provide additional controls. See how Google uses information from sites and apps.
Google Analytics
Some of Our Applications may use Google Analytics to understand how the Application is used. Google uses the data collected to track and monitor use of those Applications. You can opt out of Google Analytics in Your browser by installing the Google Analytics opt-out browser add-on. For more information on Google's privacy practices, see the Google Privacy Policy.
Google AdMob (In-App Advertising)
Some of Our Applications are ad-supported and display advertising served by Google AdMob and its advertising partners. Ad services may collect and use device advertising identifiers, IP address, and app usage information to serve and measure ads. In the European Economic Area, the United Kingdom, Switzerland, and other places where it is required, Google's consent message asks before personalized ads are shown, and on iOS We also ask through App Tracking Transparency. Ad-request eligibility and personalization are separate. Declining consent or iOS tracking permission does not guarantee that a non-personalized ad will be served; some consent states do not permit ad requests. You can also limit the use of Your advertising identifier through Your device settings:
- iOS / iPadOS: Settings > Privacy & Security > Tracking (App Tracking Transparency), where You can decline tracking requests per app or turn off "Allow Apps to Request to Track" entirely.
- Android: Settings > Privacy > Ads, where You can reset or delete Your advertising ID.
For more information, see how Google uses information from ads.
Product Analytics
Our websites and some Applications may use PostHog, a product analytics service, to collect page views, feature usage events, and session information such as the pages You visit, the links You use, Your browser and device type, Your approximate location from Your IP address, and a random identifier stored in a cookie or local storage, so We can understand how the sites and Applications are used and improve them. On Our websites, PostHog loads only after You accept analytics cookies in the banner, and withdrawing that choice stops it. We do not use session recording, and We do not send Your diet and allergy preferences, Your Content, or anything You type to PostHog. See the PostHog Privacy Policy for that provider's practices.
What We Never Use for Ads or Analytics
Your Content, AI chat conversations, diet and allergy preferences, client portal records, and Remote Support Session data are never used for ad targeting or shared with advertising providers. Diet and allergy preferences are also never sent to analytics providers.
Retention of Your Personal Data
Qutzl LLC retains Personal Data only as necessary for the purposes in this Policy, and afterwards only to the extent needed for legal obligations, disputes, or enforcement. The Chef's Kiss section controls its specific record periods, deletion exceptions, rollout limitations, and unverified legacy or backup behavior. The standard company-wide periods below do not establish a verified physical-deletion deadline for every Chef's Kiss copy. Backups and archives are encrypted. Our standard periods for other data are:
- Account and Application Content such as saved recipes, meal plans, notes, documents, preferences, and chat history: kept while Your Account is active, except where an Application keeps it for a shorter period, such as Chef's Kiss chat history, described in the Chef's Kiss section above. After You delete Your Account or ask Us to, We delete or anonymize it within 30 days. Copies in routine backups expire within 90 days after that; copies held in long-term archive storage (Amazon S3 Glacier) have a minimum retention period of 180 days and are deleted when that period ends.
- Client portal records: invoices, payments, contracts, and support tickets are kept for 7 years after the account closes to meet tax, accounting, and legal obligations.
- Remote Support Session records: connection logs (date, time, duration, Device name and identifier, IP address, and technician) are kept for 12 months for security and billing. We do not keep video or audio recordings of sessions.
- Managed Services data: handled according to the Business Customer's agreement and returned or deleted when the engagement ends, except for backup copies, which expire within 90 days, or within 180 days where held in long-term archive storage.
- Usage Data and server logs: kept for no more than 12 months unless needed to investigate a security incident or required by law.
Transfer of Your Personal Data
Qutzl LLC is based in the United States of America, and Our Service Providers operate in the United States of America and other countries. If You access the Service from outside the United States of America, Your information will be transferred to, stored, and processed in the United States of America and in other countries where Our Service Providers operate, where data protection laws may differ from those of Your jurisdiction.
Where the GDPR or UK data protection law applies, We take the steps those laws require for international transfers, such as relying on Service Providers certified under the EU-U.S. Data Privacy Framework or on standard contractual clauses, and We apply the safeguards described in the Security section regardless of where data is processed. You may request more information about these safeguards through the contact methods below.
Delete Your Personal Data
You have the right to delete, or to ask Us to delete, the Personal Data We have collected about You. You can do this by signing in to Your Account and using the in-app deletion or export controls where available, by opening a ticket at Our support desk or using Our contact form, or, for Chef's Kiss, by using the account deletion request form linked from the Application. We will confirm Your request, verify Your identity where necessary, and complete deletion within 30 days, except for data retained as described in the Chef's Kiss section or needed to meet legal obligations, resolve disputes, or enforce Our agreements.
Deleting an Application from Your Device does not by itself delete Account data stored on Our systems. Store purchase history remains subject to the applicable Store's records and policies. Data held in a Business Customer's systems is controlled by that customer; please direct requests about it to them.
Disclosure of Your Personal Data
Business Transactions
If Qutzl LLC is involved in a merger, acquisition or asset sale, Your Personal Data may be transferred. We will provide notice before Your Personal Data is transferred and becomes subject to a different Privacy Policy.
Law Enforcement
Under certain circumstances, Qutzl LLC may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency).
Security of Your Personal Data
The security of Your Personal Data is important to Us. We use commercially reasonable administrative, technical, and physical safeguards designed to protect Personal Data, such as encryption of data in transit and at rest, including Our backups and archives, access controls that limit data to the people who need it, and reputable hosting providers. However, no method of transmission over the Internet or method of electronic storage is 100% secure, and We cannot guarantee absolute security.
If We become aware of a breach of security affecting Your Personal Data, We will notify You and the relevant authorities where required by applicable law.
Children's Privacy
Our Service is intended for adults and is not directed to anyone under the age of 18. We do not knowingly collect Personal Data from anyone under 18. If You are a parent or guardian and You are aware that Your child has provided Us with Personal Data, please contact Us through Our support desk. If We learn that We have collected Personal Data from anyone under 18, We will delete that information and close any related Account.
GDPR Privacy (Legal Basis & Rights)
Legal Basis for Processing
If You are in the European Economic Area or the United Kingdom, We process Personal Data only when We have a legal basis to do so, which may include: Your consent; performance of a contract with You; compliance with a legal obligation; protection of vital interests; or Our legitimate interests (such as operating, securing, and improving the Service), provided those interests are not overridden by Your rights. Diet and allergy preferences in Chef's Kiss can be special category data about health or religious beliefs, and We process them only with Your explicit consent, as described in the Chef's Kiss section above. When enabled, Chef's Kiss can apply automated provisional restrictions as described above. You can request manual review or appeal through Help & Support. The specific feature disclosures above describe the information used and the limits of those restrictions.
Your Rights under GDPR
Where the GDPR applies to You, You have the right to:
- Request access to the Personal Data We hold about You.
- Request correction of inaccurate or incomplete Personal Data.
- Request erasure of Your Personal Data, subject to legal retention requirements.
- Object to or request restriction of Our processing of Your Personal Data.
- Receive a copy of Your Personal Data in a portable format.
- Withdraw consent at any time where processing is based on consent, without affecting the lawfulness of processing before withdrawal.
To exercise any of these rights, use any of the methods in the Contact Us section. We will respond within one month, extendable as the law allows for complex requests, and may need to verify Your identity before acting on a request. You also have the right to lodge a complaint with Your local data protection authority. Where We process Personal Data on behalf of a Business Customer, We will refer Your request to that customer and support its response.
CCPA/CPRA Privacy Notice (California Residents)
This section applies to California residents, to the extent the CCPA/CPRA applies to Qutzl LLC, and supplements the rest of this Privacy Policy. In the preceding twelve months We have collected the following categories of personal information, from You directly, from Your Devices, from Stores and sign-in providers, and from Business Customers: identifiers (such as name, email address, IP address, and account or Device identifiers); customer records (such as billing address, company, and payment confirmation details); commercial information (such as purchases and subscriptions); internet or network activity (such as pages visited and Application usage); approximate location derived from IP address; the Content You provide to Our Applications; and sensitive personal information, namely account login credentials and the Chef's Kiss diet and allergy preferences that may reveal health information or religious beliefs. The sources, purposes, and retention periods are described in the Collecting and Using Your Personal Data, Use of Your Personal Data, Chef's Kiss, and Retention sections above. We use sensitive personal information only to provide the Service You request and to secure Your Account, not to infer characteristics about You, and We do not knowingly sell or share the personal information of consumers under 16 years of age.
Selling and Sharing
We do not sell personal information in exchange for money. Where Our websites or Applications use third-party analytics and advertising services (such as Google AdSense, Google Analytics, and Google AdMob), that use may involve the disclosure of identifiers and internet activity information for cross-context behavioral advertising, which the CCPA/CPRA treats as "sharing." You have the right to opt out of that sharing.
Your Rights
As a California resident, You have the right to:
- Know the categories and specific pieces of personal information We have collected about You.
- Request deletion of Your personal information, subject to legal exceptions.
- Request correction of inaccurate personal information.
- Opt out of the sale or sharing of Your personal information.
- Not receive discriminatory treatment for exercising Your privacy rights.
How to Exercise Your Rights
Submit a request through Our online support desk at https://billing.qutzl.net/submitticket.php, or by any other method in the Contact Us section. We may need to verify Your identity before responding, and You may designate an authorized agent to submit requests on Your behalf. To opt out of sharing for cross-context behavioral advertising on Our websites, decline advertising cookies in Our cookie banner or through the Cookie settings link in the footer of every page; in Our Applications, use the device controls described in the Analytics and Advertising section above. Our websites also treat the Global Privacy Control (GPC) signal as a decision to decline analytics and advertising cookies for the browser that sends it.
Privacy Rights in Other U.S. States
Several other states, including Virginia, Colorado, Connecticut, Utah, Texas, and Oregon, have consumer privacy laws. Whether or not those laws apply to Qutzl LLC, We offer residents of every U.S. state the same rights:
- Confirm whether We process Your personal data, and access it.
- Correct inaccurate personal data.
- Delete personal data You provided or that We hold about You, subject to legal exceptions.
- Obtain a portable copy of Your personal data.
- Opt out of targeted advertising, the sale of personal data, and profiling that produces legal or similarly significant effects. We do not sell personal data. The Chef's Kiss section describes conditional automated provisional restrictions and how to request manual review or appeal.
We process sensitive data, such as Chef's Kiss diet and allergy preferences, only with Your consent or as needed to provide the feature You request. Submit requests by any method in the Contact Us section, and We will respond within 45 days, extendable once by 45 days where the law allows. If We decline Your request, You can appeal by replying to Our decision within 60 days. We will answer the appeal in writing within 60 days, and if You are not satisfied You may contact the attorney general of Your state.
Do Not Track and Global Privacy Control
We do not respond to legacy "Do Not Track" (DNT) browser signals, as no common industry standard for DNT was ever adopted. Our websites honor the Global Privacy Control (GPC) signal: a browser that sends it is treated as having declined analytics and advertising cookies, which also serves as a request to opt out of the sale or sharing of personal information for that browser, and You can still turn those cookies on through the Cookie settings link in the footer if You choose to.
Changes to this Privacy Policy
We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the "Last updated" date at the top. For material changes, We will make reasonable efforts to provide more prominent notice, such as an email or an in-app notice, before the change becomes effective. You are advised to review this Privacy Policy periodically; changes are effective when posted on this page unless the notice states a later date.
Contact Us
If You have any questions about this Privacy Policy or wish to exercise any of Your privacy rights, You can contact Us by any of these methods:
- Online Support Desk: https://billing.qutzl.net/submitticket.php
- Contact form: https://billing.qutzl.net/contact.php
- Mail: Qutzl LLC, Attn: Privacy, PO Box 154, Karthaus, PA 16845, United States of America