Privacy Policy
Effective 15 August 2026
Who we are
GeoInsight is a terrain and sky-condition API. The controller of your personal data is:
- I2S soft
- al. Wojska Polskiego 29/4, 70-473 Szczecin, Poland
- VAT ID: PL8511617243
- Data protection contact: privacy@geoinsight.dev
This policy explains what we collect, why, and what you can do about it. It covers the GeoInsight website, dashboard and API.
What we do not collect
It is easier to start here, because for a geospatial service these absences matter:
- We do not store the coordinates you query. When you ask for the elevation, horizon or timezone at a location, we compute the answer and return it. The coordinates are not written to our database. Our usage records hold only which account made how many billable units of calls on which day — never where you asked about.
- We use no analytics and no tracking. There is no Google Analytics, no Plausible, no Matomo, no advertising pixel and no third-party script of any kind on our pages.
- We do not sell or share your data with advertisers or data brokers, and we do not use it to train machine-learning models.
- We never see your full card number. Payments are handled entirely by Stripe on Stripe's own pages.
- We do not send personal data to our error-tracking tool. Sentry is configured to suppress personally identifiable information in both our API and our terrain service.
What we collect and why
Account data
Your name, email address and a cryptographic hash of your password — never the password itself. We record whether you have verified your email. We need this to create your account, authenticate you and contact you about the service.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Checking your password against known breaches
When you set or change a password, we check it against the Have I Been Pwned database of breached credentials and refuse passwords that appear there. The check uses k-anonymity: we compute a SHA-1 hash of your password, send only the first five characters of that hash, and compare the returned list locally. Your password never leaves our server, and neither does its full hash.
Legal basis: our legitimate interest in protecting accounts from credential-stuffing attacks (Art. 6(1)(f) GDPR).
Billing data
When you buy credits, Stripe collects your billing address and, for businesses, your VAT ID, so that tax can be applied correctly. We store a reference to your Stripe customer record, the card type and the last four digits, and a record of each purchase: which package, how many credits, and the Stripe session identifier.
Legal basis: performance of a contract, and a legal obligation to retain accounting records (Art. 6(1)(b) and (c) GDPR).
API keys and usage
We store your API keys in hashed form together with a short non-secret prefix, so you can recognise a key in your dashboard. We count how many billable units your account consumes per day, and we keep short-lived counters for the hourly, daily and weekly rate-limit windows.
Legal basis: performance of a contract, and our legitimate interest in enforcing limits and preventing abuse (Art. 6(1)(b) and (f) GDPR).
Technical logs and error reports
Our servers keep standard operational logs, which can include IP addresses, timestamps and the endpoint that was called. If something breaks, an error report is sent to our error-tracking provider with the technical details of the failure, configured to exclude personal data.
Legal basis: our legitimate interest in keeping the service secure and working (Art. 6(1)(f) GDPR).
Who else processes your data
We keep the list short on purpose. Each of these acts as our processor under a data processing agreement:
| Provider | Purpose | What they receive |
|---|---|---|
| Stripe | Payments and tax | Name, email, billing address, VAT ID, payment details |
| Sentry | Error tracking | Technical error details; personal data suppressed by configuration |
| Email provider | Verification and password-reset messages | Your email address and the message content |
| Hosting provider | Running the service | Everything stored by the service, as infrastructure |
Our terrain and light-pollution data comes from public scientific datasets. Retrieving it involves no personal data — we ask a public data source for a piece of the map, not for anything about you.
Transfers outside the EEA
Some of our providers, including Stripe and Sentry, operate infrastructure in the United States. Where personal data is transferred outside the European Economic Area, the transfer relies on the European Commission's Standard Contractual Clauses, together with the technical measures described in this policy. You can request a copy of the relevant safeguards from the contact address above.
How long we keep it
| Data | Retention |
|---|---|
| Account details and API keys | until you delete your account |
| Purchase and invoice records | 5 years from the end of the tax year in which the purchase was made |
| Daily usage counts | 24 months |
| Error reports | 90 days |
| Login sessions | 2 hours of inactivity, or until you log out |
Purchase records outlive account deletion because tax law requires us to keep them. Everything else tied to your account goes when the account does.
Your rights
Under the GDPR you can ask us to:
- give you a copy of the personal data we hold about you;
- correct anything inaccurate;
- delete your data, subject to records we must keep by law;
- restrict or object to processing based on our legitimate interests;
- export your data in a portable, machine-readable form;
- withdraw any consent you have given, without affecting processing that already happened.
Write to privacy@geoinsight.dev and we will respond within one month. If you think we have handled your data badly, you can complain to the President of the Personal Data Protection Office (UODO), Poland — see https://uodo.gov.pl/.
Security
Passwords are stored only as hashes. API keys are stored hashed too, which is why we can show a secret exactly once, when it is created, and never again. Traffic is served over HTTPS. Access to production data is limited to people who need it to run the service.
No system is perfectly secure. If we ever discover a breach that puts your rights at risk, we will notify the supervisory authority and, where required, you.
Cookies
We set two strictly necessary cookies and nothing else. The Cookie Policy lists them and explains why no consent banner is required.
Changes to this policy
If we change how we handle your data, we will update this page and move the effective date at the top. For changes that materially affect you, we will email account holders rather than rely on you noticing.