Boldfinch HB

Lazy Lion Matcha

AdMob Recipients and Destinations

Last updated: August 25, 2026

See also: Privacy Policy · Terms of Service · Support · Website Privacy Notice

Prepared next-release notice. This appendix is prepared for the first later Lazy Lion Matcha App release that links to it. It does not change the Privacy Policy for version 1.0.0, does not confirm that a market is available, and is not legal approval for any market. The unchanged version 1.0.0 Privacy Policy is at https://boldfinch.net/lazy-lion-matcha/privacy-policy/versions/2026-07-17/

Version date: August 25, 2026

Effective date: August 25, 2026, for this prepared document version. It applies to an App only after a separate publication workflow makes it current for a later App release.

Source and account-evidence date: August 10, 2026. The dated account and source evidence below is a snapshot, not proof that the same recipients, settings, or destinations apply at a later time. It must be refreshed before a market is activated.

What this appendix covers

This appendix describes the global factual AdMob recipient and destination baseline for a later Lazy Lion Matcha release. It is part of the Privacy Policy and does not replace an applicable regional privacy notice, consent flow, or other legal requirement.

The potential advertising data categories are IP address and coarse location, user-agent, device and operating-system information, App and ad-unit request context, consent and ATT status, an advertising identifier only when available and permitted, ad or creative interactions, diagnostic and fraud signals, and click or impression data. Depending on context, these categories can be personal or pseudonymous information. They are not anonymous merely because they do not contain a name or email address.

Contracted Google entity and specifically identified parties

Contracted Google entity. The account-linked Swedish AdSense Terms reviewed on August 10, 2026 name Google Ireland Limited as Boldfinch HB's Google counterparty for the ordinary AdMob flow. The account evidence did not expose the original acceptance date or a terms version. Google Ireland Limited is the direct contractual counterparty; it is not a statement that all technical processing occurs only in Ireland or only at Google.

Specifically identified parties.

  • Boldfinch HB is the App publisher and decides to use the AdMob SDK.
  • Google Ireland Limited is the identified Google contractual counterparty for the ordinary AdMob flow.

Google may act as an independent controller for ordinary AdMob services. Boldfinch does not have a direct contract with every downstream buyer or provider, and this appendix does not claim that Google is the only technical recipient.

Dynamic recipient categories

The following are documented dynamic categories. An entity being eligible in a category does not mean that it received a particular user's data.

  • Google AdMob and Google services may receive the initial ad request and operate the advertising service.
  • Authorized Buyers, buyers, DSPs, advertisers, and ad servers may receive bid-request data from Google server-to-server or participate in a winning ad delivery.
  • Creative hosts and certified measurement, verification, and fraud-prevention providers may receive device-side requests when a winning creative loads or is measured.

The August 10, 2026 account snapshot recorded Google plus 407 Authorized Buyer demand rows. It also recorded a larger, dynamic Google-certified ad-source universe. The public evidence did not provide a complete country, retention, or actual-request recipient list for every category.

Google's Authorized Buyers Terms and Program Guidelines are Google's downstream contractual framework. They do not make a public category list proof that every listed organization received data from this App.

Data, purpose, storage, and access by serving outcome

The App's requested mode and the provider's final serving outcome are different things. Google-controlled serving, demand, and recipient behavior cannot be fully observed from the App. A regional review must approve every externally reachable outcome before that market can be activated.

Serving outcomeData and purposeStorage or access behaviorRecipient and destination status
PERSONALIZEDMay use the listed ad-request data and, only where available and permitted, an advertising identifier for personalized advertising and related measurement, security, and fraud prevention.Google or a downstream recipient may access or store its own advertising, device, network, consent, or identifier data. The exact technology and retention for every recipient are not fully known.Google may process the request and dynamic buyer, advertiser, ad-server, creative, measurement, verification, or fraud categories may be involved. Country and recipient-specific retention are PENDING.
NPAUses contextual request data for ad delivery, measurement, security, and fraud prevention without behavioral ad personalization. NPA does not mean that no personal or pseudonymous information is processed.Google or a downstream recipient may still access or store contextual, device, network, consent, interaction, measurement, or fraud data. The exact storage and access behavior is not fully known.The same Google and dynamic recipient categories can be relevant. Destinations and recipient-specific retention remain PENDING.
LIMITED ADSMay limit advertising uses or selection under Google-controlled rules, while still using data needed for contextual delivery, security, fraud prevention, or measurement. Limited Ads does not mean anonymous or processing-free advertising.Google or a downstream recipient may still access or store data for the limited service. The exact scope and each recipient's storage or access behavior are PENDING.Google and dynamic categories can remain relevant. The final recipient and destination for an individual request are not known in advance.
NO_REQUESTNo App-level AdMob request is made because eligibility is false or unknown, a market is inactive or disabled, or a technical fail-closed condition applies. It is not a user-selectable ad-free product tier.No ad request is sent by the App for that attempt. The App can still keep its local daily-gate state and other local settings described in the Privacy Policy.No AdMob request recipient is expected for that attempt. This row does not prove deletion of information previously processed by Google or another recipient.

Google's UMP result, a UMP rejection, NPA, Limited Ads, an ATT refusal, or another privacy signal can affect personalization, identifiers, or whether an App-level request is allowed. None of those signals by itself proves that all personal or pseudonymous processing, international processing, storage, or downstream disclosure has stopped.

Destinations, retention, and explicit unknowns

Google describes Ads Services as using global infrastructure and does not provide Boldfinch with a product-specific country list for all AdMob processing. Google Ireland Limited is the contractual counterparty; the country where a particular request, bid, creative, measurement event, or fraud check is processed can be different or unknown. Dynamic recipient categories likewise have unknown or changing countries.

The following published retention information was recorded on August 10, 2026:

  • Google AdMob User Activity reports: 90 days.
  • Google Ads Activity, Cohort, and Privacy & messaging reports: 2,555 days.
  • Google describes partial anonymisation of IP addresses in some logs after nine months and removal or anonymisation of some cookie or advertising-ID information after 18 months.

This is not a complete AdMob or downstream-recipient retention schedule. Google may retain information longer for security, fraud, legal, financial, and service-continuity reasons. Retention for an Authorized Buyer, advertiser, ad server, creative host, or other dynamic recipient is PENDING unless a dated source identifies it.

Evidence sources and reassessment trigger

The account and source snapshot was reviewed on August 10, 2026. It included account-linked Swedish AdSense Terms, AdMob demand and source views, and the following public Google materials:

Reassess this appendix before activation and whenever Google terms or the contracting entity, UMP or privacy messages, the Buyer or source universe, mediation, ad format, data categories, retention, destinations, App SDK, account controls, applicable law, or active countries change. If a rule requires an exact recipient to be named and this appendix cannot name it, the affected private jurisdiction-matrix row cannot become APPROVED.

Privacy choices and requests

Applicable privacy and consent choices can be revisited in Settings → Ad privacy choices when that entry is available. On iOS, ATT is a separate device permission. The App's short ad notice links here; it is not a substitute for an applicable regional consent or privacy flow.

Boldfinch cannot use the App's Data deletion ID to retrieve a Google advertising profile. That ID is for the separate PostHog server-data request flow and is not sent to Google AdMob for this purpose. For information Google processes as an independent controller, use Google's applicable privacy controls and request channels.

For the fuller global explanation, see https://boldfinch.net/lazy-lion-matcha/privacy-policy/