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.

Geocode

Geocode API

The purpose of this first endpoint is to return geographic coordinates from a full or partial address.

To make a request to the Geocode API, you must send the request using the POST method to the following endpoint: 

Note: Currently returning only to directions located in Brazil.

The Geocode API has been updated to V2. The endpoint https://api.maplink.global/geocode/v1/geocode will still work, but it is recommended to use the new endpoint for more accurate results and because new features will be exclusive to the new version.

List of parameters

Mandatory parameters

It is mandatory to provide at least one. It is not necessary to provide all of them. However, the more information provided, the more accurate the result will be.

  • road – Street name or part of it;
  • number – Address number. DO NOT provide the additional information.
  • city -City name;
  • state – State;
  • country – Country;
  • district – District name;
  • zipcode – Zip code;
  • label – Complete address. It is recommended to type the text in the order “Street name, number, zip code, district, city, state”.

Note: There is a limit of 200 points for sending in a single request.

Optional parameters

  • mainLocation – Object with two parameters to limit the address search area:
    • center – Object with the reference coordinates for the search results. The coordinates can be entered in the following formats:
      • Object with the lat and lon properties that represent latitude and longitude respectively. Example: {"lat":-23.0852, "lon": -46.98020}
      • Array with latitude and longitude. Example: [-23.0852,  -46.98020]
      • Coordinates encoded as geohash. Example: "6tr6df675"
    • radius – Search radius, in meters, from the central point defined in center. If not entered, the default value is 500,000 meters (500 km).
  • limit – Limits the number of results returned. It is a query param, informed in the URL itself. For example: https://api.maplink.global/geocode/v2/geocode?limit=1

Example 1 – Search for coordinates from address

In the following example, we will request the coordinates for the address “Alameda Campinas, 579, São Paulo – SP, CEP 01404-100”. The full request is below:

{
    "road": "Alameda Campinas",
    "number": 579,
    "city": "São Paulo",
    "state": "SP",
    "zipcode": "01404000"
}

The query could also be made using the parameter label, as shown in the example below:

{
    "label": "Alameda Campinas, 579, 01404000, São Paulo,SP ",
    "city": "São Paulo",
    "state": "SP",
    "zipcode": "01404000"
}

In both cases, the following information is returned in the response:

  • found – Number of records returned.
  • results – Array of objects with all the results found:
    • id – Address identifier provided in the request;
    • address – Object with address information:
      • road – Name of the road;
      • district – District;
      • zipCode – Zipcode;
      • city – City;
      • state – State;
      • mainLocation – Object with the geographic coordinates of the point:
        • lat – Latitude;
        • lon – Longitude;
      • numberAsInteger – Address number, but returned as an integer instead of a string;
    • type – Indicates the best element found in the cartographic database for returning the geographic coordinate;
    • score – Reference score of the result of the geocoding process;
    • label – Complete address found used in the geocoding process.

The full response can be found below:

{
    "found": 1,
    "results": [
        {
            "id": "6684353bf0662a1541ff635d",
            "address": {
                "road": "ALAMEDA CAMPINAS",
                "number": "579",
                "district": "JARDIM PAULISTA",
                "zipCode": "01404000",
                "city": "SÃO PAULO",
                "state": {
                    "name": "SÃO PAULO",
                    "code": "SP"
                },
                "mainLocation": {
                    "lat": -23.566329468025202,
                    "lon": -46.653621381930805
                },
                "numberAsInteger": 579
            },
            "type": "ROAD",
            "label": "ALAMEDA CAMPINAS, 01404000, JARDIM PAULISTA, SÃO PAULO, SP",
            "score": 100.0
        }
    ]

Note: The higher the score, the greater the relevance of the result for the requested address. For example, if the request has all the address elements filled in and they were found in the cartographic database, a higher score is expected. If the request only has a zip code, for example, the score will be lower.

Example 2 – Search for coordinates from zip code

In this example, we will make a request informing only the zip code 01014-000:

{
    "zipcode": "01014000"
}

The full response can be found below:

{
    "found": 1,
    "results": [
        {
            "id": "66843498f0662a1541f9c308",
            "address": {
                "road": "RUA BOA VISTA",
                "district": "CENTRO",
                "zipCode": "01014000",
                "city": "SÃO PAULO",
                "state": {
                    "name": "SÃO PAULO",
                    "code": "SP"
                },
                "mainLocation": {
                    "lat": -23.54685803583,
                    "lon": -46.63338712495
                }
            },
            "type": "ROAD",
            "label": "RUA BOA VISTA, 01014000, CENTRO, SÃO PAULO, SP",
            "score": 100.0
        }
    ]
}