Sendby
Privacy Policy
1. Files, photos and videos
The apps process content you select, together with information such as its name, type and size, to preview, prepare and send it. Content currently travels over verified private-network, encrypted WebRTC direct connections. Sendby connection servers do not relay file or text bodies, and a failed direct connection does not automatically fall back to a file relay or public-network content route.
iOS creates temporary sending copies when necessary and performs cleanup when items are removed, cleared or on a later launch. Removing these copies does not delete your original photos or files. iCloud or another file provider may download selected content to make it available, under that provider's rules.
2. Text and clipboard
iOS processes text only when you explicitly type or paste it; it does not automatically read the clipboard in the background. Text cards remain in the editing or sending list for the current app session. Their bodies are not written to sending history or history thumbnails and are not uploaded to the connection server.
The website and Windows receiver display text cards temporarily and write to the clipboard only when you select Copy. Cards are not automatically saved as files or included in a file ZIP. Closing or clearing the receiving page loses temporary text; copy anything you need first.
3. Local storage and recipients
iOS stores preferences such as language, appearance and device name, as well as sending history, on the device. History may include file names, sizes, sending times, recipient names and small previews; it is not a backup of the original files. System backups may include some app data depending on the operating system and your settings.
The website stores preferences such as language in the browser. Received files may be held temporarily in the page or written to a folder you authorize. Windows stores the receiving directory, language preference, received files and a count-limited file history. Clearing a page cache or uninstalling the app does not delete copies already saved by recipients, independent backups or server logs.
A directly connected peer receives the device name, receiving status, content metadata and content needed for display and transfer. Check the recipient before sending. When receiving is enabled, nearby devices that meet the receiving conditions can initiate transfers.
4. Discovery, connections, downloads and updates
Device discovery still requires internet access. The service processes source IP addresses, temporary device identifiers, pairing relationships and connection signaling for discovery, connection setup, security checks and request limiting. Current discovery and pairing state is primarily held in memory and cleared through the connection-close or session-expiry mechanisms. This does not mean proxy access logs are deleted at the same time.
Modern nearby discovery does not send actual device names to the server as a discovery directory. Names and statuses are provided to peers through the connected channel. Connection negotiation may involve network addresses. “No server relay of content bodies” does not mean “no personal information is processed.”
Following a Windows download link or explicitly selecting Check for updates in PC settings requests an installer or official release information from sendby.space. Servers and the reverse proxy process the source IP address, request path, access time, response status and browser or client information carried by the request, as needed to handle it. Related access and error logs are handled under section 6. Version comparison takes place locally on the PC; update checks do not upload the installed version number, selected content, file names or content bodies. Finding an update does not automatically download or install it; the official download link opens only when you explicitly select Download. Hosting the app installer is separate from transferring user content.
5. Permissions, hosting and third parties
Local-network access connects nearby devices. Touch to send uses new spacebar requests from the computer and your first approval for the current computer connection on the phone; it does not collect phone motion. While the same connection and approval remain valid, later fresh spacebar requests do not require repeated approval. Approval is revoked when you leave the foreground Send page or disconnect; requests after reconnection or revocation require new approval. You can also explicitly tap a device to send. Photo permissions and system pickers read selected items. You can use limited photo access and manage permissions in system settings. Denial may prevent the corresponding feature from working.
Sendby currently uses Alibaba Cloud servers located in Shanghai, China for its website, discovery service and Windows downloads. Alibaba Cloud is the hosting provider; hosting, the reverse proxy and security operations process the necessary connection information and logs described in sections 4 and 6. Additional logs, snapshots and backups are addressed below. Alibaba Cloud's own service rules are described in its Legal Statement and Privacy Policy, which do not replace our personal information protection duties to Sendby users. The server location does not mean that all third-party processing occurs in China or that third parties keep no logs.
The support mailbox uses Feishu Mail to process the sender address, messages and attachments you voluntarily provide, to handle and answer your requests. Do not provide passwords, verification codes or unnecessary files. Mailbox storage locations, provider access and backup deletion mechanisms depend on Feishu's applicable service agreements, privacy policy and actual account settings. We remain responsible for access we authorize and for handling privacy requests; those responsibilities are not transferred to the provider. Where provider backups exist, their copies may not be removed at the same time as our deletion.
Apple services, iCloud, your file providers, browsers and operating systems operate under their own rules. Pro in-app purchases are provided through Apple. The app uses StoreKit to retrieve product information, verify transactions and restore purchases, using information such as product identifiers, transaction status and expiry dates to determine available features. Apple handles payments and refunds under its rules. The app does not upload purchase receipts to Sendby's connection server or read payment-card information. Purchase availability and conditions are described in section 4 of the Terms of Use.
6. Logs and personal information retention
For service security and troubleshooting, servers record necessary access and error logs, which may include IP addresses, access times, request addresses, response statuses, referring pages and browser information. Clients may also generate local failure or connection diagnostics. These records may contain personal information but do not relay file or text bodies.
Log retention follows applicable law, including at least six calendar months for relevant network/security logs subject to that requirement. Dedicated Sendby access and error logs are now independently archived for at least six calendar months from capture and deleted during routine cleanup after that period, unless a legal hold applies. Archives are restricted to authorized operations access. Records that must be retained by law may not be immediately deletable. The statutory six-month network-log requirement does not automatically apply to all personal information.
For additional Sendby logs, snapshots and backups that we control, actually enable and that contain personal information, our retention management rule is at least six calendar months from capture or copy creation, followed by routine cleanup unless legally preserved. This management rule does not mean that all separate cloud resources are included in the dedicated log archive. We cannot currently confirm the full enabled scope or actual deletion periods for those resources, and cannot guarantee that their copies are cleaned up at the same time as the dedicated archive. This rule does not extend the lifetime of temporary device content or discovery sessions and does not replace the email rule below. Sections 1 to 3 describe storage and cleanup of on-device content and records.
Support and privacy-request email is subject to deletion 90 days after case closure, except for open cases, disputes or legally required retention. Network-log retention does not automatically apply to email. Cleanup uses reminders based on case-closure dates and manual review before deletion. Provider-side backup limitations are described above.
7. Your choices and privacy requests
You can cancel unfinished transfers, remove selected items, clear temporary received content, change permissions and manage saved files. Stopping a feature does not recall content already delivered to a recipient. Records required by law may not be immediately deletable; recipient files, system backups and server records require separate handling.
Send access, correction, deletion and other privacy requests to hello@sendby.space. Describe your request without sending passwords or verification codes. We will reply with an outcome or progress update within 15 working days of receiving your request, or sooner if the law requires a shorter deadline. If identity checks, an extension or legally required retention are necessary, we will explain why and complete further handling in accordance with applicable law.
Sendby is a general-purpose file transfer tool, not specifically directed at children, and does not set its own universal minimum age; iOS distribution follows the actual App Store age rating and regional rules. A store rating or download does not replace legally required guardian consent or safeguards for children's personal information. Guardians can use the mailbox above for privacy requests concerning a child in their care. We will verify only the information necessary to handle the request and act in accordance with applicable law.
8. Policy updates
If processing purposes, information categories, providers, retention arrangements or your rights change materially, we will update this policy, state its updated and effective dates, and provide notice as required by applicable law. Where separate consent is required, we will obtain it before the relevant processing; publishing this policy does not replace required consent.