Privacy Policy

This policy covers LogAgency AI Office, an internal, AI-assisted operations tool run by LogAgency. It explains how the tool accesses, uses, stores and shares Google user data.

Operator: LogAgency. Effective date: 2026-09-28.

1. Google user data the tool accesses

The tool uses the Google Sheets API with one Google account that LogAgency operates for this tool. It does not offer sign-in to anyone outside LogAgency.

• Read access (spreadsheets.readonly): the tool reads the Google Sheet in which LogAgency keeps the business inquiries it receives. An inquiry row contains what the inquirer submitted, such as their name, company name, email address, phone number and message.
• Write access (spreadsheets), held separately from read access: the tool writes one value, an internal reference ID, into one reserved column of that Sheet. The rest of the Sheet is protected against edits by this account.

The tool does not request access to Gmail, Google Drive files, Google Calendar, contacts or any other Google product data.

2. Why it accesses the data and how it is used

• To check each inquiry for missing or inconsistent information and, with staff approval, give it an internal reference ID.
• To look up the inquirer's company and public website, so that staff have context for their reply. Staff may also export a copy of the Sheet for this processing.
• To show LogAgency staff the inquiries and their status, and to assign each inquiry to a staff member.
• To prepare draft replies for staff. A person reviews and approves each email before it is sent to the inquirer. The tool does not send email automatically.

Some of this work, such as checking inquiries, company research and drafting replies, is assisted by an AI model (see section 4).

LogAgency does not sell Google user data. LogAgency does not use Google user data for advertising or ad targeting.

3. What is stored

All of the following are stored on a computer operated by LogAgency:

• in a private directory: the Google authorization credentials, copies of the Sheet exported by staff, company research notes, reply drafts, and records of staff approvals and sent emails;
• in the local data folder of the staff interface: a list of inquiries prepared from the Sheet for staff review.

Data handled by the external processors in section 4 is also held by them, as described there.

4. Sharing and external processors

• Email delivery. When a person approves an email, the recipient's email address and the message are sent through LogAgency's business email provider, Hiworks, which delivers the message. A copy of each sent message also goes to LogAgency's own business mailbox.
• Company research. The inquirer's company name and website address are used to look up that company's public web pages.

• AI-assisted processing. Inquiry data from the Sheet, including the details listed in section 1, may be processed by Anthropic's Claude model through Claude Code, which the LogAgency operator uses with an individual Claude Max subscription. In that account, the setting that allows Anthropic to use conversations to improve its models is turned off. Anthropic processes this data, and may store it, under its own terms and privacy policy.

5. Retention and deletion

LogAgency keeps personal data only as long as it is needed for its operations, for audit and safety purposes, and to meet legal obligations. When it is no longer needed, LogAgency deletes it or makes it anonymous.

LogAgency can stop the tool's access at any time by revoking its authorization in the Google account settings.

6. Security

• Read access uses the read-only Google Sheets scope. Write access uses a separate credential with the Google Sheets scope.
• Writes are limited in the software to the one reserved column, and the Sheet itself is protected so that the account cannot edit other cells.
• The files holding the Google authorization tokens are readable only by the operating account on the computer that stores them.
• The staff interface is not published on the internet.
• Every customer email requires a person's review and approval before it is sent.

7. Google API Services User Data Policy

LogAgency AI Office's use and transfer of information received from Google APIs adheres 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 User Data Policy, including the Limited Use requirements.

Data obtained through Google Workspace APIs is not used to train, develop or improve generalized or non-personalized AI or machine-learning models.

8. Contact

For questions about this policy or about data held by LogAgency AI Office, contact LogAgency at contact@logagency.co.kr.