How OFFMUSE handles Google user data.

1. Scope

This Privacy Policy applies to OFFMUSE Blogger Automation and the OAuth application named Blogger_자동등록_FINAL. The service is a private automation utility used to manage publishing workflows for Google Blogger accounts controlled by the authorized account owner.

2. Google user data accessed

The service may request the Google Blogger OAuth scope https://www.googleapis.com/auth/blogger. Through the official Blogger API, the automation may access information necessary to operate the workflow, including Blogger account information, blogs managed by the authorized user, blog identifiers, posts, drafts, and publishing status.

3. How Google user data is used

Google user data is used only to provide the publishing functionality requested by the authorized account owner. This includes identifying available Blogger sites, selecting a target blog, creating draft posts, publishing posts, and checking the result of publishing operations.

Google user data is not used for advertising, behavioral profiling, credit decisions, or sale to third parties.

4. Storage and retention

The public website at offmuse.com does not receive or store Google OAuth access tokens. OAuth authorization is handled through Google and Google Apps Script. The automation may store limited operational metadata such as blog IDs, post IDs, timestamps, status values, and error logs in the authorized user's Google Apps Script properties or Google Drive when that workflow is configured.

Operational metadata is retained only as long as reasonably necessary to operate, troubleshoot, and audit the publishing workflow, and may be deleted by the account owner.

5. Sharing and disclosure

OFFMUSE does not sell Google user data. Google user data is not shared with advertisers or unrelated third parties. Data may be processed by Google services used to operate the workflow, such as Google Blogger, Google Apps Script, and Google Drive, according to the account owner's configuration and Google's applicable terms.

6. Security

The automation is designed to avoid manually storing OAuth access tokens outside Google's authorization environment. Access is limited to the scopes required for the Blogger publishing workflow, and the account owner controls authorization through their Google Account.

7. Revoking access and deletion

The account owner can revoke the application's Google Account access through their Google Account security settings. After access is revoked, the automation can no longer use the associated Blogger authorization. Any locally stored operational metadata can also be removed from the owner's Apps Script or Google Drive environment.

8. Google API Services User Data Policy

OFFMUSE's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements where applicable.

9. Changes to this policy

This policy may be updated when the automation's functionality or data practices change. The current version will remain available at this URL with its effective date shown above.