SnagFlow

SnagFlow Privacy Policy

Effective date and last updated: October 2, 2026

1. Introduction

SnagFlow is a local-first field inspection and reporting tool provided by an individual developer. This Privacy Policy explains how SnagFlow accesses, processes, stores, exports, and protects information relating to you, and how you can manage that information.

The current version of SnagFlow does not require a SnagFlow account and does not provide developer-operated cloud synchronization. Project data is stored locally on your device by default and is not automatically uploaded to a SnagFlow-operated server. Release builds do send limited usage events, crash diagnostics, and remote-configuration request information to Google Firebase, as described below.

When access to the camera, photos, or similar device resources is needed, the App will request permission through the operating system. You may refuse or revoke permission, but the related feature may then be unavailable.

2. Information Processed by the App

Depending on the features you choose to use, SnagFlow may process the following information locally on your device.

2.1 Local profile information

You may enter an inspector name, company name, email address, telephone number, inspector photo, company logo, and default signature. This information is used to prepare, display, and export inspection reports.

2.2 Project and inspection information

You may create and store project names, descriptions, inspection locations or room locations, customer names, reference numbers, inspection company and inspector details, project summaries, custom fields, issue titles and descriptions, issue locations, assignee information, recommended actions, priorities, statuses, due dates, cost estimates, currencies, and other report content.

You are responsible for ensuring that you have a lawful basis and any necessary authorization to process customer details, addresses, contact information, signatures, site records, and other third-party information entered into the App.

2.3 Photos and media information

When you take a photo or select an image from the system photo library, SnagFlow processes the selected image, previews, thumbnails, annotations, and necessary media metadata such as file name, MIME type, dimensions, file size, creation time, file hash, and photo-library asset identifier. This information is used to document site issues, manage inspections, and create reports.

SnagFlow does not record audio while taking inspection photos. A photo is copied to the system photo library only when you enable or actively use the relevant save option.

2.4 Signatures

You may add inspector or customer signatures. A signature may be stored locally as an image or stroke data and may be included in a report or project backup. Because signatures may identify an individual, you should use this feature only with appropriate authorization.

2.5 Diagnostic and crash information

Release builds use Google Firebase Analytics, Crashlytics, and Remote Config to measure feature use, diagnose crashes and errors, and retrieve app settings. Analytics events may include screen views; feature and button use; selected camera or photo-library source; report export or sharing type and item count; language and theme; project and issue identifiers generated by the App; and issue status or priority. Search events record the search length and category, not the search text.

Firebase may also process pseudonymous app or installation identifiers and app, device, operating-system, language, country or region, and time-zone information. Crashlytics may receive crash and error stack traces, related app state, and device or operating-system diagnostics. Remote Config requests may include the app version, operating-system version, language, country or region, time zone, Firebase App ID, and bundle identifier. Firebase SDK data is sent when network access is available. Project names or descriptions, photos, signatures, and PDF contents are not intentionally included in Firebase events or crash-report logs.

SnagFlow also stores certain diagnostic logs locally, such as launch events, screen routes, interface actions, feature and subscription states, error messages, crash stack traces, thread names, and limited runtime information. The App attempts to redact common tokens, passwords, API keys, cookies, telephone numbers, email addresses, and local file paths from local logs. These local diagnostic logs are not automatically uploaded; in release builds, they are retained for up to 15 days and may be viewed, cleared, exported, or shared by you where the relevant controls are available.

2.6 Purchases and subscriptions

Optional Pro subscriptions are processed by the app store and payment system associated with your device. SnagFlow does not directly collect or store card numbers, payment passwords, or complete payment details. The App may receive and locally store a product identifier, plan type, purchase status, restoration result, and subscription entitlement status to provide or restore Pro features.

3. Device Permissions

SnagFlow may request the following permissions when required by a feature you choose to use:

  • Camera: to take photos of site issues.
  • Photos or media: to select inspection photos and, when you choose, save photos to the system photo library.
  • Legacy Android storage: on certain older Android versions only, to read a selected image or complete a file save or export operation.

The current version does not request microphone, location, contacts, telephone, SMS, Bluetooth, calendar, or body-sensor permission for its core features. You can revoke granted permissions in the device settings at any time. Features that depend on a revoked permission may no longer work.

4. Purposes of Processing

SnagFlow processes information only as necessary to:

  • create and manage inspection projects and issue records;
  • capture, select, annotate, and organize site photos;
  • generate, preview, export, and share PDFs, images, spreadsheets, data files, and project backups;
  • store local profiles, templates, language, theme, and other preferences;
  • provide, verify, and restore subscription entitlements;
  • measure feature use and diagnose errors, crashes, and operational problems using Firebase services;
  • retrieve remote app configuration; and
  • maintain the security, stability, and operation of the App.

5. Storage and Retention

Project and issue records, photos, annotations, signatures, reports, templates, local profiles, settings, and cached entitlement information are stored by default in the App's local database, private application directory, or temporary directory.

  • You may delete projects, photos, signatures, reports, logs, or other content through the relevant features in the App.
  • Local diagnostic logs in release builds are retained for up to 15 days and are then deleted or overwritten through the App's cleanup process.
  • Firebase service data is retained and deleted under the applicable Google Firebase service settings and retention policies; retention periods may vary by service.
  • Uninstalling the App will generally remove information in its private application directory. Copies already exported, shared, saved to the system photo library, included in a device backup, or stored by another app will not automatically be deleted.
  • Temporary files and caches may be removed earlier by the App or operating system.
  • Transaction records held by an app store are retained by that store according to its legal obligations and privacy policy.

You should export any backup you wish to keep before uninstalling the App, changing devices, or clearing application data.

6. Sharing and Disclosure

SnagFlow does not sell personal information, provide personal information to data brokers, or use project data for targeted advertising or cross-app or cross-website tracking.

Information may leave SnagFlow's local storage in the following circumstances:

  1. Export or sharing initiated by you: When you share a PDF report, photo, Excel, CSV, JSON, project backup, or diagnostic log, the selected content is sent through the system share sheet to the email app, cloud storage service, messaging app, or other recipient selected by you. The recipient processes the information under its own privacy policy.
  2. App store services: Google Play or the Apple App Store may process product queries, purchases, purchase restoration, subscription status, version checks, and related technical information. Such processing is governed by the relevant platform's privacy policy.
  3. Google Firebase: Release builds send the limited usage events, crash diagnostics, identifiers, and device or app information described in Section 2 to Google Firebase for analytics, crash reporting, and remote configuration. Google processes this data under its own terms and privacy information. This telemetry is separate from project files and is not sent to a SnagFlow-operated project-data server.
  4. Legal and safety requirements: The developer may comply with valid legal process where required by applicable law or where necessary to protect the lawful rights and safety of users, the public, or the developer. Because SnagFlow does not operate a server for project data, the developer generally cannot access project content stored only on your device.

7. International Data Processing

SnagFlow does not automatically upload local project data to a developer-operated server. Google Firebase and app store providers may process the limited information described in this policy outside your country or region. A service you choose through the system share sheet may also process a file internationally. Each provider's privacy information describes its processing locations, safeguards, and available rights.

8. Security

SnagFlow uses measures such as operating-system application sandboxing, local-first storage, permission controls, data minimization, and log redaction to reduce information risks. Communications with external app store services use the security mechanisms provided by those services.

No method of storage or transmission can be guaranteed to be completely secure. You should protect your device passcode and device account, safeguard exported files and backups, and select sharing recipients carefully.

9. Your Choices and Rights

Depending on applicable law, you may have rights to access, correct, delete, restrict processing of, withdraw consent to, export, or complain about the processing of personal information. Because project data is stored locally on your device by default, you can normally view, correct, export, or delete it directly in the App.

You may also:

  • revoke camera or photo permission in the system settings;
  • clear local diagnostic logs;
  • delete projects, photos, signatures, reports, and other local content;
  • clear the App's data or uninstall the App; and
  • contact the developer with questions or a request available under applicable law.

The current version does not provide SnagFlow account registration, so there is no SnagFlow account-deletion process. To delete information already exported or shared with a third party, remove it from the relevant storage location or contact that third party.

10. Children's Privacy

SnagFlow is a productivity tool for field inspections, property, construction, maintenance, and related professional work. It is not designed specifically for children. The developer does not knowingly collect children's personal information through a developer-operated account or project-data server. Release builds' Firebase usage and diagnostic processing is described in this Policy. If you believe a child has used SnagFlow to process personal information without appropriate authorization, please contact the developer using the email below.

11. Third-Party Services

SnagFlow may use or access the following third-party platform features:

  • Google Play Billing and the Google Play Store;
  • the Apple App Store, Apple's app-version lookup, or in-app purchase services;
  • Google Firebase Analytics, Crashlytics, and Remote Config. See Firebase privacy and security information for information about Google's handling of Firebase service data; and
  • third-party apps or services you select through the system share sheet.

Third-party services process information under their own terms and privacy policies. This Privacy Policy does not govern processing independently determined by a third party.

12. Changes to This Policy

The developer may update this Privacy Policy to reflect changes to the App, technical implementation, applicable law, or platform rules. The updated policy will be posted on this page with a revised “Last updated” date. Where required by law or platform rules, material changes affecting your rights will also be communicated through an in-app notice or another appropriate method.

13. Contact the Developer

Developer type: Individual developer
App: SnagFlow
Privacy and support email: weiyifang001@outlook.com

If you have a question about this Privacy Policy or SnagFlow's information practices, email the developer with “SnagFlow Privacy Request” in the subject line.