Privacy Policy
Effective date: 2026-10-07
Robota LLC operates RoboGNSS at robognss.com and app.robognss.com. Our postal address is 5015 Voyager Dr #7, Dallas, TX 75237, United States. This policy covers our website, hosted GNSS correction service, related tools, and support. Contact support@robognss.com about personal data or this policy.
Information we handle
- Accounts and billing. Clerk handles sign-in; we receive account identifiers and profile information such as your name and email. We do not receive your password. Paid subscriptions use Clerk Billing with Stripe for payment processing. We handle plan, subscription, and billing references but do not store card numbers.
- Base stations. We handle source names, mountpoints, declared coordinates, reference frames, station identifiers, and the positions broadcast in streams. Stream records can include connection times, client IP addresses, client software, data volumes, and message statistics.
- Rovers. The base owner decides, for each rover login, whether rover data is recorded and displayed. We can record connection information, NMEA sentence counts, fix quality and positions, including tracks. Records can include IP addresses, client software, and data volumes. 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 and archives. RTCM corrections pass through the service to connected rovers and configured destinations. When archiving is enabled, raw observations are stored for the plan’s retention period and can be downloaded as RINEX.
- Credentials and connected tools. We maintain credentials, permissions, and connection settings needed to authorize streams, pull sources, forwarding destinations, API calls, and connected agents. Protect credentials you hold and give tools only the access they need.
- Support and security. We handle correspondence, reports, supplied contact and technical details, and request metadata needed to deliver the service, diagnose failures, investigate abuse, and meet legal obligations.
Base owners are responsible for giving rover operators the required notices and obtaining any permissions needed for recording. If another account holder records your rover data, contact that owner or ask us for help with a privacy request.
How we use information
We use it to relay and monitor streams, manage access, provide archives and requested processing, show rover history, apply plan limits, bill for subscriptions, answer support requests, and send service notices. We also detect abuse, including misrepresented or duplicate stations, protect service security, and understand website use.
We do not sell personal data or use it for advertising. Our Terms of Use limit our use of customer content to providing and securing the service and carrying out your instructions.
Providers and destinations
| Provider or category | Purpose and information involved |
|---|---|
| Hosting providers | Run the service, store its records and archives, and process technical requests and logs. |
| Clerk and Stripe through Clerk Billing | Account identity, sign-in, subscriptions, billing, and payment details. |
| PostHog | Website and dashboard analytics described below. |
| Cloudflare | DNS and related network services. |
| Resend | Transactional notifications, including supplied report details and contact information when an email notification is sent. |
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.
If you configure forwarding or a pull source, data and connection information are exchanged with your chosen caster. Requested external survey processing sends the observations and information needed to the selected processing service. Connected agents receive access within permissions you approve. Those destinations and providers have their own terms and privacy practices.
We may disclose relevant information to comply with law, respond to valid legal requests, investigate abuse, or protect people, systems, and legal rights.
Usage analytics and cookies
PostHog receives pageview events and associated page URLs, referrers, event times, browser and device information, IP-derived approximate location, and generated visitor or session identifiers. Requests reveal your IP address. Our integration disables session replay and automatic click and form-interaction capture. The service may also send explicitly configured product events.
PostHog uses cookies and browser local storage to maintain identifiers and relate visits. These identifiers are pseudonymous; leaving out your name or email does not make all events anonymous. Clerk uses cookies and storage needed for sign-in. We do not use advertising cookies.
Browser privacy settings and tracker blockers can restrict analytics; service functions do not depend on PostHog. Blocking sign-in storage can prevent sign-in. Clearing identifiers does not delete events already sent. Consent for analytics, where required by law, is separate from agreement to our terms.
Files used in free tools
The survey point shifter, RINEX position updater, and photo GPS shifter process files in your browser. Those files are not uploaded to us. The RINEX converter requires an account and processes uploaded files on our servers. Its temporary copy is removed after conversion; it is not retained as an account archive. Hosting providers process that file to perform the conversion.
Retention, recording controls, and closure
Archived observations and saved rover data follow the base owner’s archive retention: Free 7 days, Pro 30 days, Fleet 90 days, and Enterprise 90 days. Contact us to discuss longer Enterprise archive retention by agreement, with confirmation that it can be delivered. Connection records are kept for that period after their last recorded connection ends. Saved tracks use the time they were recorded. Fix and connected-time bars cover the latest 24 hours. Cleanup removes expired data, though storage failures can delay removal. A downgrade applies the shorter window at the next cleanup, without a grace period for older archives.
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 remains until its retention period ends. Turning recording on again makes unexpired history available; it does not fill the period when recording was off.
Deleting a base removes its rover connection records and credentials. Its saved tracks become inaccessible and are removed by cleanup.
Account closure disables streams and access once processed; it does not erase all account data. Your account, base, and credential settings are kept rather than deleted to keep the account closed and prevent later billing updates from restoring access. There is no automatic deletion deadline for these settings. They remain while retained for that purpose, subject to review of whether they are still needed and any applicable erasure request. Recorded observations and rover history still expire on the retention above.
Support correspondence, operational and security logs, legal records, analytics, and provider-held payment and identity records have separate lifecycles. We retain these according to their purpose, security needs, applicable legal duties, and relevant disputes; no fixed deletion period is promised here for those categories or provider backups. Contact us for earlier removal, export help, or review of retained personal data. We explain any lawful reason a request cannot be fully met.
Your privacy rights
Email support@robognss.com to request access, correction, deletion, or an available portable copy of personal data. Identify the account, base, rover, or interaction involved. We may verify your identity and authority before disclosing or deleting information.
Depending on applicable law, you may also object to or restrict processing, withdraw consent, appeal a denied request, or complain to a privacy regulator. We will respond within applicable deadlines and explain lawful limits. Withdrawing consent does not undo earlier lawful processing. Download archives you need before their retention expires.
Roles and international processing
Robota determines how to use account, support, security, and product-analytics information. Customers control the streams they supply, destinations they configure, and rover recording they enable. Where we process data for a business customer, its instructions and applicable data-protection duties also matter. Contact us before submitting data that requires a data processing agreement so the necessary terms and arrangements can be established.
Where applicable law requires a legal basis, our own processing is based on providing the service under a contract, legitimate interests such as security and support where permitted, legal obligations, or consent where required. A customer’s rover recording may require its own lawful basis.
Robota is based in the United States. Providers and destinations may process information in the United States and other countries with different privacy laws. Contact us about arrangements relevant to your information. Use of RoboGNSS is not consent to an international transfer, and this policy does not claim a particular transfer safeguard covers every use.
Security, children, and changes
No service is perfectly secure. Protect stream and account credentials, use appropriate network security, and revoke access you no longer need. If a personal-data breach requires notice, we will notify affected people and authorities within the time and in the manner required by applicable law.
Accounts are for people aged 18 or older. We do not knowingly invite children to create accounts. Contact us if you believe a child has provided personal data so we can investigate and take appropriate action.
We will post revisions here and update the effective date. We will give notice of material changes through the dashboard or account email and provide any further notice or consent required by law.
Robota LLC
5015 Voyager Dr #7
Dallas, TX 75237
United States
support@robognss.com