Beta privacy explanation · Updated 14 October 2026
File contents stay between your devices.
Approved transfers travel directly over local HTTPS between the Safari companion and your Windows PC. The public website, internal account sandbox and payment provider do not receive the transferred file contents.
The PC and browser use filenames, file sizes, checksums and transfer records to perform and recover a handoff. These are local transfer data, not marketing analytics. Local browser copies use that PC origin’s storage and can be removed with the app’s explicit discard actions.
Saved access is local to the PC connection.
The Safari companion remembers authorization in its own PC origin. Approve browsers and transfers on your PC, and revoke access there when needed. This website cannot read that saved connection, approve a transfer or discover your PC automatically.
Setup still uses services.
Trusted HTTPS setup, hostname resolution and certificate renewal can involve external infrastructure. A setup service needs limited installation and certificate metadata; it must not receive the PC’s private keys or act as approval for a file transfer. This beta uses assisted configuration.
Beta setup requests
The setup request form asks for your email, optional name and optional short message, with your agreement to use them to respond about beta setup. Do not send files, filenames, private keys, pairing links, passwords or network/DNS details.
Netlify processes and stores submissions in the site’s private Forms dashboard and applies spam filtering. It may also store the visitor IP address, submission time and spam-check metadata for processing and spam prevention. Authorized site administrators can read requests. No email notification, automatic reply or marketing subscription is configured for this form. The beta operator may reply to your email when available; there is no guaranteed response time or setup appointment.
The beta retention target is to review and manually delete setup requests within 90 days of submission. Automatic deletion is not configured. To request removal sooner, use the same form with the email originally supplied; ownership may need to be checked before removal.
Accounts are an internal sandbox.
If internal sandbox configuration is enabled, Supabase handles email/password authentication and minimal account, test-purchase and installation records. Stripe hosts test checkout and billing management. Do not enter real card information in this demonstration. The sample price and legacy entitlement are internal test fixtures, not Personal or Teams plans.
Personal beta transfer use needs no commercial account. Teams and broader device networks are planned. No transfer histories, filenames, file hashes or pairing credentials belong in the commercial service.
No ads or marketing trackers here.
This site includes no advertising SDK or marketing analytics. Website hosts and authentication/payment services may process the access, security and transaction data needed to operate their services. This is not a claim that visiting the website creates no server logs.
Keep the copies you need.
A browser copy marked Ready to save has passed SideDrop’s integrity check; you still need to complete Save to Files. Browser storage can be cleared or reclaimed. Check the exported file before dismissing its local copy or deleting your original.
Beta questions
Use the setup request form to contact the beta operator. Final publisher and paid-service support details are still needed before a general paid launch. Never send a private pairing link, token, certificate key or personal file as public troubleshooting material.