Privacy Policy

Information FileHub handles

FileHub handles account and work information needed to provide transaction workspaces, checklists, tasks, file storage, and email features. This can include your name, work email, organization and role; transaction and listing details; checklist and task content; files and file metadata; and information you choose to enter or upload.

If you use a FileHub Inbox address, FileHub receives the email sender, subject, date, a limited text excerpt, and attachments sent to that address.

When you connect Gmail, FileHub uses Google OAuth permissions to identify the connected account, find messages with attachments from the previous 14 days, and read those messages and their attachments for the File Inbox. Gmail authorization also includes email-send permission. FileHub sends application emails through Resend. Synced message details can include the sender, subject, message date, a limited text excerpt, and attachment names and contents. FileHub does not use Gmail content for advertising.

When you ask FileHub to analyze a document, its document contents may be sent to Google Cloud Document AI to return text and page suggestions. When you prepare an electronic signature request, the selected documents and signer details are sent to DocuSeal to provide that service.

How information is used

FileHub uses information to authenticate users, enforce organization and transaction access, display and organize transaction work, store and preview files, provide requested OCR and signature workflows, and send emails to recipients selected by the user.

Google user data is used only to provide the Gmail inbox features described above and in response to user actions or configured inbox synchronization. We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models.

Storage and retention

FileHub stores application records in its database and keeps private files in Cloudflare R2. Gmail access and refresh tokens are encrypted before they are stored. FileHub does not store your Google password.

Gmail messages and unimported Inbox attachments synced to FileHub expire and are deleted after 14 days. If you import an attachment into a transaction, it becomes a transaction file and remains available until an authorized user deletes it or the transaction’s organization removes it under its file practices.

Disconnecting Gmail revokes FileHub’s Gmail authorization and removes the stored connection tokens. It does not automatically delete transaction files that you previously imported. You can also revoke access from your Google Account security settings.

When information is shared

FileHub shares information with service providers only as needed to operate the features you use: Clerk provides account authentication; Cloudflare provides application hosting, private file storage, and inbound email processing; Resend provides outbound email delivery, receiving the recipients, message content and selected attachments needed for that delivery; Google provides Gmail and, when requested, Document AI; and DocuSeal provides electronic signature workflows. Email content is sent to the recipients you specify. Users who are authorized for a transaction may see its transaction information and files.

We do not sell personal information or Google user data. We may disclose information when required by law or to protect the security of FileHub and its users.

Your choices and requests

You choose whether to connect Gmail and whether to request email, OCR, or signature actions. You can disconnect Gmail in FileHub or revoke the connection in your Google Account. Authorized users can delete Inbox attachments and transaction files using the available FileHub controls.

For privacy questions or requests about information in FileHub, contact info@opendeed.ai. Your organization may administer transaction records and files that you are authorized to access.

Changes to this policy

We may update this policy as FileHub changes. The current version will be posted on this page with its effective date. If a change materially affects how Google user data is used, we will update the relevant disclosures before applying the new use.