Privacy Policy

AI Renamer helps users rename files in connected Google Drive folders using templates, AI-generated suggestions, approval queues, and rollback history. This policy applies to the data collected or processed by the service when someone visits the public site, creates an account, connects Google Drive, or uses rename workflows.

If this software is deployed by a third party or customized for a private workspace, the operator of that deployment is responsible for providing any additional notices, contact details, or jurisdiction-specific terms required by law.

The service may process account details, workspace information, Google Drive connection details, file metadata, extracted document context, rename rules, approval decisions, rollback actions, diagnostics, and usage events.

• Authentication data such as name, email address, and user identifiers returned by the configured sign-in provider.
• Google Drive connection information, including the scopes granted, folder selections, and encrypted refresh-token data needed for background processing.
• File metadata such as names, paths, identifiers, timestamps, and related folder information.
• Document content or extracted text when that information is required to generate a better rename suggestion.
• Operational records such as rename suggestions, approval status, audit logs, retries, diagnostics, and usage metrics.

AI Renamer uses this information to authenticate users, monitor selected folders, generate rename suggestions, apply or roll back file changes, maintain workspace history, secure the service, and improve reliability.

The service is designed to support both manual approvals and automated application. That means the product may continue processing connected folders in the background when users have enabled that behavior.

Google Drive access is handled through a dedicated Drive authorization flow that is separate from basic app sign-in. The product requests only the scopes it needs for the configured workflow, and those permissions are used to inspect files, generate rename suggestions, and rename files inside the connected folders.

When AI naming is enabled, relevant file context may be sent to the configured model provider, such as OpenAI or Gemini, or to a provider selected by the workspace through bring-your-own-key settings. The application is designed around strict JSON suggestions and does not store hidden reasoning traces as product data.

Information may be processed by infrastructure and integration providers that support the product, such as hosting, authentication, database, Google API, logging, and AI model services. The service is not intended to sell personal information.

Data may also be disclosed when required to comply with law, enforce the product's terms, investigate abuse, or protect users, the operator, or third parties.

The product includes measures intended to protect sensitive connection data, such as encrypted storage for refresh tokens and provider credentials, access controls around workspace actions, and audit records for important rename events.

Retention periods may differ depending on how the deployment is configured. Workspace operators may choose to keep logs, suggestions, and activity history for operational, audit, or support purposes.

Users can generally pause monitored folders, disconnect Drive integrations, switch between approval and automation settings, and request deletion or export of their data from the operator of the deployment they use.

If you need to exercise a privacy right under applicable law, contact the operator of the service instance you are using so they can verify the request and respond based on their deployment-specific obligations.

This policy may be updated as the product changes. When material changes are made, the operator should publish an updated version on the public site with a revised effective date.