Sprigge is a cooking and recipe app developed by Marcin Szetela. This Privacy Policy explains what information Sprigge processes, how it is used, and what choices you have.
Information Stored on Your Device
Sprigge stores your recipes, ingredients, cooking steps, app preferences, recent searches, cooking sessions, cook logs, and saved dish photos locally on your device. This information is used to provide the core app experience.
If you delete the app, locally stored app data may be removed from your device. If you export a backup, the exported file is controlled by you.
Waitlist Emails
If you join the Sprigge waitlist or beta invite list, we collect the email address you submit. We use it to send a TestFlight invite and one launch note. We also store the date of signup, the page referrer, browser user agent, consent text version, and unsubscribe status so we can operate the list reliably and honor opt-outs.
Waitlist emails are stored in Cloudflare Workers KV and sent through Resend, which may use Amazon SES infrastructure for delivery. When someone joins the waitlist, Sprigge also sends an admin notification to mars.marcin@gmail.com.
Waitlist emails include an unsubscribe link for future launch/update emails. You can also contact us to request removal of your waitlist email.
Information Sent to Sprigge Services
Some features use Sprigge's backend services and AI processing. When you use recipe import, recipe generation, screenshot import, link import, the cooking assistant, or in-app feedback, the information needed for that request may be sent to Sprigge's servers.
This may include:
- recipe text you enter,
- recipe URLs or other links you provide,
- screenshots or images you choose for recipe import,
- recipe content and cooking context needed by the assistant,
- app language and formatting preferences needed to return useful results.
Sprigge uses this information to provide the requested feature, improve reliability, prevent abuse, and protect the service from excessive automated use.
If you send feedback from within the app, the message you write, the selected feedback type, and basic technical context such as app version, build number, language, and platform may be sent to Sprigge so we can read and respond to bug reports or feature ideas. Feedback content is not used as analytics data.
If you use paid features, Sprigge may process purchase status, product identifiers, and purchase-related identifiers through Apple and our purchase management provider so we can unlock Pro features and restore purchases.
Photos and Screenshots
Sprigge may ask for access to your photo library when you choose a screenshot or image for recipe import, or when you add a photo to your cook log. Sprigge may ask for camera access when you choose to take a photo of a finished dish.
Cook log photos are stored on your device. Screenshots used for recipe import may be sent to Sprigge's backend and AI providers to extract recipe information.
Link and post import
When you use link import, Sprigge may process the URL you provide and recipe-related text extracted from the page.
For some third-party links, including links to posts or pages on third-party websites, apps, or social platforms, Sprigge may open the link in an in-app viewer. Sprigge does not import content automatically. If you tap Import, Sprigge may extract recipe-related text and standard page metadata from the page or post to help create a recipe.
Sprigge does not intentionally collect your browsing history, social media credentials, private messages, followers, likes, comments, or other social account data. Sprigge does not download videos, audio, or media from social platforms.
Third-party pages opened in the in-app viewer are provided by the relevant third-party service and may be subject to that service's own terms and privacy policy.
If you choose to process imported content with Smart Import, the extracted text, source URL, recipe content, and your edits may be sent to Sprigge's backend and our AI provider, currently Anthropic, to generate the structured recipe.
Voice and speech recognition
Sprigge may request microphone and speech recognition permissions for hands-free cooking features.
When enabled, voice controls can be used to navigate cooking steps, repeat a step, check timers, open ingredients or notes, dictate a cooking note, or ask the cooking assistant a spoken question.
Sprigge does not record or store raw audio. Speech recognition is used to convert your speech into text so Sprigge can run the requested cooking action.
Speech recognition may be provided by the operating system or platform speech services.
If you ask the cooking assistant a spoken question, the resulting text transcript, recipe context, and related cooking context may be sent to Sprigge's backend and our AI provider, currently Anthropic, to generate a response.
Notifications
Sprigge may ask for notification permission to support cooking timers. Timer notifications are used only to notify you about timers you start while cooking.
Third-Party Services
Sprigge may use third-party service providers to operate app features, including cloud hosting, waitlist storage, email delivery, AI processing, URL/link import, abuse prevention, purchase management, and Apple TestFlight beta distribution.
These providers process information only as needed to provide their services to Sprigge.
AI Features
When you use Smart Import or other AI-assisted recipe features, the recipe content you choose to provide may be sent through our backend to a third-party AI service provider solely to convert it into a structured recipe or provide the requested cooking assistance.
Our current AI service provider is Anthropic. We do not use this content to identify you, and we do not store it on our servers after the request is completed, except for temporary processing, security, debugging, or abuse-prevention purposes where necessary.
Anthropic states that, by default, inputs and outputs submitted through its commercial API are not used to train its models unless a customer explicitly opts in or provides feedback for that purpose.
Analytics and Diagnostics
Sprigge collects limited anonymous usage analytics to understand whether the app works well during beta testing and after launch. This helps us improve reliability, understand feature usage, debug failed flows, and prioritize product improvements.
Analytics may include product interaction events such as:
- app opens and onboarding completion,
- recipe import started, succeeded, or failed,
- share-sheet payload received, recipe saved, and cooking mode started or completed,
- timer started and voice mode enabled,
- feedback opened or submitted,
- backup exported or imported.
For these events, Sprigge may include coarse metadata such as app version, build number, platform, app language, import source type, error code, and broad count or duration buckets.
Sprigge stores a random anonymous install ID locally on the device to estimate unique installs. This ID is not an advertising identifier, is not used for tracking across apps or websites, and is not linked to a user account.
We use Meta/Facebook SDK to measure app advertising performance and basic app events, such as app launch. We do not send recipe text, ingredients, photos, screenshots, email addresses, names, or other user-generated recipe content to Meta through this integration. We do not collect the iOS advertising identifier (IDFA) or ask for App Tracking Transparency permission in this version.
Sprigge does not collect recipe text, prompts, full URLs, cookbook names, photos, screenshots, cooking notes, ingredients, email address, or personal content as analytics data.
Analytics data is processed using our service providers, including Vercel for backend hosting and Upstash Redis for aggregated analytics storage. Aggregated analytics counters are retained for up to about 90 days.
Outside the Meta/Facebook SDK described above, Sprigge does not use IDFA, App Tracking Transparency tracking, cross-app tracking, session replay, autocapture, data brokers, or other external analytics SDKs. Sprigge does not use analytics data to track users across apps or websites and does not share recipe content with advertisers or data brokers.
During TestFlight testing, Apple may collect diagnostic, crash, installation, session, and feedback information according to Apple's TestFlight and privacy terms.
Data Retention
Sprigge keeps local app data on your device until you delete it or delete the app. Backend request data may be retained temporarily in logs or infrastructure systems for debugging, reliability, abuse prevention, and security.
We aim to keep server-side operational data only as long as reasonably necessary for these purposes.
Waitlist email records are kept until the beta/launch communication purpose is complete, until you unsubscribe from future updates, or until you ask us to delete your waitlist email, unless a longer retention period is needed for security, abuse prevention, or legal compliance.
Your Choices
You can:
- choose not to grant camera, photo library, microphone, speech recognition, or notification permissions,
- unsubscribe from future waitlist launch/update emails using the link in the email,
- delete recipes, cook logs, photos, and preferences from the app where supported,
- delete the app to remove local app data from your device,
- contact us with privacy questions or deletion requests related to backend processing.
Children's Privacy
Sprigge is not intended for children under 13. We do not knowingly collect personal information from children.
Security
We use reasonable technical and organizational measures to protect information processed by Sprigge. However, no method of transmission or storage is completely secure.
Changes to This Policy
We may update this Privacy Policy as Sprigge evolves. If we make material changes, we will update the "Last updated" date above.
Contact
If you have questions about this Privacy Policy or Sprigge's data practices, contact:
Marcin Szetela
hello@sprigge.app