Speye - Privacy Policy & FAQ

Data Collection

Speye is designed from the ground up with local-first privacy principles. Below is how data storage, services, and backups are handled:

          Local Storage: Speye is designed with privacy in mind. All notification data, including text, history, and image attachments, is stored locally on your device in a private database. We do not store or transmit any sensitive data by ourselves.
        

Third-Party Services (Play Flavor vs FOSS Flavor)

Speye is released in two distinct flavors. Third-party integrations depend strictly on the build flavor you install:

Google Play Flavor: Integrates third-party services like Google AdMob and Google Play Services. These services may collect device identifiers and usage statistics for ad personalization and analytics. Review Google's Privacy Policy for details.

          FOSS / F-Droid Flavor: 100% ad-free and open-source. Contains no Google Play Services, no AdMob SDKs, and zero third-party telemetry libraries. (Note: Google Drive cloud backup is omitted in the FOSS build as it relies on Google APIs).
        

Cloud Backup

If you use the Google Play version and choose to enable Google Drive Backup, Speye uploads your data to a private folder in your personal Google Drive account. This data is not accessible by the developers or any other third parties, and stays under your control.

Local file backup (`.spy` export/import) is supported on all flavors and requires no cloud connectivity.

General Questions

Speye is a free app to keep track of your notifications and never lose them.

You can export your notifications to a .spy file in the Settings page and import them back whenever you want, on any device. Alternatively, on the Google Play flavor, you can connect your Google Drive account to make periodic backups of your data and restore it.

Speye is completely free to use and is open source, but contains ads on the Google Play flavor. You can make a 1-time purchase on Google Play to remove ads forever. Alternatively, you can get the ad-free FOSS version from F-Droid (note: the F-Droid build lacks Google Drive integration due to requiring Google Play Services).

Security Questions

Speye does not store any remote data by itself and saves your notifications in your local storage. On the Google Play flavor, Google AdMob services may use your account data for targeted ads, which is not controlled by Speye itself. The F-Droid build contains no AdMob or Google tracking.

By default, all data stays on your device. On the Google Play flavor, if you enable Google Drive Backup, an encrypted .spy file is stored in your private app data folder. A .spy file only contains saved notification data such as texts and attachments.

Speye doesn't and will never share your personal data. However, if someone copies your .spy backup, they can import it on their phone to view your notification history.

Miscellaneous Questions

In the Settings page, click the Speye logo 5 times.

From the debugging options, enable the "Enable logging" option, then proceed with your desired action (import/export, cloud login etc.). In the activity logs, any error should now be visible. Copy them and share them with me through the contact option on the Settings page.

From the debugging options, enable the "Show Test Button" option and return back to the History page. You will now be able to access the test button to send yourself different types of test notifications.