Golden Drop privacy

Last updated: October 5, 2026

Temporary file and delivery metadata

For a file delivery, Golden Drop processes the uploaded file, original filename, byte size, SHA-256 checksum, creation time and expiry time. It also stores random server object identifiers and hashes of the access and delete secrets.

For upload rate limiting, the service records an upload event keyed to the observed client address or an internal hashed Golden client identity. Current rate-limit events are pruned after the active upload window; the production default is one hour.

Delivery, expiry, revocation and abuse control

The service uses this information to deliver the requested file, enforce size and storage limits, stop expired or revoked links, clean up temporary copies and limit abusive upload volume.

The Golden Drop service does not use an LLM to inspect, summarize or classify uploaded content.

Files are temporary

Golden Drop is transport, not long-term storage. Files delivered through Golden expire after 1 hour. Every request checks expiry state, and background cleanup removes expired copies and metadata.

Private URL tokens are kept out of ordinary access logs

The Golden Drop application runs without its ordinary access log, and the dedicated nginx vhost has access logging disabled. This is specifically to avoid copying temporary URL tokens into normal request logs.

Expire or revoke

You can choose the supported lifetime when a file is delivered. If you are the uploader and retain the management key, you can revoke the file before expiry.

Questions about Golden

Use the existing Golden connection and account help page for support related to your Golden account or connection.