How ROI.dog protects access and account data

Authentication and account boundaries

Users authenticate before accessing dashboards, saved reports, billing controls, or connected Google Ads accounts. Account-specific application routes are separated from the public website and excluded from search indexing.

Google Ads connection

A Google Ads connection starts only after the user completes Google's OAuth authorization flow. ROI.dog's product workflows are designed to query and analyze authorized account data; they do not apply campaign mutations or change bids, budgets, keywords, ads, or conversion settings.

Users can disconnect the account in ROI.dog and can revoke authorization through their Google Account controls.

Data handling

ROI.dog processes the account data needed for the selected audit, report, monitoring view, or tool. Saved reports and application records may be retained so an authenticated user can return to their results. The Privacy Policy describes the applicable data categories, purposes, providers, retention, and user controls.

The service does not publish customer-level Google Ads data or use private audit results as public SEO statistics.

AI and service-provider boundaries

When a feature uses an AI provider, ROI.dog sends the information needed to produce that requested analysis under the active provider configuration and the consent described in the product. Payment checkout and subscription management are handled through Stripe-hosted billing workflows.

Logging and analytics

ROI.dog uses operational logs and product analytics to understand errors and product usage. Sensitive URL values and common credential fields are redacted before supported PostHog error and analytics events are sent. Meta and PostHog measurement remain part of the public product experience.

Your controls

• Revoke Google authorization through your Google Account
• Disconnect the selected Google Ads account from ROI.dog
• Manage an active subscription through the billing portal
• Request privacy or account assistance through cs.pyxl@gmail.com

Reporting a security concern

Send a concise description, affected URL or feature, reproduction steps, and potential impact to cs.pyxl@gmail.com. Do not include access tokens, passwords, customer data, or other secrets in the initial message.

No internet service can promise absolute security. ROI.dog reviews reports in good faith and prioritizes issues based on credible risk and impact.