Tide & Sky Privacy Policy

Last Updated: October 5, 2026

AO Inc. ("we," "us," or "our") establishes this Privacy Policy to explain how information is handled in the iOS application Tide & Sky (the "App").

1. Information Used by the App

1.1 Location Information

The App may access your device location to provide information relevant to your current area, including tides, sunrise and sunset, moonrise and moonset, weather, waves, and related information.

Location information is accessed only when you grant permission through iOS.

The App processes the latitude and longitude of your current location on your device to select the nearest port or relevant location. We do not transmit or store the raw latitude and longitude of your current location on our servers.

For a selected port or location, the following information may be transmitted to external services or our data delivery infrastructure as necessary to provide App functionality:

The latitude and longitude of the selected port or location may be sent to Apple WeatherKit to retrieve weather information.
A port ID identifying the selected port may be sent to our wave information delivery infrastructure to retrieve wave information.

A port ID identifies the selected port and is not the raw latitude or longitude of your current location.

We do not provide the precise latitude or longitude obtained by the App from your current location to Google AdMob, TelemetryDeck, or PostHog for advertising personalization or analytics purposes.

1.2 Notifications

The App may use iOS notification functionality to provide notifications related to tides, the sun, the moon, and other relevant information.

Notifications are provided only when you grant permission and may be disabled at any time through iOS Settings.

1.3 In-App Purchases and Subscriptions

The App uses Apple StoreKit 2 to provide in-app purchases or subscriptions through the App Store.

Payment processing is handled by Apple. We do not directly collect or store credit card numbers or other payment method information.

The App may use purchase status information provided by Apple to determine access to purchased features, verify subscription status, and restore purchases.

2. Advertising

The App may display advertisements in the free version or other applicable areas using Google AdMob and the Google Mobile Ads SDK provided by Google LLC.

For purposes including ad delivery, measurement, fraud prevention, and service improvement, the Google Mobile Ads SDK may collect or use information including:

IP address and approximate location inferred from an IP address or similar information
Device identifiers
Advertising identifiers, when available and when any required permission has been granted
Information about advertisements displayed and interactions with advertisements
Information about App launches and interactions
Crash logs, performance data, and other diagnostic information
Other information necessary for ad delivery and advertising measurement

Google's privacy policies and applicable terms govern Google's processing of this information.

Google and the advertising partners identified in the applicable consent interface may process information for these purposes. Non-personalized or limited ads do not mean that no information is processed. In updated versions, an active Premium subscription prevents banner display and new banner loads. Purchasing Premium does not turn off the separate usage-analytics setting.

3. Personalized Advertising and Tracking

Depending on your region, consent choices, and device settings, the App may display personalized advertisements.

If data is used in a manner that constitutes "tracking" as defined by Apple, the App uses Apple's App Tracking Transparency ("ATT") framework and requests your permission before such tracking occurs.

You can use the App without allowing tracking. If you decline or withdraw permission, Google's SDK applies the relevant restrictions, which may result in non-personalized or limited ads, or no ads. Advertising consent, iOS tracking permission and usage analytics are separate choices.

Updated versions use Google's UMP IDFA explanation, where applicable, before the iOS tracking-permission request. Earlier versions may request that permission directly through iOS. The explanation itself does not grant tracking permission.

You may change your tracking permission at any time through iOS Settings.

4. Advertising Consent in the EEA, United Kingdom, Switzerland, and Other Applicable Regions

In the European Economic Area ("EEA"), United Kingdom, Switzerland, and other regions where consent is required, the App uses Google User Messaging Platform ("UMP") to provide required information and obtain your choices regarding advertising and related data use.

Advertisements are delivered only to the extent permitted by your choices, applicable laws and regulations, and the consent status determined through Google UMP.

Updated versions refresh consent information for free users at launch, show Google's initial form only when required, and check whether ads may be requested before starting the advertising SDK and before new banner loads. Permission to request an ad does not by itself mean consent to personalized advertising.

Where Google UMP requires it, Settings > About provides "Ad privacy settings", or "Do Not Sell or Share My Personal Information" for applicable US privacy sections, opening Google's official form directly. US opt-out choices are conveyed through UMP's GPP signals for the advertising SDK to apply. In updated versions, a required withdrawal entry remains usable after upgrading to Premium, while ads remain disabled. Older versions may use a different label or entry behavior.

The App does not collect age or treat an unknown age as verified adulthood. Updated versions set Google's ad-content limit to G (general audience). This filter is not age verification.

5. Usage Analytics

The analytics service used by the App depends on the version installed on your device. Older versions use TelemetryDeck, provided by TelemetryDeck GmbH. Versions updated to the new analytics implementation use PostHog, provided by PostHog Inc. Users who continue to use an older version may therefore continue to send analytics to TelemetryDeck. We use these services to understand usage trends and improve the App's features and user experience, not for advertising targeting.

App-defined analytics events describe feature use through fixed event names and values, such as App opening, onboarding choices, location and notification permission status, use of Premium features, subscription plan selection, purchase and restore outcomes, the number of saved places, notification types, display and widget settings, review requests, and requests to prepare or present sharing controls. A sharing event does not confirm that you completed a share. Purchase events do not include payment details, receipts, or transaction identifiers. These events do not include names, email addresses, device coordinates, the ports or places you select or search for, notification content, or shared content.

5.1 Older Versions: TelemetryDeck

In addition to App-defined events, the TelemetryDeck SDK sends session and usage information and standard technical metadata. This includes App and SDK versions and build information; operating system, device model and architecture; screen size, scale and orientation; language, locale, region and time zone settings; appearance and accessibility settings such as text size and reduced motion; calendar and time information; and session counts, duration, first use and days of use.

The SDK hashes a device identifier (on iOS, the identifier for vendor, with a generated identifier as a fallback) before sending it. TelemetryDeck states that it salts and hashes the received identifier again on its servers. Identifiers and session information allow recurring usage to be counted; we do not describe all analytics information as fully anonymous. TelemetryDeck receives the source IP address as part of the network connection and states that it does not store IP addresses on its servers. See TelemetryDeck's privacy information.

Older versions initialize TelemetryDeck automatically and may not offer an in-app analytics switch. The PostHog control described below applies to versions with the new analytics implementation.

5.2 Updated Versions: PostHog

PostHog receives only App events on a fixed allowlist and their permitted values, together with App and SDK versions, build information, event time, a session identifier, a random identifier generated on your device for the installation, and App and development or production environment labels. Events and properties outside the allowlist are removed before sending. Unlike the older TelemetryDeck implementation, device model, operating system, locale and accessibility metadata are not included in the permitted event properties.

The random identifier does not contain your name or email address, but allows usage from the same installation to be counted over time. This information is not fully anonymous. The App does not identify users by name or email, create person profiles, or link these identifiers to an App account. Automatic screen and interaction collection, session replay, automatic error collection, surveys and analytics log sending are disabled.

The App's widgets and Watch app do not include our PostHog analytics SDK.

Analytics requests are sent to PostHog's EU endpoint, https://eu.i.posthog.com. IP-based location lookup is disabled for these events. PostHog still receives your IP address and connection information needed to handle network requests. EU hosting does not mean every aspect of the provider's processing or support takes place only in the EU. See PostHog's Privacy Policy.

Analytics are enabled by default when no saved preference exists. Enable "Don't share usage data" under Settings > About, or the equivalent label in your language, to opt out; disable it to resume. The saved choice survives restarts and is applied before analytics starts. The App's features remain available when analytics are disabled.

The deletion of unsent events described here applies only to versions using AnalyticsKit 0.1.1. It is not provided by the earlier AnalyticsKit 0.1.0 implementation or the older TelemetryDeck implementation. In versions using AnalyticsKit 0.1.1, opting out stops new collection and transmission, cancels pending analytics transfers and clears queued, unsent events. If queue cleanup cannot complete, analytics remain disabled until cleanup succeeds. Deleted events are not restored when you resume.

The earlier PostHog implementation using AnalyticsKit 0.1.0 stops new collection when you opt out, but does not guarantee removal of queued events or cancellation of requests already in progress. An updated policy does not change the behavior of an older installed version. Requests already received by a server cannot be recalled, and opting out does not delete information already sent to either analytics service.

Contact [email protected] to discuss questions or deletion requests. We review the information you provide to determine whether we can locate the relevant data and what action is available, and explain the result. Because analytics use installation identifiers, your name or email address alone may not allow us to match your events. The App does not currently display or automatically attach an analytics identifier to support inquiries. Provider retention and deletion terms also apply; we do not promise a fixed deletion date for analytics already sent.

Information processed by advertising SDKs, and crash and diagnostic information that Apple may provide according to your settings, are handled separately from the usage analytics described above.

6. Apple Services

The App may use the following services and frameworks provided by Apple as necessary to provide App functionality:

StoreKit
WeatherKit
Location-related functionality such as Core Location
Notification-related functionality such as User Notifications
App Tracking Transparency
Diagnostic and crash information provided through the App Store and iOS

When retrieving weather information, the latitude and longitude of the port or location selected on your device are sent to Apple WeatherKit.

Apple's privacy policies and applicable terms govern Apple's processing of information.

7. Cloudflare

The App may use Cloudflare R2 and other services provided by Cloudflare, Inc. as infrastructure for delivering wave information and other data required by the App.

When retrieving wave information, communications may include a port ID identifying the selected port.

In the course of providing these services, Cloudflare may process IP addresses and other technical network information associated with communications.

Cloudflare's privacy policies and applicable terms govern Cloudflare's processing of information.

8. Information Stored by Us

Saved ports, the current port selection, notification rules, display and widget settings, and cached weather or wave information are stored on your device. Some data is shared with the App's widgets through an on-device App Group. The App does not provide iCloud synchronization for these records. Depending on your device's backup settings, local App data may be included in Apple backups.

When you use the companion Watch app, Apple WatchConnectivity transfers selected port IDs, the selected index, language, display and widget preferences, Premium access status and update timestamps between your paired devices. The Watch app keeps its own local copy; deleting the iPhone App alone does not guarantee removal of that copy.

We do not store the raw latitude and longitude obtained by the App from your current location on our servers.

When wave or similar information is requested, a port ID identifying the selected port may be transmitted to our delivery infrastructure. We do not use this information for the purpose of identifying individual users.

The App does not provide a user account creation feature or use your name or email address as an analytics identifier. If you contact support, we receive the sender address and information you choose to include and use them to respond. We do not automatically link support inquiries to analytics events.

If we later introduce user accounts, cloud synchronization, or other functionality that stores user information on our servers, we will update this Privacy Policy as appropriate.

9. Disclosure to Third Parties

We do not sell personal information collected from users to third parties without their consent, except as required by law.

Information may, however, be processed by service providers identified in this Privacy Policy, including Apple, Google, TelemetryDeck, PostHog, and Cloudflare, to the extent necessary to provide the App.

10. Your Controls

You may manage the following, where available, through iOS Settings or settings provided within the App:

Location access
Notifications
Tracking permission under App Tracking Transparency
Advertising privacy settings and consent choices
Usage analytics opt-out under Settings > About, in versions using PostHog

You can remove saved ports and notification rules or change settings within the App. Deleting the App removes its local App data; offloading the App while retaining its data and copies in backups are separate. Deleting the App does not delete analytics already sent, cancel an App Store subscription or guarantee deletion of data shared with a remaining extension. Manage Apple backups and subscriptions separately through Apple's controls.

11. Children's Privacy

The App is intended for a general audience and is not specifically designed or directed toward children.

We do not intentionally seek to collect personal information from children through the App.

12. Security

We endeavor to implement reasonable safeguards designed to reduce the risk of unauthorized access, disclosure, alteration, or other misuse of information handled through the App.

13. Changes to This Privacy Policy

We may update this Privacy Policy as necessary due to changes in App functionality, external services, laws, regulations, or other circumstances.

If we make material changes, we will provide notice through this page, within the App, or by another appropriate method.

14. Contact

For questions regarding this Privacy Policy or the handling of information in the App, please contact:

AO Inc.
Email: [email protected]

15. Operator

AO Inc.