Privacy Policy

Effective May 4, 2026. Last updated September 27, 2026

1. Summary

This policy describes what information CruiseSignal collects, why, who we share it with, and how you can exercise your rights. We try to collect the minimum we need to monitor cruise prices and notify you about price drops on bookings you've recorded. We do not sell your personal information for money. The iOS app reports a few app events to Meta to measure our advertising, which some U.S. state laws treat as "sharing"; section 16 explains what is sent and how to opt out.

2. Who is responsible for your data

The data controller is Overclock Studio ("CruiseSignal", "we", "us"). Contact:

Email: support@cruisesignal.app

For users in the United Kingdom or the European Economic Area, please see section 19 for our representative under Article 27 of the UK GDPR and EU GDPR if and when we appoint one.

3. Information we collect

3.1 Account information

Email address (required to sign in via one-time code).
Name (provided by Sign in with Apple, or by you).
Apple user identifier (a stable opaque ID returned by Apple if you use Sign in with Apple) and the OAuth tokens issued by Apple to verify your sign-in. We do not see or receive your Apple ID password.
Account timestamps (created, updated, last sign-in, deleted-at).

3.2 Booking and price-watch information you enter

Cruise line, ship, sail date, sailing length, region.
Reservation / booking number.
Cabin class and category, number of adults, number of children.
Fare type, rate code, deposit type (refundable / non-refundable), guarantee flag, paid-in-full flag, booked-at date.
Price you paid, currency.
Booking confirmations you choose to scan (screenshots, photos, PDF pages, or pasted text), which can include passenger names and other details printed on the confirmation. We use them only to fill in your booking and do not keep the files.

The reservation number is treated as confidential — it is stored only to identify your booking when you reference it (we do not call the cruise line or file claims on your behalf).

3.3 Subscription and entitlement

Whether you have an active subscription, where it was bought (App Store or web), the product identifier, the entitlement period, and a stable user identifier we share with our subscription provider (Superwall) to attribute purchases to your account.
We share your account identifier, email address, and name with Superwall in the iOS app and the web app, and your email address is passed to web checkout so the purchase is tied to your account.
We do not receive or store your payment-card information, your Apple ID password, or your Apple Pay token. Apple processes App Store transactions; Stripe processes web transactions.

3.4 Device and technical information

Device model, operating-system version, app version, language and locale, time zone, and a stable installation identifier.
Push-notification permissions and, when enabled, tokens issued by Apple Push Notification service.
On iOS, your App Tracking Transparency choice and, only if you allow tracking, your device's advertising identifier (IDFA).
IP address (used by our auth and edge layers for rate-limiting and abuse prevention; see section 3.5).
User-agent string from any web requests.
Diagnostic and crash data, log lines, and anonymous performance traces.

3.5 Authentication and security data

Session tokens and the IP address and user-agent of the device that created the session (used to detect abuse and to log you out of compromised sessions).
One-time email codes (deleted after they expire or are used).

3.6 Product-analytics events

Pseudonymous events about how you use the app (for example: "started onboarding", "added booking", "viewed paywall", "tapped notification"). Events include a stable user identifier, a device identifier, the event name, and contextual properties needed to interpret it (for example, the screen name).
We try to avoid putting free-text or sensitive content into analytics events. We do not put your reservation number, payment information, or password-equivalent secrets in analytics events.

3.7 Communications with us

If you email support@cruisesignal.app, we receive your email address, the contents of the message, and any attachments.
If you use the in-app support chat, we receive your account identifier, email address, name, and the messages you send.

3.8 Waitlists

If you join a cruise line's waitlist, we store your email address or account identifier and the cruise line, so we can tell you when we support it.

3.9 What we do not collect

We do not collect precise location, contacts, your photo library, microphone, health, or biometric data. A photo or screenshot reaches us only when you choose to scan a booking confirmation (section 3.2).

4. Where we get it

Directly from you (account creation, booking entry, support emails).
From your device (technical and diagnostic data).
From Apple (the user identifier, name, and email returned by Sign in with Apple, plus subscription receipts and entitlement events).
From Superwall (subscription state for your account, including web purchases processed by Stripe, and paywall events).
From cruise-line public listings (sailing and pricing data — this is not personal data, but we associate it with your booking when monitoring).

5. How we use it

To create and authenticate your account.
To monitor cruise pricing on the sailings you've recorded and to send price-drop and policy-deadline notifications.
To provide, maintain, secure, and improve the Service (including debugging, reliability monitoring, and fraud prevention).
To process and validate your subscription via Apple, Superwall, and Stripe.
To respond to your support requests.
To measure how well our advertising works (section 16).
To send transactional messages (sign-in codes, account messages, alerts you have enabled).
To enforce our Terms and protect the rights, safety, and property of CruiseSignal, our users, and the public.
To comply with legal obligations.

We do not use your data to make automated decisions that produce legal or similarly significant effects on you.

6. Legal bases (UK / EEA users)

If UK or EU GDPR applies to you, our legal bases are:

Contract (Article 6(1)(b)): to provide the Service you signed up for, including monitoring your bookings and processing your subscription.
Legitimate interests (Article 6(1)(f)): to keep the Service secure, prevent abuse, debug errors, measure reliability and usage at an aggregate level, and improve features. You can object at any time (see section 12).
Consent (Article 6(1)(a)): for push notifications, advertising measurement with your device's advertising identifier when you allow tracking in the iOS app, and any optional analytics or communications that require consent in your jurisdiction. You can withdraw consent at any time without affecting the lawfulness of processing carried out before the withdrawal.
Legal obligation (Article 6(1)(c)): to comply with applicable laws, court orders, and regulatory requests.

We share personal information with the categories of recipients listed in section 8 ("sub-processors and service providers"), and additionally:

Compliance and law enforcement. We may disclose information when we believe in good faith it is required by law, legal process, or government request, or to investigate or prevent a violation of our Terms, fraud, or a threat to safety.
Business transfers. If we are involved in a merger, acquisition, financing, reorganization, or sale of assets, your information may be transferred to the successor entity, subject to confidentiality and continued protection consistent with this policy.
With your direction. If you ask us to share information (for example, to a travel agent), we will.

We do not sell personal information for money. The advertising measurement described in section 16 may count as "sharing" under some U.S. state laws.

8. Sub-processors and service providers

We use the following service providers to operate CruiseSignal. They process personal information on our instructions, under written contracts that require them to protect it.

Apple Inc. — App Store distribution, Sign in with Apple, in-app purchase processing, Apple Push Notification service.
Superwall, Inc. — paywall delivery, web checkout, subscription status, and conversion analytics.
Stripe, Inc. — payment processing for subscriptions bought in the web app.
Mixpanel, Inc. — pseudonymous product-analytics events from the iOS app and the web app.
PostHog, Inc. — pseudonymous product-analytics events and feature flags from the iOS app and the web app.
Cloudflare, Inc. — Workers compute, edge delivery, Hyperdrive, KV (session cache), Email Service for sign-in codes and price-drop alert emails, and cookie-free Web Analytics on our website.
BuzzKit — delivers push notifications in the iOS app and receives your account identifier, device token, and app events.
OneSignal, Inc. — delivers push notifications to older versions of the iOS app.
Meta Platforms, Inc. — measures our advertising from app events sent by the iOS app (section 16).
Featurebase — runs the in-app support chat and receives your account identifier, email address, name, and the messages you send.
Slack Technologies, LLC — receives internal alerts about price drops we find, including your email address, account identifier, and booking prices, so our team can check that alerts are correct.
Google LLC (Gemini API) — reads the images and the text of a booking confirmation you scan to fill in your booking details. We do not keep the files.
TypeSafe — reads the text of a booking confirmation to fill in your booking details.
Axiom, Inc. — log and OpenTelemetry trace ingestion (used for debugging and reliability).
Our PostgreSQL database provider — primary application data store.

A current list of sub-processors and any material changes will be kept on this page. If we add a new sub-processor that materially expands the categories of data processed about you, we will update this section before the change takes effect for your account.

9. International data transfers

CruiseSignal is operated from the United States, and several of our sub-processors are also based in the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States and other countries with data-protection laws different from those in your country.

Where required, we rely on the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, and other lawful transfer mechanisms with our sub-processors. You can request a copy of the safeguards we use by emailing support@cruisesignal.app.

10. How long we keep it

Account data — kept while your account is active. If you delete your account, we deactivate it promptly and stop active use of the account for the Service. We then delete or anonymize personal information when it is no longer needed for the purposes below and as required by applicable law.
Booking and price-watch data — kept while the sailing is active and for up to 12 months after the sail date so you can reference history and to allow late-arriving claim adjustments.
Subscription receipts and billing records — kept for at least 7 years for tax, audit, and dispute purposes (or longer if required by law).
Authentication logs and security events — kept for up to 90 days for abuse prevention.
Application logs and traces — typically kept for 30–90 days, depending on the system, for debugging and reliability.
One-time email codes — deleted on use or expiry, whichever is sooner.
Backups — encrypted and rotated; deletions in production propagate to backups within the backup-rotation window.
Support correspondence — kept for up to 3 years after the last interaction.

We may retain information for longer where required by law, to enforce our Terms, to defend legal claims, or to investigate fraud or abuse.

11. How we protect it

We use technical and organizational measures designed to protect your information, including encryption in transit (TLS), encryption at rest where supported by the underlying provider, restricted access to production systems, OAuth-based access from the app, short-lived bearer tokens with session-cache invalidation, environment isolation between development and production, and routine vulnerability and dependency review.

No system is perfectly secure. If we learn of a security incident affecting your personal information, we will notify you and any regulator as required by law.

12. Your rights and choices

Depending on where you live, you may have rights to:

Access the personal information we hold about you.
Correct inaccurate information.
Delete personal information.
Port a copy of your information in a structured, commonly used format.
Object to or restrict certain processing, including processing based on legitimate interests.
Withdraw consent at any time, where processing is based on consent.
Lodge a complaint with your local supervisory authority (in the UK, the Information Commissioner's Office at ico.org.uk).

To exercise these rights, email support@cruisesignal.app or use the in-app account-deletion option. We may need to verify your identity before completing your request. We will respond within the timeframe required by applicable law (typically 30–45 days), and we will not discriminate against you for exercising a right.

13. U.S. state-specific rights

Residents of California, Virginia, Colorado, Connecticut, Utah, and other U.S. states with comprehensive privacy laws have specific rights, including the right to know what personal information is collected, the right to correct, delete, port, and to opt out of "sale" or "sharing" of personal information. We do not sell personal information. The advertising measurement in the iOS app (section 16) may be "sharing" under these laws. To opt out, choose Ask App Not to Track, or turn off tracking for CruiseSignal in Settings → Privacy & Security → Tracking on your iPhone, or email us and we will stop sending events linked to your account.

13.1 Categories of personal information (CCPA/CPRA)

In the past 12 months we have collected:

Identifiers (name, email, account IDs, device IDs, IP, and the iOS advertising identifier if you allow tracking).
Commercial information (subscription state, purchase history via Apple or Stripe, and the cruise bookings and prices you record).
Audio, electronic, or visual information (booking confirmation images you choose to scan, which we do not keep).
Internet or other electronic network activity (app interactions, diagnostics).
Geolocation only at the country/region level inferred from IP — no precise location.
Inferences drawn from the above to provide and improve the Service.

We collect these for the purposes described in section 5. We have not "sold" personal information in the preceding 12 months. We may have "shared" identifiers and app activity with Meta for advertising measurement, as described in section 16.

13.2 Sensitive personal information

We do not collect or use "sensitive personal information" as defined by the California Privacy Rights Act, except for the limited purposes expressly permitted without an opt-out (for example, account authentication and security).

13.3 Authorized agents

California residents may use an authorized agent. We will require written authorization and may verify directly with you.

13.4 Shine the Light

California Civil Code §1798.83 permits residents to request information about disclosures to third parties for direct-marketing purposes. We do not share personal information with third parties for their direct marketing.

14. Children

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If we learn that we have collected personal information from a child under 13, we will delete it promptly. If you believe a child has provided us information, contact us at support@cruisesignal.app.

15. Push notifications and email

With your permission, we send push notifications about price drops, policy deadlines, account events, and other Service-related messages. You can disable them at any time in your device settings. If you use CruiseSignal only on the web, we send price-drop alerts by email instead; you can turn them off with the Email Notifications switch in Settings or the link at the bottom of any alert email. Transactional emails (sign-in codes, account messages) are required to use the Service and cannot be disabled while you have an account; closing your account stops them.

16. Analytics, advertising measurement, and cookies

We use Mixpanel and PostHog for pseudonymous product analytics in the iOS app and the web app.

The iOS app includes the Meta SDK to measure our advertising. It sends a few app events to Meta, such as completing sign-up, viewing the subscription screen, and subscribing. The app asks for App Tracking Transparency permission. If you allow tracking, these events include your device's advertising identifier (IDFA). If you do not, Meta receives only aggregated measurement data that is not linked to your device. You can change your choice at any time in Settings → Privacy & Security → Tracking. The app also reports install and subscription milestones to Apple's SKAdNetwork, which does not identify you. The web app and our website do not include the Meta SDK.

The web app sets one httpOnly session cookie that keeps you signed in. Mixpanel, PostHog, Superwall, and the support chat store identifiers in your browser's cookies and local storage. Our website uses Cloudflare Web Analytics, which sets no cookies.

17. Do Not Track and Global Privacy Control

Our website at cruisesignal.app is a marketing site that does not set advertising cookies and does not track you across sites, and the web app does not include advertising SDKs. Browsers' "Do Not Track" and "Global Privacy Control" signals are honored to the extent applicable: our website and web app do not sell or share personal information for cross-context behavioral advertising, so there is nothing for these signals to opt out of there. In the iOS app, your App Tracking Transparency choice controls advertising measurement (section 16).

18. Changes to this Policy

We may update this Policy from time to time. If a change is material, we will give reasonable advance notice (in-app or by email) and, where required by law, obtain consent. The "Last updated" date at the top of this page reflects the date of the most recent change.

19. Contact

Privacy questions, requests under section 12 or 13, and complaints about how we handle personal information:

Email: support@cruisesignal.app
Controller: Overclock Studio
EU/UK Article 27 representative: not appointed unless required by applicable law.

If you are in the EU/EEA, the UK, or Switzerland and we have not resolved your concern to your satisfaction, you may contact your local data-protection authority.

Questions? Email support@cruisesignal.app.