Privacy Policy

If you create a FileBench account, we process the information needed to run it:

• Your email address and password (stored as a salted, one-way hash — we cannot read your password).
• Your account identity (an internal account ID) and any optional profile details you choose to set, like a display name.
• Authentication and session information — a session cookie and its associated login records (see "Cookies" and "Logs" below) — used to keep you signed in and to let you review or revoke your own active sessions.
• If Google sign-in is enabled for your account: your Google account ID, email address, name, and profile picture (if available), shared with FileBench by Google when you choose to continue with Google. FileBench uses this only to create or sign in to your FileBench account, never to access your Gmail, Drive, Calendar, Contacts, or any other Google data, and never for advertising.

You upload files to FileBench so we can run the specific processing operation you request — converting, compressing, editing, inspecting, or otherwise transforming that file. Files are private by default: nobody else can see or download them unless you deliberately create a share link (see "Share links" below).

Uploaded files, and the output files a processing job produces, are kept only temporarily:

• Guest uploads (no account): kept for approximately 1 hour after upload, then deleted.
• Registered accounts: kept for approximately 7 days, then deleted.

Deletion runs on a recurring automated schedule, not the exact instant a file's retention window ends — there can be a short delay between a file becoming eligible for deletion and the cleanup process actually removing it. Output files you generate follow the same retention window as the file they came from.

Uploaded and generated files are stored in private cloud object storage — the storage bucket itself is not publicly browsable or listable. When your browser needs to upload a file or download a result directly, FileBench's server generates a temporary, cryptographically signed link (a "presigned URL") scoped to that one file and valid for a limited time. We don't publish the storage credentials that create those links, and this policy doesn't describe our infrastructure setup beyond that high level.

Uploaded files are processed automatically by FileBench's own backend infrastructure, using standard media and document tooling appropriate to the operation you request — for example FFmpeg for audio/video, image-processing libraries for pictures, PDF tooling for documents, and OCR (text recognition) for scanned pages. Processing is automated: FileBench staff do not manually open, view, or review the content of your files as part of normal operation.

FileBench performs a basic, automated file-type check on uploads (confirming the file actually is the format it claims to be) so it can offer the right tools — this is a technical check, not a review of your file's contents.

FileBench's codebase includes optional malware-scanning support (ClamAV) that can be enabled per deployment. As of this policy's last-updated date, malware scanning is not active in FileBench's production environment. If that changes, uploads would be scanned automatically before processing, and this section will be updated to say so.

Like most web services, FileBench's infrastructure records standard operational information to keep the service running and secure:

• IP address and browser user-agent string, associated with login sessions and rate-limiting.
• Request and error logs, and timestamps, generated by normal server operation.
• Security-relevant account events — sign-in, sign-out, session revocation, password/Google-account linking — kept as an internal audit trail.
• Content-Security-Policy violation reports, a standard browser security mechanism that helps us notice broken or malicious scripts on the site.

We don't collect device fingerprinting, precise location, or any browser/device details beyond what's listed above.

FileBench runs its own first-party, self-hosted product analytics — for example, which tools get used and whether a conversion completed — stored in FileBench's own database. There is no third-party analytics, advertising, or tracking service (no Google Analytics, no ad pixels, no cross-site tracking) installed on FileBench.

FileBench uses a small number of cookies, all functional — none are used for advertising or cross-site tracking:

• A signed-in session cookie, if you have an account and are logged in.
• A guest session cookie, which lets FileBench recognize your uploads/jobs across requests before you create an account.
• A short-lived security cookie used only during Google sign-in, to protect that process against forgery.
• A language-preference cookie that remembers whether you're using FileBench in English or Arabic.

Your theme preference (light/dark/system) is stored in your browser's local storage, not a cookie. Because every cookie above is essential to running the site or is a simple preference — never advertising or third-party tracking — FileBench does not show a cookie-consent banner.

If share links are enabled, you can generate one to let someone else view or download a specific file without creating a FileBench account. Anyone with a valid, unexpired share link can access the file it points to — treat a share link like you would any other link that grants access to a file. A share link stops working once its underlying file expires or is deleted, whichever comes first.

Account information and uploaded files are retained on different schedules:

• Uploaded/generated files: deleted automatically per the guest (~1 hour) or registered (~7 days) windows described above.
• Account information (email, account ID, session/security history): kept for as long as your account exists.

Deleting an individual file does not delete your account, and deleting your account does not necessarily happen instantly — see "Your rights and choices" below for how to request either.

Running FileBench relies on a small number of infrastructure providers, in these categories:

• Cloud compute infrastructure, to run FileBench's servers.
• Cloud object storage, to hold uploaded and generated files privately (see "Private storage" above).
• Google, as an optional authentication provider — only if Google sign-in is enabled (see "Account information" above).

FileBench does not currently use an email-delivery provider (no account/marketing emails are sent) or any payment/billing provider — FileBench has no paid plans or subscriptions.

Whatever privacy law applies to you, FileBench aims to make the following straightforward without requiring a formal legal process:

• Access — ask what account information we hold about you.
• Correct — update your account details (display name, email) yourself, or ask us to.
• Delete files — remove any individual file, or your whole file library, from your file library page at any time.
• Delete your account — request deletion of your account and its associated information.
• Ask a question — contact us at the address below with any privacy question.

FileBench does not claim certification under, or guaranteed coverage by, any specific privacy law (for example GDPR or CCPA) — this section describes what we actually offer, not a legal compliance guarantee.

If FileBench's practices change in a way that affects this policy, we'll update this page and its "last updated" date above.

Privacy questions or requests: support@filebench.app.