Privacy Policy

Effective date: 2026-04-27 · Last updated: 2026-04-27

This policy describes how OurSEO Agent ("the Agent", "we", "us") handles user data, with specific attention to data accessed through Google APIs. OurSEO Agent is operated by D.intelligence Lab, a digital marketing intelligence operation registered in the Republic of Korea, and distributed under the OurDigital brand. Contact: [email protected].

1. What OurSEO Agent is

OurSEO Agent is an internal, command-line SEO auditing tool (Python 3.10+) that runs entirely on the operator's local workstation. There are no OurSEO Agent servers and no centralized backend — every user runs their own local copy. All intellectual property in OurSEO Agent belongs to D.intelligence Lab — All rights reserved.

2. Google data we access

OurSEO Agent requests the following OAuth scopes only when a client engagement requires them:

Scope	What it grants	What we do with it
`https://www.googleapis.com/auth/business.manage`	Read access to a merchant's Google Business Profile accounts, locations, daily performance metrics, and reviews.	Generate Local SEO audits comparing the merchant's website against their canonical Business Profile record. Aggregate review velocity and performance metrics into client SEO reports.

OurSEO Agent does not edit Google Business Profile listings, post Updates, reply to reviews, or take any other write action on a merchant's behalf at the version covered by this policy (v1.x). Any future expansion of the agent's write surface will be announced in a policy update before it ships.

We do not request any other Google scopes (no Gmail, no Drive, no Calendar, no YouTube, no Photos).

3. Where the data is stored

When a merchant grants consent, Google issues an OAuth refresh token. That token is stored as a JSON file on the operator's local workstation at:

~/.config/secrets/ourseo/tokens/<profile-name>.json

with file permissions 0600 (owner read/write only). The directory is 0700. The token is not transmitted to any OurSEO Agent server, third-party SaaS, or analytics endpoint. There is no "OurSEO Agent cloud" because the project does not operate one.

Merchant data fetched at runtime — account names, location records, performance metrics, reviews — is written to local files under the operator's project directory (typically data/clients/<client-slug>/<date>/) for the duration of the active engagement.

4. Compliance with Google's Limited Use Policy

OurSEO Agent's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

Google user data is used solely to provide and improve user-facing features of the agent (SEO audit and reporting).
Google user data is not transferred to third parties except as needed to provide or improve user-facing features (which, in OurSEO Agent's architecture, never happens — there are no third parties involved at runtime).
Google user data is not used or transferred for serving advertisements, including retargeted advertising or personalized advertising.
Humans do not read Google user data unless the operator has explicit consent from the user, the data is necessary for security purposes (e.g., investigating abuse), or to comply with applicable law.

5. Sharing

OurSEO Agent does not share Google user data with any third party. All processing happens locally on the operator's workstation. No analytics, no error reporting, no usage telemetry is collected or transmitted.

When the operator generates a client report (e.g., a CSV or Notion document), distribution of that report to the client is out of scope of this policy and is governed by the operator's own data handling agreement with the client.

6. Retention and deletion

We retain Google data only for as long as the client engagement that authorized access remains active.

A merchant can revoke OurSEO Agent's access at any time at myaccount.google.com/permissions. Revocation invalidates the refresh token immediately; subsequent API calls return invalid_grant and the operator must delete the local token file and re-onboard if access is needed again.

The operator can also delete a merchant's data at any time by removing the corresponding token file (rm ~/.config/secrets/ourseo/tokens/<profile>.json) and the per-client data directory (rm -rf data/clients/<slug>/).

7. Security

All tokens are stored at file mode 0600 and parent directories at 0700.
The agent uses the official google-auth and google-auth-oauthlib libraries for OAuth flows; tokens are never logged or printed to stdout.
API calls are made over TLS to Google's official endpoints (mybusiness.googleapis.com, mybusinessbusinessinformation.googleapis.com, businessprofileperformance.googleapis.com, mybusinessaccountmanagement.googleapis.com).
We do not collect operator passwords, API keys, or any credentials beyond what the OAuth flow itself produces.

8. Children's data

OurSEO Agent is a B2B tool for digital marketing professionals. It is not directed at children under 13, and we do not knowingly collect data from children.

9. License and rights

All intellectual property in OurSEO Agent belongs to D.intelligence Lab. This is proprietary software provided for internal and contracted-client use only. Reproduction, redistribution, reverse-engineering, and derivative works are prohibited without prior written permission — All rights reserved.

10. Changes to this policy

We may update this policy as the agent evolves. Material changes — particularly any expansion of the OAuth scopes requested or any change to the read-first architecture stated in §2 — will be announced via:

An update to this page with a revised "Last updated" date.
A note in OurSEO Agent's release notes.
Re-prompting for consent if the new scopes require it.

11. Contact

Questions about this policy or about how a specific merchant's data has been handled should be directed to:

Andrew Yim · D.intelligence Lab
Email: [email protected]