Privacy policy

Effective September 22, 2026

Alexandria is an open-source retro game library and player maintained by Arnaud Ferreri. This policy covers the Alexandria app and this public website.

1. Data on your device

Alexandria uses files and information needed to browse, organize, and play your collection: game files and filenames, library entries, favorites, recent games, play time, saves, save states, screenshots, artwork, settings, and diagnostic information. Much of this information stays on your device unless you enable a connected service, export it, or share it yourself. Features differ between app versions and platforms.

Alexandria does not require a separate Alexandria account. Native apps communicate directly with the selected cloud provider. Optional web sync passes supported library records and saves through Alexandria’s server to your Dropbox account without retaining those files on the server.

2. Optional Google Drive connection

If you connect Google Drive, Alexandria requests the drive.appdata permission. This permits it to create, read, update, and manage its own files in Google Drive’s hidden application-data folder. It does not grant access to your other Drive documents, photos, or folders.

Alexandria uses this access to back up, restore, and synchronize supported app data between your devices. Depending on your settings and app version, that data can include:

• Game saves, save states and their history, plus screenshots.
• Library records, game identifiers and filenames, favorites, recent activity, and play time.
• App preferences, emulator options, and supported connected-account settings.
• File metadata, checksums, and an account identifier used to match the correct account and detect sync conflicts.

Connected-account settings can include Archive.org session cookies and RetroAchievements usernames and access tokens. These allow a signed-in session to be restored on another device. They are sensitive credentials; enable cloud sync only with accounts and devices you trust. Game ROMs and BIOS files are not part of the automatic save-sync exchange.

Google authorization happens through Google’s sign-in and consent flow. Alexandria receives authorization tokens, not your Google password. On Apple platforms its Google tokens are stored in the device Keychain; Android uses Google Play services for authorization. Google Drive tokens are not included in the shared settings exchange.

Google data is used to provide these user-facing sync and backup features, not to build advertising profiles or train general-purpose AI models. Alexandria’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

3. Other services you choose to use

On supported platforms, you can also use Dropbox or iCloud for sync. When multiple providers are enabled, supported data restored from one provider can be reconciled with local data and synchronized to another enabled provider. Each provider stores and processes that data under its own terms and privacy policy.

Browsing, downloading, fetching artwork or metadata, checking for updates, or using achievements can contact services such as Internet Archive, GitHub and libretro resources, LaunchBox, RetroAchievements, and the selected content or update host. Those services receive the requests required for the feature and normal connection information such as your IP address. Signing in to one of these services is governed by that service’s policies.

Alexandria does not sell Google user data or use it for targeted advertising. Web Dropbox transfers pass through the site’s hosting infrastructure as described below; these files are not retained there for developer access.

4. Storage and security

Connected cloud data is stored in your selected provider accounts. Local credentials use the storage mechanisms implemented for the platform, including Keychain on Apple devices. Google authorization and Drive transfers use HTTPS.

Cloud sync is not represented as end-to-end encrypted by Alexandria. Your provider’s security controls and your device and account security matter. Keep independent copies of important saves: no synchronization or backup system can guarantee that data will never be lost.

5. Your choices, retention, and deletion

• Stop syncing: turn off automatic sync or disconnect the provider in Alexandria’s settings. Disconnecting stops future use through that connection; it does not automatically erase existing local files or cloud backups.
• Revoke Google access: remove Alexandria in your Google Account’s third-party connections.
• Delete Google Drive app data: use Google Drive on the web, open Settings → Manage apps, find Alexandria, and use the option to delete hidden app data when available. Revoking access alone is not a request to delete stored backups.
• Delete local data: remove files using Alexandria or your device’s file-management controls. Uninstalling may leave exported files, files in shared storage, or cloud copies; remove those separately if desired.
• Other cloud copies: use Dropbox or iCloud’s controls to remove data stored there. Stop sync on connected devices first if you do not want local copies uploaded again.

Local and cloud data can remain until you remove it or the relevant provider removes it under its retention rules. Recovery copies and older backups may remain after a sync operation. Alexandria’s developer cannot directly delete private files from your cloud account; contact us if you need help finding the appropriate controls.

6. Diagnostics and support

Alexandria can keep local diagnostic information for troubleshooting. If you choose to email support or share a diagnostic report, the recipient receives the information you send, such as your email address, device details, filenames, and logs. Review reports before sharing them and do not send passwords or authorization tokens. Support correspondence is used to respond to and investigate your request and retained as needed for that purpose and applicable legal obligations.

Apple, Google, distribution platforms, and cloud providers may separately process diagnostics or account information according to their own policies and your settings.

7. This website

This public website includes the Alexandria web player at /play. Imported game files, prepared LaunchBox metadata, the SQLite library, and saves are stored in this browser. Optional Dropbox sync shares favorites, recent games, and compatible battery/clock saves for supported systems with the native apps. ROMs, emulator save states, native settings, and unsupported platforms are not uploaded or modified by web sync. Library records and saves pass through Alexandria’s server to Dropbox without being retained on the server. A Dropbox refresh token is encrypted in a Secure, HTTP-only browser cookie for up to one year; server-side requests use it to renew access. A short-lived cookie protects Dropbox sign-in. Disconnecting removes this connection cookie and keeps local and Dropbox files. Clearing site data removes local browser data. Emulator resources are loaded from EmulatorJS, artwork from libretro resources, and requested downloads from Internet Archive through Alexandria’s server; these services receive normal network request information. Download requests pass through Alexandria’s hosting provider without storing game files there. A secure session cookie remembers access to the password-protected player for 24 hours. It has no account registration, advertising, analytics scripts added by Alexandria, or unrelated game-data collection forms. Its hosting and delivery providers, including OpenAI Sites and Cloudflare, may process IP addresses, browser information, request logs, and security-related technical data to serve and protect the website. Their own privacy policies govern their processing: OpenAI and Cloudflare. Following an external link takes you to a separate service.

8. Children

Alexandria is not directed to children under 13, and the developer does not knowingly collect their personal information through support or this website. If you believe a child has sent personal information to the developer, contact us so it can be addressed.

9. Changes and contact

Updates to this policy will be posted here with a revised effective date. Material changes in how Google data is used will be disclosed, and additional consent obtained where required.

For privacy questions or requests, contact Arnaud Ferreri at arnaud.ferreri@gmail.com. Depending on where you live, you may have rights to access, correct, delete, or restrict the processing of personal information. Requests concerning your provider account should also be directed to that provider.