Effective date: 24.09.2026 App: TripSlide (com.ground.tripslide), Android Developer: Kholodkov Maksim

This document describes what data the TripSlide app (the “App”) processes and how it is used.

1. At a glance

• The App has no sign-up and no accounts — we do not collect your name, e-mail or phone number.
• We run no servers of our own. Photos, captions and rendered slides are created and kept on your device and are never uploaded by us.
• We use two third-party services: Firebase Analytics (Google) to understand which features are used, and RevenueCat to operate the Pro subscription.
• The App contains no ads, no advertising SDKs, and we never sell your data.

2. What we process

2.1. Photos

• The App reads gallery photos only when you act: “From recent photos” takes your latest shots, “Your own carousel” uses the ones you pick in the system Photo Picker.
• Reading recent photos requires READ_MEDIA_IMAGES (on Android 12 and below, READ_EXTERNAL_STORAGE). The Photo Picker path needs no permission at all.
• Every photo used in a carousel is copied into the App’s private storage (filesDir/carousel_media), because the picker only grants temporary access. Those copies are visible to the App alone.
• Rendered slides are written to the shared gallery (Pictures/TripSlide/<carousel name>/<platform>/) and, for LinkedIn, a PDF to Download/TripSlide/<carousel name>/ — only when you tap Save. In shared storage the files are visible to other apps: that is the point of exporting.
• Photos are never uploaded to our servers, never embedded in analytics events and never leave your device through us.

2.2. Voice and microphone

• RECORD_AUDIO exists so you can dictate captions.
• Audio is captured only while you hold the microphone button. The App does not store recordings — they are handed straight to the system speech recognition service.
• Recognition is performed by the speech service of your operating system (android.speech.SpeechRecognizer). On most devices that is a Google service, and it may send audio to Google servers and handle it under its own privacy policy. We do not control that and never receive the audio.
• Only the recognised text comes back, and it becomes your caption. The text is stored locally in the App’s database and is baked into the image when you export.