Privacy Policy

Information we handle

• Account information: your name, email address, verification status and account settings. If you use a password, the portal stores a password verifier. If you sign in with Google, we use your Google account identifier and verified profile information to identify your account; we do not receive your Google password.
• API and subscription information: API keys and labels, key status, request counts, plan limits, subscription periods and billing references. These records allow us to authenticate requests and apply shared quotas across your keys.
• Geocoding requests: addresses, coordinates and other query parameters you send are processed by the gateway and geocoding service to return results. Requests may contain personal or precise location information. Send only information you are entitled to use, and avoid sensitive information that is unnecessary for geocoding.
• Support information: the name, reply email, topic and message you submit through the contact form or email. Do not include API keys, passwords, verification links or payment card details.
• Technical information: IP addresses, browser and device information, timestamps, request/error information, cookies and security-check results handled by the website, hosting and security services. Operational logs may contain request metadata or query information depending on the service and hosting configuration.

Why we use this information

We use information to provide the service you request, sign you in, verify accounts, process geocoding requests, measure usage, manage subscriptions, respond to support enquiries and investigate errors, misuse or unauthorized access. Billing records may also be needed for accounting and legal obligations.

Where applicable law requires a lawful basis, the relevant basis depends on the activity: providing a requested service or contract, meeting legal obligations, protecting and operating the service through legitimate interests, or consent where required for an optional feature.

Cookies and external services

The portal uses session and authentication cookies for sign-in, security and form protection. A normal sign-in lasts up to 8 hours and uses a browser-session cookie. If you choose Remember me, the sign-in cookie can last up to 30 days. Blocking these cookies may prevent account features from working.

• Google: optional Google sign-in processes identity information. Google Fonts and hosted assets may receive browser requests when the website loads. See Google’s Privacy Policy.
• Cloudflare: hosting-edge protection and Turnstile security checks process technical information to detect abuse. Website measurement may also be provided where enabled. See Cloudflare’s Privacy Policy.
• Stripe: payment details are entered on Stripe-hosted pages. The portal retains customer, subscription, payment status and invoice references; it does not receive your full card number or card security code. See Stripe’s Privacy Policy.
• Maps and infrastructure: map tiles, hosted libraries, website hosting and email providers process the requests needed to deliver those services. Map providers can receive information about the map area you view, as well as normal browser-request information. OpenStreetMap resources are covered by the OSMF Privacy Policy.

External providers operate under their own terms and privacy notices. Their processing locations may differ from your country. Where applicable, international processing must be handled with the safeguards required by relevant privacy law.

Sharing and access

Information is used by authorized operators and service providers as needed to deliver, secure and support Geocoding.info. Administrative actions can be recorded for accountability. We may disclose information where legally required or necessary to investigate misuse and protect the service or other users. API keys are credentials: keep them private and revoke a key if it may have been exposed.

How long information is kept

Account and subscription records are retained while needed to operate the account and service. Usage and security records are retained according to operational, abuse-prevention and support needs. Support correspondence is retained while needed to handle the enquiry and related follow-up. Billing and audit records may need to be kept longer for accounting, legal obligations or disputes. Retention decisions take account of the purpose, sensitivity, legal requirements and whether the information is still needed; backup copies may remain until the relevant backup is replaced.

Your choices and privacy requests

You can choose whether to use Google sign-in, manage your API keys in the dashboard and cancel subscription renewal through billing. Revoking a key or cancelling renewal does not itself delete account or billing records. Accounts without Stripe billing records can be deleted from Account settings after identity confirmation. This removes profile and sign-in details and revokes API keys; usage and security records may remain under an internal account ID. For Stripe-linked accounts, contact support so billing and retention requirements can be reviewed before deletion.

To request access, correction, deletion or other privacy assistance, contact [email protected] from the email associated with your account where possible. We may verify your identity before acting. Available rights and exceptions depend on applicable law; some information may need to be retained for security, accounting or legal reasons. You may also contact the relevant data-protection authority where that right applies.

Children and changes to this notice

Geocoding.info is intended for developer and business use and is not directed at children. Contact us if you believe a child has provided personal information through the service.

We may update this notice when the service or its data practices change. The date above identifies the latest version.