Deltamath Modifier Privacy & data practices
Privacy policy Written like we actually respect you.

A real privacy policy.
No dark patterns. No tracking games.

This page explains, in detail, what the Deltamath Modifier extension does with your data: basically nothing. No sneaky collection, no weird telemetry—just what is required to operate a visual-only Chrome extension and read anonymous analytics that Google itself aggregates.

Chrome-compliant · GDPR · CCPA Extension scope: client-side UI only
No personal data stored
Purely cosmetic overlay logic
Data snapshot What we actually keep
Zero tracking
Local setting: enabled / disabled Stored in chrome.storage
Personal info: Not collected
Browsing history: Not collected
Passwords, messages, grades: Never touched

Privacy Policy

This is the full, detailed privacy policy for the Deltamath Modifier Chrome extension. It is written to be transparent, Chrome-store-friendly, and brutally clear about what does and does not happen with your data.

Last updated
[Insert Date]
Developer: [Your Name / Org]

1. Introduction

This Privacy Policy describes how this browser extension (“the Extension,” “we,” “our,” or “us”) handles information, including data that may be provided through aggregated analytics made available by the Chrome Web Store Developer Dashboard. The Extension itself does not directly collect, store, transmit, process, or analyze personal information or sensitive data from users. Instead, certain high-level, non-identifying, aggregated analytics categories may be provided automatically by Google as part of the Chrome Web Store’s developer insight tools.

We are committed to transparency, user safety, and adherence to global privacy regulations, including the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), and other relevant standards. This document explains what information we may receive, how such information is used, and what rights and controls users maintain.

This Privacy Policy governs your use of the Extension available on the Chrome Web Store. The Extension is designed to operate within the user’s browser environment without collecting or transmitting user data. The Extension performs only client-side interface adjustments and does not communicate any personal or browsing information to our servers, because we do not operate servers or remote data endpoints.

However, Google may provide anonymized, aggregated analytics to extension developers for the purposes of understanding general usage metrics, performance insights, or broad behavioral categories. These analytics categories may include:

  • User Activity
  • Website Content
  • Personally Identifiable Information (PII) classifications

These analytics categories reflect Google’s categorization of aggregate metrics only and do not indicate that the Extension collects or stores data itself. This policy is intended to clarify these practices fully, openly, and without ambiguity.

2. What Data the Extension Itself Collects

2.1 Direct Data Collection by the Extension

The Extension does not directly collect:

  • Personal data
  • Browsing history
  • User input
  • Keystrokes
  • Mouse movements
  • Scroll data
  • Network details
  • Account information
  • Cookies
  • IP addresses
  • Device identifiers
  • Demographic information
  • Website content
  • Images, text, or videos displayed on websites

The Extension does not monitor, intercept, record, log, or transmit any such information.

2.2 Local-Only Settings

The only information stored locally is:

  • A boolean toggle setting (“enabled” or “disabled”)

This value:

  • Remains entirely within chrome.storage.sync/local
  • Is not transmitted off the device
  • Is not shared with anyone
  • Contains no identifiable data
  • Is user-removable at any time

3. Google Chrome Web Store Aggregate Analytics

3.1 What These Analytics Are

The Chrome Web Store may provide developers with anonymous, aggregated analytics. These do not include identifiable user data. Instead, they categorize user behavior into high-level buckets, such as:

  • User Activity (e.g., extension install, open rate)
  • Website Content Interactions (in aggregate)
  • PII Categories (only as classification labels in analytics dashboards)

These analytics represent Google’s internal categorization, not data collected by the extension.

3.2 Examples of Analytics Categories Provided

Chrome Web Store analytics may show:

  • Number of installations
  • Number of uninstalls
  • Number of active users
  • Region-level aggregated data
  • Chrome version usage
  • Generic interaction metrics
  • Aggregate “interest categories” related to Google accounts

These DO NOT include:

  • Names
  • Email addresses
  • Exact browsing data
  • Messages
  • Passwords
  • Form entries
  • Individual identities
  • Personal behavioral histories

3.3 Purpose of These Analytics

We may use the anonymized analytics provided by Google to:

  • Improve extension stability
  • Identify performance issues
  • Understand general usage patterns
  • Determine compatibility with browser versions
  • Analyze installation trends
  • Guide feature updates
  • Improve localization decisions
  • Provide better support experience

All analytics remain fully anonymized and aggregated.

3.4 Opt-Out from Analytics

Users may prevent Google from providing analytics indirectly through:

  • Adjusting Google Account ad personalization settings
  • Restricting Chrome usage reporting
  • Using Chrome’s “Do Not Track” options
  • Blocking third-party cookies

4. Types of Data Categories Google May Classify

4.1 User Activity Category

This may include aggregated metrics like:

  • Number of times the extension icon is clicked
  • Number of active sessions
  • Usage frequency
  • Installation and uninstall counts
  • Device OS distribution
  • Browser versions

The extension itself does not record activity. This is purely Google’s anonymous reporting.

4.2 Website Content Category

Google may categorize browser environments into high-level classifications, such as:

  • Commonly visited content categories
  • Types of pages where extensions are enabled
  • Aggregate content interactions

This category does not contain site content, text, images, user messages, uploads, or downloads.

The Extension never reads page content beyond identifying UI elements necessary for functionality and never stores or transmits anything.

4.3 Personally Identifiable Information (PII) Category

This category does not mean PII is collected. It refers to Google’s internal label describing whether an extension could theoretically interact with PII-heavy environments.

The Extension itself:

  • Does not access PII
  • Does not process PII
  • Does not handle user accounts
  • Does not require login
  • Does not interface with third-party profiles
  • Does not transmit PII anywhere

Google may still place the extension into this analytics category based on webpage contexts where the extension may operate, not based on actual data collection.

5. How Data Is Used

5.1 Extension Functionality

All interface modifications performed by the Extension occur locally and do not rely on collected data.

5.2 Analytics Usage

Any analytics available via Chrome Web Store:

  • Are anonymous
  • Cannot identify users
  • Cannot be reverse-engineered
  • Are processed and controlled by Google
  • Are used strictly for extension improvement

We do not sell, share, trade, license, or distribute any analytics data.

6. Legal Basis for Data Handling

6.1 GDPR Compliance

Even though we do not collect personal data, we adhere to GDPR principles:

  • Lawfulness, fairness, transparency
  • Data minimization
  • Purpose limitation
  • Accuracy
  • Storage limitation
  • Integrity and confidentiality

6.2 CCPA / CPRA Compliance

Under California law:

  • We do not “sell” personal data
  • We do not collect personal information
  • Users do not need opt-out mechanisms for data selling
  • No advertising identifiers are collected
  • Analytics remain anonymized

6.3 Children’s Online Privacy Protection Act (COPPA)

The Extension:

  • Is not targeted to children
  • Does not collect age, birthdates, or demographic data
  • Is safe for general audiences
  • Contains no tracking

7. Data Retention

7.1 Local Data

Only the “enabled/disabled” toggle is stored. Users can delete it by:

  • Resetting Chrome sync
  • Clearing extension storage
  • Uninstalling the extension

7.2 Analytics Retention

Analytics retention is fully controlled by Google. We have no ability to access raw data or modify retention periods.

8. Data Deletion / User Rights

Users maintain the right to:

  • Remove the extension at any time
  • Delete all locally stored data
  • Disable Chrome sync
  • Clear Chrome’s storage
  • Restrict analytics sharing at the Google Account level

Under GDPR:

  • Right to access
  • Right to restrict processing
  • Right to erasure
  • Right to data portability
  • Right to object
  • Right not to be subject to automated decision-making

Since we do not collect identifiable data, these rights apply to analytics only insofar as Google provides the mechanisms.

9. Security Practices

9.1 Extension-Level Security

The Extension:

  • Contains no remote code execution
  • Does not load remote scripts
  • Operates fully locally
  • Contains no telemetry endpoints
  • Performs no external network communication
  • Has no server-side infrastructure

9.2 Google's Security Measures

All analytics are:

  • Aggregated
  • Anonymized
  • Filtered through Google’s internal privacy systems
  • Protected by industry-standard safeguards

10. Third-Party Sharing

We do not share analytics with:

  • Advertisers
  • Data brokers
  • Affiliates
  • Third-party platforms
  • Government agencies
  • AI training datasets
  • External service providers

The only “third party” involved is Google, which provides analytics.

11. Changes to This Policy

We reserve the right to update this Privacy Policy to:

  • Comply with new laws
  • Improve clarity
  • Reflect changes in extension behavior
  • Reflect changes in Google’s analytics categories

Users will be notified through the Chrome Web Store listing page.

12. Contact Information

For privacy questions, concerns, or requests:

  • Email: [Your Contact Email Here]
  • Developer: [Your Name or Organization]

We will respond to all inquiries in compliance with applicable regulations.

13. Summary

In plain language:

  • The Extension does not collect personal data.
  • Google may provide anonymous, aggregate analytics.
  • We do not access, store, or transmit sensitive information.
  • All analytics are used solely for performance and improvement.
  • Users retain full control over their data via browser and Google account settings.
This Privacy Policy ensures full compliance with Chrome Web Store requirements and global privacy standards, while being honest about what actually happens in this extension: a visual glow-up for Deltamath, and nothing else.