Effective date: November 5, 2026
This Privacy Policy applies to Share & Act for Android and iOS. The Android app, package ltd.tcool.android.shareact, is published by Kan Huang under the Google Play developer display name Super Ratel. The iOS app uses bundle identifier com.tcool.shareact.ios. TCool LTD is the website and support brand; the Android publisher information is not an identification of the iOS App Store seller. Contact dev@tcool.ltd about this policy or a privacy request.
Share & Act routes content that you choose to share to a configured bot webhook. It does not require a separate Share & Act account. This policy covers both apps; third-party bots, Google services, source apps, and exported copies have their own privacy practices. See also the Share & Act Terms of Service.
What stays on your device
Android. The app stores bot connection settings, webhook addresses and credentials, routing rules, templates, optional test samples, preferences, task records, delivery state, and local operational counters in its private Android storage. Depending on your settings and the task state, records can include selected content, instructions, URLs, and request metadata.
Sensitive configuration and task records use encryption with Android Keystore-managed keys. Staged attachments and signed purchase information are also protected by Android’s app-private storage controls; not every temporary file or purchase preference uses an additional app-level encryption layer. No system can guarantee complete security.
The Android app disables operating-system backup of its private app storage. The app does not provide a TCool cloud account or automatic synchronization of bot settings, rules, or task content.
iOS. The app stores rules, bot settings, selected content, task history, and delivery state in an AES-GCM-encrypted state file in an App Group container shared by the main app and its share extension. Encryption keys, bot credentials, and the Google Drive refresh token use the iOS Keychain with AfterFirstUnlockThisDeviceOnly protection: they become available after the first device unlock following a restart and are not migrated to another device through backup.
Temporary attachments and request-body files are staged with iOS file protection and are excluded from backup. This is not a claim that every temporary file has an additional app-level encryption layer, or that all iOS app data is excluded from backup. iOS storage and Keychain protections do not provide an absolute security guarantee. The iOS app also does not provide TCool account-based cloud synchronization.
Background transfer credentials. Where the installed version uses background URLSession, an authorized network task includes the Google access token or bot Authorization headers needed by its recipient. iOS manages that task and may hold or persist these request credentials for the task lifetime under system controls. Keeping the main bot credentials and Google refresh token in Keychain does not mean every authenticated-request copy stays only in Keychain or that access tokens never reach system-managed storage. Google authorization headers are sent to Google, not to the bot.
Content you choose to send to a bot
When you share supported text, a link, an image, or a PDF, the app evaluates your rules and may prepare a request to the configured webhook endpoint. Requests can include your selected content, instructions, URLs, file references, task identifiers, and related metadata shown or used by the configured workflow.
Sending requires your action or the automatic-delivery approval you grant to a rule. Review the endpoint, rule, and selected content before sending. You are responsible for choosing a trustworthy recipient and for having permission to share information about other people.
The configured bot or endpoint receives the request directly. We do not operate a general TCool server that receives these routed payloads. The recipient may retain, analyze, or otherwise process what you send under its own terms. Share & Act does not control a recipient’s AI model, training practices, retention, output, or deletion. An accepted webhook submission is not confirmation that the bot completed its work.
Images, PDFs, and Google Drive
File workflows request authorization for the drive.file scope through Google’s Android authorization service or, on iOS, a Google OAuth authorization page in a system authentication session. This scope is used to create and access files associated with the app rather than to browse your entire Drive.
When you choose a supported file workflow, the app may copy the attachment into its private cache or no-backup staging storage, upload it directly to your Google Drive, and send the file identifier, file name, MIME type, and private Drive URL to the configured bot. Temporary staged copies are removed by the transfer lifecycle or cleanup process; interrupted work may retain its inputs until cleanup, cancellation, or expiry.
The app does not make uploaded files public or create an anyone-with-the-link sharing permission. The receiving bot needs its own permission or Google Drive connection to read a private file. Authorizing Share & Act does not authorize that bot on your behalf.
Google authorization tokens are not forwarded to bot endpoints. The app uses short-lived Google access tokens for the immediate Drive operation or obtains a new token for an approved background transfer; it does not persist those access tokens as bot credentials.
iOS authorization. A Google refresh token is retained in Keychain so the app can obtain a short-lived access token for a later authorized Drive upload. Google tokens are used only for Google authorization and Drive requests, not as bot credentials. For a file workflow, the configured Grok Routine or other bot receives a files reference containing the file identifier, name, MIME type, and private URL, together with the task and rule instructions; it does not receive your Google access or refresh token. The bot still needs its own access to the private Drive file.
You can revoke authorization in your Google Account settings. Revocation may stop later file transfers. Deleting a rule, clearing app storage, or uninstalling Share & Act does not delete files already uploaded to Drive; manage those copies in Google Drive.
Purchases by platform
The current iOS version has no in-app purchases and does not collect Apple purchase receipts or payment details. The following purchase and restoration description applies to Android only.
Google Play purchases and restoration
Google Play processes the optional one-time, non-consumable lifetime purchase. It is not a subscription. The app receives product and purchase information such as the product identifier, purchase state, purchase token, signed receipt, and acknowledgement state to verify, acknowledge, unlock, and restore eligible purchases.
Signed purchase data is cached in app-private storage for verification at startup. The app does not send purchase receipts or purchase tokens to a TCool billing backend. It does not receive your full payment-card details or Google Account password.
Restoration queries Google Play using the applicable purchasing account. Store synchronization, account selection, connectivity, refunds, and revoked transactions can affect the result. A failed restore is not a request to pay again. Purchase records maintained by Google are separate from local app storage and remain governed by Google’s policies.
Permissions, clipboard, and background work
Android
- Network access is used for your configured HTTPS webhook, Google Drive file operations, and Google Play billing.
- Notification permission is requested for relevant delivery and transfer status features.
- Supported Android versions may use system-scheduled background work or user-initiated data-transfer jobs for work you initiated or approved.
- Selected files arrive through Android’s sharing or document interfaces; the app does not request unrestricted access to your photo library, contacts, location, camera, or microphone.
- Copying setup prompts or configuration uses Android’s clipboard at your request. Android, your keyboard, and device-level clipboard services may handle copies under their own settings.
iOS
- Shared text, links, images, and PDFs arrive through the iOS share sheet or user-selected content, rather than unrestricted access to your device’s content.
- Optional on-device speech input requests microphone and speech-recognition permission when used. Audio is transcribed on the device; the app does not upload the recording to TCool, Google, or a bot, and does not fall back to online speech recognition. If on-device recognition is unavailable, use typed input. Recognized text becomes editable task content and is sent only if you submit or authorize that workflow.
- Network access is used for your configured webhook and authorized Google Drive operations. Clipboard copies are made at your request and remain subject to iOS, keyboard, and device settings.
- Where supported by the installed version, user-initiated or rule-authorized transfers may use system-managed background network tasks. Scheduling, device conditions, app suspension, and an explicit force-quit can delay or prevent progress; the app cannot run continuously in the background. Background features are version-dependent and do not guarantee delivery or completion of work by a remote bot.
These permissions do not authorize unrelated content to be sent to a bot.
Diagnostics and support
The app keeps local operational counters and safe diagnostic information, such as app version, error codes, delivery states, and, on Android, purchase-query counts. It does not automatically upload these diagnostics to a TCool analytics server. Billing diagnostics are designed not to include account details, complete receipts, signatures, order numbers, or purchase tokens.
If you contact support or choose to share logs or configuration, we receive the information you provide, including your email address and any attached content. Review it before sending; do not include bot secrets, Google tokens, full receipts, or sensitive files. Support correspondence may be retained as reasonably necessary to respond, resolve issues, prevent abuse, and meet applicable obligations.
Retention and deletion
Local settings, bot credentials, rules, and task information remain subject to the app’s deletion and retention behavior and the relevant platform’s storage controls. Task states and retention settings can affect how long content is kept; pending work may need its input until delivery, cancellation, or expiry.
Use the available bot and rule deletion controls for those records. On Android, use Settings to clear the app’s storage or uninstall it for local removal; eligible Google Play purchases can still be restored. On iOS, deleting the app (rather than offloading it) removes its app data according to iOS behavior, but Keychain items may persist after deletion. Do not rely on uninstalling to revoke Google access: revoke it in your Google Account, and delete bot connections and rules using available app controls before removal where possible.
Deletion does not recall requests already received by a bot, remove uploaded Drive files, delete exported configuration or clipboard copies, or erase Google’s purchase records. Delete remote copies through the relevant service. To request deletion of information you sent to our support address, contact us; limited records may be retained where required for security, disputes, or legal obligations.
Advertising and analytics
The Android and iOS apps do not contain an advertising SDK or a third-party behavioral analytics SDK, do not sell personal information, and do not use routed content for TCool advertising profiles. Google Play, Android, Apple, iOS, and third-party services may separately process technical, billing, security, and service information under their own policies.
Website access
Opening this page or the Terms of Service loads tcool.ltd, hosted on Cloudflare Pages. Hosting infrastructure may process IP addresses, browser user agents, requested resources, and request times to deliver and secure the website.
The TCool website uses Google Analytics for website visits and interactions. Those website analytics are separate from the Android and iOS apps and may involve cookies or browser/device information under your browser settings and Google’s policies. Opening a legal page does not send your bot credentials, routing rules, or shared files to the website.
See Cloudflare’s Privacy Policy and Google’s Privacy Policy.
Adults only
Share & Act is intended for users aged 18 and over, not for children. Do not provide information or content unless you have the necessary rights and consent. If you believe personal information was provided to our support service inappropriately, contact us.
Changes and contact
We may update this policy as the app or its data flows change and will show the effective date on this page. Material changes may also be communicated through the app or store where appropriate.
Questions or privacy requests: dev@tcool.ltd.









