Deutsch   English   Français   Italiano  
<v5b428$1b0h$1@nnrp.usenet.blueworldhosting.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!panix!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Andrew <andrew@spam.net>
Newsgroups: comp.mobile.android
Subject: Re: Android keyboard: your choice.
Date: Mon, 24 Jun 2024 06:34:49 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v5b428$1b0h$1@nnrp.usenet.blueworldhosting.com>
References: <20240617114559.a2970ac2923facc44a2ec355@gmail.com> <v4ov83$j5oj$1@dont-email.me> <v4sojj$1gqik$1@dont-email.me> <lde8tqF9a76U1@mid.individual.net> <v4tkrl$1bpq$1@nnrp.usenet.blueworldhosting.com> <ldfbtsFe5o7U2@mid.individual.net> <v4u0gv$1rom7$4@dont-email.me> <ldia0iFrps7U6@mid.individual.net> <v51gft$2kg3e$1@dont-email.me> <ldj1v5Fs5uU1@mid.individual.net> <v54msb$2s6v$1@nnrp.usenet.blueworldhosting.com> <ldpag2Ftm5tU3@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 24 Jun 2024 06:34:49 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="44049"; mail-complaints-to="usenet@blueworldhosting.com"
Cancel-Lock: sha1:aQYZ+pRLi3aQq7pFovocXcmBimA= sha256:wlm9Wbhpra1CYvHb6OPKuhUuxcIE/nMSss7DyZLZtsY=
	sha1:JewQDi+JexINUSQ5NN14B/I1twk= sha256:f2jBoqXYrUIAFkxvK+3yaNvGmwfWTj6b5l2PfKUU8/g=
X-Newsreader: PiaoHong.Usenet.Client.Free:1.65
Bytes: 3705
Lines: 43

Arno Welzel wrote on Sun, 23 Jun 2024 03:01:57 +0200 :

> See here:
> 
> <https://firebase.google.com/docs/projects/learn-more?hl=en>

The goal is to understand things. To that end, I am far less concerned with
Firebase Cloud Services than with Firebase App Indexing, which is explained
rather clearly below in this cite:

> Google Services Firebase App Indexing (search related):
>  <https://medium.com/android-news/firebase-app-indexing-for-personal-content-getting-personal-content-into-search-c52bfe45b3ac>
>    "A note about privacy: The personal content index only exists
>     on the user's device. None of the user's personal content is 
>     uploaded to Google servers and it only remains on the device
>     while the app is installed. However, aggregated statistics
>     about apps' usage of App Indexing and other system health 
>     information may be uploaded to Google servers."

From that alone, it's clear Google is *definitely* the recipient of the
Firebase App Index aggregated statistics which are uploaded periodically.

The simplest way I can summarize what that cite clearly states, is this:
a. Google isn't gathering the data (which is to be found in a local search)
b. The app is gathering the data (to be found in a local search)
c. But the app isn't uploading that data (which it stored on the device)
d. The app is just storing the data (making it available to the search)
e. Google says they only upload "aggregate statistics" about that data.
f. Not the data itself.

In summary, of three things, we only fully know two of them:
a. We know what data each app is storing in the Firebase App Indexing db
b. We know who is uploading that index (google) and to where (google)
c. But we do not know how much of that index google is uploading

Certainly the Firebase App Indexing contains extremely detailed accounts of
your activities, down to every contact you've connected with and every app
you've used and every location you've searched for and which songs and
movies you've viewed, etc.

But Google says they only upload to their servers an "aggregate index".
Whatever that is.

Does anyone know more about what this "aggregate index" actually contains?