Data and privacy
Effective October 11, 2026. RouteMyAgent is the service’s trade name. Contact support@routemyagent.dev for privacy, access, correction or deletion requests.
Account and payment records
Clerk handles sign-in and account recovery. The router links your verified Clerk user identifier to an internal account. We retain promotion claims, rentals, usage-time accounting, balances, credit purchases, payment and webhook references, and hashed router tokens to operate access, reconcile payments and investigate problems. Stripe-hosted Checkout collects payment details; our router does not collect or store card numbers.
Provider keys and routed content
Your attached NVIDIA key is encrypted using AES-256-GCM in a separate credential database for the active rental. The encryption key is stored separately from that database. Normal ledger backups exclude both. Restarts restore active-rental keys into process memory for routing. Disconnecting or rental expiry deletes the saved attachment. Disk snapshots or externally created backups can retain encrypted copies; physical erasure is not guaranteed. Libraries and memory allocators may retain temporary copies; immediate zeroization is not guaranteed. Administrators can access server memory, so this is not a zero-knowledge service.
Prompts, conversation context, tool definitions and results, and model responses pass through the server to NVIDIA. The normal routing path processes these bodies in memory without maintaining a chat-history database or writing request and response bodies to disk. Your coding client and NVIDIA handle their own copies under their own settings and policies. Do not include credentials in prompts or support messages.
Operational data and service providers
Routing metadata includes timestamps, model and provider identifiers, request status, usage, quota counters and credential fingerprints. Some quota, security and rate-limit alerts are saved to disk. Short-lived request accounting and IP-based abuse-limit counters are held in memory. Container operational logs rotate by size, not by a fixed number of days.
The router is hosted on DigitalOcean in Toronto, Canada. Clerk provides authentication, Stripe handles payments, and NVIDIA receives inference requests. Cloudflare provides the domain’s DNS; the website is not currently routed through its reverse proxy. These providers process data under their own policies and may process it in other regions. We use the records above for service delivery, accounting, security, support and payment reconciliation.
Browser storage
Clerk manages authentication storage and cookies. The portal uses session storage for non-secret pending purchase identifiers and choices so a retry does not create a duplicate purchase. It does not save NVIDIA keys or revealed router tokens in browser storage. Router tokens are shown once for you to save privately in your client configuration.
Retention and your choices
There is no automatic account, rental or billing-record deletion schedule in the current service. Durable account, billing, rental and operational records remain until the operator removes them; backups can retain copies. We do not promise a fixed retention period or automatic deletion after expiry. Provider-key attachments are temporary as described above.
You can disconnect the attached key and revoke router tokens in the portal. This stops their use but does not erase billing history or refund purchased time. New usage time pauses when no model request is running; older wall-clock rentals retain their original deadline. Email support@routemyagent.dev for access, correction, account closure or deletion. We may need to verify account ownership and retain records required for accounting, security, disputes or applicable law. Removing our records does not remove information held by your client or service providers.