Privacy Policy

1. Introduction

This Privacy Policy describes how we collect, use, and protect your personal information when you use our chatbot, which interacts with the Gemini AI API and stores your questions in our database.

2. Information Collected

When using our chatbot, we collect the following types of information:

  • Conversation Information: All messages you send and receive through the chatbot.
  • Identification Data: We may collect data such as IP address and geographic location information.

3. Use of Information

The information collected is used for the following purposes:

  • Interaction with the AI API: Your messages are sent to the Gemini API to generate appropriate responses.
  • Question Storage: Your questions are stored in our database for analysis and service improvement purposes.

4. Information Sharing

We do not share your personal information with third parties, except in the following cases:

  • Service Providers: We may share information with vendors who help us operate our service, such as the Gemini API.
  • Legal Compliance: We may disclose information to comply with legal obligations or respond to legal processes.

5. Information Security

We implement appropriate security measures to protect your information from unauthorized access, alteration, disclosure, or destruction. These measures include:

  • Encryption: Use of encryption to protect data in transit.
  • Restricted Access: Access to information is limited to employees and partners who need this information to operate our service.

6. Your Rights

You have the right to:

  • Access and Correct: Request access to your personal information and correct inaccurate data.
  • Delete Data: Request the deletion of your personal information, subject to certain conditions.
  • Withdraw Consent: Withdraw your consent to the processing of your personal information.

7. Changes to the Privacy Policy

We reserve the right to update this Privacy Policy at any time. We will notify you of any significant changes through our website or other appropriate communication channels.

8. Contact

If you have any questions about this Privacy Policy, please contact us at [email protected]

9. Consent

By using our service, you agree to the collection and use of your information as described in this Privacy Policy.

This Privacy Policy has been created to ensure that your personal information is treated with security and respect. We appreciate your trust and are committed to protecting your privacy.

Trip

Storing routes with Route Storage

Route Storage is a new feature that can be used in conjunction with the Trip API to store fixed route solutions for longer.

By default, routes are stored for 7 days. With Route Storage, this period can be extended to 5 years. This new feature has been developed especially for companies that work with fixed routes, due to risk management contracts with their insurers, for example.

Factors such as map updates, new roads or paving of existing roads can cause the route to change from time to time. But with Route Storage, the stored route will always remain the same, without any changes.

Main features

  • Storage of the route with a date specified by the client, with a limit of up to 5 years;
  • Guarantee that stored routes will not change;
  • Performance gains, because once the solution is cached, it won’t be necessary to resend the request, reducing response times.

To use the feature, simply enter the expiryIn parameter with the date in timestamp format of when the route should be stored.

After that, the route ID can be queried normally via the endpoint https://api.maplink.global/trip/v1/solutions/{tripid}

There’s no need to send the route again, just use the generated ID.

Changing and deleting stored routes

If you need to change the storage end date or delete a route, this is done via our support channels.

Just send us an email to [email protected], including the route ID to be edited and the clientID used to generate the route.

Example – Storing and querying routes with Route Storage

In this example we have a route between São Paulo and Campinas, where we have added the parameter expiryIn with the date 31/08/2025, in timestamp format.

{
    "calculationMode": "THE_FASTEST",
    "points": [
        {
            "latitude": -23.580581,
            "longitude": -46.656743,
            "siteId": "SP"
        },
        {
            "latitude": -22.893165,
            "longitude": -47.064792,
            "siteId": "CAMPINAS"
        }
    ],
    "expiryIn": 1756648905000,
}

The route ID will be returned in the response and can be consulted normally until 31/08/2025 on the endpoint https://api.maplink.global/trip/v1/solutions/{tripid}