Security Policy.
Architecture & Governance.

Technical security controls and data protection protocols • Updated November 18, 2026

Zero-Trust Security Principles

At RubyBug LLC, security is engineered directly into our architecture from the ground up. We adhere to the principle of least privilege, strict tokenized authorization, end-to-end transport encryption, and continuous automated vulnerability surveillance.

1. Data Encryption Standards

In Transit (TLS 1.3)

All client-to-server and server-to-marketplace traffic mandates modern HTTPS using TLS 1.3 encryption with ECDHE forward secrecy cipher suites. HSTS (HTTP Strict Transport Security) is enforced across all domains.

At Rest (AES-256)

Database volumes and application token stores utilize industry-standard AES-256 GCM encryption. Cryptographic keys are managed within dedicated hardware security modules (HSM) with strict separation of duties.

2. Tokenized Authentication & Scoped Access

RubyBug Apps connects to external eCommerce marketplaces (such as TikTok Shop Open API, Shopify Partner API, Amazon SP-API) exclusively through tokenized OAuth 2.0 flows:

  • Zero Password Storage: We never capture, store, or process merchant master marketplace passwords.
  • Least-Privilege Scoping: Authorizations request solely the minimal API permissions needed to read orders and sync inventory statuses.
  • Short-Lived Access Tokens: Marketplaces issue temporary access tokens refreshed via encrypted token rotation endpoints.

3. Network & Edge Perimeter Security

Our production environments reside behind hardened cloud network perimeters:

  • DDoS Mitigation & Web Application Firewall (WAF): Enterprise edge routing filters automated bot scraping, SQL injection, and layer 7 attack vectors.
  • Network Segmentation: Public web endpoints are strictly segregated from backend processing nodes via isolated Virtual Private Clouds (VPC).
  • Internal Access Control: Internal administrative access requires hardware-backed Multi-Factor Authentication (MFA) and strict role-based access control (RBAC).

4. Continuous Vulnerability Management

Software dependencies, container images, and source code are monitored continuously:

  • Automated Dependency Auditing: Static code analysis and Dependabot security scanning run on every repository push to detect known CVEs.
  • Patching Cadence: Critical security vulnerabilities are remediated within 24–48 hours of public advisory disclosure.
  • Audit Logging: System activities, token handshakes, and administrative actions generate tamper-evident audit logs preserved for security analysis.

5. Incident Reporting & 72-Hour Breach SLA

We maintain a documented incident response procedure. If any security incident compromises merchant data, RubyBug LLC guarantees notification to affected platform partners and merchants within 72 hours.

Security researchers and users may report vulnerabilities directly via our Incident Reporting Portal or email aissatalyah524@hotmail.com.

6. Security Inquiries

Security Team: RubyBug LLC Information Security

Physical Address: 1001 S MAIN ST, STE 600, KALISPELL, MT 59901-1498

Security Inbox: aissatalyah524@hotmail.com

Emergency Vulnerability Disclosure: Submit Security Incident Report →