emploidai Marketplace

emploidai Marketplace

Geo Encoder Decoder privacy policy

Policy content supplied in the product package by its publisher.

← Back to Geo Encoder Decoder

Privacy Policy for Geo Encoder Decoder Dify Plugin

This Privacy Policy explains how the Geo Encoder Decoder Plugin ("the Plugin") collects, uses, and handles your information when used within the Dify platform.

1. Information We Handle

a. User-Provided Geolocation Data

The Plugin allows you to:

  • Convert an address to geographic coordinates (geocoding)
  • Convert coordinates to a human-readable address (reverse geocoding)

You may provide the following:

  • A location string (e.g., "New York City")
  • A latitude and longitude pair (e.g., 40.7128, -74.0060)

This data is used solely to call the OpenCage Geocoding API. The Plugin does not persist or log this information.

b. API Response Data

The Plugin returns the data received from the OpenCage API, which may include:

  • Coordinates or address data
  • Confidence score and formatted results
  • Metadata such as timezone or country

This response is processed in-memory and returned directly to the Dify interface. No data is stored.

c. Usage Data

General usage metrics (e.g., how often each tool is used) may be collected by the Dify platform as part of its standard analytics practices. This is governed by Dify’s Privacy Policy.

2. How We Use Your Information

  • Input Data: Used only to query the OpenCage API as requested by the user.
  • Output Data: Returned as-is from the OpenCage API. The Plugin does not manipulate or store the response.

3. Data Storage

This Plugin does not store any information.

  • All request/response flows are handled in-memory.
  • No database or external storage is used.

4. Third-Party Services

This Plugin sends requests to the OpenCage Geocoding API.

You are responsible for complying with OpenCage’s Privacy Policy when using their service through this Plugin.

5. Your Choices

You control all input into the Plugin:

  • No API key is stored within the plugin — it must be provided via environment variable (OPENCAGE_API_KEY).
  • You may stop using the Plugin at any time without any residual data being stored.

6. Changes to This Policy

We may update this Privacy Policy as the Plugin evolves. Any updates will be reflected in this document or the plugin description.

7. Contact Us

If you have questions about this privacy policy, please contact the plugin author:
Ayush3941 / geo_encoder_decoder