When you use MediaPipe Solution APIs, processing of the input data (e.g. images,
video, text) fully happens on-device, and MediaPipe does not send that input
data to Google servers. As a result, you can use our APIs for processing data
that should not leave the device.
MediaPipe Android Solution APIs will contact Google servers from time to time in
order to receive things like bug fixes, updated models, and hardware accelerator
compatibility information. MediaPipe Android Solution APIs also send metrics
about the performance and utilization of the APIs in your app to Google. Google
uses this metrics data to measure performance, API usage, debug, maintain and
improve the APIs, and detect misuse or abuse, as further described in our
Privacy Policy.
You are responsible for obtaining informed consent from your app users about
Google’s processing of MediaPipe metrics data as required by applicable law.
Data we collect may include the following, across all MediaPipe Android Solution
APIs:
Device information (such as manufacturer, model, OS version and build) and
available ML hardware accelerators (GPU and DSP). Used for diagnostics and
usage analytics.
App identification information (package name / bundle id, app version). Used
for diagnostics and usage analytics.
API configuration (such as image format, resolution, and MediaPipe version
used). Used for diagnostics and usage analytics.
Event type (such as initialize, download model, update, run, and detection).
Used for diagnostics and usage analytics.
Error codes. Used for diagnostics.
Performance metrics. Used for diagnostics.
Per-installation identifiers that do not uniquely identify a user or
physical device. Used for operation of remote configuration and usage
analytics.
Network request sender IP addresses. Used for remote configuration
diagnostics. Collected IP addresses are retained temporarily.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-05-03 UTC."],[],[],null,["MediaPipe APIs Terms of Service\n-------------------------------\n\nLast modified: November 12, 2021\n\nUse of MediaPipe Solution APIs is subject to the\n[Google APIs Terms of Service](https://developers.google.com/terms),\n[Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy),\nand the terms below. Please check back from time to time as these terms and\npolicies are occasionally updated.\n\n**Privacy**\n\nWhen you use MediaPipe Solution APIs, processing of the input data (e.g. images,\nvideo, text) fully happens on-device, and **MediaPipe does not send that input\ndata to Google servers**. As a result, you can use our APIs for processing data\nthat should not leave the device.\n\nMediaPipe Android Solution APIs will contact Google servers from time to time in\norder to receive things like bug fixes, updated models, and hardware accelerator\ncompatibility information. MediaPipe Android Solution APIs also send metrics\nabout the performance and utilization of the APIs in your app to Google. Google\nuses this metrics data to measure performance, API usage, debug, maintain and\nimprove the APIs, and detect misuse or abuse, as further described in our\n[Privacy Policy](https://policies.google.com/privacy).\n\n**You are responsible for obtaining informed consent from your app users about\nGoogle's processing of MediaPipe metrics data as required by applicable law.**\n\nData we collect may include the following, across all MediaPipe Android Solution\nAPIs:\n\n- Device information (such as manufacturer, model, OS version and build) and\n available ML hardware accelerators (GPU and DSP). Used for diagnostics and\n usage analytics.\n\n- App identification information (package name / bundle id, app version). Used\n for diagnostics and usage analytics.\n\n- API configuration (such as image format, resolution, and MediaPipe version\n used). Used for diagnostics and usage analytics.\n\n- Event type (such as initialize, download model, update, run, and detection).\n Used for diagnostics and usage analytics.\n\n- Error codes. Used for diagnostics.\n\n- Performance metrics. Used for diagnostics.\n\n- Per-installation identifiers that do not uniquely identify a user or\n physical device. Used for operation of remote configuration and usage\n analytics.\n\n- Network request sender IP addresses. Used for remote configuration\n diagnostics. Collected IP addresses are retained temporarily."]]
