Controlled beta

Privacy Notice

This notice describes the information practices currently supported by the Local Intelligence controlled non-paying beta.

Effective August 6, 2026

Information handled by the beta

Local Intelligence may handle information that you submit or generate while using the controlled beta.

  • Email addresses and subscription preferences.
  • Home and followed ZIP codes, saved areas, and personalization choices.
  • Technical logs, security events, and basic service-usage information.
  • First-party product analytics use random anonymous visitor and session cookies. The service stores one-way hashes, page paths, and coarse activity categories—not email addresses, ZIP codes, search terms, IP addresses, user-agent strings, query strings, or raw referring URLs.
  • When Local Brief email measurement is enabled, HTML messages may include a signed first-party image URL and signed first-party story links. The service retains only the first observed open for a delivery and the first observed click for a delivery or story. It does not store an IP address, user-agent string, raw referrer, or external destination with those observations.
  • Test-mode billing identifiers generated while validating the subscription system. Current test-mode activity does not create a real customer charge.

How information is used

Information is used to personalize local content, operate and secure the service, diagnose problems, honor subscription and unsubscribe choices, and evaluate the controlled beta.

Email-open measurements are directional because mailbox privacy features and image proxies can load images automatically, and security scanners can follow links. These aggregate signals are not treated as proof that a particular person read a message.

The controlled beta is not operated for the purpose of selling personal information.

Service providers

The service may rely on hosting, database, payment-testing, analytics, security, and email-delivery providers. Information is shared with those providers only as needed to operate or protect the service.

A future live-payment launch may require an updated notice describing live billing operations before real customer payments are accepted.

Retention and security

Information may be retained for as long as reasonably necessary to operate the beta, preserve security and billing-test records, satisfy legal obligations, or resolve disputes.

Reasonable technical and organizational safeguards are used, but no online system can guarantee absolute security.

Your choices

You may change saved areas through available product controls and use the unsubscribe link in Local Brief messages when email delivery is enabled.

New Local Brief requests require email confirmation before delivery begins. A confirmation link expires and can be used only once; opening the link alone does not subscribe the address.

During the controlled beta, privacy or deletion requests should be submitted through the same onboarding, invitation, or project-contact channel through which access was provided. A permanent public support contact must be published before paid launch.