This Privacy Policy explains how Future Share LLC and its affiliates (collectively, "GlobalGPT," "we," "us," or "our") collect, use, disclose, retain, and protect personal information when you use the GlobalGPT websites, mobile applications, browser extensions, integrations, and related services (collectively, the "Services").
The Services include Yukie, GlobalGPT's AI assistant and connected-service features, operated by Future Share LLC. References to GlobalGPT in this Policy also cover Yukie.
This Policy applies to GlobalGPT as a controller of personal information. If we process personal information on behalf of an organization under a separate agreement, that agreement governs the processing performed for that organization.
By using the Services, you acknowledge the practices described in this Policy. Where applicable law requires consent, we will request it before collecting or using the relevant personal information.
1. Information We Collect
1.1 Information you provide
Depending on how you use the Services, you may provide:
- account and profile information, such as your name, email address, username, profile image, and authentication information;
- prompts, text, files, images, audio, video, links, instructions, feedback, and other content you submit to the Services ("User Content");
- communications with customer support;
- preferences, survey responses, and marketing choices; and
- transaction information, such as the product or subscription purchased and billing status. Payment card information is processed by our payment providers, such as the Apple App Store, Google Play, or other payment processors, and we do not store full payment card numbers.
1.2 Information collected automatically
When you use the Services, we may collect:
- device and browser type, operating system, app version, language, and device identifiers;
- IP address and approximate location derived from the IP address;
- dates, times, pages, features, models, and tools used;
- referral URLs, interaction data, diagnostic information, crash reports, and security logs; and
- cookie and similar technology data as described in our cookie notices or consent controls.
We collect precise location, contacts, photos, microphone data, or other device-protected information only when a feature requires it and after obtaining the permission required by the device or applicable law.
1.3 Information from third parties
We may receive information from:
- identity and login providers when you choose a third-party sign-in method;
- app stores and payment processors;
- analytics, fraud-prevention, and security providers;
- business partners where permitted by law; and
- third-party services that you choose to connect to GlobalGPT.
Google Sign-In can provide basic identity information, such as your email address and name. We use this information to create, authenticate, and manage your GlobalGPT account. Account email addresses and identifiers, including those associated with Google Sign-In, may also be used for the product analytics and advertising conversion measurement described in Section 6. Google Sign-In does not itself authorize access to Gmail messages, Drive files, or other Google connected-service content.
Information received through Google Sign-In and other Google APIs remains subject to applicable Google policies. Additional restrictions for Google Connected Service Data are set out in Section 2.
2. Google Integrations and Google User Data
Connecting a Google service is optional and separate from signing in to GlobalGPT with Google. Before a new connection or reconnection, GlobalGPT presents an in-product disclosure about the data involved, AI processing and sharing, storage, and deletion. You must choose "Agree and continue" to proceed; cancelling or closing the disclosure ends that connection attempt. For OAuth connections, the Google permission screen follows this disclosure, and GlobalGPT accesses the service's data only after you authorize the connection. You may continue to use features that do not require Google service access without connecting that service.
For purposes of this Policy, "Google User Data" means information obtained through Google Sign-In or other Google APIs, including raw data and data aggregated, anonymized, or derived from that data. "Google Connected Service Data" means Google User Data obtained through a Google service connection to perform a user-requested task, including service content, connected-account metadata, and saved, aggregated, anonymized, hashed, or other derived data and results.
The connected services covered by this Section include Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides, Google Merchant Center, Google Search Console, and Google Analytics 4. Sections 2.1 through 2.5 describe our handling of Google Connected Service Data and the additional restrictions we apply to it, including saved content and derived results. We do not sell Google Connected Service Data or use it for advertising, unrelated profiling, or general-purpose AI model training.
Basic identity information obtained solely through Google Sign-In for account login is handled as described in Sections 1.3, 3, 5, and 6, subject to applicable Google policies. Information obtained through a connected service remains Google Connected Service Data even if an email address or another value matches information in a sign-in profile. Copying, hashing, or saving connected-service data as account information does not remove the restrictions in this Section.
2.1 Google permissions and how we use them
GlobalGPT may request the following permissions when you connect a Google service or use a Google-connected feature:
| Google OAuth scope | Data accessed or action performed | User-facing purpose |
|---|---|---|
https://www.googleapis.com/auth/gmail.readonly |
Read email messages and related metadata without modifying or deleting them | Find, display, summarize, compare, or extract information from email in response to a user's request |
https://www.googleapis.com/auth/gmail.send |
Send email from the connected Gmail account | Send an email that the user has explicitly instructed or confirmed GlobalGPT to send |
https://www.googleapis.com/auth/gmail.modify |
Read and manage messages, labels, and drafts; message deletion uses Trash, while deleting a saved draft permanently removes that draft | Organize email and labels, create, update, or delete drafts, mark messages as read or unread, archive messages, or move them to or restore them from Trash as requested by the user |
https://www.googleapis.com/auth/gmail.settings.basic |
Read and manage basic Gmail settings, including filters and the account's email signature | List, create, or delete email filters, or view and update the user's signature, in response to a user request |
https://www.googleapis.com/auth/calendar.calendarlist.readonly |
Read the names, IDs, time zones, and access details of calendars available to the connected account | Let the user choose a calendar for a requested scheduling or booking task |
https://www.googleapis.com/auth/calendar.events.freebusy |
Read free/busy availability on calendars the user can access, without reading event details through this permission | Suggest meeting times in response to a scheduling request |
https://www.googleapis.com/auth/calendar.events.readonly |
Read calendar events and related event details without creating, editing, or deleting events | Display schedules, answer calendar-related questions, and use relevant event context for a user-requested task |
https://www.googleapis.com/auth/calendar.events |
Permit viewing and managing events, including creating, changing, or deleting them; GlobalGPT currently uses this permission to create events | Book a meeting the user requests, send invitations to attendees, and optionally add a Google Meet link |
https://www.googleapis.com/auth/drive.file |
Read, create, edit, or delete Drive files made available to GlobalGPT, including files opened with it or created through it; this permission alone does not grant access to all Drive files | Find, open, and work with relevant Drive, Docs, Sheets, or Slides files for a user-requested task |
https://www.googleapis.com/auth/spreadsheets |
Read and edit spreadsheet content and structure | Analyze, create, update, or format spreadsheets that the user selects, identifies, links, or instructs GlobalGPT to use |
https://www.googleapis.com/auth/documents |
Read and edit Google Docs content and structure | Read, summarize, create, revise, or format documents that the user selects, identifies, links, or instructs GlobalGPT to use |
https://www.googleapis.com/auth/presentations |
Read and edit Google Slides content and structure | Read, summarize, create, revise, or format presentations that the user selects, identifies, links, or instructs GlobalGPT to use |
https://www.googleapis.com/auth/content |
Authorize Merchant Center account and product access; GlobalGPT currently uses it only to read accessible accounts, processed products, product statuses and issues, and data source configurations | Display and summarize the user's Merchant Center products, explain reported product issues, and inspect data source settings; the integration does not edit products or upload feeds |
https://www.googleapis.com/auth/webmasters.readonly |
Read accessible Search Console properties and search-performance data, including queries, pages, clicks, impressions, click-through rates, and positions | Analyze the user's selected site's search performance and produce requested SEO reports and recommendations |
https://www.googleapis.com/auth/analytics.readonly |
Read Google Analytics accounts, GA4 properties and data streams, and selected reporting dimensions and metrics | Analyze traffic, landing pages, engagement, and key events for the user's selected property and requested report |
The drive.file permission may be requested with Google Docs, Sheets, or Slides access, or when you connect Google Drive directly.
The Merchant Center content scope can authorize broader actions than the read operations GlobalGPT currently provides. The permissions shown by Google describe the scope's technical capabilities; our actual use is limited to the functions described above.
An OAuth scope may technically authorize access broader than the item involved in a particular request. GlobalGPT limits its actual access and use through product design and instructions to the Google content necessary to complete the user's requested feature. We do not use these permissions for background surveillance, unrelated profiling, advertising, or undisclosed purposes.
The permissions requested depend on the Google service and the connected features being authorized. A service connection may request several related permissions together, and additional permissions may be requested when a task needs them. Granting a permission does not by itself instruct GlobalGPT to perform every action it permits. GlobalGPT will not send an email, change Gmail content or settings, create a calendar event, or create, edit, or delete a connected file unless the action was initiated or confirmed by the user through a visible product interaction, including a request in a Yukie conversation.
2.2 Purposes and limits of use
We use Google Connected Service Data only to:
- authenticate and maintain the connection requested by the user;
- perform the specific Google-connected task requested by the user;
- display the requested data or result to that user;
- maintain a user-facing feature that the user has chosen to use;
- prevent fraud, abuse, and security incidents; and
- comply with applicable law.
We do not use Google Connected Service Data to build user profiles for advertising, target advertisements, measure advertising, retarget users, determine creditworthiness, make lending decisions, sell data, or provide data to data brokers or information resellers. We do not use it for general product analytics or unrelated marketing, including when the data has been aggregated, anonymized, or transformed into a derived result.
2.3 AI processing of Google Connected Service Data
Some user-requested features, including tasks in Yukie conversations, use artificial intelligence to summarize, analyze, transform, draft, or organize content. When a user invokes and authorizes such a feature, GlobalGPT may transmit only the Google Connected Service Data reasonably necessary to complete that request to contracted infrastructure or AI service providers acting on our behalf. For example, an email summary may require the relevant email content, while an analysis of Merchant Center issues may require the selected product details and reported issues. Google data returned by a connected tool may form part of the AI input and the response shown to the user.
Such processing is limited to producing or delivering the result requested by that user. We require applicable service providers to process the data only under our instructions, protect it appropriately, and not use it to create, train, or improve any general-purpose, shared, or provider-wide machine learning or artificial intelligence model.
GlobalGPT does not use or permit the use of Google Connected Service Data, including raw, aggregated, anonymized, or derived data, to create, train, or improve a machine learning or artificial intelligence model beyond a model personalized solely for that specific user and the approved user-facing use case. GlobalGPT currently does not use Google Connected Service Data to train even such a user-specific personalized model.
We do not combine Google Connected Service Data into a general training corpus, evaluation dataset, retrieval corpus shared across users, or product-wide model-improvement dataset.
2.4 Sharing and human access
We do not transfer Google Connected Service Data except as permitted by the applicable Google policies:
- where necessary to provide or improve a Google-connected feature that is visible and prominent to the user, with the user's consent, including transfers to infrastructure or AI service providers acting on our behalf solely for that feature and subject to purpose and confidentiality restrictions consistent with this Policy;
- where necessary to investigate security incidents, fraud, bugs, or abuse;
- where required to comply with applicable law or valid legal process; or
- as part of a merger, acquisition, or sale of assets after obtaining the user's explicit prior consent.
Service providers do not receive Google Connected Service Data for their own advertising, unrelated analytics, model training, or other independent purposes. The general disclosure categories in Section 5 do not expand these permitted transfers.
Our personnel and contractors are not permitted to read Google Connected Service Data except when:
- the user has given documented, explicit consent for a person to view specific messages, files, or other data, such as for a support request;
- access is necessary to investigate a security incident, fraud, bug, or abuse;
- access is required by applicable law; or
- the data is aggregated and anonymized and is used only for internal operations permitted by Google's Limited Use requirements, subject to the prohibitions on advertising, sale, and model training in this Section.
2.5 Storage, OAuth tokens, and deletion
Content and results. We process and retain Google Connected Service Data only as needed for the purposes described in this Section and subject to applicable Google API storage and caching restrictions. Depending on the feature used, relevant Google content and derived results may appear in conversation history, files saved in the user's Computer workspace, and generated outputs. These saved items may be used as context for the user's subsequent tasks. We do not create a separate permanent archive of the user's Google account.
OAuth credentials. OAuth access and refresh tokens are stored to maintain the connection selected by the user. Tokens are encrypted at rest and transmitted using secure protocols. They are not used for unrelated purposes.
Disconnecting in GlobalGPT or Yukie. You can select Disconnect for a Google service in the available connected-app settings. This deletes that connection's locally stored OAuth credentials and stops new requests through that stored connection. Disconnecting does not itself revoke the authorization shown in your Google Account or automatically delete content already saved in conversations, files, or outputs.
Revoking access in Google. You can separately revoke GlobalGPT's authorization from your Google Account settings at https://myaccount.google.com/permissions. Revocation prevents further access using that authorization. If Google rejects a subsequent API request or token refresh because the authorization is no longer valid, reconnecting is required to use the connected feature again. Revoking access does not itself delete content previously saved in GlobalGPT.
Account closure. The Delete account control in your GlobalGPT profile deactivates your account after email verification. It does not automatically erase all associated data. Account closure does not itself disconnect Google services, delete stored Google OAuth credentials, revoke Google's authorization, or delete Google User Data and derived results saved in conversations, Computer workspace files, or generated outputs. To stop future access to a Google service, use Disconnect while you still have access to your account, or revoke GlobalGPT's authorization in your Google Account at any time, as described above.
Google data deletion requests. To request deletion of stored Google OAuth credentials, Google User Data, or saved derived results, including after closing an account, contact productsupport@glbgpt.com. Provide the email address previously used for your GlobalGPT account, your account ID if available, and, if possible, the relevant conversations or files. We may request information needed to verify your identity. Account closure and a request to erase stored data are separate processes; deletion requests are handled as described in Sections 8 and 10. Limited retention may apply where required by law or necessary for permitted security purposes. Residual backup copies are subject to the backup lifecycle described in Section 8.
2.6 Google Limited Use disclosure
GlobalGPT's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
The restrictions in Sections 2.1 through 2.5 control if another provision of this Policy could otherwise be read to permit broader access, use, storage, or transfer of Google Connected Service Data. A general consent or another legal basis described elsewhere in this Policy does not authorize a use prohibited by this Section or the applicable Google policies. All Google User Data, including basic Google Sign-In information, remains subject to the applicable Google policies referenced above.
3. How We Use Personal Information
We use personal information to:
- provide, operate, maintain, and secure the Services;
- create and administer accounts and subscriptions;
- process user instructions and generate requested outputs;
- provide customer support and respond to requests;
- personalize user-selected settings and product experiences;
- process payments through payment providers and maintain transaction records;
- detect, prevent, and investigate fraud, abuse, security incidents, and violations of our terms;
- analyze reliability and aggregate usage patterns, test features, and improve the Services;
- communicate service, account, security, and policy updates;
- send marketing communications where permitted and honor opt-out requests;
- comply with law and enforce or defend legal rights; and
- carry out another purpose disclosed at the time of collection with any consent required by law.
Google Connected Service Data is subject to the narrower purposes and restrictions in Section 2 and is not used for general product analytics, advertising, or general model improvement. The use of basic sign-in and account information for analytics and advertising conversion measurement is described separately in Section 6 and remains subject to applicable Google policies.
4. AI Features and User Content
GlobalGPT provides access to AI-powered features and third-party AI models. User Content may be transmitted to the model or service selected by the user, or to a model selected by GlobalGPT to provide the requested feature. The provider, model, and applicable controls may vary by feature.
We use User Content to provide the requested output, maintain service reliability, prevent abuse, and comply with law. We do not use User Content to train our general-purpose AI models unless we separately and clearly disclose that use and obtain any consent required by law.
Where third-party AI providers process User Content, we use provider offerings and contractual or technical controls intended to prevent the provider from using business API data to train general-purpose models. The stricter restrictions in Section 2 always apply to Google Connected Service Data and cannot be overridden by a general consent relating to other User Content.
AI outputs may be inaccurate. Users should review outputs before relying on them or using them to take consequential actions.
4.1 GlobalGPT Chrome extension
The GlobalGPT Chrome extension ("Extension") lets you use your GlobalGPT account, including Yukie, AI chat, and creation, translation, transcription, and text-recognition tools, in Chrome's side panel. This Section explains what the Extension accesses and how that information is handled. The rest of this Policy also applies to information processed through the Extension.
What the Extension accesses. The Extension accesses the following only when you start a task or choose to share it:
- Web page content. When you start a page task (for example, asking about or summarizing a page, using a right-click action, or allowing a read request from Yukie), the Extension reads the visible text, headings, links, and tables of the page or tabs you choose. It does not read pages in the background.
- Selected text and video information. Text you select and send, and the title, description, and captions of a YouTube video you ask the Extension to summarize. For a video without captions, the video's public web address is processed by an AI model to produce a transcript.
- Files, images, screenshots, and audio. Files and images you upload, screenshots you capture for a tool such as text recognition, and audio you upload or record. The microphone is used only while you are recording for live transcription or note taking, after you grant Chrome's microphone permission.
The Extension does not read passwords, payment card fields, hidden form values, or form text you have not submitted. It does not read your browsing history or cookies, and it does not read tabs other than the ones you choose. It does not click, submit, buy, or delete anything on websites.
How it is used. Content you share through the Extension is sent to GlobalGPT over an encrypted connection to provide the feature you requested, including processing by AI models as described in this Section 4. It is stored with the related conversation, task, or creation in your GlobalGPT account and is retained and deleted under Section 8, like your other GlobalGPT content. We do not sell this content, use it for advertising, or use it for purposes unrelated to the Extension's features.
Site access you control. For each website you can allow access once or always. One-time access is removed right after the page is read. You can remove "always allow" sites in the Extension's settings or in Chrome's extension settings at any time. You can turn off microphone access in Chrome's site settings.
Sign-in and local storage. When you sign in, the Extension stores a GlobalGPT sign-in token and your preferences (such as language and the sites you always allow) in Chrome's local extension storage on your device. Signing out removes the token. You can clear the Extension's local data in its settings or by removing the Extension.
Diagnostics. The Extension does not include page text, selected text, form values, or web addresses with query strings in logs or analytics.
5. How We Disclose Personal Information
Google Connected Service Data may be disclosed only under Section 2.4. The categories below do not permit sharing Google Connected Service Data for unrelated affiliate activities, partner promotions, advertising, general analytics, or a corporate transaction outside the conditions in that Section.
We may disclose personal information to:
- Service providers and subprocessors. These include cloud hosting, storage, authentication, security, customer support, analytics, payment, and AI service providers. Depending on the feature selected, AI providers may include OpenAI, L.L.C., Google LLC, Anthropic, PBC, and other providers identified in the relevant product interface or subprocessor notice. They may process information only to provide services to us and subject to applicable contractual restrictions.
- Analytics and advertising measurement providers. We may disclose account information and activity in our Services for product analytics, account identification, and registration or advertising conversion measurement as described in Section 6, subject to applicable Google policies and legal requirements. These disclosures do not include Google Connected Service Data.
- Affiliates. We may disclose information to entities under common ownership or control, subject to this Policy.
- Business partners. We may disclose information for a co-branded feature, event, referral, or promotion when we provide notice and obtain any consent required by law.
- Authorities and other parties for legal or safety reasons. We may disclose information to comply with law or valid legal process, enforce our terms, protect rights and safety, or detect and address fraud, abuse, or security incidents.
- Parties to a corporate transaction. Information may be reviewed or transferred in connection with a financing, merger, acquisition, reorganization, bankruptcy, or sale of assets, subject to applicable law.
- Other parties at your direction. We disclose information when you ask us to do so or consent to the disclosure.
Public posts, shared links, or content that a user deliberately makes public may be visible to others. We do not sell Google Connected Service Data, and we do not disclose it for targeted or cross-context behavioral advertising.
6. Cookies, Analytics, and Advertising
We and our providers may use cookies and similar technologies to operate the Services, remember preferences, understand usage, measure performance, prevent fraud, and, where permitted, support marketing. Consent controls are provided where required by law.
Product analytics. We use providers such as PostHog to associate activity in our Services with a GlobalGPT account, analyze product use, and measure registration or sign-in events. This can involve our account identifier and account email address, including an email address received through Google Sign-In.
Advertising conversion measurement. Registration events may be sent to advertising measurement providers to match registrations to advertising interactions and measure campaign performance. For X (Twitter), this can include the account email address; for TikTok, it can include hashed versions of the account email address and account identifier. The email address used for these events may be one received through Google Sign-In. Hashed identifiers can still be used for account matching. Other registration or sign-in measurement events may be sent to providers such as Google, Meta, Microsoft, and OpenAI Ads, with event and attribution information that varies by provider. These uses remain subject to applicable Google policies and legal requirements, including consent where required; this Policy does not replace any required consent.
You may control cookies through available cookie settings and browser controls. Disabling necessary cookies may prevent parts of the Services from working.
Google Connected Service Data, including messages, attachments, files, calendar events, connected-account metadata, and raw, aggregated, anonymized, hashed, or other derived data, is not used or disclosed for advertising, ad measurement, retargeting, marketing analytics, or the creation of advertising profiles. The cookie, analytics, and marketing activities described above do not authorize those uses of Google Connected Service Data.
7. Legal Bases for Processing
Where the laws of the European Economic Area, United Kingdom, Switzerland, or another jurisdiction require a legal basis, we rely on one or more of the following:
- performance of a contract, including providing the Services requested by the user;
- consent, including for optional integrations and certain marketing activities;
- our legitimate interests in operating, securing, supporting, and improving the Services, balanced against the user's rights;
- compliance with a legal obligation; or
- protection of vital interests.
You may withdraw consent at any time. Withdrawal does not affect processing that occurred before withdrawal.
8. Retention
We retain personal information only for as long as reasonably necessary for the purposes described in this Policy, including providing the Services, maintaining user-selected history, complying with legal obligations, resolving disputes, preventing fraud and abuse, and enforcing agreements.
Retention depends on the type of information, the feature used, account settings, legal requirements, and security needs. When information is no longer required, we delete or anonymize it. If immediate deletion from encrypted backups is not technically practicable, we isolate the information from active use until the applicable backup is overwritten.
Google Connected Service Data and Google OAuth credentials are additionally governed by Section 2.5. General retention purposes in this Section do not expand the permitted uses of Google Connected Service Data in Section 2.
9. Security
We maintain administrative, technical, and organizational safeguards designed to protect personal information, including:
- encryption in transit using secure modern protocols;
- encryption at rest for OAuth tokens and other sensitive information;
- access controls based on role and business need;
- credential and key-management controls;
- logging, monitoring, vulnerability management, and incident response processes; and
- contractual confidentiality and data-protection obligations for personnel and applicable service providers.
No system is completely secure. Users are responsible for protecting their account credentials and should notify us promptly of suspected unauthorized access.
10. Your Choices and Rights
Depending on your location, you may have the right to:
- access and obtain a copy of personal information;
- correct inaccurate personal information;
- delete personal information;
- restrict or object to processing;
- withdraw consent;
- receive certain information in a portable format;
- opt out of marketing communications;
- opt out of a sale or sharing of personal information where applicable; and
- appeal a decision or complain to a data-protection authority.
You may update certain information in your account settings. Marketing emails include an unsubscribe method. You may disconnect Google as described in Section 2.5.
To exercise a privacy right, contact productsupport@glbgpt.com. We may request information reasonably necessary to verify identity and authority. Authorized agents may submit requests where permitted by law. We will not discriminate against a user for exercising a privacy right.
Deleting information necessary to provide the Services may require deletion or limitation of the associated account or feature. We may deny or limit a request where permitted by law and will explain the basis where required.
11. U.S. State Privacy Disclosures
Residents of California and other U.S. states may have additional rights under applicable state privacy laws. The categories of personal information we may collect are described in Section 1. The purposes of collection are described in Sections 2 through 4, and the categories of recipients are described in Section 5.
GlobalGPT does not sell Google Connected Service Data or share it for cross-context behavioral advertising. If our treatment of other personal information constitutes a "sale," "sharing," or targeted advertising under applicable state law, eligible users may submit an opt-out request through available privacy controls or by contacting productsupport@glbgpt.com.
Subject to applicable exceptions, eligible users may request access, correction, deletion, or portability, and may use an authorized agent. We may verify requests as permitted by law.
California Civil Code Section 1798.83 may permit certain California residents to request information about disclosures for third-party direct marketing. Requests may be sent to productsupport@glbgpt.com.
12. International Data Transfers
GlobalGPT and its service providers may process personal information in the United States and other countries whose data-protection laws may differ from those of the user's location. Where required, we use recognized transfer mechanisms, such as Standard Contractual Clauses, and supplementary safeguards.
13. Children's Privacy
The Services are not directed to children under 18 or the minimum age required by applicable law. We do not knowingly collect personal information from children who are not permitted to use the Services. If you believe a child has provided personal information in violation of this section, contact productsupport@glbgpt.com.
14. Third-Party Services
The Services may link to or interoperate with third-party websites, applications, models, or services. Their privacy practices are governed by their own policies. This Policy governs personal information processed by GlobalGPT, including the restrictions GlobalGPT applies when it transfers data to a provider acting on its behalf.
15. Changes to This Policy
We may update this Policy to reflect changes in the Services, law, technology, or our processing practices. We will post the updated Policy and update the effective date. Where required by law, or where a change materially expands how we use Google User Data or other personal information, we will provide additional notice and obtain consent before applying the new use.
16. Contact Us
Future Share LLC is responsible for this Policy.
For privacy questions, requests, complaints, or Google User Data deletion requests, including requests relating to Yukie, contact:
Email: productsupport@glbgpt.com
Website: https://www.glbgpt.com
If you are located in a jurisdiction that gives you the right to contact a supervisory authority, you may do so at any time.

