Legal

Privacy

Bidadari Drop keeps as little as it can, for as short a time as it can.

What is stored

• The file, encrypted on the server’s private storage, until the Drop expires, is revoked, or reaches its download limit.
• Drop details: the file name, type, size, a checksum, the expiry time, the download limit and count, and (if you set one) a hash of the password. Share and management links are stored only as one-way hashes. After the Drop is gone, these details are kept for about 7 days, then deleted.
• Operational records: download events and security events (for example blocked file types or repeated wrong passwords), kept for 30 days.

Network addresses

To apply rate limits, Bidadari Drop stores a keyed hash of your network address, not the address itself. The hosting provider may keep ordinary web server logs, including IP addresses, under its own policies.

Links and passwords

Share and management tokens live in the part of the link after #, which browsers do not send in the page request. They are sent to the server only in the body of a request. Passwords are never part of a link and are stored only as a hash.

Encryption, honestly

Files are encrypted at rest on the server. The server can decrypt them to deliver them, so Bidadari Drop is not end-to-end encrypted and is not zero-knowledge.

Deletion and backups

When a Drop expires or is revoked, Bidadari Drop removes the active server copy. Hosting backup retention, where applicable, is governed by infrastructure backup policies. We cannot delete a copy that a recipient has already downloaded.

What we do not do

• We do not sell data.
• There is no public directory or search of Drops.
• There are no advertising trackers, analytics or third-party scripts on any page.
• The only cookies are short-lived, same-site functional cookies for the upload form (and for operator sign-in).
• If you switch between light and dark mode, that choice is remembered in your own browser only. It is never sent to us.