Subprocessors
Last updated: November 10, 2026
This page is the current list of the third parties uploadthefile.com uses to provide the Service, and the place where we announce changes to it. It lets customers who are controllers see, at one address, every party that processes personal data on their behalf (section 1), the independent recipients of web addresses we use to prevent abuse (section 2) and the providers we use for our own processing (section 3). The Data Processing Terms refer to this page.
1. Subprocessors for Covered Content
Under section 7 of the Data Processing Terms, you give us general written authorisation to engage these Subprocessors. They process Covered Content, meaning personal data in Your Content and personal data of Visitors collected by features you configure. Each works under data processing terms with us, shown in the last column. These are the same rows as Annex III of the Data Processing Terms.
| Provider and legal entity | Purpose | Processing location | Data protection terms |
|---|---|---|---|
| SupabaseSupabase Pte. Ltd. | Database and authentication: account and page records, and the visitor data collected by the features you configure (email gate, contact form, email box) | Sweden (AWS eu-north-1, Stockholm) | Supabase data processing addendum, which forms part of its terms of service and includes the EU standard contractual clauses and UK and Swiss addenda |
| CloudflareCloudflare, Inc. | Hosting, CDN, DNS and Workers compute; R2 object storage of all uploaded files (four buckets: published pages, upload quarantine, archive copies and legal-hold copies); Durable Objects and Containers for upload handling, file conversion and media scanning; Workers AI inference (for the PDF-chat feature only); image downscaling and video frame extraction for automated content moderation; headless browser rendering and image derivation to generate the preview thumbnails shown to a page owner on their dashboard; and the CSAM scanning tool | Cloudflare global network. The R2 buckets were created with Cloudflare’s Western Europe location hint, which Cloudflare treats as best effort; no jurisdiction or location restriction is set | Cloudflare data processing addendum, incorporated in its self-serve subscription agreement; it provides the EU standard contractual clauses, and Cloudflare, Inc. participates in the EU-US Data Privacy Framework |
| OpenAIOpenAI OpCo, LLC | Automated NSFW classification of uploaded images and of frames extracted from uploaded video. Receives a downscaled copy (approximately 640px) of the image or frame being checked — never the stored file. OpenAI does not use this data to train or improve its models, and retains no copy of it beyond the request. | US | OpenAI data processing addendum, incorporated in its services agreement for customers outside the EEA and Switzerland |
| ResendPlus Five Five, Inc. (trading as Resend) | Email delivery of notifications to page owners, including notices that carry the messages Visitors send through a contact form on a Published Page | US | Resend data processing addendum, concluded when its terms of service are accepted; it provides the EU standard contractual clauses and a UK addendum |
Document conversion (Office documents to PDF) and media scanning run in disposable Cloudflare Containers that have no internet access, so no separate third party is involved.
2. Independent recipients for abuse prevention
To stop abuse, we send web addresses to two services that are not our Subprocessors: we have no data processing terms with them, they use what they receive under their own terms, and we send them web addresses, not your files. A web address taken from a file can contain personal data. We send these addresses as an independent controller, for the safety purposes described in section 3.3 of the Data Processing Terms and in our Privacy Policy.
| Provider and legal entity | Purpose | Processing location |
|---|---|---|
| Google Safe BrowsingGoogle LLC | Checks whether a web address is listed as unsafe. Receives the address of a Published Page, the web addresses found as links in uploaded HTML, SVG and ZIP-hosted website files, and the destination of a short link. It receives no file contents other than those addresses. A match refuses the upload. | US |
| urlscan.iourlscan GmbH | Receives a short link’s destination address when we re-screen the link (we look up existing scan results for it), and addresses that an administrator chooses to have scanned. We submit scans with “unlisted” visibility, never “public”. Under urlscan’s terms an unlisted scan is not public, but vetted security researchers and security companies on its platform can see it. | EU |
3. Service providers for our own processing
We also use the following providers for the processing we carry out as an independent controller: account, billing, email, sign-in, analytics and operations alerts, as described in our Privacy Policy. They are listed for transparency. They are not Subprocessors under the Data Processing Terms.
| Subprocessor | Purpose | Processing location |
|---|---|---|
| Supabase | Database and authentication for account data | Sweden (AWS eu-north-1, Stockholm) |
| Cloudflare | Hosting, CDN, and compute for the Service itself; Turnstile bot checks on sign-in, sign-up and forms. When you buy a domain through the Service, Cloudflare also acts as registrar: it receives the registrant contact details you give us and handles them in its own right, under its registrar terms and the rules of ICANN and the registry, which can require it to disclose them | Global edge network |
| Resend | Transactional email (team invites, billing and account notices) | US |
| Polar | Merchant of record and reseller for paid plans and domains: sells, charges, invoices and handles refunds; an independent business for buyer data under its own terms | US |
| Sign-in with Google (Google acts as an independent controller of your Google account), and Google Analytics (loaded only with your cookie consent) | US | |
| Ahrefs | Cookieless website analytics on our marketing pages (no cookies, no cross-site tracking; raw IP addresses are discarded and never stored) | Singapore (entity) / US (storage) |
| GitHub | Sign-in with GitHub (GitHub acts as an independent controller of your GitHub account) | US |
| Microsoft | Sign-in with Microsoft (Microsoft acts as an independent controller of your Microsoft account), and Microsoft Clarity session recordings, heatmaps and product events on our public pages and, with on-screen content masked, in the dashboard (loaded only with your cookie consent; Microsoft acts as an independent controller) | US |
| PostHog | Product feedback: the answers people give to our in-product questions (thumbs up or down, the reasons chosen, an optional note, and for the thumbs the name of the link just published) and that a question was shown, sent from our servers (with your cookie consent, linked to the recording of that visit). With your cookie consent, also session recordings and product events on every page except the admin tools and customer-published content, with typed text masked everywhere and, in the dashboard and account screens, all on-screen text except our own buttons, menus and page headings, pictures and the names in links masked in the browser. Recordings may be analysed by PostHog’s AI tools (Replay Vision), which run on Google models (a PostHog subprocessor, possibly outside the EU, no training on the data). From our servers, it also receives that a checkout payment failed or expired, with the plan, billing period and pseudonymous identifier | US (entity) / EU, Frankfurt (storage); AI analysis may run outside the EU |
| Telegram | Operations alerts to our staff: the event type and identifiers such as account and page identifiers; never file contents | British Virgin Islands / United Arab Emirates (Telegram group entities) |
4. How we announce changes
Before a new Subprocessor starts to process Covered Content, or replaces an existing one, we post the change on this page, with the date it takes effect, at least 30 days in advance. That posting is the notice. You may object on reasonable data-protection grounds within that period by emailing contact@uploadthefile.com; section 7 of the Data Processing Terms sets out what happens next. If a Subprocessor must be replaced at short notice for security or continuity reasons, we post the change as soon as we can and your right to object runs from that posting. Check this page to follow changes; the log below records each one.
Changes to the lists in sections 2 and 3 are recorded in the same log. They do not carry the 30-day notice period, because those providers are not Subprocessors.
5. Change log
- November 10, 2026: Corrected and completed this page. (1) Supabase: removed “file storage”; it holds our database and authentication, and uploaded files are held in Cloudflare R2. (2) Cloudflare: the purpose now names R2 object storage of uploaded files (four buckets, no location restriction), Durable Objects and Containers, and Cloudflare’s separate role as registrar for domains bought through the Service moved to the list of providers for our own processing. (3) OpenAI: the contracting entity is OpenAI OpCo, LLC. (4) Resend: added to the Covered-Content subprocessors, because it delivers the notices that carry messages Visitors send through contact forms. (5) Google Safe Browsing and urlscan.io: moved out of the subprocessors into a new list of independent recipients, because we do not have data processing terms with them and they receive web addresses, not files. (6) Telegram: added to the providers for our own processing, because it receives operations alerts. (7) Polar is described as merchant of record and reseller, and Google, GitHub and Microsoft sign-in as independent controllers of your account with them. (8) Each Covered-Content subprocessor now shows its legal entity and the data processing terms it works under. (9) Supabase: the location now names the region of our database, Sweden (AWS eu-north-1, Stockholm). (10) Cloudflare: the location now says where the R2 buckets are (Western Europe location hint). All of this describes processing that was already under way; none of it is advance notice of a new subprocessor.
- November 1, 2026: Removed VirusTotal. It was listed for an optional file-hash lookup that our administrators could run by hand; that lookup was never used, and it has now been switched off and removed from the Service. No data goes to VirusTotal.
- October 30, 2026: When a visitor has accepted analytics cookies and PostHog is recording the visit, a feedback answer (or the notice that a question was shown) now also carries that recording’s session id and PostHog’s random identifier for the browser, so the answer can be opened next to its recording. Both ids are ones PostHog already receives from the recording itself; without that consent nothing is added. Still sent from our servers; 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 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.
6. Contact
Questions about this list or our subprocessor relationships? Email contact@uploadthefile.com.