YOUR CHOICES, CLEARLY EXPLAINED
Privacy Policy
Effective: October 19, 2026. Last updated: October 23, 2026. Cosine Studio operates Swipe Photos and this website. The Android app is named Swipe Photo (com.photoswipe.app). This policy explains what information is handled, why, who receives it, and the choices available to you.
1. Scope and contact
This policy covers our website and the Android and iOS editions of the product. Features and information handling differ by platform, version, permissions and settings; the relevant sections apply to the features you use. No product account is currently required. For privacy questions, requests or complaints, contact Cosine Studio at easysoftware2022@gmail.com.
2. Your photos, videos and local records
With your system authorization, the app reads accessible photos and videos, thumbnails and media information such as identifiers, dimensions, duration, file size, creation time and embedded metadata to display and organize your library. Our app does not operate a developer-hosted photo or video upload, backup or facial-recognition service. Original media remains managed by your device and any photo-cloud service you separately use.
Viewed-media identifiers, pending review or deletion selections, cleanup statistics, settings and reminder choices are stored locally to preserve progress and provide the corresponding features. Widgets may keep a local cache of authorized media for display. These records are not a separate copy or backup of your library.
3. Permissions and your actions
Photo and video access may be limited to selected items or your full library where supported by the operating system. Notification permission is used for optional local reminders. You can decline or revoke permissions in system settings; related features may then be unavailable. Membership does not expand permissions. Browsing or marking an item does not by itself complete deletion: the app provides review and the applicable system confirmation before a supported deletion action.
On Android, deleting reviewed items uses the system media trash request. Recovery, retention and space reclamation are controlled by the system or media provider. On iOS, the system photo-library deletion rules apply. Check your system trash or Recently Deleted album and maintain independent backups of important media.
4. Photo locations, maps and sharing
Some photos contain sensitive capture coordinates in EXIF metadata. Android may request access to original media location to read those existing coordinates; the app does not request real-time device location. In iOS, displaying a place name for geotagged media or displaying or opening a map may send the photo’s capture coordinates to Apple Maps or Apple’s reverse-geocoding service. This may happen when a place label appears, without opening a map. The app does not send these capture coordinates to Firebase. On other platforms, resolving a place name may send coordinates to the operating system’s geocoding provider, and opening a map passes the selected location to the map provider. These services apply their own privacy rules.
When you initiate sharing, the system shares the selected media, which may include embedded metadata, with the app or recipient you choose. That recipient may retain or forward it under its own practices. Check the content, metadata and recipient before confirming. We do not receive a copy merely because you use system sharing.
5. Usage analytics, crash diagnostics and configuration
The Android release integrates Google Firebase Analytics and Crashlytics to understand feature use, measure stability and investigate failures. Collection is enabled by default in the current release build; debug builds disable it by default. Depending on the service, information may include app-instance or installation identifiers, device and operating-system details, app version, usage events, timestamps, crash stack traces and diagnostic state. Google may also process network information such as IP addresses while providing these services.
Our app-defined analytics and diagnostic fields do not contain photo or video content, filenames, media URIs or EXIF coordinates. The current Analytics configuration disables advertising-identifier collection and default advertising-personalization signals. These limits do not mean the analytics and crash services process no information.
Use “Usage analytics and crash diagnostics” in Android app settings to control the corresponding Firebase collection together. Restart the app for crash-diagnostic changes to fully take effect. Turning collection off affects future collection; it does not withdraw reports already uploaded. It does not revoke photo access or clear your local review progress. Contact us for requests about previously processed information.
In iOS versions that provide Firebase Analytics, Crashlytics, Remote Config and paywall experiment attribution, the corresponding optional data collection is off by default. After you actively turn on “Usage analytics and crash diagnostics” in app settings, these services may be used to understand feature use, diagnose crashes and errors, retrieve paywall configuration, and evaluate paywall layouts and purchase flows.
Depending on the service and automatically recorded events, iOS information may include usage events, durations and timestamps, device and operating-system details, app version, app-instance or installation identifiers, purchase events, crash stack traces and diagnostic state. Google may process IP addresses or other network information and infer an approximate region. Our custom paywall events use fixed screen or feature actions, paywall entry points, selected plans, layout variants, experiment and configuration identifiers, purchase-flow results and verified purchase-conversion events.
The iOS app does not upload photos or videos, media identifiers or filenames, photo capture coordinates, or PhotoKit cloud identifiers to Firebase. Transaction identifiers used by our attribution logic are stored locally and are not included as custom analytics or attribution parameters. The current iOS configuration does not collect advertising identifiers, and the app does not set a Firebase user ID. App-instance or installation identifiers can still relate information to the same installation.
You can turn the same iOS setting off. New Analytics and paywall-attribution events then stop; crash-collection changes fully take effect after restarting the app. A request already in progress may still complete. Turning collection off does not withdraw information already sent to Google, revoke photo access or erase local review history. If a later release introduces additional processing purposes, we will update this notice and provide the relevant disclosures and choices before enabling them.
6. Advertising status
The Android package includes Google Mobile Ads and its consent-support SDK, but advertising is currently disabled: the app does not initialize advertising or request or display ads. The website and current iOS implementation do not use an advertising SDK. If advertising is enabled in a future release, we will update the relevant notice and provide the disclosures and choices required for the applicable region before enabling the associated processing.
7. iOS iCloud and store purchases
The iOS app can optionally synchronize PhotoKit cloud identifiers for viewed photos, videos and screenshots, grouped by category, through your Apple iCloud account where the feature is available to members. This is off by default and is not a backup of original photos or videos. Apple handles the iCloud service and may download iCloud photo content through its Photos services. Turning off history synchronization or resetting local history does not by itself erase existing iCloud records; use available Apple account or iCloud controls and contact us if you need assistance. Android does not currently provide this iCloud feature.
Where purchases are available in your released version and store region, Google Play handles Android subscriptions and Apple handles iOS purchases. The app obtains product and purchase information, transaction or purchase tokens, purchase and acknowledgement status, and membership entitlement information to complete purchases, restore access, and refresh entitlement when the app returns to the foreground. Android purchase tokens are handled in app memory and exchanged with Google Play; they are not sent to a developer-operated backend. Store providers process your store-account and payment information. We do not receive your full payment-card details or store password.
8. This website and support email
This website has no account, media-upload form, advertising or analytics SDK. Firebase Hosting delivers it and may process technical request data such as IP address, request time and browser information for delivery, security and operation. If you explicitly change language, the site saves only that preference in your browser’s local storage. Clear this site’s browser data to remove it; the preference is not sent to our database.
If you email us, we receive your email address, message and attachments you choose to send to answer questions, resolve problems and handle rights requests. Our email service provider also processes that correspondence. Please send only necessary details such as platform, app version and a description of the problem; do not send private media, passwords or full payment credentials.
9. Purposes, service providers and transfers
We use information to provide the features you request, preserve your choices, improve reliability, respond to you and meet legal obligations. Where applicable law requires a legal basis, processing is based on providing the requested service, a lawful legitimate interest, legal obligations, or your consent where required. A device permission or acceptance of general terms does not replace any legally required consent for a separate purpose.
We do not sell your personal information or share it for cross-context behavioral advertising. Information is handled by the service providers described above when needed for their services, by recipients you select, or where disclosure is legally required or necessary to protect lawful rights. Google, Apple and email providers may process information outside your country under their documented arrangements. Applicable transfer protections and your local rights continue to apply. We do not promise a particular processing country.
10. Retention, reset and deletion
Local app records remain until the relevant feature clears or replaces them, you clear app storage, or you uninstall, subject to any separately enabled platform synchronization or backup. Resetting browsing history removes viewed-history records; it does not clear Android cleanup statistics or pending review selections. Clearing app data or uninstalling does not delete photos from the system library, cancel a store subscription, or erase existing iCloud or provider-held records.
We retain support correspondence only as long as reasonably needed to resolve the request, maintain necessary service records or comply with law, then delete or anonymize it. Firebase analytics and crash information follow the applicable service’s retention and deletion controls and our configured settings; Google Play and App Store purchase records follow their respective providers’ controls and legal requirements, and iCloud records follow Apple’s controls. Turning off collection does not erase previously uploaded data. You may request deletion through our contact address; we will assess what we control and can identify, explain any lawful retention, and assist with provider controls where relevant.
11. Your rights and information security
Depending on applicable law, you may request access, correction, deletion, restriction, portability, withdrawal of consent or objection to processing, and complain to your competent privacy authority. Exercise in-app and system choices directly or email us. We may ask for proportionate information to verify a request, but do not require private photos or passwords. We respond within applicable legal time limits. Withdrawing consent does not make earlier lawful processing unlawful, and necessary local features do not depend on optional analytics.
We use reasonable access restrictions, local platform protections and the security measures of the service providers we use. No storage or transmission method is absolutely secure. Protect your device and accounts; if you suspect a privacy or security problem involving this product, contact us with enough information to investigate safely.
12. Children and policy changes
The product is a general-purpose media-organizing tool and is not directed to children under 13 or the relevant local minimum age. We do not knowingly solicit their personal information. Where required, minors must use the product with a parent or guardian’s permission. If you believe a child has sent us personal information improperly, contact us so we can review and take appropriate action.
We will update this page and its date when practices change. Material changes will receive a clear notice, with additional consent requested where required before the changed processing begins. Questions about this policy or a platform-specific feature can be sent to Cosine Studio at easysoftware2022@gmail.com.