← Back to Home

Privacy Policy

NoAdCode by ElseandIF

Last Updated: January 2026
Effective Date: January 2026

1. Introduction

ElseandIF ("we", "us", or "our"), the company behind NoAdCode, is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and protect your personal data when you use the NoAdCode platform, website (noadcode.com), WordPress plugin, and related services.

Company: ElseandIF
Address: B4-201, Nyati Evara, Nyati Estate Road, Undri, Pune, Maharashtra, India
Contact: [email protected]

2. Google User Data

NoAdCode integrates with the Google Ad Manager API to provide ad management services for WordPress publishers. This section explains how we handle Google user data.

2.1 What Google Data We Access

When you connect your Google account via OAuth 2.0, NoAdCode accesses:

  • Google Ad Manager Network Information: Your network code and network name
  • Ad Unit Configurations: Ad unit IDs, names, sizes, and settings from your GAM account
  • Basic Profile Information: Your email address for account identification

2.2 How We Use Google Data

  • To display your Google Ad Manager ad units on your WordPress website
  • To configure ad placements and targeting settings
  • To authenticate your identity and authorize access to your GAM account

2.3 Data Sharing

We do not share your Google user data with third parties. Your Google Ad Manager data is used solely to provide the NoAdCode service to you.

2.4 Data Storage & User Isolation

  • OAuth tokens are encrypted and stored securely using field-level encryption
  • Your Google password is never stored - we only use OAuth tokens
  • You can revoke access at any time through your Google Account settings

Hub Mode User-Level Isolation: In Hub Mode, OAuth tokens are stored with user-level isolation. Each publisher's Google Ad Manager data is sandboxed; one user's credentials or ad units can never be accessed, viewed, or utilized by another user of the NoAdCode platform. We use field-level encryption to ensure that even in our database, your tokens remain unreadable to unauthorized processes.

2.5 Google API Limited Use Disclosure

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

Specifically:

  • We do not use Google Ad Manager data to serve, target, or inform advertisements.
  • We do not allow humans to read your Google Ad Manager data unless we have your affirmative agreement for troubleshooting a specific support issue.
  • We do not use Google data to train AI/Machine Learning models.
  • We do not sell, rent, or lease your Google user data to third parties for any reason.

3. Other Data We Collect

3.1 Information You Provide

  • Account Information: Name, email address (via Google OAuth)
  • Business Information: Company name, website domains
  • Payment Information: Billing details processed via Razorpay (we do not store card numbers)

3.2 Automatically Collected Information

  • Technical Data: IP address, browser type, device information
  • Usage Data: API calls, feature usage, error logs

4. Data Security

We implement robust security measures:

  • Encryption: All data transmitted via TLS/HTTPS; sensitive data encrypted at rest
  • Access Controls: Role-based access and authentication
  • Token Security: OAuth tokens encrypted with field-level encryption
  • Infrastructure: Hosted on SOC 2 compliant infrastructure

5. Your Rights

You have the right to:

  • Access: Request information about your personal data
  • Correction: Request correction of inaccurate data
  • Deletion: Request deletion of your data
  • Revoke Access: Revoke Google OAuth access at any time

To exercise these rights, contact us at [email protected]

6. Contact Us

For questions about this Privacy Policy or our data practices:

Email: [email protected]
Address: ElseandIF, B4-201, Nyati Evara, Nyati Estate Road, Undri, Pune, Maharashtra, India

7. Regional Privacy Policies

For region-specific privacy information, please see: