This policy describes version 1.3.0 of the Android app OneTap: Long Screenshot, formerly named OneTap Capture X, published by motionbox96. Its package name is com.onetapshot.onetapshot. Older versions may have different features, service providers or settings, so their behavior may differ from the version described here.
Your captures are processed and stored on your device. You can choose to send content through sharing or confirmed browser translation. The app does not automatically upload your screenshots, PDFs or extracted text to our own server or Firebase.
Google services used by the app process identifiers, usage information and diagnostics. Crash reporting is automatic in release builds. The app's optional usage analytics is off by default.
1. Screenshots and local processing
After you approve Android's screen-capture permission, the app captures the screen content you choose. It can combine captured sections into a long screenshot, edit images, extract text using optical character recognition (OCR), translate text on the device and create PDFs. Long capture is manual: you scroll the page and capture each section. This version does not use an Android Accessibility service.
Captured images, edits, PDFs and cached OCR text are stored locally in app storage or saved to your device's Gallery or files, depending on the action you choose. Screen content is not routinely sent to Google for OCR or on-device translation. Those features use Google's ML Kit on-device models; the diagnostic and download traffic associated with ML Kit is described below.
The floating control needs Android's permission to appear over other apps. You can stop screen capture by dragging the floating control to its bottom close target or using Stop capture in the ongoing notification. The app does not require an account or sign-in and does not request contacts or precise GPS location for its features.
2. Content you choose to send elsewhere
Browser translation is different from on-device translation. If you choose browser translation and confirm the app's prompt, OneTap opens Google Translate in an external browser. The extracted text and selected target language are included in the URL and sent to Google. That URL may also be retained in browser history. Google and your browser provider then handle the information under their own privacy policies.
When you use Share, the selected image, PDF or text is handed to the app or recipient you choose through Android's sharing interface. Copy places selected text on the device clipboard, subject to Android's clipboard controls. Opening a detected website, phone number or email address passes that selected information to your browser, dialer or email app. These actions are initiated by you; the recipient apps and services have their own data practices.
3. Advertising and Google services
Google AdMob and advertising choices
The ad-supported app uses Google Mobile Ads (AdMob) to show banner, native, interstitial and optional rewarded ads. AdMob processes device and other identifiers, including the Android advertising ID where available; IP address, which can indicate approximate location; app and ad interactions such as launches, taps and video views; and technical diagnostic information.
This information is used to serve and measure ads, understand performance and prevent fraud or abuse. AdMob may share information with Google and advertising parties according to its configuration, your choices and applicable requirements. Data handling can vary with the ad, device and consent status. Advertising does not depend on granting the app access to precise GPS location.
The app uses Google's User Messaging Platform for consent and privacy choices where required. Ad requests wait for the platform's consent-status checks. When offered, Settings → Ad privacy choices lets you review or change those choices. Choosing non-personalized ads does not mean that no identifiers, IP information or diagnostics are processed. A rewarded ad-free period temporarily suppresses ad display; it is not a general opt-out from all SDK data processing.
Firebase Crashlytics and service diagnostics
Firebase Crashlytics is enabled automatically in release builds to help us identify and fix failures. Reports can include crash state, stack traces, app version, operating-system and device details, and a Crashlytics installation identifier. Related Firebase Installations and Sessions services can process installation identifiers and foreground or session information used for service operation and diagnostics.
Our app-generated Dart diagnostic reports remove error messages and file paths and limit reported values to technical information. Automatic native Crashlytics reports are managed by Google's SDK. This version has no separate switch to disable crash reporting; turning optional usage analytics off does not disable Crashlytics or the other required service diagnostics.
Optional Firebase usage analytics
Usage analytics is off by default. If you enable Settings → Usage analytics, Firebase Analytics receives feature and screen events that help us understand how the app is used. Our custom events use fixed feature names and limited values such as success or failure, image format and a bounded item count. They do not include captured text, screenshots, filenames or a user-supplied identity. Firebase can also process associated app-instance, device and technical information.
The app disables advertising-ID collection and advertising consent signals for this optional Analytics integration. That setting is separate from AdMob's use of advertising identifiers. You can turn usage analytics off at any time to stop future app analytics collection; doing so does not erase reports already received.
ML Kit models and diagnostics
OCR, language identification and in-app translation use Google ML Kit. Translation models that are not yet on the device are downloaded from Google, and downloads may use mobile data as well as Wi-Fi.
ML Kit and its supporting Google services can send service usage and diagnostic information such as installation and device identifiers, app and feature versions, model-download or detection events, identified or configured languages, input/output size metadata, timing and error information. The OCR and in-app translation processing remains on the device; this diagnostic traffic is separate from sending the captured image or recognized text for remote processing.
Google's SDK disclosures describe HTTPS/TLS protection for these network transmissions. Google processes Firebase and ML Kit information as a service provider; advertising sharing is governed by AdMob's disclosures and the relevant advertising choices.
4. Your settings and permissions
Capture: approve or end Android's screen-sharing session, stop capture from its notification or close target, and manage overlay and other app permissions in Android Settings.
Usage analytics: leave the optional switch off, or change it in OneTap Settings at any time. This switch controls the optional Analytics integration, not ads, crash reports or ML Kit diagnostics.
Ad privacy: use the app's ad privacy choices when they are available for your consent status or region. Android's privacy or Ads settings may also let you reset or delete the advertising ID; available controls depend on your Android version.
External content: decline browser translation or sharing when you do not want the selected text or file sent to another service.
Saved content: delete captures in Library and review any separate Gallery, Files, exported or shared copies.
5. Storage, backups, retention and deletion
Your local captures and their app records remain until you delete them, clear the app's data or uninstall the app, subject to where the files were saved. Exported files and Gallery copies can remain after app data is cleared or the app is removed. Delete those copies separately in the relevant Gallery or file app; recipients can also retain content you shared with them.
This version excludes the app's private data from Android cloud backup and device transfer. Your Gallery or photo-management app may independently back up shared images according to its own settings. Deleting an image locally does not necessarily delete a photo-service backup.
Google and advertising services retain diagnostics, identifiers and measurement data according to their policies, service requirements and applicable account settings. Local deletion, resetting an advertising ID or turning analytics off does not automatically delete information already received by those services. We do not promise immediate or universal deletion of SDK records.
You can contact us to request help with access, correction or deletion, or to exercise other privacy rights available in your location. Include the app name, relevant dates and a description of the request. Because OneTap has no user accounts and SDK reports may not be linkable to an email address, we may be unable to identify every record as yours. We will assess what can be identified and handled through available provider controls, explain any limitations and direct you to appropriate device or provider settings where necessary.
6. Support messages and this website
If you email us, we receive your email address and the information or attachments you choose to provide. We use that information to respond to the request, investigate the reported issue and meet applicable legal obligations. Support correspondence is retained for handling the issue and any related follow-up or legal need; you can ask us about deleting it.
This support website has no added analytics, advertising scripts, tracking pixels or custom tracking cookies. It is hosted by Netlify, which may process standard request information such as IP address and browser or request metadata to provide and secure its hosting service. Following an external link takes you to a service with its own privacy practices.
7. Provider privacy information
The following pages explain the Google services and website host discussed above:
Provider processing may take place in countries other than your own, under the provider's applicable terms, privacy policies and safeguards.
8. Changes to this policy
We will update this page and its date when the app's privacy practices change. Material changes may also be explained in the app or its store listing. This page describes the version identified at the top; installing a newer or older version can change the features and services available to you.
9. Contact
Publisher: motionbox96
App: OneTap: Long Screenshot (formerly OneTap Capture X)
Android package: com.onetapshot.onetapshot
Privacy and support: motionbox96@gmail.com