Privacy Policy

1. Scope

CruiseKit (“we,” “us,” or “our”) operates cruisekit.app and the CruiseKit mobile app, including the MyDay and MyCrew experiences. This policy describes the information those services handle, why we use it, and the controls available to you.

2. Information we handle

Account and sign-in information

CruiseKit can use anonymous Firebase Authentication and, when you choose to link an account, Google or Apple sign-in. Depending on the method, Firebase Authentication and the identity provider may provide a user ID, name, email address, profile image, and provider identifier. Anonymous accounts generally have a user ID without a name or email address.

Saved cruise and MyDay information

Saved cruises, itinerary choices, cabin details you enter, schedule items, all-aboard entries, and related planning data may be associated with your account in Firebase Firestore or kept on your device, depending on the feature. Spend entries, budgets, drink-package tracking, and port-planning notes are planning records you enter; they are not bank, card, or payment-processor records and are currently stored locally on the device.

MyCrew information

If you use MyCrew, Firestore stores group details, membership, display names, messages, and manual status check-ins you intentionally share. The current app does not request or collect precise or approximate location and does not provide live or background location tracking. Other members of a group can see shared group content while they remain members. Account deletion also removes any legacy MyCrew location records from older builds.

Support and deal requests

When you contact us or request help with a cruise deal, we handle the name, email, phone number, note, cruise details, and other information you submit so we can respond. These requests may also create support emails through our email provider.

Usage, device, and diagnostic information

If you allow optional website analytics, Google Analytics may receive page and feature interactions, device/browser details, approximate region, and campaign information. The mobile app may use Firebase Analytics and Firebase Crashlytics for feature use, app/device details, crash reports, diagnostics, and identifiers used by those services. Do not include private information in free-text fields when reporting a problem.

3. Website analytics choice and local technologies

CruiseKit keeps Google Analytics off on this website unless you choose to allow it. We save only your analytics choice in local storage for this control. Essential browser storage used for authentication, security, saved preferences, or core site operation is not disabled by the analytics choice.

Change website analytics choice.

4. How we use information

• Authenticate accounts and restore account-linked data.
• Provide MyDay, saved cruise, MyCrew, and support features.
• Keep shared groups working for their remaining members.
• Respond to support and deal requests.
• Understand reliability and feature use, where analytics or diagnostics are enabled.
• Prevent abuse, investigate errors, and protect the service.

5. Service providers and sharing

We do not sell personal information and do not share it with third parties for their independent marketing. Providers process information for CruiseKit only as needed to deliver their services:

• Google Firebase for Authentication, Firestore, Analytics, and Crashlytics.
• Google Analytics for optional website usage measurement after consent.
• Google and Apple when you choose their sign-in methods.
• GitHub for static website hosting and deployment infrastructure.

Affiliate or booking sites receive information under their own policies only after you choose to follow an outbound link. We do not send them your MyDay or MyCrew records.

6. Payments and financial information

CruiseKit does not process cruise bookings, card payments, or bank transactions, and we do not collect card or bank account numbers. The Spend feature stores user-entered planning amounts locally so you can compare onboard spending with a budget; it is not connected to your payment card or cruise-line folio.

7. Retention and deletion

Account profile and account-linked Firestore data are generally kept while the account remains active. MyCrew messages and group data remain available to group members until removed through the product or account-deletion process. Local device data remains until you clear it in the app or remove the app.

You can request deletion from MyDay by CruiseKit even if you can no longer access the app. Authenticated deletion removes the account, account-linked Firestore records, MyCrew membership, check-in/location data, messages authored by the account, and requester-linked lead records. Shared groups remain for other members; an empty group owned only by the requester is deleted. See the account-deletion instructions.

In-app deletion begins immediately. Verified email requests are completed within 30 days. Limited security logs, provider backups, diagnostics, and prior support or deal-request emails may remain until their normal retention periods end. We do not use retained copies to recreate a deleted account.

8. Security and your choices

We use access controls and Firebase security rules to limit account and MyCrew data to authorized users. No internet service can promise absolute security. You can choose whether to link an identity provider, whether to share a manual MyCrew status, and whether to allow website analytics. Do not send passwords, sign-in codes, or card details to CruiseKit support.

9. Children

CruiseKit is not directed to children under 13, and we do not knowingly collect personal information from children under 13. A parent or guardian who believes a child submitted information can contact us to request review and deletion.

10. Changes and contact

We may update this policy as CruiseKit changes. We will update the date at the top when we make changes. Questions, privacy requests, and account-deletion support can be sent to info@cruisekit.app, or through the contact page.