Privacy policy

What the service needs

Dropvilo does not require an account, real name, phone number or payment details. Temporary device IDs, session tokens, IP addresses and signaling information are used to connect devices, recover an approved session and limit abuse. Device nicknames are optional; avoid entering a real name if it is not needed.

Your files and messages

Files and messages travel between paired browsers over encrypted WebRTC channels. The signaling application does not receive their content. The recipient can save what you send; Dropvilo cannot delete the recipient’s copies. Encryption does not make the website anonymous or guarantee that a recipient or device is trustworthy.

Storage you control

Optional saved theme preferences and transfer history are off by default. Use Privacy settings to opt in or withdraw. Saved history includes file names, sizes, direction, status and times; it does not store reconnect credentials or a permanent peer identity. During an accepted transfer, browser storage can hold received file bytes. Verified progress and checksum state used for recovery stay in the open tab’s memory. Received browser files can remain until you remove them or clear site data. Browser storage can also be evicted.

History saved before you withdraw remains until you delete it. Turning history off stops new history records and hides saved records from the sharing view; it does not pretend to erase received files. Delete local data or request deletion.

Connection providers

The deployed website is hosted on Render. Its infrastructure can process request addresses and operational logs under its own policies. The default STUN service is operated by Google and can receive your IP address during connection discovery after pairing approval. A configured TURN relay carries encrypted traffic and can see connection metadata. The other device may learn network addresses through WebRTC. Hosting, email and relay retention are not controlled by clearing your browser.

Temporary server information

The application keeps signaling and approval information in memory rather than an account database. Idle identities and unconnected approvals expire after about 30 minutes; active sessions can extend that period. Rate-limit counters are short-lived. A restart clears application memory. This is not a retention guarantee for hosting-provider logs.

Operational errors

If an error occurs, the browser can send a fixed diagnostic code to this website so the operator can detect failures. The report does not include file names, file contents, text messages, tokens, nicknames or a browser stack trace. The server records the code, time and application release; ordinary network requests still expose connection metadata to the host. If the operator enables Sentry, these limited events are forwarded from the server to Sentry for error alerts. Browser analytics, session replay and automatic user profiling are not enabled. Hosting and monitoring records are separate from your local transfer history and are not erased by the local deletion button.

Support and email

If you choose to email Lasin, your email provider and the operator’s email provider process your address and message. Send only what is needed to answer your question, and do not send private files, identity documents, payment details or passwords. No newsletter or marketing-email system is included in the app. You can ask for support emails to be deleted or for optional follow-ups to stop.

Adults only

The sharing service is intended for people aged 18 and over. It is not directed at children, and no child profiles or verified parental-consent process are offered. The app does not verify age or record an age declaration. If you are under 18, do not use sharing. If you believe a child’s information has been sent to the operator, contact us to request review and deletion. Visiting the website still makes a normal request to the hosting provider.

Your choices and requests

You can decline optional storage and still transfer files. For access, correction, deletion or privacy questions, email lasin90746@gmail.com. Describe what information you mean without sending an ID document. The operator may ask for proportionate information needed to locate the record and avoid deleting someone else’s data.

See Cookies and browser storage, Terms of service and operator details. Material changes should be reflected here before new collection is introduced.