Updated August 17, 2026 · Covers Garritson Works LLC websites, messaging services, and Pocket Chef
The short version: We collect only what is needed to operate our websites, respond to service inquiries, and make our apps work. We do not sell your data, and mobile information is never shared with third parties or affiliates for marketing or promotional purposes.
Garritson Works LLC is a family-run Utah limited liability company founded by Ryan Garritson in Salt Lake County. We build mobile software and operate local-service information and connection websites, including the Website Landlord properties that let consumers call or text about a service need.
Account information. When you create an account, we collect your email address and display name through Firebase Authentication (operated by Google). This lets you sign in and sync data across your devices. You can also sign in with Apple, in which case Apple controls what information is shared with us.
Website and service inquiries. When you call or text a phone number shown on one of our local-service websites, we receive the phone number used to contact us, the destination number/site, call status, and any text or voicemail content you choose to provide. We use this information only to respond to your inquiry, understand the service requested, help with scheduling, and connect you with an appropriate local provider.
Call and messaging records. We use Twilio to provide local phone numbers and process calls, text messages, and voicemail. Missed-call, voicemail, and inbound-text events may be stored in our Cloudflare infrastructure and sent to our private operator notification channel. Live calls are not recorded. Voicemail may be recorded and transcribed when a caller chooses to leave a message.
Location. Pocket Chef may request your location to find nearby grocery stores and retailer availability. The app uses the location for the store search you request. We do not retain your precise location in our own databases. Google services used for sign-in and app delivery may also derive a general location from an IP address as described in Google's privacy disclosures.
Grocery store credentials. When you connect your Kroger-family store account (Smith's, Ralphs, Fred Meyer, etc.), authentication is handled via Kroger's OAuth flow. We store an access token and refresh token on your device so the app can add items to your online cart. These tokens are never sent to our servers.
Voice and audio. Pocket Chef offers voice input for recipe dictation, audio-file import, voice search, and pantry walkthroughs. Apple's Speech framework converts audio to text; depending on device, language, availability, and the recognition request, Apple may process speech on the device or on Apple's servers. The resulting text may be sent through our Cloudflare proxy to the Anthropic Claude API to structure the recipe or grocery items you requested. Audio itself is not sent to Anthropic. If Save Voice Recordings is enabled, the recording is kept with the recipe for playback and may be stored in Firebase Cloud Storage so it remains available across the user's devices. Turning the setting off before saving keeps only the transcript. Deleting the recipe also requests deletion of its stored recording.
Photos. Pocket Chef lets you photograph cookbook pages and recipe cards. Photos are sent to the Anthropic Claude API for text extraction and recipe parsing and are handled under Anthropic's applicable API privacy and retention terms.
Share imports and social recipe links. When you choose Pocket Chef from another app's Share sheet, Pocket Chef collects only the link, text, images, or user-owned audio that you selected to share. Before the first cloud-processed Share import, Pocket Chef asks for permission and explains the processing; you can turn that permission off in Settings. The selected content is sent through our Cloudflare Worker. Anthropic may structure the recipe, and—when automatic social-link processing is enabled—ScrapeCreators, SocialKit, or Supadata may retrieve public recipe details associated with the shared link. Pocket Chef does not send the rest of your recipe library. Local raw capture files are deleted after secure request handoff; abandoned staging files are removed after one hour and abandoned raw inbox files after 24 hours. A successful public-link import may be cached as a validated structured recipe with its source attribution for a rolling 90 days so other users do not require repeated provider processing. User-supplied images, text, and audio are not placed in that shared cache. Raw social media and raw transcripts are not placed in Pocket Chef's long-lived cache.
Recipe and meal plan data. Your recipes, meal plans, grocery information, and cooking history are stored in Firebase Firestore (operated by Google) so they sync across your devices. Recipe photos and saved voice recordings may be stored in Firebase Cloud Storage. This data is associated with the app identity or account used for sync and is not published publicly.
Apple Reminders. Pocket Chef can sync grocery information with an Apple Reminders list on your device. This data stays within Apple's ecosystem and is governed by Apple's privacy policy.
Crash diagnostics. We use Firebase Crashlytics (Google) to receive automatic crash reports so we can find and fix bugs. A crash report includes device model, operating system, app version, and a diagnostic stack trace. Crash reports are not linked to your account or identity, and they never include your recipes, lists, photos, voice input, or message content. You can read Google's handling at Firebase Privacy & Security.
We use the following third-party services to operate the apps:
Website visitors may initiate a conversation by tapping a Text us link or by texting the local number published on a Website Landlord site. We send conversational replies only about that consumer-initiated request, such as answering questions, gathering the service address or job details, and helping schedule an estimate. We do not use these inquiries for bulk or promotional messaging.
Message frequency varies with the conversation. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent to receive text messages is not a condition of purchase. We retain message records only as reasonably needed to operate, document, secure, and improve the inquiry service.
Account and recipe data is stored in Google Cloud (Firebase) data centers in the United States. Data is encrypted in transit (TLS) and at rest. Kroger OAuth tokens are stored locally on your device in the iOS Keychain.
Our apps are rated 4+ and are safe for family use. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us so we can delete it.
You can delete your account and associated data at any time from the Settings screen. This permanently removes the account from Firebase Authentication and requests deletion of its recipes, meal plans, grocery data, cooking history, recipe photos, and saved voice recordings from Firebase. If you need help, email us and we will process your request within 30 days.
If we make material changes, we will update this page and note the new effective date at the top. For significant changes, we may also notify you inside the app.
Questions or requests? Reach out anytime:
Website or messaging questions: ryan@garritsonworks.com
App support: support@garritsonapps.com