Privacy policy
How ExactAgo handles user data
ExactAgo is designed as a static, browser-based app. By default, it does not operate its own backend for storing your personal photo library.
1. Data you choose to add
When you add photos from your device, from Google Photos, or from another supported import service, the app stores the selected photo data, titles, timestamps, and related metadata in your browser on the current device. This local data is used to power the album view, countdowns, and photo frame.
2. Connected photo services
If you use a connected photo service, the app requests only the credentials and access needed for that specific import flow. For example, the Google Photos flow uses Google credentials and the Google Photos Picker scope to fetch only the photos you explicitly select. It does not request write access back to your Google Photos library.
3. Local storage and preferences
ExactAgo stores application data in your browser, including the local album, titles, selected language, mosaic preferences, and certain photo-view settings. This data stays on the device and browser profile you are using unless you clear it, export it, or move it yourself.
4. Export and import files
If you export your album, the resulting file contains the photo data and metadata needed to restore your local album later. If you share or upload that export file elsewhere, you are responsible for that action and the privacy implications of the destination.
5. What the app does not do by default
This app does not, by default, send your local album to an application server operated by ExactAgo. It also does not create a separate user account database for your photo collection. The photos you add remain in your browser unless you deliberately export or transmit them.
6. Third-party services and hosting
The app may depend on third-party services such as Google Identity Services and the Google Photos Picker API when you use those import features, and future versions may support other photo services as well. If this site is hosted by someone, that hosting provider may still collect standard web server logs or analytics outside the app itself. If you deploy the app yourself, you are responsible for the hosting environment and any data collection introduced there.
7. Your choices
You can remove photos from the local album, clear browser storage, revoke connected service access such as Google access, or stop using any import flow at any time. Because the app is local-first, many privacy controls are directly in your hands on the device where the data lives.