Last updated: July 17, 2026<\/p>\n\n\n\n
This Privacy Policy explains how user information is handled in the screen capture app \u201cToripo\u201d (hereinafter referred to as the \u201cApp\u201d).<\/p>\n\n\n\n
The App captures the screen of an Android device in response to user actions and allows captured images to be saved, reviewed, and shared. It provides features including local saving of captured images, saving to Dropbox, settings for save locations and display sizes, purchase of Unlimited mode, and notifications about the App.<\/p>\n\n\n\n
To provide its features, the App may store the following information on the user\u2019s device.<\/p>\n\n\n\n
Screenshots contain what is displayed on the user\u2019s screen. If sensitive information, such as personal information, authentication credentials, payment information, messages, or photos, is displayed on the screen, that information may be included in the captured image.<\/p>\n\n\n\n
The App uses Android\u2019s screen capture feature (MediaProjection) to provide screenshot functionality. Screen capture is performed only when the user grants permission on the operating system\u2019s confirmation screen and initiates a capture operation.<\/p>\n\n\n\n
The App may also use the following permissions and system features.<\/p>\n\n\n\n
The App may communicate with the following external services as a result of user actions or the operation of App features. Communications related to Firebase may occur automatically when the App starts or while it is being used.<\/p>\n\n\n\n
During these communications, network information such as IP addresses, information about the device, operating system, and App environment, service-specific identifiers, OAuth credentials, images being uploaded, information required for purchase processing, and similar information may be transmitted to the relevant service to the extent necessary for each feature. Information transmitted to an external service is handled in accordance with that service\u2019s privacy policy and terms of use.<\/p>\n\n\n\n
Dropbox Privacy Policy<\/a> The App is not designed to collect or transmit screenshots captured by the user, the contents of those screenshots, file names, save locations, Dropbox OAuth tokens, or similar information to servers independently managed by the developer.<\/p>\n\n\n\n However, through the Google Firebase features used by the App, the usage data, crash information, device and App information, identifiers, and other information described in this Privacy Policy may be transmitted to Google\u2019s systems. The developer may view aggregated usage information and crash information through the Firebase Console and similar tools. Information is also transmitted to external services to the extent necessary when the user uses features such as saving to Dropbox, Google Play in-app purchases, or displaying external pages.<\/p>\n\n\n\n The App does not include an SDK for displaying advertisements. Collection of the Advertising ID and transmission of ad personalization signals are disabled, and permissions related to the Advertising ID and AdServices are excluded from the App.<\/p>\n\n\n\n To improve quality, understand usage, investigate problems, and deliver notifications, the App uses Firebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging, Firebase Installations, and related services provided by Google LLC. These features generally operate automatically when the App starts or while it is being used. The App currently does not provide settings that allow users to disable each of these forms of data collection individually.<\/p>\n\n\n\n Firebase Analytics (usage analytics)<\/strong> The Analytics information explicitly logged by the App consists of capture starts, capture results (success or failure), results of saving to the device (success or failure), results of saving to Dropbox (success or failure), and the verified access tier (Free or Unlimited). The access tier is recorded as a user property named \u201caccess_tier.\u201d The App does not set names, email addresses, telephone numbers, or similar information as custom Analytics events or user properties.<\/p>\n\n\n\n Firebase Crashlytics (crash reporting)<\/strong> Firebase Cloud Messaging (notification delivery)<\/strong> The custom Analytics events, user properties, and Crashlytics diagnostic information defined by the App do not include screenshot images or their contents, file names, save location paths, or Dropbox OAuth tokens.<\/p>\n\n\n\n The App is not designed for the purpose of selling user information to third parties. Information may be transmitted to the external services described in this Privacy Policy to the extent necessary to provide App features, analyze usage, investigate crashes, deliver notifications, process purchases, and perform related operations. Each service provider, including Google, processes information in accordance with its own privacy policy and terms of use.<\/p>\n\n\n\n Information transmitted to Firebase may be processed or stored in countries or regions where Google or its service providers maintain facilities, including locations outside Japan. Information may also be disclosed in accordance with applicable law when disclosure is legally required.<\/p>\n\n\n\n Screenshot images saved on the device are stored in the location selected by the user. The user is responsible for managing, sharing, and deleting those images.<\/p>\n\n\n\n On-device data such as App settings, external service integration information, and purchase status can be deleted by clearing the App\u2019s data in the device settings or uninstalling the App. However, images saved to the device\u2019s shared storage or MediaStore may remain after the App is uninstalled.<\/p>\n\n\n\n For images already transmitted to Dropbox and information related to the integration, please delete the images or disconnect the integration through Dropbox.<\/p>\n\n\n\n Data transmitted to Firebase is retained and deleted in accordance with the retention periods configured by the developer in Firebase and Google Analytics and with Google\u2019s policies. According to Google, Crashlytics retains crash stack traces, related identifiers, and similar data for 90 days before beginning the process of removing that data from live and backup systems. Deletion of data associated with a Firebase Installation ID may require a certain amount of time within Google\u2019s systems.<\/p>\n\n\n\n Uninstalling the App stops future communications from the App. Clearing the App\u2019s data through the device settings also deletes locally stored identifiers and similar data; however, if the App is subsequently launched, new identifiers may be generated and communications may resume. Data already transmitted to external services may not be deleted immediately. For deletion requests or other inquiries regarding data transmitted to Firebase, please contact us through the form below. We will respond to the extent required by applicable law and technically feasible.<\/p>\n\n\n\n Images captured with the App may contain personal or confidential information belonging to the user or a third party. Please carefully review the contents before saving, sharing, or uploading an image.<\/p>\n\n\n\n For information about the handling of data, stored files, access logs, and similar information by external services accessed through or integrated with the App, please review the terms and privacy policies of those services.<\/p>\n\n\n\n This Privacy Policy may be revised in response to additions or changes to App features, changes to external services, changes in laws and regulations, or similar circumstances. If a material change is made, users will be notified by an appropriate method.<\/p>\n\n\n\n
Google Privacy Policy<\/a>
Privacy and Security in Firebase<\/a><\/p>\n\n\n\n5. Data Sent to Developer-Managed Servers<\/h6>\n\n\n\n
6. Advertising, Usage Analytics, Crash Reporting, and Notifications<\/h6>\n\n\n\n
Identifiers associated with an App instance, the Firebase Installation ID (FID), App version, device model, operating system, language, approximate region, and events such as App launches, user interactions, and notification engagement may be transmitted. This information is used to understand how features are used, improve quality, and identify problems at an early stage.<\/p>\n\n\n\n
When a crash or a non-fatal error recorded by the developer occurs, information such as the stack trace, relevant App state at the time of the error, device model, operating system, App version, Crashlytics Installation UUID, FID, session information, Analytics breadcrumbs showing actions immediately before the event, and developer-defined diagnostic information such as the processing phase may be transmitted. This information is used to investigate and fix problems and improve App stability.<\/p>\n\n\n\n
Information such as the App version, FID, FCM registration token, Firebase SDK information, and notification delivery and interaction information may be transmitted. Even if the user has not granted Android notification permission, Firebase automatic initialization may cause an FID and FCM registration token to be generated and transmitted. If notification permission has not been granted, notifications will not be displayed in the operating system\u2019s notification area.<\/p>\n\n\n\n7. Transmission and Disclosure to Third Parties<\/h6>\n\n\n\n
8. Data Management, Retention, and Deletion<\/h6>\n\n\n\n
9. Important Notes<\/h6>\n\n\n\n
10. Changes to This Privacy Policy<\/h6>\n\n\n\n
11. Contact<\/h6>\n\n\n\n