Privacy policy

FileDost is device-based. It does not require a user account for its main sharing workflows.

Direct transfers

Live transfers use a browser-to-browser WebRTC connection. Signalling information is temporary, and the transferred file bytes are not intentionally stored by FileDost in direct-transfer mode.

Temporary storage workflows

Receive Files and Park & Pick Up Later may store files temporarily on the hosting server until they are downloaded, deleted, or expire. Personal Devices pickup packages are encrypted in the browser with AES-GCM before upload, so the server stores encrypted package bytes.

Metadata and local storage

FileDost may keep operational metadata such as device identifiers, filenames, sizes, timestamps, transfer status, and audit events. Browser storage may retain device names, preferences, and saved-device records.

File quality

FileDost does not intentionally resize, recompress, or re-encode files. The original file bytes are transferred, so image, video, audio, and document quality is not reduced.

Your choices

Use expiry settings, delete temporary files after pickup, remove saved devices when no longer needed, and deploy FileDost over HTTPS on public hosting.