Lucky Orange
Lucky Orange declares 20 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Amazon Web Services, Google Cloud and OpenAI. The list last changed on Nov 5, 2026: 0 added, 0 removed, 1 changed. 1 tracked vendor, MinIO, names Lucky Orange as a subprocessor.
Subprocessors CSV of Lucky Orange's subprocessors · Atom feed of Lucky Orange's subprocessors DORA draft CSV of Lucky Orange's subprocessors as declared by Lucky Orange what's this? ·
20 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| AWS | Cloud infrastructure | US | |
| Braintree by PayPal | Payment Processing | US | |
| Buddy | CI/CD & DevOps Automation | US | |
| Calendly | Call Scheduling | US | |
| Cloudflare | CDN provider | Processing is performed at the data center â� (https://www.cloudflare.com/network/) that is closest to the End User | |
| Docusign | Electronic Signature & Agreement Management | US | |
| Elastic | Cloud infrastructure | US | |
| Google Cloud | Cloud infrastructure | US | |
| HelpScout | Customer Support | US | |
| Mailgun | Email Delivery | US | |
| Notion | Cloud-based Workspace & Documentation | US | |
| OnePage | CRM | US and Ireland | |
| OpenAI AI | Generative AI | US | |
| Postmark | Email Delivery | US | |
| ProsperStack | Customer Retention | US | |
| QuickBooks | Customer Management | US | |
| Salesforce/Pardot | Marketing Automation & Lead Management | US | |
| SingleStore | Data Lake | US | |
| TypeForm | Survey & Feedback Management | US | |
| Zapier | Workflow Automation | US |
Web TechnologiesCSV of Lucky Orange's web technologies · Atom feed of Lucky Orange's web technologies
Lucky Orange's homepage made 256 requests to 23 domains, 11 services controlled by another company, and 2 domains not identified.
11 third parties by category: Advertising 3Analytics 2A/B Testing 1Other 5
ordozen.comroeyecdn.com
5 tracked companies loaded by the homepage are not in Lucky Orange's subprocessor list. A website can use a service without it processing customer data.
Subprocessor of (1)CSV of the companies listing Lucky Orange · Atom feed of the companies listing Lucky Orange
MinIO min.io Session recordings and form analytics; processes visitor IP addresses, browser data, session recordings, and any personal data captured in form interactions
Service statusCSV of Lucky Orange's status page incidents · Atom feed of Lucky Orange's status page incidents
90 days agotoday
- 1 incident in 90 days
- 0 major or critical
- 2 h 46 min typical time to resolve
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Data Accessibility Delay | minor | 2 h 46 min | |
| Visitor Table Unavailable | major | 4 h 10 min | |
| Delayed data ingestion | minor | 8 h 53 min | |
| Delay in data processing | minor | 1 h 16 min |
Incidents per month
critical major minor no impact stated
Components affected
| Component | Incidents | Bar |
|---|---|---|
| Web App | 1 |
As Lucky Orange's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by Lucky Orange's subprocessorsCSV of incidents reported by vendors Lucky Orange lists · Atom feed of incidents reported by vendors Lucky Orange lists
62 reported incidents in the last 30 days, by 6 of the vendors Lucky Orange lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that Lucky Orange was involved.
And 37 more. All of them: CSV · Who is around them.
ChangesCSV of Lucky Orange's changes · Atom feed of Lucky Orange's changes
See the list as we read it on any date: Time machine
- Changed subprocessor: Cloudflare locations: Processing is performed at the data center â� (https://www.cloudflare.com/network/) that is closest to the End User → Processing is performed at the data center (https://www.cloudflare.com/network/) that is closest to the End User evidence: subprocessor: Cloudflare list before and after: subprocessor: Cloudflare
- Changed subprocessor: Cloudflare locations: Processing is performed at the data center (https://www.cloudflare.com/network/) that is closest to the End User → Processing is performed at the data center â� (https://www.cloudflare.com/network/) that is closest to the End User evidence: subprocessor: Cloudflare list before and after: subprocessor: Cloudflare
- Changed subprocessor: Cloudflare locations: Processing is performed at the data center â� (https://www.cloudflare.com/network/) that is closest to the End User → Processing is performed at the data center (https://www.cloudflare.com/network/) that is closest to the End User evidence: subprocessor: Cloudflare list before and after: subprocessor: Cloudflare
- Changed subprocessor: Cloudflare locations: Processing is performed at the data center (https://www.cloudflare.com/network/) that is closest to the End User → Processing is performed at the data center â� (https://www.cloudflare.com/network/) that is closest to the End User evidence: subprocessor: Cloudflare list before and after: subprocessor: Cloudflare
- Changed subprocessor: Cloudflare locations: Processing is performed at the data center â� (https://www.cloudflare.com/network/) that is closest to the End User → Processing is performed at the data center (https://www.cloudflare.com/network/) that is closest to the End User evidence: subprocessor: Cloudflare list before and after: subprocessor: Cloudflare
- Changed subprocessor: Cloudflare locations: Processing is performed at the data center (https://www.cloudflare.com/network/) that is closest to the End User → Processing is performed at the data center â� (https://www.cloudflare.com/network/) that is closest to the End User evidence: subprocessor: Cloudflare list before and after: subprocessor: Cloudflare