Back to home

Privacy Policy — Micro: Pay per use

Effective date: July 2026

Micro ("Micro," "we," "us," or "our") operates the "Micro: Pay per use" Chrome extension (the "Extension"). This Privacy Policy explains what information the Extension collects, how we use it, and the choices you have.

The Extension is currently in validation mode. Its sole purpose is to discover which subscription-based websites users would want pay-per-use access to. No payments are processed, and no user account is required or created. The Extension collects minimal, mostly anonymous data to measure aggregate demand across installations.

1. Information We Collect

We have designed the Extension to collect as little as possible, and to keep most data on your own device.

1.1 Information Sent to Micro's Servers

Anonymous installation ID — a random UUID generated once on first install and stored locally as micro_user_id in chrome.storage.local. It is never linked to any personal identity. It is sent with wishlist submissions and interaction events, but not with domain-check calls.

Domain names (domain check)— on every qualifying page visit (each page that has not already been dismissed or wishlisted), the site's hostname is sent to Micro's backend to check whether it is a known partner, alternative, or blacklisted domain. This call includes only the domain name — never the full URL — and does not include the anonymous installation ID.

Domain names (interaction events) — the hostname of a visited website is also sent as part of the following interaction events:

  • The Extension detects a monetized site, at most once per domain per installation (event type: detected)
  • The overlay displays a Micro partner match (event type: partner_shown)
  • The overlay displays alternative pay-per-use options (event type: competitor_shown)
  • You dismiss the overlay (event type: dismissed)
  • You add a site to your wishlist (event type: wishlisted)
  • You click through to a partner or alternative link (event type: redirected); this event also includes the domain of the destination you clicked, as an additional field

Page title — the browser tab title, sent only when you manually add a site to your wishlist.

Site category — a classification label (one of: ai-tool, content/media, saas, education, video, other) inferred from URL structure. Sent with events and wishlist submissions.

Detected signals — URL path patterns found on the page (e.g. /pricing, /subscribe) that triggered detection. Sent only when you add a site to your wishlist.

IP address— your IP address is received by Micro's backend with every request and is used solely to enforce rate limits (for example, a maximum number of requests per minute). IP addresses are stored temporarily for this purpose and deleted within approximately 24 hours.

Anonymous diagnostic and error information — limited technical error data used to keep the Extension working. It is not linked to your identity.

1.2 Information Stored Only on Your Device

The following is stored locally in chrome.storage.local and is never transmitted to any server:

  • Full wishlist records— each local entry includes the date added and any additional metadata used by the Extension's interface. The backend receives only the domain, page title, category, and detected signals (see above); the complete local record stays on your device.
  • Per-domain dismissed flag — a boolean that suppresses the overlay for a given domain on future visits. When you dismiss the overlay, the domain name is sent to the backend as a dismissed event (see above), but the local flag that hides the overlay going forward stays only on your device.
  • Per-domain detection record (micro_detected) — a record of which domains have previously triggered detection, used to ensure the detected event is sent at most once per domain per installation, rather than on every visit.
  • Tab detection cache — temporary cached results of which open tabs have been identified as monetized, used to avoid re-running detection on every page load.

1.3 Features Available When the Product Leaves Validation Mode

Micro's roadmap includes an optional wallet and "Pay with Micro" checkout. When those features become available, we may collect information you choose to provide — such as an email address for a wallet login, wishlist and pay-per-use requests, and payment information (which would be handled by a third-party payment processor and not stored by Micro). These features do not exist today, and this policy will be updated before they are introduced.

2. Information We Do Not Collect

The Extension does not:

  • Read page body text, article content, or any other page content
  • Collect full URLs — only the domain (hostname)
  • Capture passwords or record keystrokes
  • Read your email
  • Access payment or financial information on the sites you visit
  • Record or build a history of your browsing
  • Monitor your browsing beyond matching the current domain against our list
  • Collect your name, email address, or any other personally identifiable information
  • Collect precise location

3. How We Use Your Information

All collected data is used exclusively to understand aggregate demand — which types of subscription sites users would most want pay-per-use access to. This informs product decisions about which vendors to work with first. Specifically, we use data to:

  • Detect whether a site you visit is a known partner, alternative, or blacklisted domain, and display an optional notification
  • Record anonymous interest signals (detections, wishlist additions, dismissals, redirects) to measure demand
  • Enforce rate limits and protect the service from abuse
  • Diagnose and fix errors and improve the Extension

We do not perform individual-level profiling.

4. Chrome Extension Functionality

The Extension checks the current site's domain against Micro's partner and alternatives list and, when there is a match, displays an optional overlay. It does not read page content, does not automatically redirect you, and takes no action beyond what is described in this policy. You can dismiss the overlay at any time, and it will not reappear for that domain.

5. Vendor Wishlist and Aggregated Sharing

When you add a site to your wishlist, that interest is recorded to measure demand. We may share aggregated, non-identifiable statistics with vendors — for example, "127 users requested pay-per-use access to your product."

We do not share your identity, email, anonymous installation ID, or individual browsing activity with vendors.

6. Data Sharing

We do not sell, rent, or trade your information. Data is sent only to Micro's own backend, with the following limited exceptions:

  • Google Fonts— when the overlay is displayed, the Extension loads the DM Sans font from Google Fonts (fonts.googleapis.com). This sends a request to Google's servers, which may receive your IP address. Micro does not control Google's data practices; see Google's Privacy Policy for details.
  • Cloud infrastructure — our backend runs on cloud hosting infrastructure (Cloudflare) that processes requests on our behalf.
  • Legal requirements — we may disclose information if required to do so by law or valid legal process.

We do not share data with advertisers, analytics brokers, or data resellers.

7. Cookies and Analytics

The Extension does not use cookies, and our backend (Cloudflare Workers) does not set traditional tracking cookies. We do not use third-party analytics or advertising SDKs. The only identifiers involved are the anonymous installation ID described in Section 1 and your IP address, used solely for rate limiting.

8. Data Retention

  • Wishlist submissions— individual records (including the anonymous installation ID, domain, page title, and category) are retained indefinitely. This is Micro's core demand-validation dataset.
  • Domain aggregate statistics — per-domain records tracking detection count, wishlist count, category, and first/last-seen timestamps are retained indefinitely.
  • Raw interaction events — individual event records are aggregated into anonymous counts, and the individual records are deleted within approximately 48 hours of collection.
  • IP addresses — deleted within approximately 24 hours.
  • Local extension data — wishlist entries, dismissed-site flags, detection records, and cached data stored on your device are permanently deleted when you remove the Extension.

We retain information only as long as necessary for the purposes described in this policy, and securely delete or anonymize it when it is no longer needed.

9. Security

We take reasonable measures to protect your information, including encryption in transit (HTTPS), secure cloud infrastructure, access controls, and security monitoring. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.

10. Your Rights

Depending on where you live, you may have rights under laws such as the GDPR and the CCPA/CPRA, including the right to access, correct, delete, or receive a copy of your personal information, to object to or restrict certain processing, and to withdraw consent. If we ever offer marketing communications, you will be able to opt out.

Because the Extension collects almost no personal information and the anonymous installation ID is never linked to your identity, in practice:

  • You can clear all locally stored data at any time by removing the Extension from Chrome.
  • We have no way to locate or delete backend data on a per-user basis, because there is no personal record tied to you to identify.

If you have questions about your rights, contact us using the details in Section 13.

11. Children's Privacy

The Extension is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us with information, please contact us and we will take appropriate steps to delete it.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will revise the effective date above and post the updated policy. Material changes — including any expansion of data collection as new features (such as a wallet or checkout) launch — will be reflected here before those features take effect. Your continued use of the Extension after an update constitutes acceptance of the revised policy.

13. Contact Us

If you have questions about this Privacy Policy or how your data is handled, contact us at team@trymicro.io.