Peerless AI · Peerless Automations

Privacy policy

Effective September 16, 2026

This policy describes how Peerless AI ("Peerless," "we," or "us") handles information through peerlessintegrations.com and our client integration application, Peerless Automations. It covers our website inquiries and client-authorized integrations, including Google Drive and Google Sheets. A client's separate privacy notice may also apply to information that client asks us to process.

Information we collect and access

• Website inquiries: the name, company, email address, phone number, website, workflow details, timing, tools, and messages you submit through our automation-audit form or send to us directly.
• Website delivery: standard server logs may contain your IP address, requested URL, browser information, and request time. Our homepage loads fonts from Google Fonts; the font provider receives connection information when your browser requests them.
• Connected accounts: authorization tokens and connection identifiers needed to run an integration, plus file identifiers, names, contents, spreadsheet cells, and related metadata within the access you approve.
• Automation records: inputs and outputs needed for the agreed workflow, reports, snapshots, change comparisons, run status, and error information. Trademark monitoring also uses publicly available USPTO records.

Google Drive and Sheets access

Peerless Automations requests Google's drive.file permission for its Drive and Sheets connection. This enables it to create files and read or update files created by the app or explicitly selected for use with it. It does not grant general access to every file in your Google Drive. We do not request your Google password.

For an authorized reporting workflow, we use this access to create report folders and spreadsheets, save source exports and snapshots, compare records over time, and update reports with changes and source links. Data is processed only for the connected features and workflow you authorize. Additional integrations or permissions require separate authorization.

How we use information

We use information to respond to inquiries, scope and deliver services, operate authorized automations, maintain account connections, troubleshoot failures, secure the service, and meet applicable legal obligations. Workflow notifications are sent to the destinations configured for that client, such as a designated Slack channel.

Google data limits: we do not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. Human access is limited to what is permitted by Google's policy, such as with your affirmative agreement to help resolve a specific issue, for security purposes, or where required by law. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Service providers and sharing

Providers process information needed to deliver the relevant service. Our website runs on DigitalOcean, and its inquiry form uses FormSubmit to deliver requests by email. For connected automations, Nango manages account authorization and tokens, Trigger.dev runs tasks and operational logs, and Google Drive and Sheets store client reports. Browserbase may collect public source records in a cloud browser. Slack receives report or change information only when configured as a workflow destination.

We limit sharing to operating the requested service, authorized client recipients, and disclosures necessary to meet legal obligations or protect security. The trademark-monitoring workflow does not require sending Google file contents to a generative AI model. Any separate AI-enabled workflow must have its data use explained and authorized for that purpose. Providers may process information in countries other than yours.

Storage, retention, and security

Report files and snapshots may remain in the client's Google Drive until the client deletes them. Connection credentials are managed separately from report files through the authorization service. Workflow platforms may retain execution records and logs for their configured retention periods.

We retain information as needed to provide the agreed service, investigate operational issues, and meet legal or contractual obligations. Retention varies by the type of information and the client arrangement; this policy does not promise a fixed automatic deletion period. We use access controls and secure connections to protect information, but no system can guarantee absolute security.

Your choices, revocation, and deletion

You can revoke Google access through your Google Account connections settings. Revocation stops future access through that authorization; it does not automatically delete files already created in your Drive, prior reports, or retained operational records.

To disconnect an integration, request access to or correction of your information, or request deletion of information we retain, email thomas@peerlessintegrations.com. Identify the account or organization and the data involved; do not send passwords or API keys. We may verify your authority before acting. We will explain any records that must be retained for legal obligations or that remain under a client's control. You can also delete app-created files directly in your own Drive.

Changes and contact

We may update this policy as services change. The effective date above identifies the current version. Material changes to how a connected workflow uses data will be communicated as appropriate before that new use.

Questions about privacy or your information: thomas@peerlessintegrations.com.