1. Overview
ChefVault is the chef-side companion app for Holler. ChefVault is focused on recipes, prep workflow, meal planning, shopping lists, ServSafe and American Culinary Federation (ACF) certification tracking, compliance notes, and chef-side Holler handoff preparation.
Holler remains the point-of-sale, payment, and accounting system. This policy applies to the ChefVault mobile app and the public website at chefvault.app.
2. Information ChefVault Processes
Based on the current mobile app codebase, ChefVault may process the following data:
2.1 Account Information
- email address
- password
- optional display name
- account access token
- account refresh token
Purpose: sign-in, account registration, session refresh, and authenticated access to API-backed features.
2.2 User Content
- recipe content
- recipe image URLs or selected file references
- meal plans
- shopping lists
- certification records
- compliance notes
- Holler handoff content
Purpose: local app workflow and optional account-backed sync or backup when API features are configured.
2.3 Notification Data
- local scheduled reminder records for certification deadlines
Purpose: remind users about certification renewals and deadlines.
2.4 Imported or Exported Files
- Paprika import files
- recipe photo or screenshot imports through Files
- local kitchen backup export and restore files
- certification snapshot export and restore files
- Holler handoff package export and import files
3. What ChefVault Does Not Currently Use
Based on the current app code and release audit, ChefVault does not currently show evidence of using:
- location
- contacts
- Bluetooth
- health data
- advertising SDKs
- tracking SDKs
- analytics SDKs
- camera capture
- microphone recording
- speech-recognition capture
4. Local Storage
ChefVault stores some app state locally on the device, including:
- account session data
- recipes
- meal plans
- shopping lists
- app preferences
- certification state
- local Holler handoff drafts
This local state supports offline or device-first workflow where possible.
5. API-Backed Features
Some ChefVault features can connect to a configured ChefVault API endpoint.
- account sign-in and registration
- recipe sync
- backend recipe import
- account-backed certification backup
- Holler handoff submission and history
These features depend on a configured API endpoint and, in some cases, an authenticated account session.
6. Notifications
ChefVault may request notification permission only for certification reminder scheduling.
- certification renewals
- deadline reminders
7. External Links
ChefVault may open external links such as:
- recipe source URLs
- ServSafe reference pages
- ACF reference pages
8. Tracking and Advertising
Based on the current app codebase, ChefVault does not currently appear to track users across third-party apps or websites for advertising purposes.
This policy does not identify a current advertising or analytics SDK in the mobile app.
9. Data Sharing
Operational data may be transmitted to ChefVault backend services when API-backed features are used. Holler handoff data may also be delivered downstream when Holler relay or Holler submission features are configured.
This policy does not identify a current advertising-data sharing pipeline in the mobile app codebase.
10. Data Security
ChefVault uses account tokens and authenticated API requests for protected backend features. Final production security posture should be reviewed again before public launch whenever backend services, permissions, or third-party services change.
11. Changes to This Policy
This policy should be updated whenever the app adds or changes:
- data categories
- permissions
- third-party services
- sync behavior
- relay or downstream integration behavior
12. Contact
For privacy or support questions related to ChefVault, contact:
For app support details and release workflow notes, see the ChefVault support page.