Remove Google login friction.
Sprag uploaders need the page URL and optional PIN, not a Google account.
Google Forms file upload alternative
File upload without making Drive the intake system.
Google Forms is a form builder with a file-upload question. Sprag is an intake system for sensitive files: accountless upload pages, operator-chosen storage, optional E2E, optional Tor ingress, and receipt records.
Comparison
Google Forms asks questions. Sprag receives sensitive files.
Google's help docs say file-upload responders need to sign in to a Google Account and that uploaded files are stored in a new Google Drive folder for the form owner. Sprag removes that account and Drive dependency from the sender path.
| Question | Google Forms file upload | Sprag |
|---|---|---|
| Sender account | Google says responders need to sign in for file upload. | Uploaders do not need a Sprag account. |
| Storage path | Uploaded files go to Google Drive. | Files stream to operator-chosen S3-compatible storage. |
| Primary job | Form response collection. | One-way secure file intake. |
| Return surface | Part of a broader Google workspace flow. | No listing, folder, retrieval, or download path for uploaders. |
| Hardening | Google account and workspace controls. | Plain HTTPS, E2E-required, or onion-only modes. |
Sprag edge
Use Sprag when the upload channel is the risk boundary.
Do not route intake through Drive by default.
Run Sprag on infrastructure and storage that match your policy.
Keep proof around what arrived.
Receipts, submission groups, manifests, and sealed pages are built around file arrival.