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.

Toll

List of parameters

Mandatory parameters

The following parameters are required:

  • legs – Array with points and vehicleType to calculate tolls. Each leg represents a section of the route. If you want to calculate the toll for different vehicles on each part of the route, for example, you can divide it into several legs. (Only required for the independent endpoint)
    • points – Coordinates that make up the section of the route. The parameter points accepts coordinates as objects, arrays, encoded in geohash or encoded as polyline, as shown in the examples below.
    • vehicleType – Text defining the type of vehicle to be considered when calculating the toll. The possible values are:
      • MOTORCYCLE
      • CAR
      • CAR_WITH_THREE_SIMPLE_AXLES
      • CAR_WITH_FOUR_SIMPLE_AXLES
      • BUS_WITH_TWO_DOUBLE_AXLES
      • BUS_WITH_THREE_DOUBLE_AXLES
      • BUS_WITH_FOUR_DOUBLE_AXLES
      • BUS_WITH_FIVE_DOUBLE_AXLES
      • TRUCK_WITH_NINE_DOUBLE_AXLES
      • TRUCK_WITH_TWO_SINGLE_AXIS
      • TRUCK_WITH_TWO_DOUBLE_AXLES
      • TRUCK_WITH_THREE_DOUBLE_AXLES
      • TRUCK_WITH_FOUR_DOUBLE_AXLES
      • TRUCK_WITH_FIVE_DOUBLE_AXLES
      • TRUCK_WITH_SIX_DOUBLE_AXLES
      • TRUCK_WITH_SEVEN_DOUBLE_AXLES
      • TRUCK_WITH_EIGHT_DOUBLE_AXLES
      • TRUCK_WITH_TEN_DOUBLE_AXLES
    • calculationDate – Date and time at which the route will be performed, in timestamp format in milliseconds. Example: 1583492400000
    • condition – (Optional) Object that indicates which values ​​should be considered for tolls where there are conditional values, such as a discounted value for tagged vehicles or a specific value for holidays. The object is composed of:
      • billingType – Indicates the type of charge that should be considered. Possible values ​​are: [ TAG, NORMAL ];
      • period – Indicates the period that should be considered to return the exact toll value. Possible values ​​are: [ NORMAL, HOLIDAY, LOW_SEASON, HIGH_SEASON ].

Accepted coordinate formats

The following formats are supported as input for the coordinates in the parameter points:

Object – Objects composed of the parameters latitude and longitude:

"points": [
	{
		"latitude": -19.50489,
		"longitude": -57.43231 
	}
]

Array – Arrays containing latitude and longitude respectively:

"points": [
	[-19.50489,-57.43231],
]

Geohash – Strings with latitude and longitude encoded in geohash:

"points": [
	"6sx1j15pf",
]

Polyline – String with all route coordinates coded as polyline:

"points": "pp`vB|fp}IlAFhCI"

Example with mandatory parameters

{
    "legs": [
        {
            "points": [
                {
                    "latitude": -23.465395,
                    "longitude": -46.375007
                },
                {
                    "latitude": -23.465957,
                    "longitude": -46.371015
                },
                {
                    "latitude": -23.467154,
                    "longitude": -46.36559
                }
            ],
            "vehicleType": "TRUCK_WITH_TWO_DOUBLE_AXLES"
        }
    ]
}

Optional parameters

  • source – Indicates in which coordinate base the tolls should be consulted. Possible values ​​are:
    • MAPLINK – Default value if the parameter is not provided;
    • GMAPS – It should be used if the route provided was generated by Routes API from Google.
  • billing – Text indicating the type of toll charge. Possible values ​​are:
    • DEFAULT – This is the default value if the parameter is not informed and indicates that the conventional toll collection calculation will be used, that is, only conventional toll plazas and gantries will be returned;
    • FREE_FLOW – In addition to toll plazas and conventional gantries, gantries that are part of the PaP or Free Flow system, currently available on some highways, will also return.
  • transponderOperators – Only for routes in Brazil. Array that indicates which integration codes should be returned, in addition to the ANTT code that will always be returned. The possible values are:

Example with optional parameters

{
    "legs": [
        {
            "points": [
                {
                    "latitude": -23.465395,
                    "longitude": -46.375007
                },
                {
                    "latitude": -23.465957,
                    "longitude": -46.371015
                },
                {
                    "latitude": -23.467154,
                    "longitude": -46.36559
                }
            ],
            "vehicleType": "TRUCK_WITH_TWO_DOUBLE_AXLES",
            "calculationDate": 1710769071000,
            "condition":{
                "billingType":"TAG",
                "period":"HOLIDAY"
            }
        }
    ],
    "billing": "DEFAULT",
    "transponderOperators": [
        "CONECTCAR",
        "SEM_PARAR"
    ],
    "source": "MAPLINK"
}