Snapisodes Download

Privacy policy

Effective 26 September 2026, last updated 10 October 2026.

Who we are

Snapisodes is made by ConsultX s.r.o., IČO 08973288, Dolní Dobrouč 149, 561 02 Dolní Dobrouč, Česká republika (the data controller). Contact: support@consultx.cz.

What the app does with your data

Snapisodes keeps the episode name and your comment for every photo in the app's database on the phone. It never writes them into your photo or video files and never changes your originals, so a comment does not travel with a photo when you share or copy it.

No account with us, no ads

The app has no server of its own, sends nothing to us and contains no advertising or analytics of its own. We cannot see your photos, episodes or comments. Data goes only to the recipients listed under Network use, and only when you use the feature concerned. The app never sends diagnostics by itself; it only prepares a text file (app and Android version, phone model, language, time zone, free space, record counts, the last crash and recent errors – no photos, file names, places or comments) that you can send yourself by e-mail or another app.

Backup

The database of episodes and comments (with episode descriptions) is part of the Android backup to your Google account (processed by Google), if you have it turned on. The app also saves a backup file to Downloads/Snapisodes/Backup: daily, shortly after each change and on request; it keeps the last four automatic copies and never deletes the ones you made yourself. The file holds file names, sizes and capture times, episode names, comments, episode descriptions, your favourites, hidden labels and a few settings; it holds no photos, photo locations, home location or sign-in. It stays after uninstalling. On Android 11 and later other apps with photo access cannot read it; a file manager with all-files access, a computer connected over USB, an app that syncs your Downloads folder and, on Android 8–10, apps with storage permission can. On request the app also saves XMP files for your computer.

Network use

Only these features use the network, never our servers:

  • Episode map downloads map tiles from OpenStreetMap (tile.openstreetmap.org); the OpenStreetMap server learns your IP address and the area you look at, not your photos. Tiles are cached on the phone.
  • Dictation passes audio to the speech recognition service of your phone (typically Google); on-device recognition is preferred when available. It starts only after you tap the microphone.
  • Place name suggestions (off by default, turned on only with your consent) pass the GPS coordinates of a photo, rounded to two decimals (about 1 km), to the phone's place search (typically Google) to suggest a name and recognise trips. Automatic episodes and the route of an episode use it the same way. You can turn it off in Settings at any time.
  • Setting home by address (optional): the address you type is sent as typed to the phone's place search (typically Google's geocoding service). The home location itself stays only on the phone and is not backed up.
  • Delete from OneDrive too (off by default, Pro): after you sign in with your Microsoft account in the browser, the app talks directly to your OneDrive through Microsoft Graph (scope Files.ReadWrite, the narrowest Microsoft offers). The app works only in the folder you choose: it searches there by file name, compares the photo's checksum (for a JPEG possibly the image data, downloading the file for that) and after the waiting period moves the copy to the OneDrive recycle bin. It uploads nothing and deletes nothing for good. The sign-in is encrypted on the phone and not backed up. Disconnecting in Settings signs out; you can also revoke access at account.microsoft.com.
  • Publishing an episode to the cloud (optional, Pro): you upload an episode to a folder you choose yourself in OneDrive or Google Drive and share that folder with whomever you like; links and permissions are managed by OneDrive or Google Drive, not by the app. Only the episode's photos and videos are uploaded: a JPEG as a copy with the episode and comment inside the file (XMP), other formats unchanged; the original on your phone is not changed. For each target you can turn on Remove location: the copies then carry no GPS coordinates (a file from which the location cannot be removed safely is not uploaded). OneDrive uses the same sign-in as above; for a folder shared by someone else the app asks for the Files.ReadWrite.All permission. Google Drive uses your Google account with the drive.file permission: the app sees only folders it created or you picked for it and files it uploaded itself. The app never deletes anything in a target and never overwrites other people's files. The phone keeps the list of targets (folder, account) and of uploaded files (cloud ID, check data); it is not backed up. Uploaded copies stay in the cloud until you delete them there.
  • Pro purchase: Google Play handles the payment (Google Play Billing); the app only learns whether Pro is active.
  • Google ML Kit library (via Google Play services): Google Play services downloads the recognition model once; content recognition computes its labels on the phone and uploads no photos, but the library itself may send technical usage data (device, app, performance) to Google.
  • Sharing and other apps: whatever you share, open in another app or edit in an editor (photos, episode text, story, photobook, diagnostics file) goes to the app you choose; Open on map passes the photo's coordinates to the map app. The app copies nothing to the clipboard by itself.

Features that send nothing

Search by photo content recognises what a photo shows on the phone, with the model Google Play services downloaded; no photos are sent (see the note on Google ML Kit above). Import from Google Takeout reads only the files you pick. Temporary photos are written by the camera only into the app's private folder; they are not in the gallery, not backed up and delete themselves after the chosen time.

Shared episodes

Optional: it applies only if you create or join a shared episode (creating one is part of Pro).

What is exchanged. Only with the members of that episode, that is people you invited and whose phones you approved: the episode's photos and videos as originals, including the GPS location stored in them; comments together with the name of their author; the episode name, description and period; the display names members chose for themselves; and the public keys of the members' devices (private keys never leave the phone). Everyone you add can see all of this.

How. Everything is encrypted end to end on the phones and goes directly from phone to phone over Bluetooth and Wi-Fi (Nearby Connections, part of Google Play services), only while the app is open and the phones are near each other. This version has no server: nothing passes through us or anyone else, and we cannot read it. An invitation is a one-time QR code (valid 48 hours) that the other phone scans; both phones then show a 3-character verification code that you compare, and the founder (or a deputy) approves each new device. While searching, the app announces random names that change every few minutes and reveal nothing about the episode.

Where it is stored. The shared-episode database (shared.db: the log of changes, the member list and the keys, which are sealed with Android Keystore) lives in the app's private data on the phone and is not backed up. Received photos are saved in Pictures/Snapisodes and videos in Movies/Snapisodes, in a subfolder named after the episode; they appear in your gallery and other apps with photo access can see them like any other photo.

Leaving and removal. You can remove your own phone from a shared episode, and the founder (or a deputy) can remove a member or a device; the episode key is then changed, so a removed phone receives nothing new. What a member has already received stays with them: copies on their phone cannot be recalled, and the same goes for the copies you received from others.

Permissions for sharing. Camera: only to scan the invitation QR code inside the app; the picture is not stored or sent anywhere. Nearby devices (Android 12 and later): the Bluetooth and Wi-Fi connection to the other phones. On Android 8–11 the system requires the location permission for Bluetooth scanning; the app does not read your location through it. Optionally you can lock shared episodes with your fingerprint, face or screen lock.

Health Connect

Optional and off by default. After you allow it, the app only reads steps and distance from Health Connect (READ_STEPS, READ_DISTANCE) to show how far you walked during an episode. It writes nothing there. The data is not stored beyond the cache on the phone and is never shared, sold or used for advertising. You can revoke the access at any time in Health Connect.

Location

The app does not track your location. It only reads GPS coordinates already stored in your photos (map, place names, recognising trips for episode suggestions). They leave the phone only as described under Network use: rounded to about 1 km for place name suggestions, and the viewed area for the map. When you open a photo in another app, edit it there or set it as a wallpaper, the original file is passed on, including its location. A city-level place name may appear in the title or subtitle of a photobook PDF; the setting “Remove location when sharing and exporting” does not apply to it, but you can switch the place names off in the export dialog.

Permissions

Photos and videos (to show and organise your library), media location, microphone for dictation (only while you dictate), notifications for the ongoing episode, and optionally Health Connect steps and distance. For shared episodes also the camera (only to scan the invitation QR code), nearby devices (Bluetooth and Wi-Fi) and, on Android 8–11 only, location (the system requires it for Bluetooth scanning; the app does not read it), and optionally biometric unlock.

Pro purchase

Payment is handled entirely by Google Play. The app only learns whether Snapisodes Pro is active on your account. It never sees any payment details.

How to delete all data

We hold none of your data, so there is nothing to request from us; you delete everything yourself:

  1. OneDrive (if you use it): in Settings → Delete from OneDrive too choose Disconnect. This deletes the sign-in and the list of waiting photos. Also revoke the app's access at account.microsoft.com → Privacy → Apps and services. Photos the app already moved to the OneDrive recycle bin are removed from it under OneDrive's rules.
  2. Publishing to the cloud: in Settings → Publish targets choose Remove for each target; the app forgets the target and its list of uploaded files, but the uploaded copies stay in OneDrive or Google Drive, so delete them there yourself. Revoke Google access at myaccount.google.com → Security → Third-party apps with account access (Snapisodes); for Microsoft see step 1.
  3. Comments and photos: the app does not write comments into your photos and videos, so there is nothing to remove from the files; deleting the app's data (step 4) removes the comments from the phone. XMP files you exported yourself are covered in step 5.
  4. Data on the phone: uninstall the app, or in Android Settings → Apps → Snapisodes → Storage choose Clear data. This removes the database of episodes and comments, settings, caches, temporary photos, the OneDrive sign-in and the last crash file.
  5. Files outside the app: with a file manager or a computer, delete the folder Downloads/Snapisodes (backups, XMP files, photobooks). In your gallery, search for photos with _recovered in the name (copies of an original saved after an interrupted write) and delete them if you do not need them.
  6. Android backup in your Google account: turn backup off, or delete the phone's backup in the Google Drive app → Storage → Backups (this deletes the backup of the whole phone).
  7. Health Connect: the app writes nothing there; revoke access in Health Connect.
  8. Shared episodes: in the shared episode remove your phone (Remove device) or ask the founder to remove you; clearing the app's data or uninstalling (step 4) deletes the shared-episode database from the phone. Received photos and videos are ordinary files in Pictures/Snapisodes and Movies/Snapisodes: delete them in the gallery or with a file manager if you do not want them. Other members keep the copies they have already received and what you added; we cannot delete those.

The services listed under Network use (OpenStreetMap, the phone's place search and speech recognition, Google Play, Microsoft) process data under their own policies.

Retention

Episodes and comments stay until you delete them or uninstall the app. The episode and comment of a photo you delete stay in the app's database and in later backups, so they come back if you restore the photo from the trash or the cloud. The app deletes them by itself after 180 days, but only while it sees your whole photo library (full access) and no memory card it saw before is missing; you can remove them earlier in Settings → Backup → Delete records of deleted photos, or by clearing the app's data. Older backup files in Downloads stay until you delete them. The route cache stays until you clear it. The OneDrive deletion history is pruned automatically.

Legal basis and your rights

We process data so the app works as you installed it (performance of a contract) and, for optional features, on the basis of your consent, which you can withdraw at any time by turning the feature off. Because the app has no account and keeps your data only on the phone, you exercise your rights of access, rectification, erasure and portability directly in the app or by uninstalling. You can also lodge a complaint with a supervisory authority; in the Czech Republic that is the Office for Personal Data Protection (ÚOOÚ, uoou.cz).

Children

The app is not directed at children.

Changes

We will publish any change on this page with a new date.

Contact

ConsultX s.r.o., Dolní Dobrouč 149, 561 02 Dolní Dobrouč, Česká republika, support@consultx.cz.

Get it on Google Play