AK JAMZ — Privacy Policy

Effective date: August 25, 2026

AK JAMZ ("AK JAMZ", "we", "us", "our") operates the AK JAMZ iOS app (the "App"), a map and feed of live and upcoming music across Alaska. This policy explains what the App collects, why, and the choices you have. It applies only to the App.

Operator: AK JAMZ
Contact: akjamz907@gmail.com
This policy is hosted at: https://ak-live-d4298.web.app/privacy

AK JAMZ does not sell the account, profile, location, search, follow, or saved-show data it controls. Browse home may show one clearly labeled advertisement: either a direct-sold AK JAMZ Sponsored card or a Google Mobile Ads placement. Ads are configured for conservative age treatment, General-rated content, and non-personalized or limited serving as consent and regional rules require. Google Mobile Ads and its advertising partners may process device identifiers for advertising delivery and measurement. Where applicable, Google may ask iOS to show Apple's App Tracking Transparency (ATT) permission; Google may access IDFA or track activity across other companies' apps or websites only if you choose Allow. You can use AK JAMZ if you do not allow tracking.

1. What we collect

We collect only what the App needs to function and improve. Service data is linked to the account that owns it. AK JAMZ product analytics is associated with persistent app/device identifiers, but AK JAMZ does not use that first-party product data for advertising or cross-app tracking. After 13+ eligibility resolves on a non-demo launch with a valid production ad-unit ID, Google's User Messaging Platform (UMP) may contact Google to refresh regional consent and privacy choices before sponsorship policy or direct inventory resolves. UMP's embedded privacy manifest declares unlinked coarse location, product interaction, and performance data for App Functionality. Google Mobile Ads initialization and the advertising request path remain separately gated by consent, sponsorship policy, and direct-inventory state.

Data type (Apple category)What it isWhen collectedWhy (Apple privacy purpose)
NameThe display, act, venue, creative, or business name you enterWhen you edit your profile or submit account-related contentApp Functionality: to operate your private profile and any public identity you choose to publish
Email AddressThe address you enter for an email/password account, or the address/private relay address you choose to share through Sign in with AppleWhen you create an email account or share an address through AppleTo authenticate your account, send verification and password-reset messages, and protect public posting, venue claims, and public act pages
Phone Number, Physical Address, and Other Contact InfoOptional venue phone/address, booking contact, website, or social links you add to a profile or claimOnly when you choose to enter itApp Functionality: to save your profile/claim and publish only the fields the relevant screen identifies as public
Precise LocationYour device's GPS coordinates, requested as "While Using the App" onlyWhen you use location-backed map features or broadcast a live postApp Functionality: to show music near you, place your live pin, provide directions, and support nearby alerts you enable
Coarse LocationA GPS point immediately rounded to two decimals for nearby alerts; Google's UMP or Mobile Ads SDK may also infer a broad area from an IP addressWhen nearby alerts are enabled, during an eligible UMP consent refresh, or when a Google ad request is permittedApp Functionality and Product Personalization for alerts and consent; Analytics, Third-Party Advertising, and Developer Advertising or Marketing for permitted Google ads
Other User ContentProfile content; live/Buzz posts; favorites, blocks, claims, and post/profile/sponsor reports you submitWhen you use those featuresApp Functionality: to operate the feature, publish what you choose, and review safety reports
Customer SupportThe message/category you send through the in-app suggestion and feedback surface, with account ID and app/build contextWhen you choose to send feedback or ask for helpApp Functionality: to review, troubleshoot, and respond to product/support submissions
Contacts (Apple's social-graph category)The creator IDs you follow/favorite or block. AK JAMZ does not read your phone address book.When you follow, unfollow, block, or unblock a creatorApp Functionality and Product Personalization: to manage Following, alerts, and content you chose to hide
Search HistoryThe town, venue text, genres, and date window in a Saved SearchWhen you save or update alert preferencesApp Functionality and Product Personalization: to remember your search and send matching alerts you request
User IDAn anonymous Firebase account identifier assigned after the eligibility screen and, if you upgrade, an Apple- or email-linked account identifierAfter the eligibility screen and when you sign inApp Functionality: to authenticate you, associate your data with your account, and enforce identity-gated actions
Device IDA push token, app-generated installation identifier, analytics app-instance identifier, app/device-bounded identifiers used by permitted Google ads, and IDFA only if you grant ATT permissionWhen eligible services start and when permitted ad, push, or analytics features run; IDFA only after you choose Allow in the iOS tracking promptApp Functionality, Analytics, Third-Party Advertising, and Developer Advertising or Marketing, including ad delivery, security, frequency management, and measurement. Google may use Device ID for tracking only after ATT authorization.
Usage Data (Product Interaction)In-app feature events, UMP consent interactions, and—when a Google ad request is permitted—ad views and interactionsAs you use the App after the eligibility screen; UMP may refresh before an ad request is permittedApp Functionality, Analytics, Third-Party Advertising, and Developer Advertising or Marketing: consent, product improvement, ad delivery, and measurement; not used by AK JAMZ for ad targeting or cross-app tracking
Other DataUnlinked service metadata, such as the Firebase user agent, declared by Firebase MessagingWhen Firebase services runAnalytics. Not linked to you and not used for advertising or tracking
Crash DataGoogle SDK crash diagnosticsWhen an SDK crash is processedAnalytics and service reliability
Performance DataUMP and Google Mobile Ads performance diagnosticsDuring an eligible UMP consent refresh or when a permitted Google ad request/response is processedApp Functionality, Analytics, Third-Party Advertising, Developer Advertising or Marketing, fraud prevention, measurement, and service reliability
Other Diagnostic DataFirebase Messaging, Google transport, and Google Mobile Ads service diagnosticsWhen eligible Firebase services or permitted Google advertising services runApp Functionality, Analytics, Third-Party Advertising, Developer Advertising or Marketing, and service reliability
Advertising DataDirect-sponsor creative request metadata and permitted Google ad requests, impressions, and interactionsWhen a direct sponsor creative or permitted Google ad is requested, displayed, or interacted withApp Functionality, Third-Party Advertising, Developer Advertising or Marketing, Analytics, security, fraud prevention, frequency management, and measurement; not tracking
Coarse age/privacy statusTwo on-device booleans: eligible (13+) and under-age-of-consent treatment; no birthday or exact age band is retainedAfter the neutral age-range screen; the treatment flag is passed to Google when UMP or an ad request is permittedApp Functionality and Third-Party Advertising: block under-13 access and apply the required Google privacy treatment

Anonymous by default. You can browse the map and upcoming feed without creating a named account. Sign in with Apple or email/password is optional for private account features. Password accounts must verify their email before publishing shows, claiming a venue, joining the public beta count, or publishing a public act page; browsing and private profile editing remain available before verification.

We do not access your phone address book or collect photos or videos, browsing history, health or fitness data, financial information, or sensitive information. AK JAMZ's first-party features do not access IDFA; Google Mobile Ads may access it only after you grant ATT permission. Apple classifies the private followed/blocked creator IDs described above as Contacts because they form a social graph. The in-app Saved Search is collected only when you save it. Precise location is never collected in the background.

The App stores interface and eligibility preferences on your device using Apple's standard UserDefaults API (declared reason CA92.1). It also creates an installation identifier there; that identifier is sent to our backend only as part of safely claiming or releasing a push token and is disclosed above as Device ID.

2. How your information is used

AK JAMZ does not use your account, profile, location, search, follow, saved-show, or first-party product-analytics data to select or target sponsorships, build an advertising profile, or track you across other companies' apps or websites. Google Mobile Ads' conditional Device ID use is described separately in Section 3.

3. Advertising

Direct AK JAMZ sponsorships

AK JAMZ sells and reviews sponsor placements directly. Creative images are hosted on our own Firebase Hosting site, not fetched from an ad network. A card is clearly labeled Sponsored and includes Why this ad?, Hide, and Report controls. Hiding removes the card for the rest of that app session. Reports go to our human moderation queue and can cause an operator to pause a campaign. The global sponsor switch can remove every card without an app update.

To return a sponsor image, Firebase Hosting receives routine web-request metadata such as the creative URL, IP address, user agent, request time, and approximate network location. The request is not authenticated and carries no AK JAMZ account or app identifier. However, IP and user-agent details can be associated with a device, so AK JAMZ conservatively discloses this Advertising Data as linked and used for creative delivery, service security/reliability, and usage analysis. It is not used to track you across companies' apps or websites. Firebase may retain Hosting IP information for a limited service-retention period. AK JAMZ does not emit a separate sponsor impression or tap analytics event in this version.

Tapping a card opens the sponsor destination you chose to visit. The destination website then receives the ordinary technical information any website receives from a visit, such as IP address, browser/device information, and request time, under that site's own privacy policy. AK JAMZ does not automatically send your account, profile, location, search, or app activity to the sponsor.

Google Mobile Ads

When the App's sponsorship switch is on, authoritative non-cache inventory confirms that no direct card is eligible, and the session has not already requested a Google banner, Google Mobile Ads may request and display one inline ad. Mobile Ads initialization is deferred until those conditions are met. UMP consent may refresh earlier—after eligibility but before the sponsorship switch or inventory resolves—and that consent-service refresh may contact Google and process unlinked coarse location, product interaction, and performance data for App Functionality. A sponsorship-OFF state prevents Mobile Ads initialization and banner requests, but does not itself suppress that earlier UMP refresh. Before requesting an ad, the App applies Google's child age-restricted treatment for ages 13–15 and teen treatment for ages 16+, a General maximum content rating, and UMP consent requirements. Depending on your region and choices, Google may serve non-personalized ads or limited ads, or the placement may remain empty. Google provides its AdChoices disclosure on served ads.

AK JAMZ's European regulations message is published and active for the EEA, United Kingdom, and Switzerland with Consent, Do not consent, and Manage options. Its published and active AK JAMZ US State Privacy Choices message covers all current and future supported US states with opt-out enabled. Both use this privacy policy and may take up to one hour after publication to appear.

For delivery, fraud prevention, frequency management, and measurement, Google and participating advertising partners may process or share an IP address and IP-derived coarse location, app/device-bounded identifiers, ad views and interactions, and crash/performance diagnostics. When Google's consent flow determines that an ATT explanation is applicable, it may ask iOS to present Apple's tracking permission. Google may access IDFA or use Device ID to link activity across other companies' apps or websites only after you choose Allow. If you choose Ask App Not to Track, AK JAMZ remains usable and Google must not access IDFA or use app data for tracking; a non-personalized or limited ad may still be served using other permitted signals. AK JAMZ does not give Google your profile, searches, follows, saved shows, account content, or precise GPS location for ad targeting.

4. Upcoming-event listings (third-party public data)

Some events shown in the "Upcoming" layer are public listings ingested from third-party sources — for example the Ticketmaster Discovery API, university calendars (UAF/UAA 25Live, UAS), arts-council and venue calendars (JAHC iCal), and curated festival data. These listings are clearly labeled as upcoming and are never presented as a confirmed live broadcast. We send no personal information to these sources; we only read their public event data. We do not control and cannot guarantee the accuracy, availability, or pricing of third-party listings — confirm details with the venue or ticket seller.

5. Where your data lives, and who processes it

Your data is stored and processed in Google Firebase, our backend. We use a small set of service providers that handle data under their service terms for delivery, security, reliability, and the limited service/product analytics described here:

We may disclose information if required by law or to protect the rights, property, or safety of our users or the public.

6. Retention and deletion

7. Your choices and controls

8. Children

AK JAMZ is not directed to children under 13 and may not be used by them. On a fresh or anonymous install, the App asks for a neutral age range before creating a new guest account or starting analytics, messaging, database listeners, or location features. It immediately discards the range and retains on-device only whether the device is eligible (13+) and whether Google must receive under-age-of-consent treatment. Ages 13–15 map to that treatment; ages 16–17 and 18+ do not. Existing eligible installs without the second value are asked once and fail closed until answered. The App does not retain a birthday or exact age band. If "Under 13" is selected, service access stays disabled and the App attempts to delete any existing anonymous guest identifier; if cleanup fails, it displays a reference to send to support. A parent can use Apple's controls to approve an age-rated app for a teen, but that does not override AK JAMZ's under-13 prohibition. If you believe a child has provided us personal information, contact us at akjamz907@gmail.com and we will delete it.

9. Security

We use industry-standard measures, including encrypted transport (TLS), authenticated access, and least-privilege database rules. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

10. Tracking and ATT

AK JAMZ does not combine its first-party account or product data with other companies' data to target advertising or build an advertising profile, and Firebase Analytics IDFV collection remains disabled. The embedded Google Mobile Ads SDK separately declares Device ID as data that may be used for tracking. Google may access IDFA or link Device ID with third-party data for advertising or measurement only after you grant ATT permission. Denying ATT does not block AK JAMZ; Google must omit IDFA and may serve only a non-personalized or limited ad using other permitted signals. AK JAMZ discloses this conditional Google SDK practice in its App Store privacy answers.

11. Changes to this policy

We may update this policy from time to time; the "Effective date" above will change. Material changes will be surfaced in the App or in the App Store listing.

12. Contact

Questions about this policy or your data? Contact us at akjamz907@gmail.com.