Legal
Privacy policy
What GIS Labs collects through this website and your account, why, and what you can ask us to do about it.
Last updated
Issued by GIS Labs LLC, Wyoming, United States
What this covers
Your spatial data never reaches us
If you are assessing us as a processor of your GIS data: we are not one. You remain both controller and processor of that data, because it never leaves your infrastructure, unless your administrator enables AI assist (optional, off by default) with an external provider (and then only the request that feature makes goes to it). We are happy to state that in writing for a procurement file.
What we collect
| Category | Fields |
|---|---|
| Account | Name, work email, organisation, and optionally job title, country and phone. Your password is stored only as a slow one-way hash — we cannot read it. |
| Licences | Licence keys, tier, seat count, the hardware fingerprints and host names of machines you activate, and the machine request (.gdr) file and signed licence (.gdl) kept for each, stored encrypted. A fingerprint is a hash of machine identifiers; it contains no personal data and does not identify a person. A host name is the name your administrator gave the computer, and can identify a person if it contains theirs. |
| Orders | What you bought, when, and the amount, from an invoice or a purchase order. Licences are not sold online, so no card details reach us; if online payment is ever switched on, they are handled by the payment provider and never reach our servers. |
| Enquiries | What you send us through a form or by email, and our replies. This includes the evaluation requests you make. |
| Security log | Sign-ins, password changes, licence actions and administrative actions, with the originating IP address and timestamp. |
We do not buy personal data, we do not build advertising profiles, and we do not use your details for anything you did not come here to do.
Why we collect it
- To provide the service you asked for — running your account, issuing licences, delivering downloads, answering your questions.
- To meet a legal obligation — keeping order records for the period tax law requires.
- To keep accounts secure — the security log exists so that a compromised account can be investigated. This is a legitimate interest, and we have kept the log to the minimum that makes it useful.
- With your consent — product updates by email, only if you asked for them, and withdrawable in one click.
Cookies
There is no cookie banner because there is nothing to consent to. We set three cookies, only when you sign in, and store one preference:
__Host-gd_session— your sign-in session. HttpOnly, Secure, SameSite=Lax, at most 12 hours (8 for administrators). Strictly necessary; without it you cannot stay signed in.__Host-gd_auth— holds only the value 1, so the page header can show “Account” instead of “Sign in”. It carries no identity and grants no access.__Secure-gd_mfa— for five minutes between your password and your two-step code. HttpOnly, sent only to the sign-in address.gd-theme— your light/dark preference, in browser local storage rather than a cookie. Never sent to us.
No analytics, no advertising trackers, no session recording, no fingerprinting. Two third-party scripts load, each on named pages only: Cloudflare Turnstile on the four forms below (creating an account, requesting an evaluation, contacting us, resetting a password), and the payment provider's (Paddle) checkout on the payment page, which exists only if online sales are switched on; they are off. Every other page runs only our own code.
How long we keep it
- Account details — while your account is open, then deleted on request.
- Licence records — for the licence term plus 12 months afterwards, so a renewal or a dispute can be resolved.
- Order records — 10 years from the order, as tax law requires.
- Security log — 24 months, then deleted.
- Web server logs — the address, page, browser and time of each request, kept 30 days to find faults and abuse, then deleted. Licence keys, request signatures and the one-time token of a sign-in or reset link are removed before the line is written.
- Backups — nightly and encrypted, kept 30 days, then deleted. Data deleted from the site leaves the backups within that time.
- Enquiries and evaluation requests — from an address with no account, 24 months from the request, then deleted. From an account, they go when the account is deleted.
Who else sees it
Only the providers we need to run the service, and only what they need:
- Cloudflare — DNS, the TLS connection and the tunnel in front of this site, so every request passes through it (address, page, browser). Its Turnstile check on the four forms above reads signals from your browser to tell a person from a script.
- OVHcloud — hosting, in Frankfurt (EU). The server holds the account data described above, the logs and the backups.
- Zoho — email: delivers account and licence email, and holds our inbox.
- Paddle — payment, only if online sales are switched on (they are off). Paddle would handle card data; we never see it.
We do not sell or rent personal data, and we do not share it for advertising. We will disclose data if a valid legal order requires it, and will tell you unless prohibited from doing so.
Your rights
Depending on where you live you may have the right to access, correct, delete, restrict or object to our processing of your data, to receive a copy in a portable format, and to withdraw consent. We honour these requests wherever you are, rather than only where a statute compels us to.
In the portal, Account & security has Download my data, a copy of everything we hold about your account, and Delete my account. For anything else, email [email protected] and we will respond within one month. Deleting an account with an active licence ends that licence, so that one goes by email and we confirm before acting.
Security
- TLS on every connection to this site.
- Passwords stored as slow one-way hashes, never in a readable form.
- Sessions that can be revoked, and that a password change invalidates everywhere.
- Rate limiting and lockout on authentication.
- An audit log of account and licence actions.
If a breach affects your data we will tell you and any relevant regulator without undue delay, with what we know and what we are doing about it. To report a vulnerability, email [email protected] — see architecture.
Contact
GIS Labs LLC, Wyoming, United States is the controller for the data described here. Reach us at [email protected]. If you are not satisfied with our response you can complain to your local data-protection authority.
See also our terms of service.
Other legal documents
These documents are read together. Where a signed agreement with GIS Labs says something different, the signed agreement wins.
Questions about any of this — including redlines your legal team needs — go to [email protected].