1. Information we handle
- Account information: your name, email address, account status, and sign-in details. If you use a local password, a password hash is stored.
- Files and shares: the files you upload, filenames and folder paths, sizes, file types, share titles and descriptions, expiration dates, access settings, and any recipient or invitation details you provide.
- Usage and technical records: download events and counts, timestamps, the IP address received by the service, browser or user-agent information, and operational or security logs.
Only upload or enter information that you are authorized to share. A file's contents may include information about other people.
2. Google sign-in
If you choose Google sign-in when it is enabled, Google authenticates you and provides your Google account identifier, name, email address, and profile-picture information. Drop uses this information to link or identify your local account, sign you in, and display your profile.
Drop requests the basic openid, email, and profile permissions. It does not request access to your Gmail messages, Google Drive files, calendar, or contacts, and it does not receive your Google password.
The linked account identifier, email address, name, and profile-picture URL may be stored with your Drop account. Authentication information is handled during sign-in to establish your session.
Google account data is not sold, used for advertising, or used to train artificial-intelligence models. It is used for the sign-in and account features described here. Drop's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements where applicable.
3. How we use information
We use information to operate accounts, authenticate users, receive and deliver files, create archives, resume uploads, enforce share passwords and limits, and show sharing activity. We also use it to troubleshoot problems, prevent misuse, maintain security, and recover the service.
If an email feature is used, account or share information and recipient addresses are used to deliver the requested invitation, notification, or account message. Drop does not sell personal information or use it for advertising.
6. Storage, security, and retention
Files and account information are held on the operator's self-hosted systems and storage. HTTPS protects the browser connection. Stored files are accessible to authorized service administrators; this is not an end-to-end encrypted storage service.
- Shares: the current default expiry is 7 days, although the uploader or administrator may choose a different expiry. Expiration blocks normal share access; it does not immediately erase the underlying files.
- File cleanup: the current configuration schedules expired share files for cleanup 30 days after expiry. Cleanup runs periodically and may be delayed by operational issues.
- Accounts and activity: account details, linked sign-in information, share metadata, and download records may remain until removed by the administrator or through an account/deletion request.
- Logs and backups: the application schedules old-log cleanup after 14 days and database-backup cleanup after 7 days. Infrastructure logs, active log files, manual backups, or recovery copies may remain longer. Deletion from the live service does not immediately remove every backup copy.
Retention settings can change. The policy will be updated when the practices described here materially change.
7. Access, unlinking, and deletion
You can update available profile information and unlink Google from your profile's Linked Accounts section. You can also remove the connection through your Google account's third-party connections.
Unlinking or revoking Google access does not itself delete your Drop account, previously stored profile details, or files. To request access to, correction of, or deletion of your personal information, account, or uploaded files, email auth-rdz@googlegroups.com. Include the account email or relevant share URL so the request can be located. We may need to verify your identity before acting.
Some information may need to remain for security, legal obligations, or backup recovery. We will explain relevant limitations when responding. We cannot erase copies that recipients have already downloaded or retained independently.
8. Changes to this policy
This policy applies to Drop at drop.rdz.sh, rather than every installation of Erugo or a third party's services. Material changes will be reflected here with an updated date. If a new use of Google account data requires additional consent, that consent will be requested before the new use begins.
9. Contact the operator
For privacy questions and data-deletion requests concerning this Drop instance, contact:
Avoid including passwords, authentication codes, or sensitive file contents in your initial request.