Privacy Policy

1. Scope and roles

We handle personal data in two different situations:

• Data TAM receives directly. When you visit the site, fill in the contact form, write to us by email or WhatsApp, or are a contact person at a client company. In these cases TAM decides how the data is used and is responsible for it.
• Data TAM processes on behalf of a client company. When a company uses our platform or services, we may process data about its customers, suppliers or staff (for example, messages, orders or shipping documents). In that case we act on that company's instructions; the company is responsible for that data and for informing the people concerned.

If your data reached TAM through a client company, we recommend contacting that company first. If you contact us directly, we will help address your request.

2. Data we collect

Data you provide

• Contact form: name, email address, company, phone number, request type and the message you write.
• Communications: the content of emails or WhatsApp messages you send us and the related contact details.
• Forwarded documents: emails and attachments that client companies forward to TAM email addresses, such as shipping documents, which may include sender, recipient and shipment details.
• Clients: details of the client company's contact persons and of the users authorized to use the platform.

Technical data

Like most web services, our infrastructure may log technical data such as IP address, browser type, and the date and time of requests. We use it to operate the site, prevent abuse (for example, limiting repeated form submissions) and keep it secure.

The site currently does not set its own cookies or use third-party analytics or advertising tools. If this changes, we will update this policy.

Data processed for client companies

Depending on the features each company contracts and authorizes, we may process contact details, conversations and messages, orders, shipping documents, and other files or records needed for the configured automations.

3. How we use data

• To answer requests for information, demos or assessments.
• To provide, configure, maintain and support the platform and the contracted services.
• To run the automations and integrations the client company has configured and authorized.
• To protect the security of the site, the platform and our clients, and to prevent misuse.
• To comply with legal obligations and respond to requests from competent authorities.

We do not sell personal data or use it for targeted advertising.

4. Google and Gmail integration

We use a Gmail integration, authorized through OAuth, on email accounts belonging to the TAM team. We currently do not connect Google accounts of client companies or other people: client companies forward their documents to a TAM email address, and those emails are processed through this integration.

Google data we may access

• Email messages in the connected TAM accounts: content, senders, recipients, subject, date and other metadata. They may include data about client companies and about the people named in the documents they send us.
• Attachments to those messages.
• Gmail labels.
• The ability to send email from the connected account, when that feature is authorized.

How we use it

• To read and search the emails relevant to the configured workflow (for example, order or shipping messages).
• To download and process attachments, such as shipping documents, to extract the information the workflow needs.
• To create and apply labels to organize processed emails.
• To send emails when an authorized feature requires it, for example a confirmation or a reply.

We run these workflows with the n8n automation tool, self-hosted by TAM on our own Amazon Web Services infrastructure. Data from PDF shipping documents is currently extracted with TAM's own parser, without sending those documents to AI models. The resulting information is used in the TAM platform or in the systems the client company has designated.

Limited Use

TAM's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• We use Google data only to provide or improve the user-facing features that were authorized.
• We only transfer that data when necessary to provide those features, for security purposes, to comply with the law, or as part of a merger, acquisition or sale of assets with the user's prior consent.
• We do not use Google data for advertising, and we do not sell or transfer it to advertising platforms, data brokers or information resellers.
• We do not use Google data to determine creditworthiness or for lending purposes.
• We do not use Google data to create, train or improve generalized artificial intelligence or machine learning models.
• Only authorized members of our team access that data, and only when needed to handle the related request (for example, reviewing a document sent for processing), for security, or to comply with the law.

If another provider ever needs to receive data obtained from Google, we will first verify that its terms allow us to meet these commitments before enabling it.

Revocation and deletion

The owner of a connected Google account can remove access at any time from Third-party apps & services in their Google Account. If you sent us documents and want us to delete the data obtained from them, write to michaelballestero@theagenticmethod.io.

Google's use of your data is governed by the Google Privacy Policy.

5. Service providers and sharing

We share data only when needed to provide the service, with:

• Infrastructure providers, such as cloud hosting services (currently Amazon Web Services, where we also host our n8n instance).
• Providers of the integrations and channels we use or the client company chooses to use, such as Google (Gmail) or WhatsApp. Each handles data under its own policies.
• Other technical providers that may be needed for the contracted features, bound by confidentiality obligations and the restrictions in this policy.
• Authorities, when required by law.

Some providers may be located in, or store data in, countries other than yours. You can request the current list of providers by writing to our contact email.

6. Storage and protection

We apply reasonable technical and organizational measures, proportionate to the service, to protect data, such as encrypted connections (HTTPS) and access limited to the people and systems that need it to operate the service.

No system is completely secure. If we detect an incident affecting your data, we will act to contain it and notify the affected people or companies where appropriate.

7. Retention and deletion

We keep data only as long as needed for the purposes described, while the relationship with the client company is active, or as long as the law requires.

Data processed on behalf of a client company is kept or deleted as agreed with that company. When the service ends or an integration is revoked, we delete or anonymize data we no longer need, except data we must keep by law.

You can request deletion of your data at any time by writing to michaelballestero@theagenticmethod.io.

8. Your rights and requests

Depending on applicable law, you can request access to your data, its correction or deletion, object to certain uses, or withdraw consent you have given.

Send your request to michaelballestero@theagenticmethod.io. We may ask for information to verify your identity before acting on it. If we process your data on behalf of a client company, we will coordinate the response with that company.

9. Children

Our services are aimed at businesses and are not designed for minors. We do not knowingly collect data from minors through the site.

10. Changes to this policy

We may update this policy. We will publish the current version on this page with its update date. If a change involves using Google data in a new way, we will tell you and ask for the corresponding consent before applying it.

11. Contact

For privacy questions, requests about your data or support, write to michaelballestero@theagenticmethod.io.