This page explains what information Orbit may handle when you use the product. It is not a full legal privacy policy for every jurisdiction.

Orbit may process account information, prompts, source URLs, dashboard content, analytics events, logs, and technical information. The exact data depends on how you use the product.

Information Orbit may handle

Account and authentication data

If you create an account or sign in, Orbit may process account and authentication information, such as:

• email address
• login state
• user identifier
• authentication provider details
• basic profile information supplied by a sign-in provider

If you use a third-party sign-in provider, such as Google sign-in, that provider may also process information according to its own policies.

Dashboard content

If you create, view, debug, share, or manage dashboards, Orbit may process dashboard-related data, such as:

• prompts or topic requests
• supplied source URLs
• generated titles and descriptions
• dashboard components
• source lists
• source previews
• source scores and score explanations
• update feed entries
• maps, embeds, videos, or social feed configuration
• dashboard identifiers and owner identifiers
• sharing or visibility details

Do not put private, confidential, sensitive, or regulated information into prompts or dashboards unless you are comfortable with how that information may be processed and displayed.

Source material

Orbit fetches or receives source pages to build dashboards. Source-related data may include:

• original source URLs
• redirected or resolved URLs
• page titles
• extracted text snippets
• source details
• publication or update timestamps
• image URLs, captions, alt text, or nearby source text
• structured live-update entries
• source-fetch details

Orbit does not control third-party publisher websites. When you open a source link, you leave Orbit and interact with that publisher or platform directly.

Analytics and product events

Orbit may collect analytics and product events to understand usage and improve the service. These events may include:

• page views
• dashboard views
• source panel opens
• source link clicks
• share actions
• authentication flow events
• waitlist submissions
• feature flag checks
• browser performance signals
• error or failure events

Analytics events may include contextual properties such as dashboard ID, dashboard title, source domain, source URL, browser context, timestamps, or feature state. Orbit uses analytics to understand product behavior, reliability, and user experience.

Orbit separates public and authenticated analytics. Public pages, such as documentation and public dashboard views, use PostHog in cookieless mode without a persistent app identity. Authenticated app analytics only uses a persistent PostHog distinct ID and person-profile behavior after analytics consent is accepted. If analytics is rejected, Orbit opts out of PostHog capture and clears the stored PostHog distinct ID. Session recording is disabled.

Logs and troubleshooting

Orbit may create operational logs for:

• source collection
• source fetching
• source tagging
• dashboard creation
• AI request timing
• failures and exceptions
• performance measurement
• abuse prevention
• debugging and reliability work

Logs may include prompts, source URLs, domains, timing information, error messages, and compact details about failed or slow requests. When failures occur, stack traces or troubleshooting information may be printed or recorded.

How Orbit uses information

Orbit uses information to provide and improve the service.

This includes:

• signing users in
• rendering dashboards
• retrieving source pages
• extracting and ranking source evidence
• creating dashboard components
• showing source links and scoring details
• supporting shared or public dashboards
• measuring reliability and performance
• diagnosing failures
• preventing abuse
• improving product quality

Orbit may also use aggregated or troubleshooting data to understand source-quality problems, AI output issues, or product bottlenecks.

AI processing

Orbit may send prompts, source evidence, source details, and dashboard instructions to AI providers to create dashboard components or support source processing. The provider setup may change over time.

Those requests may include extracted source snippets, source reference identifiers, image references, source titles, domains, and current-time context needed for timestamp interpretation.

Orbit may also use custom ML models and classifiers for source-quality, evidence, live-update, media, and ranking-related tasks. These models may process source text, source URLs, page structure, image context, timestamps, and dashboard prompts as part of providing the service.

You should assume that any prompt or source material used to create a dashboard may be processed by infrastructure and model providers involved in that workflow.

Public and shared dashboards

If a dashboard is public or shared, people with access may see:

• dashboard title
• generated dashboard content
• source links
• source previews
• source scoring details
• embedded media or external components
• timestamps or update information

Because of this, avoid including private information in prompts, source URLs, dashboard titles, or generated dashboard content unless that dashboard is intended for the audience that can access it.

Cookies and local storage

Orbit may use cookies, local storage, or similar browser storage for:

• authentication state
• analytics consent state
• analytics identifiers for consented app analytics
• feature flags
• debugging preferences
• app state

For example, consented app analytics may use a distinct identifier to understand product usage, while public analytics is configured to avoid persistent identity. Authentication providers may use their own browser storage.

Third-party services

Orbit may rely on third-party services for functions such as:

• authentication
• hosting
• storage
• analytics
• AI model processing
• search and source discovery
• external source fetching
• embeds, video, maps, social feeds, or favicons

Third-party providers may process information according to their own terms and privacy practices. When you click an external source, watch an embedded video, open a map, or interact with a social feed, you may also be interacting with those third parties.

Retention

Orbit may retain information for as long as needed to:

• operate the service
• maintain accounts
• preserve dashboards
• support shared links
• investigate failures
• improve reliability
• prevent abuse
• comply with legal obligations
• resolve disputes

Retention periods can vary by data type. For example, a saved dashboard may persist longer than a transient source-fetch diagnostic. Analytics and logs may be retained according to operational needs and provider settings.

Your choices

You control much of what you submit.

Practical steps:

• avoid entering private or confidential information into prompts
• avoid supplying private URLs unless the dashboard should process them
• be careful before sharing dashboards publicly
• use available dashboard controls to edit, delete, or limit visibility where provided
• sign out when using shared devices
• review original source sites before interacting with them

If Orbit provides account or dashboard deletion controls, those controls are the first place to manage stored content.

Security

Orbit uses ordinary technical and organizational measures to operate the service. No internet service can guarantee perfect security. Users should keep account credentials secure and avoid submitting sensitive material unless necessary.

Children's data

Orbit is not for use by young children. Users should not knowingly submit children's personal information into prompts or dashboards.

Changes

Orbit may update this page as the product evolves. Source handling, analytics, providers, account features, and dashboard behavior may change. When changes materially affect how information is handled, this page may be revised.