ouRGeo · Effective date: August 17, 2026
This policy covers two separate things: the ouRGeo desktop application, and this website and its community forum. They are independent — the application works fully without an account, and nothing you do in the application is ever sent to this website.
ouRGeo collects no personal data. The application runs entirely on your local machine — there is no analytics, no telemetry, no crash reporting, and no cloud component. There is no infrastructure that could receive or store information about you, even if we wanted it to.
All R code, geoprocessing operations, and map rendering happen on your machine. ouRGeo bundles a
local R server that listens only on localhost, used to communicate between the desktop
UI and the R session running on your computer. No data is sent to a remote server by default.
ouRGeo reads and writes only the files you explicitly open or save through the application — for example, when you load a Shapefile, save a project, or export a GeoPackage. There is no background scanning, indexing, or uploading of files.
A default install of ouRGeo makes no outbound network calls. Some optional features do reach the internet — but only when you choose to use them, and only to the destination you pick:
Basemaps. If you display a public basemap (such as OpenStreetMap), your computer requests map tiles directly from that public tile server, the same way a web browser would. You can disable basemaps and work fully offline.
Data Connector. When you import from a public data source (Esri, WFS, STAC, Socrata, and similar), ouRGeo contacts that server directly to fetch the data you requested. It talks to no one else.
AI assistant. The in-app AI agent is optional. If you configure a cloud provider, your prompts and the context you share are sent to that provider under their terms. If you instead point it at a local model (for example via Ollama or LM Studio), the assistant runs entirely on your machine and nothing leaves your computer. The choice is yours.
Browsing this website requires no account and sets no tracking or advertising cookies. There is no analytics on these pages.
Creating a community account is optional, and only needed to post in the forum. When you create one we store:
Your email address, used to sign you in, verify the account, and reset a forgotten
password. It is never shown publicly and never sold or shared.
Your profile — display name, username, and anything you choose to add such as a bio,
location, website, or avatar. This is public by design; it appears next to your posts.
Your posts and replies, which are public and readable by anyone, including people who
are not signed in and search engines.
Your newsletter preference, and the date you last changed it.
If you sign in with Google or GitHub, we receive your email address, your name, and your profile picture from that provider so the account can be created. We ask for nothing beyond that, and we never gain access to your account with them.
Accounts and forum content are stored by Supabase, which hosts the database and handles authentication on our behalf. Like any web host, Supabase and our web host process technical connection information such as IP addresses and timestamps in order to serve requests and to stop abuse. We do not use that information to build any profile of you.
The newsletter is strictly opt-in. It is off unless you switch it on, and you can switch it off again at any time from your account page — the change takes effect immediately. Turning it off does not stop essential account emails such as password resets.
Your account and posts are kept until you ask us to remove them. You can edit or delete your own posts at any time, and you can request deletion of your whole account — profile, discussions, and replies — from your account page or by emailing the address below. Removed posts are hidden immediately and purged thereafter; copies may persist in database backups for a short period before those expire.
Moderators can see a log of moderation actions taken on content, which is kept so that moderation decisions can be reviewed.
Neither the application nor this website integrates any third-party analytics, advertising, crash-reporting, or tracking SDKs. In the application, the only third parties your machine ever contacts are the basemap, data, or AI providers you explicitly choose to use. On this website, the only third parties are Supabase (accounts and forum data, described above), Google Fonts and jsDelivr for page assets, and — if you use them — the sign-in provider you pick. Nothing is shared with anyone else under any circumstances.
ouRGeo is released under the GNU Affero General Public License v3, and the source code is published at github.com/CCurtis1988/ouRGeo. The source is the ultimate proof of these claims — anyone is free to read, audit, modify or redistribute it, and the AGPL guarantees those freedoms survive in anyone else’s version too.
If this policy ever changes — for instance, if a future version of ouRGeo adds optional cloud sync or remote collaboration features — the updated policy will be posted here and the effective date will be updated accordingly. Such features would always be opt-in.
Questions or concerns about ouRGeo? Reach out to cmcurtis1988@gmail.com.