Meta tags:

Headings (most frequently used words):

api, and, google, services, data, with, your, the, user, policy, stay, organized, collections, save, categorize, content, based, on, preferences, accurately, represent, identity, intent, be, transparent, about, you, access, clear, prominent, privacy, disclosures, request, minimum, relevant, permissions, deceptive, or, unauthorized, use, of, is, prohibited, child, directed, apps, maintain, secure, operating, environment, additional, requirements, for, specific, scopes, enforcement, connect, programs, developer, consoles,

Text of the page (most frequently used words):
google (86), the (85), data (60), and (49), your (44), user (43), you (40), #access (35), that (30), application (30), services (29), api (28), use (24), users (22), for (22), with (22), must (21), are (21), #policy (18), privacy (16), product (15), developer (14), service (13), other (12), requirements (12), not (12), information (11), should (11), about (11), terms (10), any (10), scopes (10), apps (9), may (9), from (9), request (9), all (8), thumb (8), page (8), these (8), console (7), represent (7), policies (7), only (7), directed (7), apis (7), this (7), under (7), can (7), using (6), accurately (6), permissions (6), including (6), oauth (6), don (6), requesting (6), down (5), developers (5), purpose (5), notifications (5), necessary (5), specific (5), limited (5), security (5), applicable (5), applications (5), additional (5), features (5), make (5), sign (5), authentication (5), requests (5), when (5), understand (4), via (4), clear (4), practices (4), child (4), secure (4), otherwise (4), found (4), also (4), comply (4), example (4), obtained (4), consent (4), appropriate (4), prominent (4), audience (4), without (4), children (4), disclosures (4), cloud (3), actions (3), play (3), need (3), code (3), identity (3), requested (3), sensitive (3), content (3), site (3), assessment (3), obtain (3), third (3), more (3), keep (3), available (3), transferring (3), selling (3), purposes (3), uses (3), prohibited (3), cases (3), provide (3), interface (3), environment (3), mixed (3), account (3), but (3), includes (3), authorization (3), client (3), credentials (3), have (3), authorized (3), undocumented (3), permission (3), which (3), will (3), well (3), what (3), context (3), disclosed (3), updated (3), accurate (3), 한국어 (2), 日本語 (2), русский (2), português (2), brasil (2), indonesia (2), français (2), español (2), deutsch (2), english (2), products (2), platform (2), firebase (2), chrome (2), android (2), web (2), store (2), program (2), connect (2), too (2), steps (2), out (2), samples (2), their (2), app (2), deceptive (2), handling (2), adhere (2), except (2), licensed (2), its (2), license (2), accordance (2), suspend (2), parties (2), specified (2), they (2), certain (2), being (2), party (2), verification (2), faq (2), restricted (2), ensure (2), based (2), advertising (2), like (2), transfers (2), aggregated (2), used (2), legal (2), law (2), investigating (2), abuse (2), view (2), unless (2), part (2), facing (2), providing (2), below (2), apply (2), derived (2), them (2), permitted (2), type (2), types (2), own (2), then (2), take (2), unauthorized (2), operating (2), require (2), games (2), able (2), primarily (2), accesses (2), websites (2), age (2), general (2), according (2), please (2), ftc (2), coppa (2), false (2), attempt (2), rendered (2), ability (2), displayed (2), disclose (2), limitation (2), why (2), where (2), possible (2), implement (2), regarding (2), easily (2), timely (2), how (2), way (2), notify (2), prompt (2), before (2), originally (2), transparent (2), time (2), manage, cookies, home, dashboard, cast, sdk, consoles, nvidia, accelerators, experts, groups, programs, youtube, twitter, linkedin, instagram, bluesky, blog, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, missing, missingtheinformationineed, complicated, many, toocomplicatedtoomanysteps, date, outofdate, issue, samplescodeissue, otherdown, transparency, required, forbidden, face, restrictions, requires, adherence, assessments, violations, result, revocation, expected, noted, details, see, java, registered, trademark, oracle, affiliates, apache, creative, commons, attribution, compliance, revoke, violation, guidelines, revoked, enables, end, violate, enforcement, accessing, demonstrate, depending, accessed, number, grants, pass, annual, letter, designated, employees, agents, contractors, successors, determine, credit, worthiness, lending, serving, ads, retargeting, personalized, interest, platforms, brokers, resellers, sales, derivations, internal, operations, jurisdictional, bug, first, affirmative, agreement, messages, files, exception, approved, nest, device, allow, humans, read, merger, acquisition, sale, assets, after, obtaining, explicit, prior, laws, improve, visible, allowed, limit, improving, raw, anonymized, described, such, heading, stated, include, within, domain, control, connected, learn, managing, enterprise, ecosystem, best, allowlisting, workspace, note, subject, each, expect, transit, rest, reasonable, protect, systems, against, unlawful, destruction, loss, alteration, disclosure, maintain, shouldn, offer, optional, feature, entirety, signing, into, associated, restriction, technology, online, protection, act, applies, known, while, responsible, obligations, review, guidance, differences, between, consult, counsel, website, some, company, organization, authority, manages, making, representations, grounds, suspension, misleading, statements, entities, allegedly, managed, reverse, engineer, derive, underlying, source, means, stipulated, official, documentation, provided, express, appears, claim, agent, header, running, ios, desktop, browser, instead, embedded, mislead, overall, there, surprises, hidden, inconsistent, marketed, lead, aggregate, analyze, sold, distributed, conducting, surveillance, front, informed, decision, grant, delete, share, behalf, misrepresent, collected, strictly, engaging, activity, deceive, following, incremental, auth, whenever, does, future, proof, might, benefit, yet, been, implemented, sense, critical, minimum, relevant, prominently, find, shown, thoroughly, manner, stores, shares, explicitly, published, consider, handle, change, new, different, than, comprehensive, accessible, publish, fully, documents, interacts, list, url, configuration, made, public, honest, explain, one, reason, utilized, secondary, both, matter, readily, value, consequences, sharing, explaining, addition, plan, was, initially, update, changes, seeks, confidential, who, wish, intent, framework, gives, directly, would, govern, check, back, occasionally, last, february, 2024, save, categorize, preferences, stay, organized, collections, guides, skip, main,

Text of the page (random words):
google api services user data policy google for developers skip to main content english deutsch español français indonesia português brasil русский 中文 简体 日本語 한국어 sign in guides google apis terms of service google api services user data policy site terms of service site policies google api services user data policy stay organized with collections save and categorize content based on your preferences last updated february 15 2024 google api services including google sign in are part of an authentication and authorization framework that gives you the developer the ability to connect directly with google users when you would like to request access to google user data the policy below as well as the google apis terms of service govern the use of google api services when you request access to google user data please check back from time to time as these policies are occasionally updated accurately represent your identity and intent if you wish to access google user data you must provide google users and google with clear and accurate information regarding your use of google api services this includes without limitation requirements to accurately represent who is requesting google user data all permission requests must accurately represent the identity of the application that seeks access to user data if you have obtained authorized client credentials to access google api services keep these credentials confidential what data are you requesting you must provide clear and accurate information explaining the types of data being requested in addition if you plan to access or use a type of user data that was not originally disclosed in your privacy policy or in product disclosures when a google user initially authorized access you must update your privacy policy and prompt the user to consent to any changes before you may access that data why are you requesting google user data be honest and transparent with users when you explain the purpose for which your application requests user data if your application requests data for one reason but the data will also be utilized for a secondary purpose you must notify google users of both use cases as a general matter users should be able to readily understand the value of providing the data that your application requests as well as the consequences of sharing that data with your application be transparent about the data you access with clear and prominent privacy disclosures you must publish a privacy policy that fully documents how your application interacts with user data you must list the privacy policy url in your oauth client configuration when your application is made available to the public your privacy policy and all in product privacy notifications should be accurate comprehensive and easily accessible your privacy policy and in product privacy notifications must thoroughly disclose the manner in which your application accesses uses stores or shares google user data your use of google user data must be limited to the practices explicitly disclosed in your published privacy policy but you should consider the use of additional in product notifications to ensure that users understand how your application will handle user data if you change the way your application uses google user data you must notify users and prompt them to consent to an updated privacy policy before you make use of google user data in a new way or for a different purpose than originally disclosed disclosures about data use should be prominent and timely your privacy policy and any in product notifications regarding data use should be prominently displayed in your application interface so that users can find this information easily where possible disclosures about data use should be timely and shown in context request the minimum relevant permissions permission requests should make sense to users and should be limited to the critical information necessary to implement your application don t request access to information that you don t need only request access to the permissions necessary to implement your application s features or services if your application does not require access to specific permissions then you must not request access to these permissions don t attempt to future proof your access to user data by requesting access to information that might benefit services or features that have not yet been implemented request permissions in context where possible only request access to user data in context via incremental auth whenever you can so that users understand why you need the data deceptive or unauthorized use of google api services is prohibited you are strictly prohibited from engaging in any activity that may deceive users or google about your use of google api services this includes without limitation the following requirements do not misrepresent what data is collected or what you do with google user data be up front with users so that they can make an informed decision to grant authorization you must disclose all user data that you access use store delete or share as well as any actions you take on a user s behalf you are not permitted to access aggregate or analyze google user data if the data will be displayed sold or otherwise distributed to a third party conducting surveillance overall there should be no surprises for google users hidden features services or actions that are inconsistent with the marketed purpose of your application may lead google to suspend your ability to access google api services do not mislead google about an application s operating environment you must accurately represent the environment in which the authentication page appears for example don t claim to be an android application in the user agent header if your application is running on ios or represent that your application s authentication page is rendered in a desktop browser if instead the authentication page is rendered in an embedded web view do not use undocumented apis without express permission don t reverse engineer undocumented google api services or otherwise attempt to derive or use the underlying source code of undocumented google api services you may only access data from google api services according to the means stipulated in the official documentation of that api service as provided on google s developer page do not make false or misleading statements about any entities that have allegedly authorized or managed your application you must accurately represent the company organization or other authority that manages your application making false representations about client credentials to google or google users is grounds for suspension child directed apps the children s online privacy protection act or coppa applies to websites apps and services directed to children under the age of 13 and general audience apps websites or services with users known to be under the age of 13 while child directed apps may use some google services developers are responsible for using these services according to their obligations under the law please review the ftc s guidance on coppa including information about the differences between mixed audience apps and apps directed primarily to children from the ftc s website and consult with your own legal counsel child directed apps if your application is directed primarily at children it should not use google sign in or any other google api service that accesses data associated with a google account this restriction includes google play games services and any other google api service using the oauth technology for authentication and authorization mixed audience apps applications that are mixed audience shouldn t require users to sign in to a google account but can offer for example google sign in or google play games services as an optional feature in these cases users must be able to access the application in its entirety without signing into a google account maintain a secure operating environment we expect all user data is secure in transit and at rest take reasonable and appropriate steps to protect all applications or systems that make use of google api service and any data derived from it against unauthorized or unlawful access use destruction loss alteration or disclosure additional requirements for specific api scopes certain google oauth api scopes the sensitive and restricted scopes are subject to additional requirements that can be found in each product s user data and developer policy or the google developer page more information about the requirements to obtain or keep access to these scopes is also available in the oauth application verification faq note if your app is only used by users within your own domain then these requirements do not apply google workspace can control access to connected applications via allowlisting learn more about best practices for managing your enterprise oauth ecosystem unless stated otherwise in the product s user data and developer policy additional requirements include appropriate access developers may only request access to the scopes for a permitted application type described by the product such application types can be found under an appropriate access heading in the product specific policy or the product s google developer page limited use your use of data obtained via the product s specified scopes must comply with the below requirements these requirements apply to the raw data obtained from the scopes and data aggregated anonymized or derived from them limit your use of data to providing or improving user facing features that are prominent in the requesting application s user interface transfers of data are not allowed except to provide or improve your appropriate access or user facing features that are visible and prominent in the requesting application s user interface and only with the user s consent for security purposes for example investigating abuse to comply with applicable laws or as part of a merger acquisition or sale of assets of the developer after obtaining explicit prior consent from the user don t allow humans to read the data unless you first obtained the user s affirmative agreement to view specific messages files or other data with the limited exception of use cases approved by google under additional terms applicable to the nest device access program it is necessary for security purposes for example investigating a bug or abuse it is necessary to comply with applicable law or the data including derivations is aggregated and used for internal operations in accordance with applicable privacy and other jurisdictional legal requirements all other transfers uses or sales of user data are prohibited including transferring or selling user data to third parties like advertising platforms data brokers or any information resellers transferring selling or using user data for serving ads including retargeting personalized or interest based advertising transferring selling or using user data to determine credit worthiness or for lending purposes you must ensure that your employees agents contractors and successors comply with this google api services user data policy secure data handling applications accessing the product specified scopes the sensitive and restricted scopes must demonstrate that they adhere to certain security practices depending on the api being accessed and number of user grants or users applications must pass an annual security assessment and obtain a letter of assessment from a google designated third party more information about the assessment requirements to obtain or keep access to the scopes is also available in the oauth application verification faq and the product s google developer page enforcement you must access google api services in accordance with the google apis terms of service if you are found to be out of compliance with the google apis terms of service this google api services user data policy or any google product policies that are applicable to the google api service you are using google may revoke or suspend your access to google api services and other google products and services if you are found in violation of other product policies terms of service or other guidelines your access to google api services may also be revoked if your application enables end users or other parties to violate the google apis terms of service and or google policies except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 license and code samples are licensed under the apache 2 0 license for details see the google developers site policies java is a registered trademark of oracle and or its affiliates 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 developers using google api services must accurately represent their identity requested data and purpose to users and google transparency via clear privacy policies and in app notifications is required only necessary permissions should be requested and deceptive practices are forbidden child directed apps face specific restrictions sensitive data requires adherence to limited use secure handling and access requirements including security assessments violations may result in access revocation all users are expected to adhere to the google apis terms of service n connect blog bluesky instagram linkedin x twitter youtube programs google developer program google developer groups google developer experts accelerators google cloud nvidia developer consoles google api console google cloud platform console google play console firebase console actions on google console cast sdk developer console chrome web store dashboard google home developer console android chrome firebase google cloud platform google ai all products terms privacy manage cookies english deutsch español français indonesia português brasil русский 中文 简体 日本語 한국어