Terms of Service
These Terms of Service govern access to and use of AI Renamer, including the public site, connected Google Drive workflows, and rename automation features. They are meant to be product-accurate and deployment-friendly: a workspace can use approvals, auto-apply, rollback, and provider integrations, but users remain responsible for how those workflows are configured and reviewed.
Last updated on April 23, 2026
1. Using the service
You may use AI Renamer only in compliance with these Terms and applicable law. The service is intended to help users connect Google Drive folders, generate rename suggestions, review those suggestions, and apply or reverse file changes.
If you are using the service on behalf of an organization, you represent that you have the authority to bind that organization to these Terms.
2. Accounts and connected services
You are responsible for maintaining the security of your account and for the permissions you grant when connecting third-party services such as Google Drive.
You must only connect folders, files, and accounts that you are authorized to access and manage. You are also responsible for reviewing your folder settings, approval rules, and automation settings on an ongoing basis.
3. AI suggestions, approvals, and user responsibility
AI Renamer can generate suggestions based on file metadata and document context, but AI output may be incomplete, incorrect, or unsuitable for a given workflow. You are responsible for determining whether to approve, reject, or auto-apply rename actions.
For sensitive documents, regulated records, or mission-critical workflows, you should keep human approval steps in place until you are satisfied that your rules and provider settings behave as expected.
4. Acceptable use
You may not use the service to violate the rights of others, bypass security controls, process data without authorization, interfere with the service, or submit unlawful, abusive, or infringing content.
You may not probe, scrape, reverse engineer, or misuse the product in a way that harms the operator, the infrastructure providers, or other users.
5. Fees, pilots, and plan changes
Some deployments may offer free pilots, paid plans, or custom enterprise arrangements. If you purchase a paid plan, you agree to the pricing, usage limits, billing terms, and renewal rules presented at the time of purchase or in a separate order form.
The operator may change plans, packaging, or feature availability over time, including introducing or retiring limits related to folders, files processed, retention, or provider options.
6. Intellectual property and feedback
The service, including its software, branding, and site content, is protected by applicable intellectual property laws. These Terms do not transfer ownership of the service or any underlying software to you.
If you provide feedback, suggestions, or requested feature ideas, the operator may use that feedback without restriction unless a separate written agreement says otherwise.
7. Availability, suspension, and termination
The operator may modify, suspend, or discontinue the service, in whole or in part, including features related to connected integrations, AI providers, or background processing.
The operator may suspend or terminate access if these Terms are violated, if the service is being misused, or if continued access creates legal, security, or operational risk.
8. Disclaimers and limitation of liability
The service is provided on an "as is" and "as available" basis to the maximum extent permitted by law. The operator does not guarantee uninterrupted availability, error-free output, or that any rename suggestion will be accurate for your specific workflow.
To the maximum extent permitted by law, the operator will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, data, or goodwill arising from your use of the service.
9. Deployment-specific terms
If this codebase is deployed by a third party or customized for a private environment, that deployment operator may publish additional order forms, security commitments, support terms, or jurisdiction-specific notices that supplement these Terms.
Where a separate written agreement conflicts with these Terms, the separate agreement will control for the covered subject matter.