Jido Maps
GDPR evidence
Turn your data into a deployed computer vision model
No public evidenceJido Maps and GDPR
CertReports found no public GDPR evidence for Jido Maps 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
- 10 Jan 2020
- Scope
- We use End-User Data for providing the core aspects of the Service to Developers, specifically to allow Developers to submit digital content to us for analysis and storage by our spatial recognition software for purposes of retrieving such digital content upon request by the Developer (in other words, to assist with Developer's augmented reality functionality in its Developer Application). In addition, as a fundamental aspect of the Service, we aggregate End-User Data from all of our Developers to provide a more functional Service to Developers and End-Users by creating persistent augmented reality functionality across Developer Applications. We use Developer Data for our own purposes of understanding how Developers use the Service, for the purpose of improving the Service over time, and to send Developers with information about Jido and the Service. By using the Service, Developers consent to these additional uses, including us sending Developers communications for marketing purposes about our business, such as to contact Developers about promotions, updates, and features of the Service. When Developers sign up for the Service, we require various information that may be considered Personal Data. To access the Service, Developers will be required to provide us with the name of the individual signing up for the Service, including such person's name and email address. In addition, there are various pieces of information that Developers can, or may in the future be able to, choose to provide through the Service. Such information may include communications that occur through the Service or outside of the Service between Developers and Jido. Further, now or in the future, we may allow Developers to provide us with access to additional information and data through integrations with third party goods and services. Finally, we automatically collect the IP address of Developers. The data described above is referred to collectively as "Developer Data." End-User Data. When End-Users use mobile applications created by Developers that use the Service ("Developer Applications"), we collect certain information while an End-User is running a Developer Application which may be considered Personal Data. Specifically, we collect End-Users' geolocation, unique device identifier, unique user ID, visual features, detected objects, and images from End-Users' camera feed, Wi-Fi networks, and other similar data related to End- Users' interaction with the Developer Application (collectively, the "End-User Data"). After a Developer has begun using the Service, we may use cookies to remember the Developer as a user of the Service and to streamline the functionality of the Service. These are first party cookies, not third party cookies, meaning that the cookies are only used to track Developer's activity on the Service, and not on third party sites or services. Other Data We Collect. When you use and visit the Service, we may also use third-party services, such as Google Analytics, Hubspot, and others, which use cookies to collect information about you.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Jido Inc.: Inactive | Live pagesha256 f7e7b2f654 |
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 Jido Maps 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 tools category) whose GDPR row is verified or vendor-stated, ranked by similarity.
No AI tools vendor has GDPR evidence in the index yet.