No public evidenceBridgera and GDPR
CertReports found no public GDPR evidence for Bridgera as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.
Evidence
- Kind
- listing
- Issued or listed
- 18 Sep 2019
- Scope
- Bridgera is in the business of providing custom software development and maintenance services to our clients and their end users. Our client engagements are formalized through a Master Services Agreement (MSA) followed by Statements of Work (SOWs) for each project we work on under the MSA. For IoT engagements, we also offer a Software as a Service (SaaS) option to our clients. In all cases, our work is driven by the scope defined by the client and tailored to specific business needs of each client. The client’s requirements define the data that is captured and processed by the bespoke software we deliver under these contracts. The data and the applications we work on are and remain the intellectual property of the client. They are the Data Controllers and we are the Data Processors. We process various categories of personal data based on the requirement of the Client contracts. For example, for a client that provide home healthcare services, we capture and process patient personal details, medication details, picture of face and wounds / injuries. For a Real Estate CRM client we process information about various communities and the amenities they provide, price points and promotions, interior pictures for virtual walkthru’s, appliance details etc. The various category of personal data we process include: • First name, last name/surname, middle name/initial, maiden name • Email address • Home address (street, zip, postal code, city) • Phone number • Photo • Gender • Date of birth, place of birth • Bank account number & routing number • National Identification Number, Social Security Number • Driver's license number, State & Validity • Employee number • IP address • Cookie ID • Location data • Login • Password • Social media profile IDs/links • Mobile device IDs • Data gathered via the Internet of Things (IoT); RFID tags, data from so-called sensors and actuators • Any “identifier” gadget • Emergency contact names, addresses and telephone numbers • Health details • Medical records & physician details • Medication details: names of medications, pictures and prescriptions We process these personal data, acting as the data processor, to fulfil our responsibilities under the client contract. The data is processed by Bridgera solely on documented instructions of the relevant client under the client contract. Many of the applications we work on are catering to the essential business operations of our clients. So we will process information about our clients services and products, prices, promotions, orders, payments and track their end customer accounts, generate reports and analytics driven insights based on data processed by the applications. We persist the data on various relational and NoSQL databases and archive old data based on client’s business rules. Data is encrypted for security purposes, based on client’s business needs. Further all applications use stringent role-based access mechanisms to limit data access. For example, HR Managers may see full SSN, while other staff may only see the last 4 digits. Applications are hosted on servers that are in the geography of the client and are protected by firewalls and other monitoring software that help prevent and detect and attempts to hack into the servers. Passwords cannot be seen even by the database Admins – they can only be reset. To summarize, we build and operate systems that implement client business rules and data processing logic/formulas. The data and systems remain under the control of client management and are the property of the client. Our role is to be their technology partner to leverage information technology to operate their business efficiently and effectively, at the required scale.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Bridgera LLC: Inactive | Live pagesha256 861e9f8afd |
What GDPR means, and what it does not
"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.
Read the GDPR guide and browse all vendors with evidenceQuestions buyers ask
Is Bridgera GDPR compliant?
There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Alternatives with GDPR evidence
Similar vendors (shared product tags or the AI infrastructure category) whose GDPR row is verified or vendor-stated, ranked by similarity.
