Privacy Policy

1. SnappFeed scope

This part of the Policy covers the native SnappFeed location-based journal and the tools integrated directly into it. SnappFeed lets you create local map memories using:

• photos captured with the camera or selected from your photo library;
• images downloaded from an HTTPS image URL you provide;
• HTML content entered and previewed by you;
• titles, descriptions, timestamps, and selected map locations.

The sections below describe these local features and the native analytics, diagnostics, maps, and notification tools used by SnappFeed.

2. Local journal, image URLs, and HTML

When you create a local memory, the App may store the following in its private device storage:

• photos captured or selected by you;
• a locally cached image downloaded from a URL you enter;
• geographic coordinates selected by you or obtained with your permission;
• titles and descriptions entered by you;
• HTML content and a locally generated snapshot preview, if you use the HTML feature;
• local file references, timestamps, onboarding status, and app preferences.

When you enter an image URL, the App connects to that URL, checks that it uses HTTPS and returns a supported image within the App's size limit, then saves a local copy. The image host necessarily receives your IP address and standard request metadata. SnappFeed does not upload the resulting local copy to a SnappFeed-operated storage server.

HTML you enter is stored locally. The App previews it with JavaScript and website storage disabled, then creates a local image snapshot for its map marker. Your HTML, snapshot, journal photos, titles, descriptions, and saved memories are not uploaded to a SnappFeed-operated storage server. The publisher does not have direct remote access to content that remains only in the App's private storage.

Locally stored data may be included in a device or cloud backup if you enable a backup service. Backup copies are controlled by you and the relevant platform or backup provider.

3. Device permissions

Camera

Camera access is used when you choose to take a photo for a local memory.

Photos

Photo-library access is used when you choose an existing image. Where supported, a system photo picker lets you choose specific images. The native journal does not scan your library in the background.

Location while using the App

Within the SnappFeed journal, location can be used to:

• show your current position and associate a map point with a local memory;
• let you choose where a photo, downloaded image, or HTML memory appears on the map.

The App does not request continuous background location access.

Notifications

Notification access is used to deliver enabled alerts and open relevant links in the App. You control alert presentation in iOS or Android settings.

You can deny or revoke permissions in device settings. A feature that depends on a denied permission may not work, but unrelated features should remain available.

4. Analytics, diagnostics, and maps

The current App includes the following SDKs and services:

Firebase

Google Firebase Analytics, Crashlytics, Installations, and Cloud Messaging can process App interactions, app-installation and device identifiers, notification interactions, device and operating-system information, crash stack traces, application state, performance or transport metadata, and related diagnostics.

AppMetrica

AppMetrica can process app interactions, device and app metadata, coarse location, technical or diagnostic information, purchase-related signals supported by the SDK, and other analytics data. The App reports events such as notification receipt or click, store-review requests, configuration failures, and page-load failures.

Google Maps Platform

Google Maps Platform provides map content. It can process map interactions, device identifiers, request metadata, crash and performance information, IP address, and location-related information needed for the map feature you use.

5. Push notifications

Apple Push Notification service or Google push services issue a device token, and Firebase Cloud Messaging issues an FCM registration token associated with an app installation. SnappFeed also integrates AppMetrica Push for notification delivery and measurement.

Notification payloads and interactions may be processed for delivery, display, navigation, analytics, security, and troubleshooting. You can disable notification alerts in device settings. Disabling alerts may not immediately invalidate an existing registration token; uninstalling the App or token rotation normally causes it to expire or be replaced.

6. SnappFeed service providers and disclosures

Information may be processed by or disclosed to:

• Google, for Firebase and Google Maps Platform;
• AppMetrica, for analytics, diagnostics, and push messaging;
• Apple, for the App Store, device services, push notifications, and optional backups;
• GitHub Pages, for this Policy's public hosting;
• the host of an image URL you choose, when the App downloads that image;
• authorities or other parties when required by law or necessary to protect rights and safety.

These providers process information under their own terms, privacy notices, and contractual obligations.

• Google Privacy Policy
• Firebase privacy and security information
• Google Maps Platform privacy information
• AppMetrica App Store privacy information
• Apple Privacy Policy
• GitHub Privacy Statement

7. Purposes of processing and legal bases

Information is processed to:

• provide local photo, image URL, HTML, and map-memory features;
• maintain local App state and preferences;
• deliver and measure notifications;
• measure use, diagnose failures, prevent abuse, and improve reliability and performance;
• comply with legal duties, resolve disputes, and enforce applicable terms.

Depending on the feature and your location, processing may rely on your consent, performance of a contract or requested service, legitimate interests such as security and service improvement, or compliance with law. You can withdraw permission-based consent through device settings or the controls described below. Withdrawal does not affect processing already lawfully completed.

8. Advertising, sale, and tracking

The App publisher does not sell your local journal content or personal information to data brokers. The local-journal feature does not use your photos, downloaded images, HTML, or saved memories for advertising.

The current iOS native App does not ask for App Tracking Transparency permission and does not intentionally use the Apple advertising identifier to track you across apps and websites owned by other companies. Analytics, notification, and device identifiers are used for the purposes described in this Policy.

9. Retention and deletion

• Local memories: photos, downloaded images, HTML, preview snapshots, titles, descriptions, and map points remain on your device until you delete them, clear App data, uninstall the App, or erase the device. Backup copies follow your backup provider's schedule.
• Local state: onboarding and preferences remain until replaced, cleared, or removed with the App.
• Push identifiers: remain usable until rotated, invalidated, deleted by the relevant service, or no longer needed for notification delivery.
• Analytics and diagnostics: are retained under the configured Firebase, AppMetrica, and Google Maps retention settings for as long as needed to provide, secure, measure, and improve the native App, after which they are deleted or aggregated.

The SnappFeed journal does not create a server-side SnappFeed account. Deleting a memory removes its active local record and associated locally managed content, subject to platform storage and backup behavior.

10. Your choices and privacy rights

You can:

• deny or revoke Camera, Photos, Location, and Notification permissions in device settings;
• delete individual local memories or remove local App data by uninstalling the App;
• manage iCloud, device, or other backup settings;
• contact the App publisher with a privacy request or objection.

Depending on applicable law, you may have rights to access, correct, delete, restrict, port, or object to processing, withdraw consent, or complain to a data-protection authority. To make a request about data controlled by the App publisher, email zakezfayaz@outlook.com. We may need enough information to verify and locate the relevant records. We may not be able to identify records that are stored only on your device or retained only in aggregated or pseudonymous form.

11. Security and international processing

The App relies on iOS or Android private storage, transport security, access controls, and service-provider safeguards. HTML previews run with JavaScript and website storage disabled, and remote images are accepted only from supported HTTPS URLs within configured limits. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed. Protect your device, passcode, platform account, and backups.

Providers may process information in countries other than your own. Where required, the responsible party uses contractual, legal, or organizational safeguards for international transfers.

12. Children's privacy

SnappFeed is not specifically directed to children. The App publisher does not knowingly use the local journal to collect children's personal information on a SnappFeed-operated server. Parents and guardians should use device parental controls and supervise a child's use of photos, image URLs, HTML, location, maps, and notifications.

13. Changes and contact

This Policy may be updated when SnappFeed features, permissions, SDKs, service providers, or legal requirements change. The date at the top will be revised. Material changes may also be communicated in the App or on the store listing.

For questions or requests about the native App, contact:

Zakez Fayaz
Email: zakezfayaz@outlook.com