Additional policy fi Google Cloud an Google Maps Platform

1. Di scope a di regulations an di role a service providers

Dis additional policy apply to di use a Google Maps Platform, location, route, environment, speech, translation, image recognition, document, data an ada Google Cloud API services weh deh pan di AIOS Business interface. AIOS Business is operated by: Immunity Invest Holdings Plc. Google services dem provide by Google in accordance wid Google's terms an conditions.

Di Google name, trademark, an services dem nuh mean a partnership, endorsement, or joint venture between Google an AIOS Business. In addition to di terms a AIOS Business, di user haffi comply wid di Google terms an documentation weh apply to him an di Google service weh yuh select.

2. Central AIOS connection an own Google Cloud project

Actions weh can be launch directly use di server-side protected Google Maps Platform API key set by di operator of AIOS Business. Di browser an di user no receive di key.

Fi a service weh need an SDK, mobile app, own data set, own domain, or unique Cloud resource, di user haffi mek dem own Google Cloud project, billing account, API authorization, key restriction, or OAuth contribution. Google maita invoice di project owna directly fi di Google fees dem weh dem incur inna dem own project; in such case, AIOS may only charge di separate AIOS service fee weh dem announce in advance.

Di API key or service account JSON specified inna di protected setting process a My project connection is stored separately an encrypted by AIOS fi each organization, it no display again later, an it can only be used fi di specifically launched Google Cloud operation a di given workspace. Wen di connection get delete, di stored credentials dem get delete tu.

Di own project can also be connected wid a Google OAuth connection. Pan di Google permission request page, di user select di account an approve di requested authorizations; AIOS can only use di connection widin di authorized scope an fi di specifically initiated operation. Access can be revoked inna di Google account or inna di AIOS contact manager.

Verifying project connectivity does not create a Google Cloud project, automatically turn on an API, or change a billing account, IAM role, DNS, or domain. Di owna a di project is responsible fi di necessary settings pan di Google side an di cost limits a him own project.

3. Package, balance an settlement

Di $0 Demo pakij no mek no Google ar ada extoernal API kaal. A Google API call thru a central AIOS connection require an active paid plan an sufficient pre-loaded API balance.

Di table shuo AIOS Business's published end-user unit prices at all times inna USD/1,000 billable events. Fi a central AIOS connection, di indicated AIOS customer price is deducted fram di API balance. In case a own project connection, Google bill directly inna di user's Google Cloud billing account.

Fi central AIOS use, only di published AIOS customer price is deducted fram di AIOS API balance. Inna di case a one own project connection, Google accounts inna di user's own Google Cloud billing account, so Google's service fee no charge to di AIOS API balance.

Di basic price a di Starter, Business an Enterprise packages dem nuh include unlimited Google API usage. Di basic subscription fee, di AIOS API balance an di Google fee weh di user's own Google Cloud project mek a three separate items. Di basis fi calculate di affiliate or partner commission can only be di base fee a di AIOS package; di cost a using Google, AI an API nuh constitute a commission basis.

Afta fail authentication, missing authorization, disabled API, quota error, or a request rejected by Google, AIOS naa go deduct a usage fee if no verified billable provider event neva happen. Google maita apply a different billing rule inna dem own Google Cloud project, fi weh di project owna is responsible.

4. Security a API Keys an Access

API key, OAuth secret, provider password, or other credentials are not allowed in a task description, chat, document, or shared field. Authentication data can only be entered inna di designated, protected setting process.

Yuh own Google Cloud key haffi protect by application an API restrictions, IP, domain, Android or iOS restrictions if necessary. Di user is obliged fi apply di principle a di least necessary authorization, fi review di key regularly an fi widdraw it immediately in case a suspicion a unauthorized use.

Di service account private key a one high-risk credential. Di user can connect a service account weh mek exclusively fi dis purpose, wid minimal IAM rights, haffi monitor di use a di key, rotate or revoke it if necessary, an securely manage or delete di local copy.

A browser key limited to di domain an di required APIs can only be used fi a map or visualization function weh a run inna a browser. Entering an unlimited server key, service account key, or OAuth secret inna a browser field is prohibited.

5. Google Maps Content, Attribution an Display

Attribution, logo, legal reference an user information provided by Google nuh fi be removed, hidden or modified in an ambiguous manner. Google Maps content haffi be clearly distinguished fram AIOS, user an third-party content.

Google Maps content may not be copy, collected, sold, mass exported, used to train a model, or converted into a database dat replace the Google service. Display, storage an caching tugeda wid a map is only permitted according to di documentation an service-specific conditions a di given API.

6. Location, address an personal data

Di user can only send addresses, coordinates, device locations or other data weh can be handle legally to di Google APIs. If di location data is related to an identified or identifiable person, an appropriate legal basis, transparent information an, if necessary, consent must be provided in advance.

Personal data cyaan be sen to Google wen yuh a use di Maps Datasets API. Data fram Address Validation, Geocoding, Geolocation, Places, Routes, Roads, environment an ada APIs maita be subject to separate storage, caching an usage limits; di results view a AIOS no in itself provide unlimited storage or reuse rights.

7. Route planning, navigation an safety

Route, traffic, weather, air quality, pollen, topography an other location-based results are informative an may be delayed, incomplete or inaccurate. Dem cyaan be used as an exclusive source inna an emergency, traffic safety, health, construction or other high-risk decision.

A real-time driving or navigation application can only be created in compliance wid Google's security requirements. Di user is responsible fi compliance wid local traffic, occupational safety, consumer protection an professional regulations, as well as fi appropriate human control.

8. Specific Use Limitations

Air quality an pollen data may only be used fi environmental risk, research, an routing purposes as permitted by Google. Di Solar API is primarily used fi support di feasibility, design, installation or user-requested offer a one energy system.

Use of Places results in the EEA is subject to separately authorized use cases. It is forbidden fi use di results a di Places Aggregate API fi mek a decision weh affect a person's housing, employment, credit, insurance or other rights.

Di results a Cloud Natural Language, Speech-to-Text, Text-to-Speech, Translation, Vision, Video Intelligence, Document AI, Vertex AI, Dialogflow an ada AI services maita bi probabilistic, erroneous or incomplete. Audio, images, documents or personal data may only be processed wid a suitable legal basis; a legal, health, financial, employment or other major decision require human review.

9. Service Change, Accuracy an Liability

Google APIs, endpoints, fields, quotas, fees, an terms may change, be restricted, or discontinued ova time. AIOS transfer di verified price change inna di published price list; provide information pan significant changes according to di applicable rules.

AIOS no guarantee di completeness, up-to-dateness or suitability a Google data fi a given business purpose. Di user is obliged fi check di result, save him important work an mek it review by a suitable professional before him use it wid professional or legal consequences.

10. Suspension an logging

AIOS may automatically limit or suspend usage weh threaten security, budget, quota, or compliance. Bypassing quotas, automated overloading, key sharing, unauthorized data collection an fee evasion are prohibited.

Di service log di billable event ID, organization, user, API name, time, status, an applied AIOS client load. Di secret API key an full location data no record inna di usage log.

Di My Project Connection log may contain di project ID, authentication type, name a di enabled APIs weh yuh detect, di time an result a di verification, but not di full API key, private key, access token, or service account JSON.

Deleting a connection terminate di use a di authentication record weh store inna AIOS, but nuh delete di user's Google Cloud project, Google-side logs, billing information, or resources. Deleting or stop dem haffi be done separately by di project owner pan di Google Cloud interface.