Privacy Policy for Visit NYC, by BLOO LLC

Effective Date: October 2, 2026

BLOO LLC ("we," "our," or "us") operates Visit NYC (the "App"). This Privacy Policy explains how information is processed when you use the App, stream or download videos, make purchases, or submit a destination suggestion through "Got Suggestions?"

1. Information We Collect

1.1 Content Delivery and Network Requests

When the App requests online content or submits a suggestion, your device communicates with our servers or service providers, including content delivery services and Apple's download infrastructure. Your IP address and technical request information are processed to establish the connection, deliver the requested service, and support reliability and security.

Hosting and content delivery providers may maintain ordinary access or security logs containing information such as an IP address, request time, requested resource, response status, and client software information. These logs are separate from our suggestion database and App analytics. We do not use this information for advertising.

1.2 Usage Analytics and Diagnostics (TelemetryDeck)

We use TelemetryDeck, provided by TelemetryDeck GmbH in Germany, to understand App usage and improve functionality, reliability, and performance. Analytics operate during ordinary App use, including visits where you only browse and do not play, download, purchase, or submit anything.

Depending on the feature used, analytics events may include:

• App launches, session activity, and changes between active and background states.
• Tabs, filters, and video details viewed, and actions requesting the blog or an App Store review prompt.
• Video identifiers and titles; playback requests, starts, pauses, buffering, completion, exits, errors, and viewing duration where available.
• Video-window opening, closing, resizing, playback controls, mute changes, and responses to performance warnings.
• Download requests, progress and status changes, completion, cancellation, retries, deletion, failures, file sizes, and elapsed times.
• Purchase offers, product identifiers, purchase attempts and outcomes, entitlement changes, and restoration attempts and outcomes.
• Suggestion-form actions and outcomes described in Section 1.4.
• App version and build, operating system, device model, language and region settings, time zone, distribution environment, and SDK session and usage measurements.
• Diagnostic context such as error codes and filtered error descriptions, network availability and connection type, available storage, low-power mode, thermal state, and device uptime.

The App configures the same analytics user value for everyone; it does not supply a unique account or installation identifier as that user value. Analytics still include SDK session identifiers and randomly generated identifiers that connect events from a particular download attempt, playback session, or suggestion-form opening. These allow related events to be analyzed together. They are not advertising identifiers.

We do not include names, email addresses, payment details, contacts, precise device location, or suggestion text as analytics fields. Diagnostic error text is filtered to remove information such as email addresses, IP addresses, credentials, full URLs, and local file paths. Purchase receipts and transaction identifiers are not sent through our analytics events.

According to TelemetryDeck's Privacy FAQ, its App analytics service does not store IP addresses and rounds event timestamps to the nearest hour. The App also sends elapsed-time and duration measurements for diagnostics and usage analysis. Additional provider information is available in TelemetryDeck's Privacy Policy and SDK parameter documentation.

1.3 Destination Suggestions ("Got Suggestions?")

Submitting a suggestion is optional. When you select Submit, the App sends the text you entered over HTTPS to Visit NYC's server. The suggestion is stored in a database for our team to review and use to plan future Visit NYC destinations and videos in the Apple Immersive Video format.

The submission contains only your suggestion text. The server adds a generated record ID and creation time. The form does not request your name, email address, current location, or device identifier, and the submission does not include the analytics session identifier. Suggestions are not delivered to our team by email. Our suggestion database has no separate fields for IP addresses or client software information; network processing and hosting logs are described in Section 1.1.

Please avoid including personal or sensitive information about yourself or anyone else. If you include such information in the text, it becomes part of the suggestion we receive and store.

Unsubmitted drafts remain in App memory and are not sent to the suggestion server. The App clears the draft after a confirmed successful submission or when the form is dismissed. If a submission fails or cannot be confirmed, the draft remains available while the form is open so you can choose to retry. A missing confirmation does not necessarily mean the server did not receive the suggestion.

1.4 Suggestion-Form Analytics

Separately from receiving suggestions, we record when the form opens, when Submit or retry is selected, whether a submission succeeds or fails, when the Privacy Policy link is selected, and when the form closes. Closing without a confirmed successful submission records whether no submission was attempted or an attempt failed. This includes opening and closing the form without submitting anything.

These events may contain a random identifier for that form opening, attempt counts, elapsed time, outcome, close reason, and a general failure category, together with the standard analytics metadata described above. A new form opening uses a new identifier. Suggestion analytics and local event logs never include your suggestion text, its length, a hash of the text, or whether you typed anything into the draft.

1.5 Purchases and Support

Purchases are handled through Apple's App Store. The App uses purchase and entitlement information to unlock content and restore access. We do not receive your payment card details through the App. Purchase-related analytics are described in Section 1.2. Apple's handling of purchase information is covered by its Privacy Policy.

If you email us, we receive your email address and the information you choose to provide so we can respond to your request.

2. How We Use Information

• Deliver videos, operate App features, and provide access to purchased content.
• Diagnose failures and improve downloads, playback, performance, and reliability.
• Understand usage trends and improve navigation and workflows, including the suggestion form.
• Review submitted suggestions to plan future destinations and immersive videos.
• Respond to support and privacy inquiries and maintain service security.

We do not sell your personal information. We do not use advertising identifiers or track your activity across other companies' apps and websites for advertising.

3. Sharing and Disclosure

Information is processed by the providers needed to operate these features, including:

• Hosting, database, and content delivery providers that handle requests, deliver media, and store submitted suggestions.
• TelemetryDeck, which processes the analytics events described above. Suggestion text is not sent to TelemetryDeck.
• Apple, which provides App Store purchases and system-managed content delivery.
• Email service providers that handle correspondence you send to us.

We may also disclose information when required by applicable law or a valid legal process.

4. Storage and Retention

We have not set a fixed retention period for submitted suggestions. They remain in the server database for review and content planning until removed. The current suggestion service has no automatic expiration period. Closing the form or deleting the App does not delete a suggestion already received by the server.

The App keeps limited download-attempt records on your device to diagnose and reconcile downloads across restarts. This record set is capped at 64 recent attempts; entries older than seven days are removed when the records are loaded. It contains no suggestion text and is excluded from device backups. App analytics events are also written to local system logs, whose retention is managed by the operating system. The analytics SDK may keep local session information and queued events to support reporting.

We have not set a fixed retention period for server access logs. Their retention depends on hosting and content delivery settings. Analytics retention is governed by TelemetryDeck's service practices; its Privacy FAQ currently describes no fixed automatic deletion schedule for stored analytics events. The local seven-day download-record limit does not apply to analytics already transmitted to TelemetryDeck.

5. Your Choices and Requests

You can use the App without submitting a suggestion. You can dismiss an unsubmitted draft to discard its text, although form-action analytics may still be recorded. The current App does not provide an in-app analytics opt-out setting.

To ask about your information or request deletion of a submitted suggestion, contact us below. Include enough information to help locate the submission, such as its text and approximate submission date, while avoiding unnecessary sensitive information. Because suggestions and analytics are not linked to a named App account, we may be unable to associate a particular record with you.

6. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in the App, our practices, or legal requirements. Updates will be posted on this page with a revised effective date.

7. Contact Us

For questions or requests about this Privacy Policy or our data practices, contact BLOO LLC at contact@visitnyc.store.