Remi

remihq.com

We have not found a subprocessor list published by Remi. We monitor 4 of its documents, which we last checked on Nov 11, 2026.

Subprocessors

None extracted.

Web TechnologiesCSV of Remi's web technologies · Atom feed of Remi's web technologies

Remi's homepage made 150 requests to 19 domains, and 7 services controlled by another company.

Analytics (4): Google Cloud, HubSpot, Meta; usually detected as Analytics: posthogCookie compliance (1): EnzuzoOther (2): reviewed as Digital asset management: Cloudinary; usually detected as Security: Amazon Web Services

7 third parties by category: Analytics 4Cookie compliance 1Other 2

Third parties 7 · 90 requests
Cloudinary cloudinary.com 33% of the page's requests 49
Google Cloud Google Analytics Google Maps Google Tag Manager 8% of the page's requests 12
HubSpot HubSpot HubSpot Analytics 6% of the page's requests 9
Meta Facebook Pixel 2.9.419 6% of the page's requests 9
posthog posthog.com 4% of the page's requests 6
Amazon Web Services on.aws 2% of the page's requests 3
Enzuzo Enzuzo 1% of the page's requests 2
First party 1 · 60 requests
Remi Cloudinary Framer Motion HSTS LottieFiles Lucide Next.js 16.3.6 Next.js App Router Open Graph PWA Priority Hints Radix UI React Turbopack Vercel Vercel Analytics Vercel Speed Insights 2.0.0 Webpack core-js 3.32.2 40% of the page's requests 60

6 tracked companies loaded by the homepage are not in Remi's subprocessor list. A website can use a service without it processing customer data.

Service statusCSV of Remi's status page incidents · Atom feed of Remi's status page incidents

Aug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: no incident reportedSep 28: no incident reportedSep 29: no incident reportedSep 30: no incident reportedOct 1: no incident reportedOct 2: no incident reportedOct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: no incident reportedOct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: no incident reportedNov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

No incidents reported since Sep 27, 2026

As Remi's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

ChangesCSV of Remi's changes · Atom feed of Remi's changes

None since tracking began.

Rating badge for Remi's site

Remi transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/remi"><img src="https://thirdpartyindex.com/badge/remi.svg" alt="Remi transparency rating on Third Party Index" height="20"></a>
[![Remi transparency rating on Third Party Index](https://thirdpartyindex.com/badge/remi.svg)](https://thirdpartyindex.com/vendors/remi)