Privacy Policy
1. Introduction
This Privacy Policy (the "Policy") describes the information collection, use, storage, and disclosure practices of RTRGRD (referred to herein as "Company," "we," "us," or "our") in connection with the RTRGRD desktop application (the "Application" or "Service"). The Application is an AI-assisted terminal workspace designed for network engineering professionals.
The Company is committed to protecting user privacy. The Application employs a local-first architecture wherein the majority of data processing occurs on the user's local device, and transmission to external services is minimized.
By downloading, installing, or using the Application, you acknowledge that you have read, understood, and consent to the practices described in this Policy. If you do not agree to this Policy, you must discontinue use of the Application.
2. Information Collection
2.1 Information Provided Directly by User
- Account Credentials. Email address and authentication tokens provided through Google OAuth or Microsoft Azure AD OAuth during account registration. Both authentication methods are facilitated through Google Firebase Authentication.
- Subscription Information. When subscription payments are enabled, payment and billing information will be processed through our third-party payment processor, Lemon Squeezy. The Company does not store complete payment card details.
- Bug Reports. If you submit a bug report through the Application, the information you provide (category, severity, summary, reproduction steps, and expected behavior) is transmitted to Company systems for issue tracking purposes.
2.2 Information Collected Automatically
- Cloud AI Query Counts. Daily counts of cloud-based AI requests, used for quota enforcement and billing.
- Per-Query AI Metadata. For each cloud AI request, the Application records the AI model used, input and output token counts, processing mode, and timestamp to the user's account record. This data is used for billing, quota enforcement, and service monitoring.
- Cumulative Token Consumption. Total AI tokens consumed, tracked for billing and usage cap enforcement.
- Subscription Status. Tier classification (Core or Apex) and associated usage quotas.
- Anonymous Rate Limiting. For users who have not signed in, a one-way cryptographic hash (SHA-256, truncated) of the user's IP address is stored temporarily alongside a daily request counter. The raw IP address is never stored, logged, or transmitted. This hashed identifier is used solely to enforce daily usage limits on anonymous cloud AI requests (currently 5 per day) and is automatically deleted after seven (7) days. Because the hash is irreversible, it cannot be used to identify or contact the user.
Not Collected. The following activities are tracked exclusively on the user's local device and are not intentionally transmitted to Company servers during normal Application operation: workflow executions, device profiling operations, terminal command history, learned command patterns, and all other local feature activity.
2.3 Information Stored Locally
- Network Credentials. SSH passwords, private keys, and enable passwords, stored using the Electron safeStorage API with operating system-level encryption.
- Device Configurations. Running configurations, interface states, and routing tables captured during device profiling operations.
- Terminal Session Data. Command history and terminal output, retained in volatile memory during active sessions.
- User Knowledge Base. User-uploaded PDF documents, learned command patterns, and custom workflows.
- Local AI Models. Machine learning models for local inference, including IBM Granite and Google Gemma models.
3. Use of Information
3.1 Primary Purposes
- Service Delivery. To authenticate users, process subscription payments, and provide access to Application features according to subscription tier.
- AI-Assisted Features. To provide command suggestions, troubleshooting analysis, and workflow automation. When cloud-based AI features are used, the Application applies an automated Sanitization Service that is designed to detect and redact network credentials, cryptographic keys, and other sensitive data from prompts before they are sent to the AI provider. Users may enable Privacy Mode to process all AI queries locally with no external transmission.
- Security and Fraud Prevention. To detect and prevent unauthorized access, abuse, or circumvention of usage limitations.
- Service Improvement. To analyze aggregate usage patterns for the purpose of improving Application functionality.
3.2 Data Processing for AI Features
When users engage cloud-based AI features, including the Copilot sidebar, War Room analysis, and Command Deck automation, the Application transmits contextual information to third-party AI providers after applying automated sanitization.
Sanitization Service. The Company has implemented a sanitization layer as a commercially reasonable measure to reduce the risk of sensitive network credentials being included in data transmitted to third-party AI providers. Prior to transmission, the Sanitization Service applies numerous pattern-matching algorithms designed to detect and redact common credential formats. This service represents a best-effort safeguard and does not constitute a guarantee that all sensitive information will be detected or redacted.
The following categories of secrets are targeted for automatic redaction:
Authentication Credentials:
- Passwords in all formats (plaintext, Type 5, Type 7, Type 8, Type 9, bcrypt, scrypt)
- Enable secrets and privilege escalation credentials
- TACACS+ and RADIUS shared secrets
- LDAP bind credentials and Active Directory service account passwords
Cryptographic Materials:
- RSA, ECDSA, and Ed25519 private keys
- X.509 certificates containing private key material
- IKE/IPsec pre-shared keys and Phase 1/Phase 2 secrets
- TLS/SSL private keys and certificate signing request private components
Network Authentication Secrets:
- SNMP v1/v2c community strings (read-only and read-write)
- SNMP v3 authentication and privacy passwords
- BGP, OSPF, and IS-IS routing protocol authentication keys
- VRRP, HSRP, and GLBP authentication strings
- MACsec connectivity association keys (CAK/CKN pairs)
Access Tokens and API Keys:
- Bearer tokens and JWT secrets
- API keys and webhook signing secrets
- Cloud provider access credentials
- OAuth client secrets and refresh tokens
Transparency and Auditability. Each sanitization operation is logged to a local audit trail accessible through the Application's Privacy Shield panel. Users may review the count of secrets redacted, categories detected, and timestamps in real time. This transparency enables users to verify that the sanitization layer is actively protecting their data.
DISCLAIMER OF WARRANTY. NOTWITHSTANDING THE FOREGOING, THE SANITIZATION SERVICE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. THE COMPANY DOES NOT WARRANT THAT THE SANITIZATION PROCESS WILL DETECT OR REDACT ALL SENSITIVE INFORMATION. Users are expressly advised of the following inherent limitations: custom credential formats or proprietary authentication mechanisms may not match predefined patterns; obfuscated or encoded secrets (e.g., Base64-encoded passwords in configuration comments) may evade detection; contextual secrets embedded in natural language descriptions or non-standard formats may not be recognized; the Company cannot anticipate every possible credential format across all network vendors and software versions.
User Responsibility. Users remain solely responsible for reviewing AI prompts before submission and for ensuring that sensitive information is not inadvertently disclosed. The sanitization layer is a technical safeguard designed to reduce risk, not eliminate it.
Privacy Mode. Users who wish to prevent AI-related data from being transmitted to external services may enable Privacy Mode. When active, Privacy Mode routes all AI inference to local models running entirely on the user's device. Privacy Mode is designed to prevent external data transmission for AI processing purposes. The Company does not warrant that Privacy Mode will prevent all forms of network communication by the Application or the underlying operating system.
4. Third-Party AI Providers
4.1 Google Cloud / Vertex AI
The Application utilizes Google's Gemini API through the Vertex AI platform for cloud-based AI inference. The Company maintains a paid commercial relationship with Google Cloud.
According to Google's published terms for paid API tiers as of the date of this Policy:
- No Training on User Data. Google states that user prompts, responses, and contextual data submitted through paid API tiers are not used to train, tune, or improve Google's generative AI models.
- Compliance Certifications. Google Cloud reports compliance with SOC 1, SOC 2, and SOC 3 standards.
- Data Processing. Google processes data pursuant to its Data Processing Addendum, available at https://cloud.google.com/terms/data-processing-addendum.
THE COMPANY DOES NOT WARRANT OR GUARANTEE THE ACCURACY, COMPLETENESS, OR CONTINUED APPLICABILITY OF GOOGLE'S POLICIES. Google's terms are subject to change without notice from the Company. Users are encouraged to review Google's current data handling terms independently.
4.2 Local AI Models
The Application includes optional local AI models that execute entirely on the user's device:
- IBM Granite 3.3 (licensed under Apache License 2.0)
- Google Gemma 3 (licensed under Gemma Terms of Use)
- Nomic Embed v1.5 (licensed under Apache License 2.0)
When operating in Privacy Mode, AI inference is performed locally. Privacy Mode is designed to prevent the transmission of user data to external AI services for processing purposes. The Company does not warrant that Privacy Mode will prevent all forms of network communication by the Application or the underlying operating system.
4.3 Bring Your Own Key (BYOK) — User-Provided API Keys
The Application includes a feature that allows Apex-tier subscribers to provide their own API keys for third-party AI services, including but not limited to Google Gemini, OpenAI, Anthropic, xAI (Grok), and Groq (the "BYOK Feature"). When BYOK is active, user prompts, contextual data, and associated content are transmitted directly from the Application to the third-party AI provider designated by the user's API key.
Data Routing. When using the BYOK Feature, the Application routes AI requests directly to the third-party provider's API endpoints using the user's provided API key. These requests bypass the Company's cloud infrastructure entirely.
Sanitization. The Company's automated Sanitization Service (described in Section 3.2) is applied to all outbound AI requests, including those routed through the BYOK Feature. The same credential redaction and sensitive data detection measures are applied before data is transmitted to the third-party provider. The limitations of the Sanitization Service described in Section 3.2 apply equally to BYOK requests.
Key Storage. User-provided API keys are stored locally on the user's device using operating system-level encryption (Electron safeStorage API). API keys are never transmitted to Company servers.
Third-Party Privacy Policies. When using the BYOK Feature, your data is subject to the privacy policy, terms of service, and data handling practices of the third-party AI provider associated with your API key.
THE COMPANY HAS NO CONTROL OVER, AND ASSUMES NO RESPONSIBILITY FOR, HOW THIRD-PARTY AI PROVIDERS PROCESS, STORE, RETAIN, OR USE DATA TRANSMITTED THROUGH USER-PROVIDED API KEYS.
Users are solely responsible for:
- Reviewing and understanding the privacy policy and terms of service of their chosen third-party AI provider.
- Ensuring that their use of third-party API keys complies with their organization's security and data governance policies.
- Understanding the data retention, training, and usage policies of their chosen provider, which may differ from the Company's arrangements with its own AI providers.
- Any costs, charges, or fees incurred through the use of their own API keys.
No Liability for Third-Party Data Handling. THE COMPANY EXPRESSLY DISCLAIMS ALL LIABILITY FOR ANY DATA LOSS, UNAUTHORIZED ACCESS, DATA BREACH, OR OTHER ADVERSE CONSEQUENCE ARISING FROM THE TRANSMISSION OF DATA TO THIRD-PARTY AI PROVIDERS THROUGH THE BYOK FEATURE. Users acknowledge that the Company cannot guarantee the security, privacy, or confidentiality practices of third-party providers.
5. Disclosure of Information
The Company does not sell, rent, or trade user information to third parties for marketing purposes.
Information may be disclosed in the following circumstances:
- Service Providers. To third-party vendors who perform services on our behalf, including cloud infrastructure (Google Firebase), payment processing (Lemon Squeezy), and AI inference (Google Cloud).
- Legal Compliance. When required by applicable law, regulation, legal process, or governmental request.
- Protection of Rights. To protect the rights, property, or safety of the Company, its users, or the public.
- Business Transfers. In connection with a merger, acquisition, or sale of assets, subject to the acquiring entity's agreement to honor this Policy.
6. Data Retention
- Account Information. Retained until the user requests account deletion or the account is terminated for violation of terms.
- Usage Metrics. Retained for ninety (90) days on a rolling basis, after which data is automatically purged.
- Anonymous Rate Limit Data. Hashed IP counters are automatically deleted after seven (7) days via Firestore TTL policy.
- Subscription Records. Retained as required by applicable tax and accounting regulations.
- Local Data. User-controlled; retained indefinitely until manually deleted by the user.
7. Data Security
The Company implements reasonable technical and organizational measures to protect user information, including:
- Encryption at Rest. Local credentials are encrypted using the Electron safeStorage API, which leverages operating system-level encryption facilities.
- Encryption in Transit. The Application is designed to utilize TLS or similar industry-standard encryption for communications with Company servers and third-party services.
- Access Controls. Administrative access to cloud infrastructure is restricted to authorized personnel on a principle of least privilege basis.
- Dependency Monitoring. Open-source dependencies are monitored for known security vulnerabilities.
Notwithstanding these measures, no method of transmission over the Internet or electronic storage is completely secure. The Company cannot guarantee absolute security of user information.
8. User Rights
8.1 General Rights
All users may exercise the following rights:
- Access. Request a copy of personal information held by the Company.
- Correction. Request correction of inaccurate personal information.
- Deletion. Request deletion of personal information, subject to legal retention requirements.
- Portability. Request export of personal information in a machine-readable format.
- Restriction. Limit data processing by enabling Privacy Mode, which prevents cloud AI transmission.
To exercise these rights, contact the Company at rtrgrd.sh@gmail.com.
8.2 European Economic Area and United Kingdom
Users located in the European Economic Area or United Kingdom are entitled to additional rights under the General Data Protection Regulation (GDPR), including the right to object to processing based on legitimate interest and the right to lodge a complaint with a supervisory authority.
8.3 California Residents
Users who are California residents are entitled to additional rights under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA), including:
- The right to know what personal information is collected, used, and disclosed.
- The right to delete personal information.
- The right to opt-out of the sale of personal information. The Company does not sell personal information.
- The right to non-discrimination for exercising privacy rights.
9. Children's Privacy
The Application is intended for use by network engineering professionals and is not directed at individuals under eighteen (18) years of age. The Company does not knowingly collect personal information from children. If you believe that a child has provided personal information to the Company, please contact us immediately at rtrgrd.sh@gmail.com.
10. International Data Transfers
User information may be transferred to and processed in the United States, where the Company's service providers maintain infrastructure. For users located in the European Economic Area or United Kingdom, such transfers are made pursuant to Standard Contractual Clauses approved by the European Commission.
11. Updates to This Policy
The Company may update this Policy from time to time to reflect changes in practices or applicable law. The "Last Updated" date at the top of this Policy indicates when revisions were last made. For material changes, the Company will provide notice through the Application interface or via email to registered users.
Continued use of the Application following the posting of changes constitutes acceptance of the revised Policy.
12. Contact Information
For questions regarding this Policy or to exercise your privacy rights, contact:
Privacy Inquiries
Email: rtrgrd.sh@gmail.com
The Company will respond to all privacy-related requests within thirty (30) days of receipt.
13. Governing Law
This Policy shall be governed by and construed in accordance with the laws of the State of New Mexico, United States, without regard to principles of conflict of laws. The exclusive venue for any dispute arising under this Policy shall be the state or federal courts located in Sandoval County, New Mexico.
This Privacy Policy is intended to describe the Company's data practices as of the Effective Date. The Company reserves the right to interpret and apply this Policy in its sole discretion.