Privacy Policy

1. Who we are and what this policy covers

The Google Workspace connection of AI Workspace is operated by ООО «Айсберг» (“we”, “us”). Contact person: Kochkin Grigorii Sergeevich. Email: kochkingrigory@gmail.com.

AI Workspace is a business AI-assistant platform. Each company that uses it has its own AI Workspace installation on a separate server, where the company's employees work with AI agents. To let those agents work with Google data, installations use a shared Google connection service at google-service.my-jarvis.ru (the “connection service”), which we operate. It handles sign-in with Google and passes each request between Google and the installation.

This policy covers this website, sign-in with Google and the processing of Google user data through the connection service. Inside a company's installation, the company decides who its users are, which agents and AI model provider are used and how long chat history and results are kept; the company's own policies and agreements apply to that processing in addition to this policy.

2. Google data we access

The connection requests the Google permissions (scopes) below. You see them on Google's consent screen, and all of them must be allowed for the connection to work. The agent uses them only for tasks a person asks it to perform, and only within the access that person's Google account already has.

• openid, userinfo.email, userinfo.profile — your Google account ID, email address and basic profile (name and profile picture). Used only to identify which Google account is connected. Company installations receive only the account ID; the email address, name and picture stay with the connection service (section 7).
• drive — your Google Drive files and the shared drives your account can open: searching files by name and content, reading file details, downloading files (regular files as they are; Google Docs, Sheets, Slides and Drawings exported to formats such as docx, xlsx, pptx, pdf or png; up to 10 MB per file), uploading new files (up to 50 MB, optionally converted to Google format), replacing the content of an existing regular file, creating folders, renaming, moving within the same drive, copying and moving to trash. This permission is not limited to files created by AI Workspace. The connection does not change sharing settings, does not move files between My Drive and shared drives (which would change their owner) and does not delete files permanently.
• documents — reading, creating and editing Google Docs your account can open: reading text and tabs, inserting and replacing text.
• spreadsheets — reading, creating and editing Google Sheets: sheet names and sizes, cell values of a chosen range, and writing values and, when asked, formulas.
• presentations — reading, creating and editing Google Slides presentations: adding, reordering, duplicating and deleting slides, editing text, shapes and tables, and reading speaker notes.
• calendar.calendarlist.readonly — the list of calendars your account can open.
• calendar.events — reading events in a time range you ask about (title, description, location, time, status and link; guest lists are not requested) and creating new events without guests, invitations, reminders or video-call links. Google's permission covers editing events in general; the current version only reads and creates events and does not change or delete existing ones.

The connection does not request access to Gmail, Google Contacts, Google Cloud administration or other users' accounts. If a future version needs more access, Google will ask for your consent again; an update of AI Workspace alone never grants it. A link to a file does not bypass the permissions of your Google account or your organization's rules.

3. Other information we process

• Connection data: the permissions you granted, Google access and refresh tokens and their expiry times, identifiers of your company's installation and of its registered client, and the sign-in state. We never ask for or store your Google password.
• Task data: the parameters of each request the agent makes (for example a file ID, a search phrase or a cell range) and what Google returns, such as file contents, document text, cell values or calendar events. The connection service passes them through to complete the request; section 7 explains what is stored.
• Upload data: a file's name, type and size, the address of its Google upload session and then the uploaded file's ID, name and link, so the agent can confirm the result (section 7).
• Technical data: what is needed to deliver and protect requests, such as the IP address at the network level and the time and outcome of a request.
• Support requests: your email address and the content of your message when you write to us.

4. How we use the data

We use Google user data only to provide the features people ask for in AI Workspace:

• to sign you in with Google and keep the connection you allowed;
• to link the connection to the right company installation and person;
• to search, read, download, create, upload and change the files, documents, spreadsheets, presentations and events a task requires, and to return the result to the agent performing the task;
• to protect the service, prevent abuse and fix errors;
• to answer support requests and meet legal obligations.

The agent acts on Google data only when a person asks it to as part of a task. Connecting Google is voluntary. Visiting this website or adding the plugin to an agent does not give anyone access to Google data: access requires your explicit approval on Google's consent screen. If a task involves data of colleagues or other people, the user and the company must have the right to process it.

5. Limited Use and prohibited uses

AI Workspace's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We also follow the Google Workspace API user data and developer policy. In particular:

• We use and transfer Google user data only to provide or improve the user-facing features described in this policy, for security purposes such as investigating abuse, to comply with applicable law, or as part of a merger, acquisition or sale of assets with your explicit prior consent.
• We do not use Google user data to develop, improve or train generalized or non-personalized AI or machine-learning models.
• We do not sell Google user data, do not use or transfer it for advertising (including personalized, retargeted or interest-based advertising) and do not use it to determine creditworthiness or for lending.
• No person reads Google user data unless you have given explicit consent for specific data, it is necessary for security purposes such as investigating abuse, it is required to comply with applicable law, or the data is aggregated and anonymized for internal operations.
• We never use Google APIs or Google user data to create, distribute or facilitate non-consensual intimate imagery (NCII), including AI-generated or digitally altered intimate imagery. This use is forbidden by our Terms of Service.
• These restrictions apply to everyone we transfer Google user data to.

6. Where data goes and who receives it

When an agent performs a task, data moves along this path: Google → connection service → your company's AI Workspace installation → the AI model provider configured by that installation. When the agent writes something, for example saves a file or adds an event, data goes back to Google. The connection service is not just a redirect page: Google's answers pass through it.

• Your company's installation runs separately from the connection service and receives the results of requests made for its users. To complete a task it may put the requested document text, spreadsheet ranges, presentation contents or events into the AI model's context, and save downloaded files in the agent's working folder.
• The AI model provider is chosen and configured by your company's installation, not by us. It receives only the data needed to perform the requested task. Our Terms of Service require installations to use providers and settings under which this data is not used to train the provider's models. Ask your company's administrator which provider and settings are used; the presence of a provider setting in AI Workspace alone does not prove these conditions are met.
• Hosting providers of the connection service, the installations and AI models may process data as part of hosting these systems.
• Other people in a chat: results may appear in a chat, a task log or a file, as the user asked and as the installation is configured. In a shared chat, the other participants of that chat can see them; a personal connection does not make a published result private.

We do not give Google tokens to AI models. Each installation receives its own tokens issued by the connection service; the original Google tokens stay in the connection service's encrypted storage. One sign-in never opens your account to another company or another person. We do not transfer Google user data to anyone else, except in the cases listed in section 5.

7. What the connection service stores

• Encrypted connection records: Google access and refresh tokens, together with the identity information Google returns with them (your account ID, email address, name and profile picture link), the tokens the service issues to installations, and short-lived sign-in records. They are stored in the service's database only in encrypted form (section 10).
• Service registry: identifiers of company installations and their registered clients, their return addresses and connection state. It contains no Google tokens and no file contents.
• Kept-version records: the IDs of the Drive versions the connection marked “Keep forever” (section 9), per connected account and file, so it can later remove its own marks. They are stored only in encrypted form, like the connection records, and contain no file names or contents.
• No content archive: the connection service keeps no copies of your files, documents, spreadsheets, presentations or events. A downloaded file (up to 10 MB) is held in memory only until it has been delivered to the installation. An uploaded file is streamed to Google as it arrives and is never written to disk. The upload's name, type, size and Google upload address are kept in memory only: the single-use upload link is valid for one hour, a transfer that has started may take up to 15 more minutes, and the result is kept for one hour after it ends. These records expire no later than 2 hours 15 minutes after the link is issued and are lost if the service restarts.
• Logs: in its production configuration the service writes no request addresses, sign-in request bodies or Google responses to its application logs, and web-server access logs are turned off for the sign-in, API and upload addresses. The web server that serves these public pages may keep standard access logs (IP address, time and page requested).

Data kept by your company's installation and its providers (results, messages, files, backups) is outside the connection service, so copies may exist elsewhere in the chain.

8. How long we keep data

• Connection records are kept while your connection is in use. Each record has an expiry time: sign-in records last up to 15 minutes, the tokens installations use for requests up to 15 minutes, and the renewal record up to one year after it was last issued. After that it can no longer be used, and you sign in again.
• Expired or unused records cannot be used for access, but may remain in the database in encrypted form until they are deleted. On a deletion request we delete them (section 11).
• Upload records: no more than 2 hours 15 minutes, in memory only.
• Kept-version records have no expiry time: the connection needs them to remove its own marks later (section 9).
• Support emails and records of completed requests: as long as needed to handle the request, protect legal rights and meet record-keeping duties.
• Data in your company's installation (chat history, task results, downloaded files, backups) is kept according to the company's settings; ask its administrator. Google user data must not be kept longer than needed for the feature the user asked for.

9. Kept Drive versions and trash

When you ask the agent to replace the content of an existing regular file (for example xlsx, docx, pdf or an image), the connection first marks the file's current version “Keep forever” in its Google Drive version history, so you can restore it. If Drive refuses to keep that version, nothing is replaced: the agent saves the new content as a new file next to the original and tells you why.

• A kept version lives in the file's own Google Drive version history, not in AI Workspace, and counts against the storage of the file's owner.
• For each file, the connection normally keeps the last 20 versions it marked itself, per company installation and Google account. When it marks one more, it unmarks its own oldest, which returns to Google Drive's usual retention. After a temporary Google error, extra versions can stay marked until a later replacement; a version your account can no longer change stays marked. Versions marked only by people or other apps are never changed; if someone also marks a version the connection marked, it cannot tell the marks apart and may later unmark it.
• Google Drive keeps at most 200 versions of one file this way; beyond that, nothing is replaced.
• You do not need to delete kept versions. If you wish, you can manage them in Google Drive: File information → Manage versions.
• Google Docs, Sheets and Slides are edited in place and keep Google's own version history.
• Files the agent moves to trash can be restored from the Google Drive trash for 30 days; after that Google deletes them.

10. Security

• Connections to the connection service and to Google use HTTPS (TLS). The service connects to its database over a local socket or verified TLS.
• Google tokens and sign-in records are encrypted at rest; the keys are kept apart from the database and the source code.
• Every request is checked against the installation it belongs to, so a token of one installation cannot be used by another.
• Administrative access to the servers is limited to the people who operate the service.

No security measure is perfect, and we cannot promise absolute security. If we learn of a breach affecting your data, we will notify affected users and authorities as the law requires.

11. Disconnect, revoke and delete your data

1. Stop one agent: turn the Google Workspace plugin off for that agent in AI Workspace. Your other agents keep the connection.
2. Sign out in AI Workspace: Plugins → Google Workspace → Sign out («Выйти») next to your account. The installation deletes its tokens for your connection and its agents stop using your Google account. An upload link issued before may stay usable for up to one hour. Signing out does not withdraw the access you granted at Google: the connection service keeps its encrypted Google tokens until they expire (section 8) or you ask us to delete them (step 4). To end Google's access itself, use step 3.
3. Remove access at Google: open myaccount.google.com/permissions, select AI Workspace and remove its access. Because the Google app is shared, this ends access for this Google account in all AI Workspace installations.
4. Request deletion: email kochkingrigory@gmail.com with the subject “AI Workspace — data deletion”. Give the email of the connected Google account and your company's installation. Do not send passwords, tokens, keys or document contents.

We confirm receipt and reply within 10 business days, and within 30 days of the request delete all records the connection service keeps for your account: connection records, upload links and the list of kept versions, unless the law requires us to keep specific records; we will tell you if so. Before deleting them, the service removes its own “Keep forever” marks while its Google access still works (section 9); versions it cannot unmark, for example after you removed access, stay marked in your Drive. You may manage them in Google Drive (File information → Manage versions) but do not have to. We may ask you to confirm that you control the account. Data in a company's installation or at its AI model provider is managed by that company: we pass such requests on to its administrator, and you can also contact them directly.

Removing access stops future access but does not undo actions already performed and does not delete documents, files or events created earlier. You manage those in Google Drive and Google Calendar.

12. Cookies and website data

These public pages use no cookies, scripts, analytics, advertising pixels or external fonts. During sign-in with Google, the connection service uses strictly necessary cookies that protect the sign-in, for example by binding your consent to your browser. Google and your company's installation use their own cookies under their own policies.

13. Children

AI Workspace is a business service for adults acting for their company. It is not directed to children under 18. If you believe a child's data has reached the service, contact us and we will delete it.

14. International transfers

The connection service, company installations, AI model providers and hosting providers may be located in different countries, so data may be processed outside the country where you are. We transfer data only to perform the task you asked for. Before using the connection for personal data that is subject to localization or cross-border transfer rules, for example under Russian Federal Law No. 152-FZ “On Personal Data”, the company must make sure its installation and AI model provider meet them.

15. Your rights

You can ask us what data we process about you, ask us to correct inaccurate data, withdraw your consent and stop the connection, and ask us to delete your data. You may have further rights under the law that applies to you. Where Russian Federal Law No. 152-FZ “On Personal Data” applies, you have the rights it gives data subjects, including the right to appeal our actions to Roskomnadzor, the authority that protects the rights of personal data subjects, or to a court. To exercise your rights, write to kochkingrigory@gmail.com. Refusing the connection never requires giving us more Google data.

16. Changes to this policy

We publish the current version at this address with its effective date. If we materially change which Google data we use, why we use it or who receives it, we will inform users before the change takes effect and ask for new consent where required. A text update alone never grants additional access.

17. Contact

ООО «Айсберг»
Contact person: Kochkin Grigorii Sergeevich
Questions about data, deletion and support: kochkingrigory@gmail.com
Website: google-service.my-jarvis.ru