Generic devices syncing retro saves through a secure cloud

Optional sync

Save and library sync under user control

Google Drive in EmuTribe is optional. When connected, it is meant to sync app data such as library metadata, saves, save states, and settings, not to turn Drive into a public game distribution service.

Required?

No

Planned scope

drive.file for files/folders used by the app

Revocation

Available in the app or your Google Account

KEY POINTS

What this page answers

Limited access

The goal is to use permissions compatible with app-created or user-selected files, not broad access to the entire Drive.

App data

The focus is library data, saves, save states, and settings, while game files remain the user's responsibility.

Transparency

The home page, Privacy Policy, and this page explain why sign-in is requested and when Drive is used.

01

How to think about sync

EmuTribe sync should be understood as a convenience layer: continue on phone, tablet, or TV with consistent library data and progress.

The user chooses whether to connect Drive. Without that connection, parts of the app may still work locally depending on version and available features.

02

What we do not do

EmuTribe does not sell Drive data, does not use Drive data for advertising, and does not provide ROMs, ISOs, or BIOS files. Game files remain the user's responsibility.

03

Revoke access

Users can disconnect Google Drive inside the app or review permissions directly in their Google Account settings.

Frequently asked questions

Is Drive required to play?

No. Drive is an optional layer for app data sync.

Does EmuTribe access my whole Google Drive?

The goal is to use limited scopes such as drive.file for files and folders used or authorized by the app.

Can I revoke access?

Yes. You can disconnect in the app or revoke access in your Google Account settings.