Privacy Policy: Comparison of Provisions Before and After the Change
Before: version effective October 23, 2026 · After: version effective November 28, 2026 (announced October 29, 2026)
Only the provisions changed in this revision are shown, with the text before and after the change side by side and the changed sentences marked. This table is provided for convenience; the full text of each version governs. View the revised Privacy Policy (effective November 28, 2026) · View the previous Privacy Policy (effective October 23, 2026)
15-3 Google Drive Full Read Access and File Editing (drive.readonly; drive for file editing; plus openid and email to identify the connected account)
| Before | After |
|---|---|
15-3 Google Drive Full Read Access (drive.readonly, plus openid and email to identify the connected account) — Internal Pilot · Who can connect: this is currently an internal pilot of the Company; in workspaces designated by the Company, only members the Company permits (owners by default) can connect their Company Google Workspace account (with the same email address as their AXIT account). Before connecting, the app explains this and obtains the user's consent. · Information received: the list, names, types, and content of files in the connected account's Drive, and search results · Purpose: only in tasks requested by the person who connected it, the AI finds and reads the files it needs and shows the list of files read together with the result. This connection is not used for conversations or notes, for tasks started by email, webhooks, bots, or other people's posts, or for tasks requested by other people, and files are created or edited only through the connection in Section 15-2. · Safeguards: the amount read per task is capped, and file content is passed to the AI as material separated from instructions. Tasks that read files through this connection run only in an isolated execution environment without shared file storage, with web search and external connections turned off. Sending the result of such a task outside AXIT (email replies, posts, GitHub, etc.) requires approval from all owners of the data, and some paths, such as published pages and saving to the library, are blocked. The work process of the task is visible only to the person who requested it, notifications hide the content, and the result content is masked when passed to later tasks requested by other people. · AI processing: sent only through the routes confirmed under Section 15-6 not to use the data for training. · Storage: the refresh token is encrypted with AES-256-GCM and kept only on the server; it is not sent to the AI execution environment. AXIT keeps a record of the files each task read (file ID, name, address, type, and number of characters read; search terms only as irreversible values) to show in the task view, and file content is not written to this record. When the task ends, its AI execution record is deleted immediately. Task outputs remain as channel messages. | 15-3 Google Drive Full Read Access and File Editing (drive.readonly; drive for file editing; plus openid and email to identify the connected account) · How it is offered: this connection is offered through two Google apps. (a) The Company's internal app: in Company workspaces designated by the Company, only the Company's Google Workspace accounts can be connected. (b) The customer app: an external app for users outside the Company, to which personal Google accounts (Gmail addresses) can be connected as well as Google Workspace accounts. The customer app is in a testing stage before it completes Google's app verification (including the security assessment); for now it can be used only in workspaces designated by the Company, and while its publishing status in Google is "Testing", only accounts the Company has registered with Google as test users can connect it. · Who connects: in either app, members the Company permits (by default, workspace owners) connect their own Google account, and only the Google account with the same email address as their AXIT account can be connected. Guests cannot connect. · How to connect: before connecting, the app explains this and obtains the user's consent. When connecting through the customer app, after allowing access on Google's consent screen, the user confirms the Google account to connect once more on an AXIT screen before the connection is completed. While the customer app's publishing status is "Testing", under Google's policy the connection ends 7 days after it was made, and the user must connect again to keep using it (the settings screen shows the date it ends). · Information received: the list, names, types, and content of files in the connected account's Drive, and search results (with File editing turned on, also the location, owner (name and email address), sharing state, and edit permission of a file to be edited; the email addresses of the people a file is shared with are not kept, only counts by domain) · Purpose: only in tasks requested by the person who connected it (including scheduled tasks that person created themselves or approved when they were set up), the AI finds and reads the files it needs and shows the list of files read together with the result. This connection is not used for conversations or notes, for tasks started by email, webhooks, bots, or other people's posts, or for tasks requested by other people. New files are created only through the connection in Section 15-2, and this connection edits existing files only when File editing (below) is turned on. · Safeguards: the amount read per task is capped, and file content is passed to the AI as material separated from instructions. Tasks that read files through this connection run only in an isolated execution environment without shared file storage, with web search and external connections turned off. Sending the result of such a task outside AXIT (email replies, posts, GitHub, etc.) requires approval from all owners of the data, and some paths, such as published pages and saving to the library, are blocked. The work process of the task is visible only to the person who requested it, notifications hide the content, and the result content is masked when passed to later tasks requested by other people. · AI processing: sent only through the routes confirmed under Section 15-6 not to use the data for training. · Storage: the refresh token is encrypted with AES-256-GCM and kept only on the server; it is not sent to the AI execution environment. AXIT keeps a record of the files each task read (file ID, name, address, type, and number of characters read; search terms only as irreversible values) to show in the task view, and file content is not written to this record. When the task ends, its AI execution record is deleted immediately. Task outputs remain as channel messages. · File editing (optional feature, drive): in workspaces designated by the Company, the person who made this connection can separately turn on "File editing". Before it is turned on, the app explains this and obtains the user's consent, and the user must allow, once more and with the same Google account, the permission that Google's consent screen shows as "See, edit, create, and delete all of your Google Drive files" (drive). With the customer app, the user confirms the account once more on an AXIT screen, and while the publishing status is "Testing", the connection ends 7 days after this point. AXIT uses this permission only as follows: in tasks requested by the person who turned it on (including scheduled tasks that person created themselves or approved when they were set up), AXIT changes cell values and text in existing files that the connected account can edit: cell values in Google Sheets, Excel files (.xlsx), and CSV files, and text in Google Docs, Word files (.docx), PowerPoint files (.pptx), and text files (.txt, .md) (find and replace, and adding text at the end; for PowerPoint files, find and replace only). This includes files in My Drive, Shared with me, and shared drives, including files owned by other people. A file that is not a Google Doc or Sheet is downloaded, only the requested cells or text are changed, and the result is uploaded back to the same file in the same format (the file's name, location, and sharing stay the same). Before uploading, AXIT marks the version before the change to be kept permanently in the file's Google Drive version history, and if it cannot, it does not make the change. The user can download or delete that kept version in Google Drive's version management. AXIT does not change formulas or macros in Excel files: it does not edit cells that contain formulas, and it does not edit files that contain macros, password-protected files, or older-format Office files (.xls, .doc, .ppt). When it edits an Excel file, AXIT leaves the formulas unchanged and clears only their stored results, so that they are recalculated the next time the file is opened. Before each change, AXIT shows a confirmation card to the person who requested the task, shows only that person the file's name, location, owner, and sharing state and the content before and after each change, and makes the change only if that person allows it. Each change request is limited to what the confirmation card can show in full (50 places), and invisible formatting characters are refused or shown visibly on the card. The confirmation card visible in the channel does not include file names or the changes, and the changes are reviewed and allowed on the web and in the desktop app. If the person declines or does not answer within 10 minutes, nothing is changed. Files are not edited in tasks that include another person's Google Drive data. AXIT does not delete files, move them to the trash, change their sharing or permissions, move them to other folders, or transfer their ownership. The information received to show on the confirmation card (the file's location, owner, and sharing state, and the current content of the places to be changed) is not sent to the AI; it is stored encrypted and deleted once the card is answered or expires. Content downloaded to edit a file that is not a Google Doc or Sheet is likewise not sent to the AI and is not stored; it is discarded as soon as the edit is finished or is not made because it was declined or expired. Edited files are also kept in the record of files the task read. File editing can be turned off at any time on the same settings screen, and it stops immediately; confirmation cards still waiting for an answer are closed. Because the permission remains in the Google Account after File editing is turned off, the user can remove it by disconnecting Drive full read access or by revoking it directly in Google (Sections 15-8 and 15-9). If another AXIT connection uses the same Google account, disconnecting does not remove the permission on Google's side, so in that case the user revokes it directly in Google. File editing is turned off when this connection is made again or when the user's AXIT sign-in address changes. |
15-4 Gmail (gmail.readonly, plus openid and email to identify the connected account)
| Before | After |
|---|---|
15-4 Gmail (gmail.readonly, plus openid and email to identify the connected account) — Internal Company Mailboxes · Who can connect: for the Company's internal work only; only mailboxes on the Company's Google Workspace domain (uniquegood.biz) can be connected, by owners and admins of the Company's workspace, and this feature is not offered to other users. · Information received: the headers (sender, recipients, subject, and date) of mail arriving in the connected mailbox; the body and attachments are received only for mail matching rules set by owners and admins, and mail that does not match is not stored. · Purpose: mail matching the rules is moved into posts in a designated channel so that the members of that channel can read it and use it in AI tasks. AI tasks started by mail are not given Drive, Calendar, or library tools. · Storage: the refresh token is encrypted with AES-256-GCM and kept only on the server; it is not sent to the AI execution environment. Mail moved to a channel (sender, recipients, subject, body, and attachments) is kept as content of that channel until it is deleted under Section 7, and delivery records (such as the Gmail message ID) are kept so that the same mail is not moved twice. | 15-4 Gmail (gmail.readonly, plus openid and email to identify the connected account) · How it is offered: through the same two Google apps as in Section 15-3. (a) The Company's internal app: in the Company's workspace, only mailboxes on the Company's Google Workspace domain (uniquegood.biz) can be connected. (b) The customer app (the same app as the customer app in Section 15-3): personal Gmail mailboxes can be connected as well as Google Workspace mailboxes. The customer app is in a testing stage before it completes Google's app verification (including the security assessment); for now it can be used only in workspaces designated by the Company, and while its publishing status in Google is "Testing", only accounts the Company has registered with Google as test users can connect it. · Who connects: workspace owners and admins connect mailboxes. For a mailbox connected through the customer app, only the person who connected it can create or edit the receiving rules for that mailbox. · How to connect: when connecting through the customer app, the app explains this and obtains the user's consent before connecting, and after allowing access on Google's consent screen, the user confirms the Google account to connect once more on an AXIT screen before the connection is completed. While the customer app's publishing status is "Testing", under Google's policy the connection ends 7 days after it was made, and the user must connect again to keep using it. · Information received: when new mail arrives, to match it against the receiving rules, AXIT receives only its Gmail message and thread identifiers, labels, time received, and size, and the headers about where it was delivered (recipients, Cc, forwarding addresses, mailing list, and message ID). Only for mail matching the rules does AXIT receive the headers, including sender, subject, and date, and the body and attachments; mail that does not match is not stored. · Purpose: mail matching the rules is moved into posts in a designated public channel so that the people who can see that channel (including members of the workspace who have not joined the channel) can read it and use it in AI tasks, and if a rule includes an instruction, the AI processes the mail as instructed (for example, summarizing or classifying it) and replies in that post's thread. AI tasks started by mail are not given Drive, Calendar, or library tools. AXIT does not send mail from the connected mailbox, and does not modify or delete mail in it. · Storage: the refresh token is encrypted with AES-256-GCM and kept only on the server; it is not sent to the AI execution environment. Mail moved to a channel (sender, recipients, subject, body, and attachments) is kept as content of that channel until it is deleted under Section 7, and delivery records (such as the Gmail message ID) are kept so that the same mail is not moved twice. |
16. Revision History
| Before | After |
|---|---|
Main changes in this revision, announced on October 17, 2026 and effective October 23, 2026 (previous version: effective July 20, 2026): (1) Sections 5 and 6: Amazon Web Services (storage in the Seoul Region, disaster-recovery copies in the Tokyo Region, Japan, and Amazon Bedrock), Functional Software (Sentry), Google (Firebase Crashlytics and Firebase Cloud Messaging), Paddle, Mailgun, and ElevenLabs were added as processors and overseas transfers, and the items and conditions of transfers to Cloudflare, Apple, and AI providers were corrected to match actual processing. (2) Sections 1 and 2: the purposes and items now include sign-in methods (email verification code, Google, and Apple), mobile device tokens, error and crash report information, note recordings, received emails, Slack imports, and Paddle payment information. (3) Sections 3 and 7: the backup retention period of "7 days" was corrected to 7 days for the database, 35 days for file storage, 14 days for search server snapshots, and the retention periods of the Tokyo copies; the Policy now states that deleted files are also deleted from the upload storage (Amazon S3) and that their previous versions are deleted after 30 days in Seoul and 14 days in Tokyo, what is deleted and what remains on membership withdrawal, workspace deletion, and content deletion (including when deleted workspaces and withdrawn users' conversations are destroyed), the retention periods of audit log entries that are contract records (5 years) and of original copies of received emails (1 year), and how records subject to statutory retention are kept. (4) Section 4: a notice about information sent to external services connected by the user was added. (5) Section 6: the description of the basis for transfers for web analytics (Google Analytics) was corrected. (6) Section 10: encryption of integration tokens, encryption at rest, file storage backups and disaster-recovery copies, and the removal of information before error reports are sent were added, and the description of audit records ("protection against forgery and alteration") was corrected to the measures actually taken (within the Service they can only be viewed, and viewing is restricted). (7) Section 15 (Google User Data) was added. The full text of the previous version is available at https://axit.team/privacy?version=2026-07-20 and also upon request to the Company. The Korean text is the authoritative version of this Policy. This translation is provided for convenience; the Korean version prevails in case of any conflict. This Policy applies from October 23, 2026. | Main changes in this revision, announced on October 29, 2026 and effective November 28, 2026 (previous version: effective October 23, 2026): (1) Sections 15-3 (Google Drive full read access) and 15-4 (Gmail): these connections can now also be made through a customer Google app (in a testing stage) in addition to the Company's internal app, so the Policy now describes how the two apps are offered, which accounts can be connected (including personal Google accounts), who connects, and how to connect (the explanation and consent before connecting, confirming the Google account to connect, and the 7-day connection limit while the publishing status is "Testing"), and states that only the person who connected a mailbox through the customer app can create or edit its receiving rules. (2) Section 15-3: the Policy now states that the connection is also used in scheduled tasks that the person who connected it created themselves or approved when they were set up. (3) Section 15-4: the information received to match mail against the receiving rules was corrected to match actual processing (the headers about where the mail was delivered, labels, etc.), and the Policy now states that moved mail becomes a post in a public channel that members of the workspace who have not joined the channel can also see, that the AI processes mail as a rule instructs and replies in the thread, and that AXIT does not send mail from the connected mailbox or modify or delete mail in it. (4) Section 15-3: the optional File editing feature (drive) was added, describing how it is turned on (the explanation and consent in the app, and allowing it once more with the same Google account), what it edits (cell values in existing Google Sheets, Excel, and CSV files and text in existing Google Docs, Word, PowerPoint, and text files, with the version before each edit of a non-Google file kept permanently in Google Drive's version history), that each edit is shown only to the person who requested the task and made only if that person allows it, what it does not do (deleting files, moving them to the trash, changing sharing or permissions, moving them between folders, transferring ownership, or changing formulas or macros in Excel files), and how to turn it off and remove the permission on Google's side. The table comparing the provisions before and after the change is available at https://axit.team/privacy?compare=2026-10-23, and the full text of the previous version is available at https://axit.team/privacy?version=2026-10-23 and also upon request to the Company. Main changes in the revision announced on October 17, 2026 and effective October 23, 2026 (previous version: effective July 20, 2026): (1) Sections 5 and 6: Amazon Web Services (storage in the Seoul Region, disaster-recovery copies in the Tokyo Region, Japan, and Amazon Bedrock), Functional Software (Sentry), Google (Firebase Crashlytics and Firebase Cloud Messaging), Paddle, Mailgun, and ElevenLabs were added as processors and overseas transfers, and the items and conditions of transfers to Cloudflare, Apple, and AI providers were corrected to match actual processing. (2) Sections 1 and 2: the purposes and items now include sign-in methods (email verification code, Google, and Apple), mobile device tokens, error and crash report information, note recordings, received emails, Slack imports, and Paddle payment information. (3) Sections 3 and 7: the backup retention period of "7 days" was corrected to 7 days for the database, 35 days for file storage, 14 days for search server snapshots, and the retention periods of the Tokyo copies; the Policy now states that deleted files are also deleted from the upload storage (Amazon S3) and that their previous versions are deleted after 30 days in Seoul and 14 days in Tokyo, what is deleted and what remains on membership withdrawal, workspace deletion, and content deletion (including when deleted workspaces and withdrawn users' conversations are destroyed), the retention periods of audit log entries that are contract records (5 years) and of original copies of received emails (1 year), and how records subject to statutory retention are kept. (4) Section 4: a notice about information sent to external services connected by the user was added. (5) Section 6: the description of the basis for transfers for web analytics (Google Analytics) was corrected. (6) Section 10: encryption of integration tokens, encryption at rest, file storage backups and disaster-recovery copies, and the removal of information before error reports are sent were added, and the description of audit records ("protection against forgery and alteration") was corrected to the measures actually taken (within the Service they can only be viewed, and viewing is restricted). (7) Section 15 (Google User Data) was added. The full text of the previous version is available at https://axit.team/privacy?version=2026-07-20 and also upon request to the Company. The Korean text is the authoritative version of this Policy. This translation is provided for convenience; the Korean version prevails in case of any conflict. This Policy was announced on October 29, 2026 and applies from November 28, 2026. |