Published App Privacy

Every user gets a private, isolated database for each app they use. Publishing an app does not share the records in that database. Files used in the app are accessible through their file links.

Per-User Data

When someone opens your published app, they do not use your database. They get their own private data store for that app.

For records saved in that private database:

• They cannot see data you entered while building or testing the app.
• You cannot see data they enter while using the app.
• Other users cannot see each other's data.

Creator Privacy

Publishing an app does not share your private database records. Files whose URLs are included in the app's code are available to people using the app. Files supplied only as build references are not automatically included in the code.

User Privacy

Users can enter information into published apps knowing their data is isolated to their account. Their data also persists across sessions and syncs across their own devices.

Visibility and Privacy

Visibility controls who can access the app. It does not grant access to private data. Public, unlisted, and private apps all use the same per-user data isolation model.

Uploaded files and generated media use public, unguessable URLs. Anyone with a file's URL can access it without signing in, regardless of the app's visibility. Making an app private does not revoke file links already shared. See Uploaded files and generated media for details.

For visibility details, see Visibility Settings.