Privacy Policy

Introduction

Welcome to Access Pilot ("we," "our," or "us"). We are committed to protecting your privacy and ensuring the security of your data. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our application to manage user permissions for various third-party platforms including Google, Meta, Microsoft, Shopify, and others.

Information We Collect

• Account Information: When you register, we collect your name, email address, profile picture, and password (if applicable).
• Authentication Data: We utilize OAuth 2.0 services from providers including Google, Microsoft, LinkedIn, Meta, and others to verify identity. We process authentication tokens to validate your access rights. We never see, store, or have access to your third-party account passwords.
• Platform Data: To fulfill the service's purpose, we access lists of assets (e.g., Ad Accounts, Pages, Properties) associated with your connected accounts. This usage is strictly limited to displaying options for granting access.
• Usage Data: We collect anonymous data on how the service is used, such as the number of access links generated and successful grant actions.

How We Use Your Information

We use the information we collect to:

• Facilitate secure access granting across 50+ supported platforms.
• Verify the identity of Clients using Multi-Provider Authentication (Google, Microsoft, LinkedIn, etc.).
• Process billing transactions for credit purchases via our secure payment processors.
• Provide Agency features such as White Labeling (displaying your logo to clients).
• Detect and prevent fraud or abuse of our services.

Data Security

We implement industry-standard security measures to protect your data. Our application architecture emphasizes client-side processing, meaning sensitive access tokens often remain within your browser's secure memory and are not persistently stored on our servers. All data transmission occurs over SSL/TLS encrypted connections.

Google API Services – Privacy & Data Use Disclosure

Access Pilot ("we," "our," or "us") uses Google OAuth 2.0 to authenticate users and facilitate secure access granting. Below is a detailed explanation of each permission we request and how we use the associated data.

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

Access Pilot serves two distinct user roles, Consultants and Clients, and handles their data differently.

1. Email Address, Profile & Identity (email, profile, openid)

Consultants (Account Holders)

Consultants may sign in to Access Pilot using Google Single Sign-On. When doing so, we collect:

• Email address – used for account creation, login, transactional notifications (e.g., when a Client grants access), and may in the future be used for promotional or advertising communications. Consultants can opt out of promotional emails at any time.
• Full name – used to create and display the Consultant's profile within the application and in communications with Clients.
• Profile photo – used to personalize the Consultant's profile within the application and may be displayed to Clients during the access-granting process.

Clients (Access Grantors)

Clients authenticate with their Google account when they open an Access Request Link sent by a Consultant. During this authentication, we collect:

• Email address – used solely to identify the person granting access. When access is successfully granted, the Client's email address is included in the notification sent to the Consultant so they can confirm who provided the permissions.
• Basic profile information (name) – used only to personalize the access-granting interface during the active session.

We do not use Client email addresses for marketing, advertising, analytics, or any purpose other than identifying the grantor to the Consultant. Client identity data is not stored beyond what is necessary to complete and record the access-granting transaction.

2. Google Analytics

These scopes are requested from Clients only during the access-granting process. Consultants do not authenticate with these scopes.

• https://www.googleapis.com/auth/analytics.readonly – "See and download your Google Analytics data." We use this read-only permission exclusively to retrieve the list of Google Analytics accounts and properties associated with the Client's Google account, so the Client can select which ones to share with the Consultant. We do not download, store, or analyze any Analytics reporting data.
• https://www.googleapis.com/auth/analytics.manage.users – "Manage Google Analytics Account users by email address." We use this permission exclusively to add the Consultant's email address as a user on the Google Analytics properties the Client selects. We do not modify, remove, or otherwise manage any other user permissions on the Client's account.

3. Google Ads

These scopes are requested from Clients only during the access-granting process. Consultants do not authenticate with these scopes.

• https://www.googleapis.com/auth/adwords – "See, edit, create, and delete your Google Ads accounts and data." We use this permission exclusively to (a) list all Google Ads accounts accessible to the Client's Google account so the Client can select which ones to share, and (b) grant the Consultant access to the selected Google Ads accounts via the Google Ads API. We do not view, edit, create, or delete any Google Ads campaigns, billing information, or reporting data. No ads data is read, stored, or transmitted beyond what is necessary to list accounts and grant user access.

4. Google Tag Manager

These scopes are requested from Clients only during the access-granting process. Consultants do not authenticate with these scopes.

• https://www.googleapis.com/auth/tagmanager.readonly – "View your Google Tag Manager container and its subcomponents." We use this read-only permission exclusively to retrieve the list of Google Tag Manager accounts and containers associated with the Client's Google account, so the Client can select which ones to share with the Consultant. We do not read or store any tag configurations, triggers, variables, or other container data.
• https://www.googleapis.com/auth/tagmanager.manage.users – "Manage user permissions of your Google Tag Manager account and container." We use this permission exclusively to add the Consultant's email address as a user on the Google Tag Manager accounts and containers the Client selects. We do not modify, remove, or otherwise manage any other user permissions on the Client's account.

Data Handling Principles

• No persistent storage of tokens. OAuth access tokens are used during the Client's active session to perform the access-granting actions. They are not permanently stored on our servers.
• No secondary use. Data obtained through Google API scopes is used only for the purposes described above and is never used for advertising, data mining, or sold to third parties.
• No data retention beyond necessity. The data is used only during the Client’s active session. Lists of accounts and properties are retrieved in real time and are not cached or stored after the session ends.
• Minimal scope usage. We request only the permissions strictly necessary to list assets and grant user access. We do not request broader scopes than needed.

Revoking Access

You can revoke Access Pilot's access to your Google account at any time by visiting your Google Account Permissions page and removing Access Pilot from the list of connected applications.

Third-Party Services

We may employ third-party companies to facilitate our service (e.g., payment processors, AI generation for reports). These third parties have access to your Personal Data only to perform specific tasks on our behalf and are obligated not to disclose or use it for any other purpose.