Privacy Policy

Last updated: January 10, 2026

Our Commitment to Privacy

At Macroid, we believe your data belongs to you. This privacy policy explains exactly how we handle your information—or more accurately, how we don't handle it, because we never collect it in the first place.

Information We Collect

None. We don't collect, transmit, or store any personal information on our servers because we don't have servers. Everything happens locally on your device.

What We Don't Collect

  • ❌ Your macro content or text
  • ❌ Websites you visit
  • ❌ Your browsing history
  • ❌ Keystrokes or typing patterns
  • ❌ Email addresses or contact information
  • ❌ IP addresses or location data
  • ❌ Usage analytics or telemetry
  • ❌ Any personal information whatsoever

How Your Data is Stored

All macro data is stored locally on your device using Chrome's built-in Storage API. Specifically:

Local Storage

  • Macro text: The content of your text macros
  • Macro labels: The names you assign to macros
  • Macro IDs: Unique identifiers for organization

This data never leaves your computer unless you choose to enable Chrome Sync (explained below).

Chrome Sync Storage

If you have Chrome Sync enabled in your browser settings, Google may sync your macros across your devices. This is:

  • Controlled entirely by your Chrome settings, not our extension
  • Encrypted by Google during transmission
  • Subject to Google's Privacy Policy, not ours
  • Completely optional—you can disable sync in Chrome settings

Permissions Explained

Chrome extensions require certain permissions to function. Here's exactly what we use and why:

Storage Permission

Why we need it: To save your macros locally on your device using Chrome's Storage API.

What we do with it: Store macro text, labels, and IDs. Nothing else.

ActiveTab Permission

Why we need it: To inject macros into the currently active tab.

What we do with it: Detect text fields and insert your chosen macro text. We don't read or transmit page content.

All URLs Permission (<all_urls>)

Why we need it: So the macro bubble can appear on any website you choose to use it on.

What we do with it: Display our UI bubble when you focus on text fields. We don't track which sites you visit or collect any data from them.

Data Sharing

We don't share data because we don't collect data. There are no third-party analytics, no tracking pixels, no advertising networks. Nothing.

Data Security

Since your macros are stored locally on your device using Chrome's secure storage API:

  • They're protected by your Chrome profile's security
  • They're isolated from other extensions via Chrome's sandboxing
  • They're only accessible when you're logged into your Chrome profile

If you use Chrome Sync, your synced data is encrypted by Google during transmission and storage.

Your Rights

You have complete control over your data:

  • Access: All your macros are visible in the side panel at any time
  • Modify: Edit or update macros whenever you want
  • Delete: Remove individual macros or uninstall the extension to delete everything
  • Export: Use Chrome DevTools to backup your macros (see our support guide)

Children's Privacy

Macroid doesn't knowingly collect any information from anyone—including children under 13. Since we don't collect any data at all, COPPA compliance is inherent in our design.

Changes to This Policy

If we ever change how we handle data (which is unlikely since we don't handle it), we'll update this policy and notify you through the extension. The "Last updated" date at the top will reflect any changes.

Open Source (Coming Soon)

We plan to make Macroid fully open source so you can inspect the code yourself and verify our privacy claims. Follow our development on GitHub (link coming soon).

Contact Us

Have questions about privacy? We're happy to answer them:

Summary

TL;DR: We don't collect, transmit, or store any of your data. Your macros live on your device, encrypted by Chrome's built-in security. We have no servers, no analytics, no tracking. Your privacy is guaranteed by our architecture, not just our promises.

This privacy policy is written in plain English because we believe transparency shouldn't require a law degree. If something is unclear, please let us know.