Data handling
Privacy & retention
File Requests is a limited file handoff service. It does not analyze document contents with AI.
What we collect
We store the requester’s verified account identity and connection details, the selected folder identifier, request text, uploaded file names and sizes, and delivery results. Uploaders need no account. A capability link permits upload but does not prove who supplied a file.
How files move
Files enter private, encrypted temporary staging for structural validation, malware scanning, and reliable delivery. Only the bound Google Drive folder receives accepted originals. Its existing sharing settings apply. Google credentials are never shown to uploaders or AI assistants.
Service providers
Firmary operates File Requests using AWS hosting and encrypted backups. Firmary sign-in processes verified requester identity and permissions under its sign-in privacy notice, including limited network-address security records. Google receives accepted files and delivery metadata for the selected Drive folder. Resend receives the requester email and receipt or delivery-alert details, without file bodies, to deliver operational messages. The AI assistant the requester connects, such as ChatGPT or Claude, receives only owner-authorized setup, request and delivery metadata through tools, never uploaded file contents or Google credentials. PostHog (US) receives the pseudonymous usage events described below.
Google user data
When a requester connects Google Drive, File Requests asks only for their Google account email and the drive.file permission, which covers only the folder they pick and the files File Requests creates in it, not the rest of their Drive. File Requests uses that access only to confirm the chosen folder and deliver accepted uploads into it. Google user data is not sold, not used for advertising, not shown to uploaders or AI assistants, and not used to train AI models. File Requests’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. A requester can remove File Requests’ access at any time from their Google Account’s third-party connections.
Retention defaults
Temporary copies are deleted after confirmed delivery, within 24 hours. A blocked delivery is purged at 72 hours, after an owner notification is queued. Delivery metadata is retained for 90 days after request closure, unless deleted sooner. Deleted application records can remain in encrypted backups for up to 14 days. These are product defaults, not legal-retention guarantees.
Deletion
The requester can delete a request from its private detail page. This revokes the link, cancels undelivered work, and purges app-held data according to the stated schedule. It does not delete files already delivered to Google Drive.
Operational messages & logs
Receipts and connection or delivery alerts go only to the verified requester. Request and delivery timestamps support expiry and truthful status. Owner- and request-bound rate counters prevent abusive uploads and enforce size and cost limits; inactive counters are removed after 48 hours. Delivery records follow the 90-day schedule above. Minimal process-error logs rotate within a 50 MB limit per container and exclude file contents and credentials. These records are not used for advertising or profiling. These pages load no advertising pixels, session replay or analytics scripts. Pages that show a note about Firmary count how often each version of the note is seen and clicked, as a daily total per app, page and version kept by Firmary sign-in. The count contains no cookies, network addresses or anything else that identifies you. Your browser remembers which version it last showed, so the next one differs.
Usage analytics
The server sends pseudonymous usage events to PostHog (US): which tool or step was used, such as creating a request, accepting an upload or delivering a file; whether it worked and, if not, a short reason code; how long it took; and whether the AI assistant was ChatGPT, Claude or another. Server errors are reported the same way, as the kind of error and where in our code it happened, never its message. Requester events are keyed by a one-way code instead of the account; uploader and delivery events carry no identifier. They contain no names, email addresses, request text, file names, file contents or network addresses. Firmary uses them only to understand and improve how its apps are used, not for advertising.
Uploaded files
Uploaded files can contain personal, financial and tax information, including identification numbers, and are delivered only to the requester’s Google Drive folder after the checks described above. Do not use this service for payment-card data, medical records, passwords, API keys, or authentication codes.
Contact the operator through Support for privacy or deletion questions.