Subprocessors

This page is the current, canonical list of the third parties uploadthefile.com uses to provide the Service. It exists so that customers who act as data controllers can see, at a single URL, every party that may process personal data on their behalf, and so that changes to that list are announced in one predictable place, as our Data Processing Terms promise.

1. Subprocessors for your content

Under Section 7 of the Data Processing Terms, you give us general authorization to engage subprocessors that may process Covered Content, meaning personal data in the files you upload and visitor data collected by features you configure. We impose data-protection obligations on each of them consistent with the Data Processing Terms. The current Covered-Content subprocessors are:

Document conversion (Office documents to PDF) runs inside Cloudflare’s infrastructure — the same subprocessor already disclosed in the table above — using a disposable, no-egress Cloudflare Container, so no separate third-party subprocessor is involved. Our internal operations alerting tools receive only minimal controller data (such as an account identifier and event type) and never Covered Content, so they are not Covered-Content subprocessors either.

2. Service providers for our own processing

Separately, we use the following providers for the processing we carry out as an independent controller, covering account, billing, email, sign-in, and analytics data, as described in our Privacy Policy. They are listed here for transparency; they are not Covered-Content subprocessors under the Data Processing Terms.

3. How we announce changes

When we add or replace a subprocessor, we update this page and record the change in the log below before the new subprocessor processes Covered Content, giving you the opportunity to object as described in Section 7 of the Data Processing Terms (by deleting the affected content or closing your account). If you need to monitor this list (for example, for your own Article 28 records), check this page or contact us at contact@uploadthefile.com and we will answer questions about upcoming changes.

4. Change log

• October 20, 2026: PostHog now also: (1) analyses session recordings with its AI tools (Replay Vision), which send a recording to a Google Gemini model run by Alphabet, one of PostHog’s AI subprocessors, possibly outside the EU, under terms that forbid training on the data; the model sees only what the masked recording shows; (2) receives from our servers that a checkout payment failed or a checkout expired unpaid, with the plan, billing period and the pseudonymous identifier, never card details, amounts, names or email addresses; (3) receives answers to a new feedback question, “What stopped you?”, asked when someone comes back from the payment page or closes a plan change, with the plan and where it was asked. It still receives no uploaded files or page content, so PostHog remains a service provider for our own controller processing, not a Covered-Content subprocessor.
• October 20, 2026: Session recordings in the dashboard and account screens (Microsoft Clarity and PostHog) now show our own buttons, menus and page headings, so we can see which part of the product someone was using. Everything else on those screens stays masked in the browser as before: file, page, link, workspace and customer names, email addresses, typed text and pictures are still not sent. No change to who receives data or where it is stored.
• October 19, 2026: PostHog now also receives session recordings and product events from the browser, loaded only after a visitor accepts analytics cookies, on every page except the admin tools and customer-published content. Typed text and the upload window are masked everywhere; in the dashboard, account and token-carrying screens all on-screen text is masked, pictures are hidden and the names in links and labels are removed in the browser, and every page address loses its query and fragment, so file, page and link names are not sent. PostHog sets a first-party cookie and browser storage (ph_ followed by the project key) and, as for any web request, receives the visitor’s IP address. Data stays in PostHog Cloud EU (Frankfurt). It still receives no uploaded files or page content, so PostHog remains a service provider for our own controller processing, not a Covered-Content subprocessor.
• October 19, 2026: PostHog now also receives a notice each time one of our feedback questions is shown (the same details as an answer, without the answer), so we can tell how many people choose not to answer. Still sent from our servers, with no script in the browser and no cookie; still no uploaded files, page content or file names, so PostHog remains a service provider for our own controller processing, not a Covered-Content subprocessor.
• October 18, 2026: PostHog now also receives, with an answer to the thumbs under a newly published link, that link’s name (for example calm-river), so an answer can be traced to the page it is about. It still receives no uploaded files, no page content and no file names, so it remains a service provider for our own controller processing, not a Covered-Content subprocessor.
• October 18, 2026: Added PostHog (PostHog Inc., using PostHog Cloud EU in Frankfurt) as a service provider for our own controller processing: it receives the answers people give to our in-product feedback questions (under a newly published link, on the help pages, and once on a first visit to the dashboard), with the page path, site language, country, plan and, for signed-in users, the same pseudonymous one-way identifier our analytics use. Answers are sent from our servers, so no PostHog script runs in the browser, no cookie is set and the visitor’s IP address is not passed on. Email addresses and long numbers typed into the optional note are removed before it is sent. It receives no uploaded files and no file, page or link names, so it is not a Covered-Content subprocessor.
• October 9, 2026: Extended Microsoft Clarity (Microsoft Corporation, an independent controller under its terms) to the signed-in dashboard and added product events. In the dashboard the whole screen is masked in the browser except our own buttons and menus, so file, page and link names are not sent; Clarity receives the dashboard page address, which can include a search term the user typed. Product events (file type and approximate size, upload outcome, sign-in attempts with the email provider but never the address, dashboard features used) and, for signed-in users, a pseudonymous one-way identifier are also sent to Microsoft Clarity and Google Analytics. All of it loads only after a visitor accepts analytics cookies. Clarity still never runs in the admin tools or on customer-published content and receives no uploaded files, so it remains a service provider for our own controller processing, not a Covered-Content subprocessor.
• October 7, 2026: Added Microsoft Clarity (Microsoft Corporation) as a service provider for our own controller processing: session recordings and heatmaps of our public pages, loaded only after a visitor accepts analytics cookies. It is not a Covered-Content subprocessor: it never runs in the dashboard, the admin tools or on customer-published content, and it receives no uploaded files. Typed text, numbers, email addresses and the upload window are masked in the browser before anything is sent.
• September 22, 2026: Added OpenAI (OpenAI, L.L.C. — the contracting entity for a US-based customer under OpenAI’s Business Terms; EEA/Switzerland and UK customers contract with a different OpenAI entity, which does not apply here) as a Covered-Content subprocessor for automated NSFW classification of uploaded images and of frames extracted from uploaded video. It receives a downscaled copy (approximately 640px) of the image or frame being checked, never the stored file, and receives no other file types, no filenames and no account data; OpenAI does not use this data to train its models and retains no copy of it beyond the request. This is a disclosure of processing already underway, not advance notice of a new one: OpenAI has performed this classification since September 4, 2026, when it replaced the Cloudflare Workers AI classifier that issue #633 found was never actually running. The Cloudflare entry above was corrected to match on September 8–16, 2026.
• September 16, 2026: Widened the Cloudflare purpose to cover page preview thumbnails on the dashboard: Cloudflare Browser Rendering lays out a page’s own markup and screenshots it, and the Cloudflare Images binding and Media Transformations derive a small still from a stored image or video. No new subprocessor: the processing happens inside Cloudflare, which is already disclosed for hosting and compute. A thumbnail is shown only to the page owner (and to an administrator, who can already open the page in full) and is never published as a social-preview card.
• September 8, 2026: Corrected the Cloudflare purpose: Workers AI serves PDF chat only; the Images-binding downscale and Media Transformations frame extraction support moderation.
• August 26, 2026: Added Ahrefs (Ahrefs Pte. Ltd.) as a service provider for our own controller processing: cookieless website analytics on our marketing pages. It is not a Covered-Content subprocessor: it runs only on pages we publish, never on customer-published content, and it receives no uploaded files. It sets no cookies and stores nothing on your device.
• July 17, 2026: Initial publication of this page. It lists the Covered-Content subprocessors already disclosed in the Data Processing Terms, and adds the service providers used for our own controller processing.

5. Contact

Questions about this list or our subprocessor relationships? Email contact@uploadthefile.com.