Privacy Policy – Google Docs Tool

1. Data Accessed

Google User Data Accessed

This application accesses the following types of Google user data:

Google Docs API Access:

• Document Content: Text, titles, headings, and other content within Google Docs documents
• Document Metadata: Document IDs, document structure, and formatting information
• Document Permissions: Information necessary to create, read, and modify documents in the user's Google Drive

Authentication Information:

• OAuth 2.0 access tokens and refresh tokens (managed by ChatGPT, not stored by this application)
• Google account identification required for API authentication

Scope of Access:

The application requests and uses only the https://www.googleapis.com/auth/documents scope, which provides read and write access to Google Docs documents only

The application does not access other Google services such as Gmail, Google Drive file metadata, Google Calendar, or any other Google APIs beyond the Google Docs API

User Authorization:

All access occurs only after the user explicitly authorizes the application through Google's OAuth 2.0 consent flow

Users may revoke access at any time through their Google Account settings

2. Data Usage

How We Use Google User Data

The application uses Google user data exclusively for the following purposes:

Document Creation and Editing:

• Create new Google Docs documents with content provided by the user through ChatGPT
• Read existing document content to determine document structure and formatting
• Modify existing Google Docs documents by appending or overwriting content as instructed
• Apply formatting (headings, text styles) to document content

Operational Functions:

• Process document titles, summaries, content, key points, action items, and custom sections provided by users via ChatGPT
• Execute document creation or modification requests exactly as instructed, without analyzing or deriving additional meaning from content beyond what is necessary to apply changes
• Manage OAuth token refresh to maintain authorized access (tokens are managed by ChatGPT, not stored by this application)

Temporary Processing:

• Temporarily process document content in memory during request execution
• Use request content for idempotency purposes (preventing duplicate document creation) for up to 24 hours in memory only

Limitations on Data Usage:

• The application does not analyze, interpret, derive insights from, or use document content for any purpose other than creating or editing documents as instructed
• The application does not use Google user data for advertising, marketing, or any commercial purposes beyond providing the core document editing service
• The application does not train machine learning models on user data

3. Data Sharing

Third-Party Data Sharing

No Third-Party Sharing:

The application does not sell, rent, share, trade, or disclose Google user data to any third parties.

Google API Transmission:

• Data is transmitted only to Google's servers as required to create or update documents using the Google Docs API
• All data transmission to Google occurs over encrypted HTTPS connections
• This transmission is necessary for the application to function and is disclosed to users through this policy

Service Providers:

The application does not use third-party analytics services, advertising networks, or other service providers that would receive Google user data

The application operates on infrastructure that processes requests, but no Google user data is shared with hosting or infrastructure providers beyond what is necessary for basic server operations (request routing, etc.)

Legal Requirements:

We may disclose data if required by law, court order, or government regulation, but only to the extent necessary to comply with such requirements

4. Data Storage & Protection

Storage Practices

Temporary In-Memory Storage:

• The application uses temporary in-memory storage only for operational purposes during request processing
• Document content is processed in server memory during request execution and is immediately discarded after the request completes
• An idempotency cache stores document IDs and metadata (document ID, title, view URL) in memory for up to 24 hours to prevent duplicate document creation; this cache is automatically purged after 24 hours

What Is Not Stored:

• The application does not store document contents, text, or personal information in persistent storage (databases, files, or cloud storage)
• OAuth access tokens and refresh tokens are not stored by this application; token management is handled by ChatGPT
• The application does not maintain logs that contain document content or sensitive personal data

Operational Logging:

• Server logs may contain high-level operational information (request status, error codes, document IDs) but do not include document content or sensitive personal information
• Logs are used exclusively for debugging and monitoring application functionality

Security Measures

Data Transmission:

• All communications between the application and Google's APIs occur over encrypted HTTPS/TLS connections
• OAuth tokens are transmitted securely using industry-standard encryption

Access Controls:

• The application requires valid OAuth access tokens for all Google Docs API operations
• Access tokens are validated for each request and must be provided by the authorized user
• Users maintain full control over their Google account permissions and can revoke access at any time

Infrastructure Security:

• The application follows security best practices for server configuration and access controls
• Regular security updates are applied to dependencies and infrastructure components

5. Data Retention & Deletion

Retention Policy

In-Memory Data:

• Document content processed during requests is discarded immediately after request completion (no retention)
• Idempotency cache entries (document IDs and metadata) are automatically deleted after 24 hours
• Operational logs are retained only as long as necessary for debugging and monitoring purposes (typically less than 30 days)

No Persistent Storage:

The application does not maintain persistent storage of Google user data

Users retain full ownership and control of all documents created or modified by the application

User Control:

• All documents created or edited by the application are owned by the user in their Google account
• Users may view, modify, or delete their documents directly in Google Docs at any time
• Users may revoke the application's access to their Google account at any time through Google Account settings, which will immediately prevent the application from accessing their data

Data Deletion Requests

Requesting Data Deletion:

Users may request deletion of any data related to their use of this application by contacting us at democraticdeveloper@gmail.com.

What Can Be Deleted:

• Any cached idempotency entries associated with the user's requests (if identifiable) can be manually purged
• Operational logs that may contain user-identifiable information can be reviewed and deleted upon request
• Since the application does not store document content, there is no document content to delete from our systems

Response Time:

We will respond to deletion requests within 30 days and confirm when deletion has been completed

Note: Documents created by the application remain in the user's Google account and can be deleted directly by the user in Google Docs

6. User Rights and Control

User Control Over Data

• Access Revocation: Users may revoke the application's access to their Google account at any time through Google Account Settings
• Document Ownership: All documents created or edited by the application are owned by the user and stored in their Google account
• Document Management: Users have full control to view, modify, share, or delete any documents created or modified by the application directly in Google Docs

7. Changes to This Policy

This Privacy Policy may be updated periodically to reflect changes in our practices, legal requirements, or the functionality of the application. The "Last Updated" date at the top of this policy indicates when the most recent changes were made.

• Users will be notified of material changes to this policy
• Continued use of the application after policy changes constitutes acceptance of the updated policy

8. Contact Information

For questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact:

Email: democraticdeveloper@gmail.com

We will respond to inquiries within a reasonable timeframe.

Effective Date: December 27, 2025