Privacy Policy

PilotSuite (“we”, “our”, or “us”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and share information when you use KitchenPilot, a product within the PilotSuite ecosystem, including the mobile app and this website.

1. Information We Collect

• Account Information: When you create an account, we collect your email address, display name, and authentication credentials through Firebase Authentication (email/password, Google, or Apple sign-in).
• App-Generated Content: Recipes, shopping lists, meal plans, community posts, and other content you create are stored securely in Google Firebase Firestore and are associated with your account.
• AI-Generated Content: When you use AI meal planning features, your meal type preferences are sent to OpenAI’s API to generate recipe suggestions. We do not send personal information to OpenAI.
• App usage: For signed-in mobile users, we record when a first recipe is saved and when the KitchenPilot Pro subscription screen is opened. These account-linked records include the action and time, iOS or Android platform, and an internal recipe ID for the first recipe. We store them in Firebase Firestore to measure onboarding and subscription interest. The records do not contain recipe text, photos, or location.
• Campaign attribution: When you arrive through a tagged marketing link, we may also record an attribution ID and campaign, creative, source, and medium labels alongside those usage records. We use a derived account identifier and campaign labels in PilotSuite’s marketing system to measure attributed app opens and signups.
• Images: Recipe images and community post photos you upload are stored securely in Firebase Storage.
• Location Data (optional): If you enable a Store Arrival Reminder, KitchenPilot collects the precise location you choose for that grocery store and securely syncs that saved store location to your account. On Android, KitchenPilot may access location in the background so the reminder can work when the app is closed or not in use.

2. How We Use Your Information

• To provide and maintain KitchenPilot’s core features (recipes, shopping lists, meal plans)
• To sync your data in real-time between the mobile app and website
• To generate AI-powered meal suggestions
• To enable community features (sharing posts, reactions, comments)
• To detect arrival at stores for which you explicitly enable Store Arrival Reminders and notify you when unchecked items remain
• To improve our app features and user experience
• To measure onboarding, subscription interest, and campaign performance
• To respond to inquiries and provide support
• To protect the security and stability of our systems

3. Store Arrival Reminders and Location

Store Arrival Reminders are optional and disabled by default. When you enable one for a grocery store, KitchenPilot uses an operating-system geofence around the saved store location to detect your arrival, including while the app is closed or not in use. The saved store coordinate is linked to your account and stored in Firebase so your chosen stores can sync across your devices.

KitchenPilot does not continuously track your movement, create or store a location history, or use location for advertising or analytics. Geofence entry is processed by your device solely to deliver a reminder when unchecked shopping-list items remain. You can disable the reminder for any store in KitchenPilot or revoke location access in your device settings. Deleting a store or your account removes its saved location according to our normal deletion process.

Alexa Connection (optional)

When you connect the KitchenPilot Alexa skill, Amazon sends KitchenPilot the item and list names recognized from your voice request, a request identifier, and a skill-specific Amazon user identifier. We store a connection record linked to your KitchenPilot account in Firebase, including that Amazon identifier after your first request, to authorize shopping-list access. We store added items in your existing lists and a request receipt to prevent duplicate additions. KitchenPilot does not receive your Amazon password or raw voice recordings.

KitchenPilot sends shopping-list names and item confirmations to Amazon so Alexa can answer your requests. Amazon processes your Alexa interactions under its own privacy policy. Alexa access is optional: you can disconnect it in KitchenPilot Account settings or at kitchenpilot.kitchen/alexa/link, and you can disable the skill in the Alexa app. Disconnecting in KitchenPilot revokes access and keeps your existing lists. Connection and request records are subject to the same account deletion process as your other KitchenPilot data.

Shopping list notifications (optional)

On compatible iPhone versions, adding groceries saves a random installation identifier with the latest addition in your account’s shopping list so the phone that added the items can be excluded from alerts. If you enable shopping list notifications, we also store this phone’s notification token, account ID, language, and registration timestamps in Firebase to send alerts to other opted-in phones signed into that same account. These identifiers are used for app functionality, not advertising or tracking.

Alerts can include item and shopping-list names, which Expo and Apple process to deliver the notification and which may appear on your lock screen. Delivery records expire after 24 hours and are removed by a periodic cleanup. Registrations expire after 45 days without refresh. Turning off shopping list notifications under Account, then Notifications or signing out unregisters that phone; deleting your account removes its registration and delivery records. You can also revoke notification permission in iOS Settings. Your saved shopping lists follow the normal content deletion process.

4. Data Storage and Security

Your data is stored in Google Firebase (Firestore, Authentication, and Storage), which provides enterprise-grade security including encryption at rest and in transit. We implement reasonable technical and administrative safeguards to protect your data from unauthorized access or disclosure.

5. Third-Party Services

• Firebase (Google): Authentication, database and image storage, including account-linked usage records and saved store locations
• RevenueCat: Subscription management and purchase status; when you use a tagged marketing link, we also attach its attribution ID and campaign labels to your subscriber record to measure subscription conversions
• OpenAI: AI meal plan generation (no personal data is shared)
• Vercel: Website and authenticated API hosting, including the endpoint that receives usage records from the mobile app

Amazon Alexa (optional): Voice request processing and spoken shopping-list confirmations when you connect the KitchenPilot skill.

We do not sell or rent your personal data to third parties.

6. Your Rights and Choices

• You can view, edit, or delete your recipes, shopping lists, and meal plans at any time
• You can update your display name and account preferences
• You can disable Store Arrival Reminders for individual stores and revoke location permission in your device settings
• You may request to access, export, or delete your personal data by contacting us at flightcrew@pilotsuite.design
• You can delete your account, which will remove all associated data

7. Children’s Privacy

KitchenPilot is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe we have inadvertently collected such data, please contact us to have it removed.

8. Updates

We may update this Privacy Policy occasionally to reflect changes in legal, operational, or technological practices. All updates will be posted to this page with an updated effective date.

9. Contact Us

If you have any questions about this Privacy Policy or your personal data, please contact us at flightcrew@pilotsuite.design.