Privacy Policy

Who we are

Robota LLC operates RoboGNSS, a hosted GNSS correction management service available at robognss.com and app.robognss.com: an NTRIP caster, stream health monitoring, and related services. Our postal address is 5015 Voyager Dr #7, Dallas, TX 75237, United States.

Information we collect

• Account information. Sign-in is handled by Clerk (clerk.com), our authentication provider. We receive your name, email address, and a unique account identifier. We never see your password.
• Base station data. The information you configure for each source: name, mountpoint, declared coordinates, reference frame, and station ID, plus the coordinates your receiver broadcasts inside its correction stream.
• Base stream information. We collect connection times, client IP addresses where available, client software names, data volumes and message statistics to operate and monitor base station streams.
• Rover data.The caster can record what rovers send: NMEA sentence counts, fix quality and positions, including tracks. It can also record connection times, the client IP address where available, client software names and data volumes. The base owner decides, for each rover login, whether rover data is recorded and displayed. Rover history and tracks are available only through the base owner’s account, including apps the owner authorizes. They are not public. Track recording and maps require Pro or above.
• Correction data. RTCM correction streams pass through our caster transiently to connected rovers. If you enable archiving, raw observations are stored for your retention period and are accessible only to your account.
• Usage analytics. We use PostHog (posthog.com) to count page views and basic interactions on our website and dashboard, so we can see which pages are useful. PostHog receives your IP address, your browser and the pages you view, and stores a cookie and a browser storage entry so that return visits are counted once. We do not send it your name or email address, and we do not use it for advertising. A tracker-blocking browser extension stops it; nothing on the service depends on it.
• Uploaded files. Files you submit to the RINEX converter are held only for the seconds the conversion takes and are deleted immediately afterward — never stored, inspected, or shared. The other free tools process files entirely on your device; nothing is uploaded.

How we use it

• To operate the service: relaying streams, showing health, enforcing access control.
• To detect abuse, including rebroadcast of licensed correction data that is not yours.
• To communicate service and account notices.
• For billing, when you subscribe to a paid plan.

We do not sell your data or use it for advertising.

Third parties we rely on

• Clerk — authentication and account management.
• Hosting providers — run the service and store its data (United States region).
• PostHog — usage analytics, as described above.
• OpenStreetMap— supplies background map tiles. Opening a map sends your browser’s IP address and the map area you view to the tile service. Rover tracks are not sent to it.
• Cloudflare — DNS.
• Stripe, through Clerk Billing — payment processing for paid subscriptions. We do not store your card details.

Retention and deletion

Archived observations and saved rover data follow the base owner’s archive retention: Free 7 days, Pro 30 days, Fleet 90 days, and Enterprise 90days. Contact us to discuss longer Enterprise archive retention by agreement. Connection records are kept for that period after their last recorded connection ends. Saved tracks use the time they were recorded. The fix and connected-time bars cover the last 24 hours. Expired data is removed during cleanup; storage failures can delay removal. If the owner downgrades, data beyond the new plan’s window is removed at the next cleanup.

To stop rover recording, open the base in the dashboard, go to Rover access, and turn off “Record rover data” for that rover login. This stops new rover records for it and hides its saved history and live rover details. Rovers continue receiving corrections. Previously saved data stays until its retention period ends. Turning recording back on makes unexpired history available again; it does not fill in the time recording was off.

Deleting a base removes its rover connection records and credentials. Its saved tracks become inaccessible and are removed by cleanup. Closing your account turns off its streams and access to them, once we have processed the change; your account, base and credential settings are kept rather than deleted, so that a later billing message cannot quietly bring the account back. Recorded observations and rover history still expire on the retention above. To have anything removed sooner, or to get a copy of your data, email support@robognss.com.

Cookies

We use the session cookies required for sign-in (set by Clerk) and the cookie PostHog sets to count return visits, described under Usage analytics. No advertising or cross-site tracking cookies.

Changes

We will post any changes to this policy on this page and update the effective date above.