Privacy Policy - SubmitReady: Photo & PDF Tools
Last updated: 7 November 2026
Developer: Rwt Studios
Android package: com.ar.submitready
This Privacy Policy explains how Rwt Studios handles information when you use SubmitReady: Photo & PDF Tools ("SubmitReady"). SubmitReady prepares photos, signature images and PDFs on your device. No account is required.
1. Files you choose and information stored on your device
SubmitReady accesses files that you select through Android's file or photo picker. It processes their contents locally to crop, resize, convert and prepare images and PDFs. It does not scan your entire photo library.
Imported copies, filenames, edit settings, application kits and prepared outputs are stored in the app's private local storage. We do not upload these documents, images, signature contents or filenames to Supabase, Google AdMob or an app-operated document server, or include them in advertising requests.
The app also keeps local preferences, cached public settings, ad-frequency records and any temporary ZIP-access expiry so these features can work between visits.
2. Saving and sharing files
When you choose Save or Share, SubmitReady sends the selected prepared copy to the storage location or receiving app you choose. That location may be on your device or with a cloud provider. Its privacy and retention practices apply to the copy you save or share. SubmitReady cannot remove copies from another app or provider.
3. App settings and update checks
SubmitReady connects to Supabase to retrieve public app settings and available release information. These requests use HTTPS and do not contain your selected files or filenames. Supabase and its hosting infrastructure receive connection information such as your IP address, request time and requested endpoint, which can appear in operational and security logs.
Supabase information: https://supabase.com/privacy
4. Advertising and consent
SubmitReady uses Google AdMob to show ads and Google's User Messaging Platform to manage applicable consent and advertising choices. These services can collect and share IP addresses, device identifiers such as the Android advertising ID and app set ID, app/ad interactions, diagnostic information and consent choices. IP addresses can be used to estimate approximate location. The app does not request precise device-location access.
5. Retention and deletion
Imported copies are kept while a kit, active draft or saved edit needs them. Saved edit recipes retain their original inputs so you can reopen and adjust a previous result. When the last reference to an imported copy is removed, the app attempts to delete that unused copy.
Delete prepared files in Library to remove their local outputs and saved edit records. Delete kits to remove their kit records; prepared files that remain separately in Library must be deleted separately. Closing a draft releases inputs that no saved edit or kit still uses.
To remove all app-local files and preferences, clear SubmitReady's app storage in Android Settings or uninstall it. This does not remove originals from the location you imported them from, copies saved or shared elsewhere, or information already processed by external services.
Google and Supabase may retain technical or advertising records for service operation, measurement, security, fraud prevention and applicable legal requirements. Retention varies by provider and record type; deleting SubmitReady's local data does not itself request deletion of those records. Use the providers' privacy controls and the privacy contact below for relevant questions or requests. SubmitReady has no user accounts or cloud document backups to delete.
6. Security
Imported and prepared files are held in app-private storage until you choose to export or share them. Supabase configuration requests use HTTPS, and Google states that Mobile Ads SDK data is encrypted in transit using TLS. No storage or transmission method can guarantee complete security.