Effective October 13, 2026 (ad measurement section added and revised October 8, 2026) · RouterGrowth is operated by Altria LLC, a Wyoming limited liability company ("RouterGrowth", "we").
This policy covers RouterGrowth's website, dashboard, API and MCP integrations, including the ChatGPT plugin. RouterGrowth is operated by Altria LLC. Contact hello@routergrowth.com about personal data or this policy.
We process account email addresses, workspace and membership identifiers, authentication records, hashed API keys, balances, billing references and transaction records to authenticate users, control access, operate workspaces, provide support and account for usage. Payment providers process payment details through their own payment interfaces.
We process the inputs you or your authorized agents send, the results returned by providers, run identifiers, timestamps, status and usage records. Depending on the operation, these may include people's names, work contact details, company and social profile information, URLs, website content, search queries, prompts, images, audio or video. We use this data to carry out the requested operation and make its results and history available in your workspace. Saved tables, watches and suppression lists contain the data you choose to store or monitor.
When you connect RouterGrowth, we process the account authorization and tool arguments sent by the client, and return tool results to that client. Arguments may contain personal data or conversation context relevant to the requested action. Connecting does not itself give RouterGrowth your entire chat history. Access is limited by the connected workspace and authorization. The client provider also processes information under its own privacy policy. Do not put passwords, payment card details or other unnecessary sensitive information in tool inputs.
If you connect Gmail, LinkedIn, Instagram or WhatsApp, we and the connection provider process account identifiers, connection status and the profile, conversation, participant, message and attachment data needed for the operations you request. Reading an inbox, receiving message events or sending a message can place this data in run results and workspace events. Authentication is completed through the connection flow; connection providers may hold the credentials or tokens needed to maintain access. RouterGrowth uses connection identifiers to route requests. Unipile supports these connected-account operations.
For inbox creation, email delivery and warm-up, the relevant providers process inbox and sender details, recipients, message content and delivery activity. Domain registration and DNS operations share domain and any required registrant/contact information with the registrar and related service providers. Registration data may be subject to registry requirements and applicable publication rules.
We share the data needed for an operation with the selected data, enrichment, search, scraping, creative, messaging, inbox, warm-up or domain provider. The providers involved depend on your request and are described in our catalog and operation information. Your authorized workspace members and connected clients can receive workspace results according to their access. Hosting, database, payment, support, analytics and monitoring providers process data needed to operate their services. We may also disclose information where required by law or necessary to investigate abuse and protect the service.
We do not sell your submitted workspace data or use your run inputs and outputs for another customer's requests. Third-party services process information under their applicable terms and privacy policies; their storage and deletion practices may differ from ours. RouterGrowth and its providers may process information outside your country.
We use DataFast for traffic and attribution analytics and LogRocket for session replay and troubleshooting. Website and service logs can include IP addresses, device/browser information, page URLs, referrers, timestamps, interactions and errors. Our site stores first-visit referral and campaign information in browser local storage and can associate it with signup. Hosting providers, including Vercel, keep operational logs.
LogRocket can record visible page text, including workspace results and balances shown on screen. Our configuration masks typed inputs, strips network request and response bodies and headers, and redacts most URL parameter values. Selected campaign and navigation parameters remain visible. Elements marked private are excluded, and some pages use stricter masking. You can block analytics and replay scripts with browser privacy controls; this does not delete previously collected records. Contact us to request access or deletion.
Pages under /lp/ load X's conversion pixel to measure campaigns and help target ads. It can set cookies and X may associate visits with an X account. The pixel is suppressed when the browser sends Global Privacy Control. If it loaded on a campaign page and you subsequently sign up, the dashboard can send a signup conversion event. We do not include your name, email or workspace content in that event. Browser controls that block third-party trackers can prevent loading.
You can revoke API keys and disconnect authorized MCP apps and supported messaging accounts from the dashboard. You can manage saved tables and suppression lists through the available workspace controls. Disconnecting RouterGrowth in ChatGPT or another client stops use of that connection but does not by itself delete your RouterGrowth workspace. To delete run history, close your account, or request access, correction or deletion of personal data, email hello@routergrowth.com. We respond within 30 days and may verify your identity before acting.
Where applicable law provides these rights, you may also request restriction or portability, object to processing, or withdraw consent for processing based on consent. Where EU/EEA data-protection law applies, you may complain to your local supervisory authority. We process data to provide the service you request, operate and secure it, comply with legal obligations, and, where required, based on consent. We explain any legal reason that prevents fulfilling a deletion request.
Updates are published here with a revised effective date.