↑

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.

Planning

Error messages – Planning

The following table shows all the error messages that can be returned by the API in the response body:

Error codeMessageDescription
VALIDATION_FAILED or VALIDATION_ERROR{ message: "", errors: [ ] }Simple validation errors. The errors array contains the detailed message for each field containing an invalid value (example: "startDate is mandatory" indicates that this field is mandatory but has not been entered).
MESSAGE_FORMAT_ERROR–The request json has errors and could not be processed.
PROFILE_NOT_FOUNDError checking trip profile with name {tripProfileName}The tripProfile with the specified name does not exist.
PROBLEM_NOT_FOUND–The problem with the specified id was not found.
SOLUTION_NOT_FOUND–The solution with the specified id was not found.
INVALID_SITE_POSITIONSome sites have not been positionnedSome of the sites have coordinates that could not be connected to a nearby road.
NO_PROJECTIONNo projection retrieved to send to route plannerSimilar to the error INVALID_SITE_POSITION, it has the same root cause, but can also occur occasionally when one of the internal services is unavailable.
EMPTY_RESTRICTION_ZONEThe name of restriction zones are invalid or the calculation of blocked arcs was not completed yet.One or more of the restriction zones reported do not exist (or have just been registered and have not yet been processed).
NO_COORDINATESNo coordinates found for arcs in mapSome of the sites were passed on without coordinates, or with incomplete coordinates.
INVALID_CALLBACK_URL_FORMAT{callbackValue} does not have a valid value. Example of allowed values: http://www.foo.br, https://www.foo.br…URL of callback entered does not have a valid format.
INVALID_TIME_WINDOWmust have the start less than or equal to the endA specified time window where the end time is earlier than the start time.
–Impossible to get optimization profileThe optimizationProfile with the specified name does not exist.
ax.rp.errXXX–Problems occurring in the route planner, usually linked to inconsistencies in the map used, occasionally due to instabilities. XXX is the numerical error code.
ax.rp.err113Not possible to create route between site A and BThe route planner has not found a path from point A to point B. Example of a case: Point A is a one-way dead-end road.
Table of possible error messages returned by the API