Privacy policy
FlickFiled privacy policy
Effective date: November 10, 2026
FlickFiled is developed and published by Stockedit LLC (legal business name: stockedit llc). It helps you review and route photos and videos on your Android device. This policy describes the app's handling of your information.
Media access
You choose which photos and videos Android allows FlickFiled to read. FlickFiled reads media content and metadata such as filename, type, size, location within device storage, and modification information to preview files, remember review progress, copy selected items, and check that the source has not changed.
Transfers you choose
FlickFiled sends media only when you route it to a destination. Google Drive and Google Photos receive the items you choose to upload. OneDrive and Dropbox receive selected items within FlickFiled's app folder. Device-folder copies stay in the folder you select. Providers process account, connection, storage, and uploaded data under their own policies. Uploads count toward your provider storage and can use mobile data.
Google user data
Drive access is limited to files and folders you grant to FlickFiled. Google Photos access is limited to creating media and albums, and reading media and albums created by FlickFiled. Google data is used to provide the requested filing, destination selection, verification, and open-in-Photos functions. FlickFiled's use of Google API information adheres to the Google API Services User Data Policy, including its Limited Use requirements. FlickFiled does not sell Google data, use it for advertising, or use it to train artificial intelligence models.
Sharing and disclosure of Google user data
FlickFiled communicates directly from your device with Google LLC for Google authorization, Google Drive, and Google Photos. Google receives the local media you choose to upload and the information needed to create, locate, and check that upload. FlickFiled receives permitted folder or album names and identifiers and saved-item metadata, such as item identifiers, media type, processing status, and verification information, to provide those functions. Stockedit LLC does not receive your Drive or Photos media on its own servers or routinely have people read that media.
FlickFiled does not forward data obtained through the Drive or Photos APIs to Microsoft OneDrive, Dropbox, Google AdMob, its purchase-verification service, data brokers, or AI services. OneDrive and Dropbox transfers use the local files you separately choose on your device. When you select Open in Google Photos, Android passes the saved item's Google Photos link to the app or browser you choose. These Google-data transfers are limited to the filing and opening functions you request; FlickFiled does not share, transfer, or disclose Google user data to other parties for unrelated purposes. Advertising and purchase processing are described separately below.
Data protection
FlickFiled uses HTTPS/TLS encryption for its cloud API and purchase-verification requests, and its Android configuration disables cleartext network traffic. Local routes, history, Google item references, pending upload references, and temporary transfer snapshots are kept in Android app-private storage, protected by Android's app sandbox and device security controls. App-data backups are disabled. Google authorization is handled through Google Play services; FlickFiled does not request or store your Google password or write Google OAuth access tokens to its database or application logs. Other provider credentials use the authentication SDK or Keystore protection described below. Your original media and copies saved in a device folder or cloud service remain subject to that device's or provider's access controls.
Local storage and account access
FlickFiled stores routes, theme preferences, review progress, transfer status, source references, and destination receipts on your device. A private temporary media snapshot and transfer checkpoints may be retained while a transfer is pending, interrupted, or awaiting resolution. Snapshots are released after verified completion or Undo. History can remain on your device so you can inspect actions and request Undo. Cloud credentials are handled through Google authorization services, Microsoft's authentication SDK, or Android Keystore-protected Dropbox storage. Android backups of FlickFiled app data are disabled.
Retention and deletion of Google user data
FlickFiled does not keep a server-side copy of your Drive or Photos media or library. Folder and album lists are loaded into app memory for destination selection. The selected destination names and identifiers, saved-item identifiers, transfer receipts, and recovery information can remain in local routes and history for as long as you retain FlickFiled's app data. History has no automatic time-based deletion. Google OAuth credentials are managed through Google's authorization service; temporary upload references needed for an unfinished transfer are stored in the app's private recovery records. Private media snapshots are removed after verified completion or Undo; interrupted or unresolved transfers can retain a snapshot until you finish or undo them.
To remove FlickFiled's local routes, history, Google item references, and temporary files, clear FlickFiled's storage in Android Settings or uninstall it. Finish pending actions and restore wanted trashed originals first, because this also removes local recovery information. You can revoke FlickFiled's Google access in your Google Account's third-party connections settings; future requests then require authorization again. Removing the app or revoking access does not delete items already uploaded to Google Drive or Google Photos. Manage and delete those copies in the relevant Google service; its retention and trash rules apply. Undo also keeps destination copies. Contact stockeditllc@gmail.com for help with these privacy or deletion controls; do not send passwords, authorization tokens, or private media.
Advertising in the free version
For the initial 13+ release, every ad request receives Google's teen age treatment, which disables personalized ads and remarketing. FlickFiled does not ask for or store your birthday. The separate ad-content limit is G. These settings do not replace Google's regional privacy choices or eliminate all advertising data processing.
The free version can display Google AdMob banner advertising. Google's advertising SDK collects and shares information such as IP address (including approximate location), device or account identifiers, ad interactions, and diagnostic information for advertising, analytics, and fraud prevention. Google's consent platform requests privacy choices where required, and Ad privacy choices is available in Settings when required. Ads are requested only after the consent platform allows them. FlickFiled does not send your photos, videos, filenames, media locations, cloud credentials, or filing history to the advertising SDK as targeting information. Pro removes ads. No additional app analytics SDK is included.
Purchases and verification
Google Play handles Pro payment and purchase history. FlickFiled does not receive your payment-card details. FlickFiled's purchase-verification service receives a Google Play purchase token and checks the exact app, product, payment state, and acknowledgement with Google before granting Pro. Tokens are processed for this check, not written to application logs or a purchase database, and are not included in support messages. The service receives no photos, videos, cloud account credentials, or routing history. Hosting and payment providers may retain technical connection or transaction information under their own policies. The app caches the verified entitlement on your device and checks purchases again to support restoration and detect revoked access.
Servers and support
FlickFiled does not operate a server that receives your photos or videos. Authentication, advertising, payment, hosting, and storage providers may process technical information needed to operate their services. FlickFiled does not sell your personal information or attach media, tokens, or transfer logs to support messages. Contact Stockedit LLC at stockeditllc@gmail.com for support or privacy questions.
Trash and Undo
Originals are kept by default. If you enable cleanup for a direction, FlickFiled checks filing and asks for Android consent before moving an unchanged original to recoverable trash. Google Photos can confirm saved-item availability and readiness but cannot verify an exact original-file backup. Android controls trash expiration. Undo stops pending cleanup or requests restoration, and retains destination copies. FlickFiled never calls permanent source deletion.
Your controls
Change media access through FlickFiled or Android Settings. Disconnect OneDrive or Dropbox in the destination settings; revoke provider consent through that provider's connected-app or account settings. Disconnecting pauses unfinished transfers and retains originals and saved copies. Manage uploaded items directly with their provider. Clearing FlickFiled storage or uninstalling removes local preferences, history, and recovery information; complete pending actions and restore wanted items first. Removing FlickFiled does not remove copies already saved to a destination.
Contact and changes
Contact Stockedit LLC at stockeditllc@gmail.com or use Contact support in Settings for privacy questions. Future changes will be reflected in the effective date and the policy available in the app and on its public website.
Developer
Stockedit LLC