Google API Disclosure

Tenwrite uses Google APIs to provide user-facing product features such as signing in with Google, selecting Google Docs, converting and exporting Google Docs, accessing selected Google Drive files or folders, reading configured Google Sheets rows for automations, publishing to Blogger, and running Drive or Sheets automations that you configure.

Google Data Tenwrite May Access

Depending on the features you use and the permissions you grant, Tenwrite may access:

Google account profile information, such as your name, email address, and account identifier;
selected Google Docs content and metadata;
selected Google Drive file and folder metadata;
Google Sheets rows and metadata used for automations;
Blogger blogs, posts, labels, publishing status, and related metadata;
OAuth authorization data, such as access tokens, refresh tokens, granted scopes, and related identifiers required to perform authorized actions.

Actions Tenwrite May Take Using Google APIs

When authorized by you, Tenwrite may use Google APIs to:

sign you in to Tenwrite;
let you select Google Docs, Drive folders, or Sheets through Google authorization flows;
read selected Google Docs for export;
read selected Drive folder metadata for automations;
read configured Google Sheets rows for automations;
create, update, schedule, or publish Blogger posts;
retrieve Blogger blog and post metadata;
run publishing workflows that you manually start or configure through automations.

How Tenwrite Uses Google Data

Tenwrite uses Google user data only to provide, maintain, secure, and improve user-facing features that you authorize and that are visible in the Tenwrite interface.

Tenwrite does not sell Google user data, use it for advertising, use it for unrelated profiling, use it for credit scoring, or transfer it to data brokers.

Storage and Security

Tenwrite may store Google-related data such as account identifiers, OAuth tokens, selected document metadata, export metadata, automation configuration, Blogger metadata, and logs as needed to provide the Services.

Google OAuth tokens are stored encrypted and used only as needed to perform actions authorized by you. Tenwrite does not store your Google password.

Tenwrite does not sell Google user data.

Tenwrite may share or transfer Google user data only as needed to provide and improve authorized user-facing features, operate and secure the Services, comply with law, prevent abuse, or use trusted service providers listed in our Privacy Policy and Sub-processors page.

Human Access

Tenwrite does not allow humans to read Google user data except where necessary to provide support requested by you, investigate abuse or security issues, comply with law, or maintain and operate the Services. Where possible, we limit access to the minimum data necessary.

Limited Use

Tenwrite’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.

Revoking Access

You can revoke Tenwrite’s Google access at any time from your Google Account permissions page. After revocation, Google-connected features may stop working until you reconnect your account.

Deleting Google Data

You can revoke Tenwrite’s Google access from your Google Account permissions page at any time. You may also contact support@tenwrite.com to request deletion of Google-related data stored by Tenwrite.

When you disconnect an integration, revoke access, or delete your Tenwrite account, we will delete or disable stored Google credentials and related data where reasonably feasible, subject to backup, legal, security, fraud-prevention, dispute-resolution, and operational retention needs.