GoodDay Briefing
Effective: August 28, 2026 · Developer: Volodymyr Vechirnii · Contact: [email protected]

Privacy Policy

This Privacy Policy explains how Volodymyr Vechirnii, shown in the App Store as “Volodymyr Vechirnii” (“I”, “me”, “my”), handles information in the GoodDay Briefing iOS application and related pages on sunseaapps.com.

Summary: GoodDay Briefing does not require an account, does not use advertising SDKs, does not sell personal information, and does not track you across other companies’ apps or websites.

1. Information used by the app

1.1 Home Area, Explore Location, and device location

You may choose a U.S. city or ZIP code as your Home Area and may separately choose an Explore Location for RV and Events searches. If you choose “Use Current Location,” the app may request iOS location access to resolve your approximate location into a city and state. GoodDay Briefing does not continuously track your movement and does not collect background GPS history.

1.2 Family Weather locations

You may save one or more Family Weather locations and optional display labels. These locations and labels are stored locally on your device. The city, state, approximate coordinates, and time zone may be sent to weather, alert, and related providers when the app refreshes Family Weather. Family Weather labels and locations are not sent to Firebase Analytics.

1.3 Weather, alerts, recreation, events, activities, and maps

To return relevant results, the app may send a city, state, approximate coordinates, date, radius, or similar request information to service providers used for weather, government alerts, recreation listings, events, activities, maps, and directions.

Depending on the feature, these providers may include Apple services, Open-Meteo, the U.S. National Weather Service, Recreation.gov/RIDB, Ticketmaster, and replacement providers used to keep the app operational.

1.4 Backend security and App Check

GoodDay Briefing uses a Google Cloud Run backend for protected app services. The app uses Firebase App Check to help verify that requests come from a genuine copy of the app. Firebase App Check and its attestation providers may process app-attestation material, temporary App Check tokens, device or app integrity signals, IP address, and related technical information needed to prevent abuse. App Check tokens are not stored in audio-cache filenames or logged by GoodDay Briefing.

1.5 Briefing audio and text-to-speech

When you choose to play a GoodDay Natural spoken briefing, the briefing text and selected voice settings are sent through the protected backend to Google Cloud Text-to-Speech so an audio file can be generated. If you explicitly select an Apple on-device voice where available, speech may instead be generated locally using Apple system speech services.

The cache reduces repeated processing, improves playback speed, and controls operating costs. GoodDay Briefing does not use the microphone and does not record your voice.

1.6 Calendar and device features

When you choose to add a plan to your calendar or open directions, the app uses Apple system features. Calendar access is requested only when needed. Items you add to Apple Calendar are managed by Apple and your configured calendar provider under their own terms.

1.7 Analytics

GoodDay Briefing uses Firebase Analytics to understand basic app usage. Analytics may include app opens, sessions, device and operating-system information, installation identifiers, main-tab visits, briefing playback and full-briefing actions, onboarding and subscription-screen actions, and Home Area city and state as coarse app preferences.

Analytics does not include:

The app does not include advertising SDKs, does not use the advertising identifier for tracking, and does not use analytics for cross-app advertising profiles.

1.8 Subscription paywall analytics

GoodDay Briefing uses Superwall to present and measure the subscription paywall experience. Superwall may process an automatically generated anonymous app-user identifier, device and app information, paywall presentation and interaction events, and subscription or purchase-status events needed to operate and measure the subscription flow.

GoodDay Briefing does not identify users to Superwall with a GoodDay account and does not send Family Weather names or locations, briefing text, saved notes, calendar content, email address, or advertising identifier to Superwall.

1.9 Support messages and website logs

If you contact me by email, I receive your email address and any information you include in your message. Website hosting providers may process standard server logs, such as IP address, browser type, requested page, and timestamp, to deliver and secure the website.

2. Purchases and subscriptions

Apple processes GoodDay Briefing subscriptions through the App Store. GoodDay Briefing uses Superwall to present the paywall and help measure subscription-flow events, but Apple and StoreKit remain responsible for purchase processing and subscription entitlement.

I do not receive or store your full payment-card details. Apple may provide the app with limited purchase information, such as product identifier, transaction status, subscription status, renewal state, expiration information, or refund status. This information is used only to unlock paid features, restore purchases, provide subscription support, measure the subscription flow, and prevent fraud.

3. How information is used

4. Third-party services

I do not authorize service providers to use GoodDay Briefing data for their own advertising profiles or cross-app tracking.

5. Data sharing and sale

6. Retention

7. Your choices

8. Children

GoodDay Briefing is intended for a general adult audience and is not directed to children under 13. I do not knowingly collect personal information from children under 13.

9. International processing

I operate from Canada. Service providers may process information in Canada, the United States, or other countries where they operate. Applicable legal protections may differ by country.

10. Security

I use reasonable technical and organizational measures, including App Check-protected backend routes, limited analytics fields, hash-only audio-cache object names, and time-limited caches. No method of transmission or storage is completely secure.

11. Changes to this Policy

I may update this Privacy Policy when app features, providers, or legal requirements change. The effective date at the top of this page will be updated.

12. Contact

Volodymyr Vechirnii
British Columbia, Canada
[email protected]