MeowShare for iOS and Android
Privacy policy
MeowShare is provided by Chhayarith Tes. It transfers files you select directly between nearby devices participating in a sharing session. It does not require an account. This policy covers the native iPhone, iPad and Android apps; including their phone-hosted browser sharing. The separately hosted browser-to-browser website is outside this native-app policy.
Direct sharing and nearby discovery
A transfer processes the selected file’s name, size and contents, and Wi-Fi transfers also use a verification hash. These go to the peer you choose. Device names and limited service information are visible to nearby devices during discovery. App-to-app Wi-Fi connection links include an address, certificate fingerprint and private one-use invitation. Keep them private. Device labels do not verify a person’s identity. App-to-app Wi-Fi requires receiver approval of the device and file. In Bluetooth mode the sender confirms the recipient, while a listening receiver gets a temporary file to save or discard; it does not use the Wi-Fi invitation/approval flow.
In Start local server, the native app on your phone serves a local page and one file you explicitly choose. Its private link allows a browser on the local network to receive that file or offer an upload for your approval. The connection uses unencrypted HTTP and shows an information notice on both screens. The page, names, file bytes and private connection token can be observed by someone able to intercept local network traffic. Use Wi-Fi you trust. The session link expires when sharing stops; no file relay or internet connection is needed.
Storage, retention and deletion
Accepted app-to-app Wi-Fi originals and receipts are stored in private app storage and remain until you explicitly delete them in MeowShare or remove the app’s data. Ending a session does not delete completed files. Received Bluetooth files and recent Bluetooth history are held in memory until saved or discarded; save a copy before closing the app. Android private originals and history are excluded from app backup and device migration. iOS backup behavior follows the operating system and the app’s storage settings.
Browser uploads are saved separately in private app storage. The browser-sharing page retains the latest 100 receipts for saving copies. Completed browser originals remain until the app’s data is removed. The receiving browser holds a downloaded file in memory until you save it or close the page; its private session link is retained in tab storage to support refreshing. File bytes are not stored in that tab storage.
Copies saved to another device, an external folder or a system/cloud file provider are controlled by that destination and must be deleted separately. The developer cannot remotely erase those copies.
Permissions
Local Network and nearby-device access support discovery and transfers. Bluetooth is optional; Wi-Fi works independently. Older Android versions associate nearby Bluetooth discovery with Location permission; MeowShare does not use that permission to obtain your geographic coordinates. Camera access is used only when you open QR scanning. Files are chosen through the native picker. Android runs a connected-device service after an app-to-app Wi-Fi connection is approved. Depending on your Android version and notification settings, the active service appears in the notification drawer or Android’s Active apps task manager. End Transfer stops the session. Phone-hosted browser sharing stops when the app leaves the foreground.
QR scanning and Android SDK diagnostics
QR images are processed on the device. iPhone and iPad use Apple Vision. Android uses the bundled Google ML Kit barcode scanner. Google documents collection of device and app information, per-installation identifiers, scanner usage and performance/error diagnostics over HTTPS. These diagnostics are separate from your transferred files; the developer has no MeowShare analytics dashboard for them. You may paste a connection link instead of opening the camera.
Google’s ML Kit disclosure and privacy policy explain its handling. MeowShare cannot independently delete Google’s diagnostic records or promise a provider retention period.
Logs, support and store services
Normal builds keep limited local transfer-stage and numeric progress diagnostics; these omit file names, invitation secrets and addresses and are not uploaded by a MeowShare service. Detailed profiling is disabled in store builds.
The apps have no advertising SDK, developer-operated analytics service, login or file relay. Apple, Google and any system/cloud file provider may process information under their own terms. TestFlight and Firebase App Distribution are separate beta distribution services. Opening the website uses your external browser and may expose normal connection information to Firebase Hosting. No file or invitation is automatically attached.
If you email support, the developer receives the address and content you send through the email provider. Send only information needed to resolve the issue. Request deletion of support correspondence using the same contact; provider/legal retention may still apply.
Security and children
App-to-app Wi-Fi uses certificate-pinned TLS, private one-use invitations, device/file approval and saved-file verification. Do not assume Bluetooth has the same protection; its app protocol does not provide the Wi-Fi TLS guarantee. Phone-hosted browser sharing uses unencrypted HTTP, identified by its in-page notice. Share only with the intended recipient and keep both apps open until completion.
MeowShare is a general file-sharing utility, not a service designed specifically for young children. It does not inspect, moderate or age-filter files selected by users. The intended audience and store content ratings must be finalized before release.
Website testing invitations
The homepage’s optional Android testing form is separate from file sharing. When the invitation service is enabled, submitting it sends your Google Play email address, form language and request time to a dedicated MeowShare request database. Chhayarith Tes uses these to arrange testing invitations and contact you about the test. A request does not automatically enroll you in Google Play testing.
Cloudflare Workers and D1 process and store requests; Turnstile checks for spam when you open the form on the live website. The request table does not store your IP address or verification token. The daily deletion job removes requests older than 89 days, aiming to remove them within 90 days; outages can delay deletion, and provider recovery copies may remain longer. Repeated requests do not extend this period. Local previews do not send addresses or load verification.
To prevent signup abuse, a separate security table stores a coded network identifier, request timing and recent rate-limit rejections; it does not store raw IP addresses or email addresses. Requests need a one-second gap and are also limited to about 10 per minute. The 20th rate-limited attempt within 60 seconds permanently blocks signup from that network. The daily job deletes expired temporary security records; outages can delay cleanup. Blocked identifiers and block times remain until manually removed. Contact us to request review of a block.
When an invitation is arranged, your email may be used in Google Play’s tester list and email correspondence. Those copies are separate from the website’s deletion job. Requests are used for testing, not marketing. To withdraw or request deletion, contact [email protected].
Contact and changes
Privacy and support contact: [email protected]. Do not send private files, passwords or active invitations. Changes to data practices will be reflected in this policy and the applicable store disclosures.