Nineteen Ninety Five Limited (trading as Dupli)
Last updated: 7 September 2026
Last updated: 07.09.2026
To provide the dupli service we engage a small number of third parties (“sub-processors”) that may process customer data or personal information on our behalf. This page lists our current sub-processors. It is referenced by our SaaS Agreement and Privacy Policy.
| Sub-processor | Purpose | Data processed | Primary location | When |
|---|---|---|---|---|
| Google Cloud Platform / Firebase (Google LLC) | Application hosting, database, serverless functions, file storage, encryption key management, logging | All customer data stored in dupli, including account, site, contractor, and safety records, uploaded files, and encrypted third-party integration credentials | Database: Australia (australia-southeast2). File storage: United States (us-west1, Oregon). Serverless functions: United States (us-central1/us-west1). | Always |
| Google Analytics / Firebase Analytics (Google LLC) | Product-usage analytics to understand how the app is used and improve it | Usage telemetry only: a pseudonymous client/instance identifier, approximate location derived from IP address, device and browser information, and in-app screen views and events. No customer records. | Google global infrastructure | Always |
| Brevo (Sendinblue SAS) | Delivery of transactional email (for example account, notification, and prequalification emails) | Recipient email address, sender and subject, and email content | European Union | Always |
| Kudosity (formerly Burst SMS) | Delivery of bulk and notification SMS | Recipient mobile number and message content | Australia | Only when an organisation has the SMS module enabled |
| Procore (Procore Technologies, Inc.) | Two-way synchronisation of projects, directory, daily logs, and documents with the customer’s Procore account | Project and vendor records, project contact names and email addresses, aggregated worker and visitor sign-in times, and prequalification documents — as directed by the customer | United States | Only when an organisation connects the Procore integration |
Locations are indicative of where data is primarily stored or processed and may change; each provider may also use its own infrastructure in other regions for redundancy and processing. Refer to each provider’s own documentation for authoritative detail.
Changes to this list
We will update this page before engaging a new sub-processor, or before materially changing the role of an existing one. Customers with questions about this page or our use of sub-processors can email [email protected]