Legal Documentation

Privacy Policy

Official Data Privacy, Google API Services Compliance, and Security Statement for RevenuePilot.

Effective Date: November 3, 2026•Last Updated: November 3, 2026

1Introduction & Application Identity

Welcome to RevenuePilot (referred to herein as "RevenuePilot," "we," "our," or "us"). RevenuePilot is a specialized B2B software-as-a-service (SaaS) application accessible online at https://revenuepilot.in.

RevenuePilot provides marketing teams, advertising agencies, e-commerce brands, and businesses with a unified command center to manage, optimize, automate, and analyze digital advertising campaigns across supported advertising platforms, specifically including Google Ads and Meta Ads.

We are strictly committed to safeguarding your personal and commercial data. This Privacy Policy discloses our information collection practices, how we protect and process your data, and how we comply with applicable regulatory frameworks and third-party platform policies, including Google's API Services User Data Policy.

2Scope of this Privacy Policy

This policy governs all interactions with RevenuePilot, including:

  • Visits to our public website (https://revenuepilot.in).
  • Creation and administration of RevenuePilot customer accounts and tenant workspaces.
  • Use of our dashboard, campaign creation tools, automated reporting, and analytics suites.
  • Authentication and data synchronization conducted through third-party platform integrations, including Google OAuth and the Google Ads API.

3Information We Collect

RevenuePilot collects only the minimum necessary information required to deliver our services reliably:

Account & Registration Data

Name, business email address, company or organization name, encrypted authentication credentials, and chosen role within your organization.

Advertising & Operational Data

Ad account identifiers, campaign metadata, ad groups, budget allocations, impressions, clicks, conversion metrics, and return on ad spend (ROAS).

Connected Service Credentials

OAuth 2.0 access and refresh tokens used to interact with third-party APIs. All refresh tokens are stored encrypted with AES-256-GCM.

System & Technical Logs

IP addresses, browser type, operating system version, error diagnostics, and timestamps required for security audits and fraud prevention.

4Google Account & Google API Data (OAuth 2.0)

RevenuePilot provides users with optional integrations with Google Cloud and Google Ads services. When you choose to connect your Google account with RevenuePilot, the following terms apply:

A. Google Scopes Requested & Rationale

openid, profile, email

Purpose: To securely authenticate your user identity, verify your email address, and establish your RevenuePilot account profile.

https://www.googleapis.com/auth/adwords

Purpose: Used exclusively when you connect your Google Ads account to RevenuePilot. Allows RevenuePilot to retrieve ad campaign hierarchies, read performance statistics (impressions, clicks, conversions, spend), and execute campaign adjustments that you explicitly configure or authorize inside the dashboard.

B. Storage & Protection of Google OAuth Credentials

Google OAuth tokens are never transmitted to unauthenticated clients. Long-lived refresh tokens are immediately encrypted using AES-256-GCM authenticated encryption before being persisted in our database. Encryption keys are maintained in separate, secure environment configurations outside of source control.

C. Google API Services User Data Policy Compliance & Limited Use Requirements

Mandatory Limited Use Disclosure

RevenuePilot's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

  • We do NOT sell, rent, or transfer user Google data to any third party for advertising, commercial brokering, or lead generation purposes.
  • We do NOT use Google user data to serve personalized, retargeted, or interest-based advertising to users.
  • We do NOT use Google user data to train, fine-tune, or calibrate generalized artificial intelligence (AI) or machine learning (ML) models.
  • Human staff are NOT permitted to read user Google data unless you provide explicit consent to investigate a specific technical error, or where required by law.

5How We Use Your Information

We process data strictly for lawful, contractually necessary purposes:

  • Providing Core Services: Rendering campaign metrics, computing ROAS, monitoring budget utilization, and displaying interactive reports.
  • Authentication & Security: Verifying user access, enforcing role-based tenant isolation, preventing unauthorized account takeovers, and auditing security events.
  • Customer Support: Assisting you with operational troubleshooting when initiated by your organization.
  • System Reliability: Monitoring API rate limits, tracking application uptime, and delivering automated anomaly alerts.

6Multi-Tenant Architecture & Data Isolation

RevenuePilot is architected from the ground up as a strict multi-tenant application. Every database record—including ad accounts, campaign statistics, client records, and audit logs—is programmatically bound to a unique tenant identifier (organizationId).

Our backend middleware enforces tenant isolation on 100% of API endpoints. It is architecturally impossible for one organization to access, view, or query the ad accounts, metrics, or credentials belonging to another organization.

7Third-Party Subprocessors

To maintain high platform availability and security, RevenuePilot relies on carefully evaluated third-party service providers:

SubprocessorFunctionData Handled
Google Cloud PlatformOAuth 2.0 & Google Ads APIUser profile, Ad performance metrics
Meta Graph APIMeta Ads IntegrationMeta campaign performance data
PostgreSQL EnginePrimary Relational StorageEncrypted account & tenant metrics
Redis / BullMQJob Queue & Session CacheEphemeral background sync tasks

8Data Retention, Disconnection & Deletion

You maintain complete autonomy over your data at all times:

  • Disconnecting Google Ads: You can disconnect your Google Ads account at any moment through Dashboard > Integrations > Disconnect. Upon disconnection, stored OAuth tokens for that account are permanently deleted from our active database.
  • Revoking Access Directly from Google: You can also revoke RevenuePilot's permissions at any time directly through Google's security portal: https://myaccount.google.com/permissions.
  • Complete Account Deletion: You may request complete erasure of your user profile, tenant organization, and associated data by emailing privacy@revenuepilot.in. All database records are permanently purged within 30 days of request receipt.

9Cookies & Tracking Technologies

RevenuePilot uses strictly necessary HTTP cookies for authentication session management, CSRF attack defense, and preference preservation (such as light/dark mode preference). We do not use intrusive third-party cross-site advertising tracking cookies.

10User Rights (GDPR, CCPA & Global Rights)

Regardless of your geographic location, RevenuePilot respects universal data privacy principles:

  • Right to Access: You may request an export of all personal data held about you.
  • Right to Rectification: You may correct inaccurate or incomplete profile information.
  • Right to Erasure: You may request deletion of all personal and commercial data.
  • Right to Restrict Processing: You may withdraw consent for optional third-party integrations at any time.

11Contact Information & Privacy Inquiries

If you have any questions, compliance inquiries, or data requests regarding this Privacy Policy or RevenuePilot's data practices, please reach out directly to our dedicated privacy contact:

RevenuePilot Privacy & Compliance Operations

Primary Privacy Contact: privacy@revenuepilot.in

General Customer Support: support@revenuepilot.in

Website: https://revenuepilot.in