Privacy Policy

Effective date: November 9, 2026

Digg Inc. ("Digg," "we," "us," or "our") runs Digg at https://digg.com. Digg Inc. is registered in Delaware and has offices in California.

This policy explains what we collect, how we use it, and the choices you have. It applies to Digg and related services. It does not apply to X, GitHub, or other third-party sites we link to or use as public data sources.

What We Collect

We collect the following types of information:

  • Public information from online sources. Digg collects and analyzes public information from services like X and GitHub, including public profiles, usernames, display names, bios, avatars, public posts, replies, reposts, quotes, media metadata, links, engagement counts, public follow or interaction signals, public GitHub profiles, repositories, stars, follows, and public activity.
  • Information we create from public data. We generate rankings, topic clusters, labels, summaries, sentiment signals, vibe/topic scores, embeddings, category tags, and other product signals from public information.
  • Visitor and device information. When you visit Digg, we may collect IP address, browser and device information, referring pages, pages viewed, clicks, searches, filters, approximate network-derived location, performance data, error reports, and similar usage information.
  • Advertising and sponsorship information. If Digg displays ads, sponsorships, or paid placements, we and our ad-serving providers may process information such as ad placement identifiers, impression and click events, approximate timing, referring page, device and browser information, IP address, and similar delivery, measurement, pacing, fraud-prevention, and reporting data.
  • Search information. If you use search, we process your search terms to return results. Story search queries may be sent to OpenAI to create a search embedding.
  • Account and profile information. If you create or use an account, we process your email address, sign-in and session information, user ID, application role, and profile information you provide, such as your username, display name, bio, avatar, and connected accounts. We use Clerk for authentication.
  • Your activity and contributions. We process the Topics and people you follow, your Diggs, saved items, comments, and other information you choose to submit. Public profile information and public contributions are visible to other people.
  • Comments and discussion activity. We collect comments and replies, including pending submissions and edits, mentions, Comment Diggs, reports and optional report notes, records of screening and moderation decisions, and a record of when you accepted our Terms, which confirms you meet their age requirement, with the version you accepted.
  • Newsletter information. If you subscribe, we process your email address, subscription preferences, and delivery information to send the newsletter and manage your subscription.
  • Information you send us. If you contact us, we collect your contact details and message.

We do not ask visitors to provide payment information, government ID numbers, or sensitive personal information through the public Digg site. Because Digg analyzes public posts and profiles, public-source data may include information that the source user chose to make public.

How We Use Information

We use information to:

  • operate Digg and show public rankings, stories, profiles, clusters, and feeds;
  • search, classify, summarize, rank, and group public content;
  • keep the service secure, reliable, and fast;
  • understand usage, fix bugs, measure performance, and improve the product;
  • deliver, measure, pace, report on, and improve ads, sponsorships, promoted placements, and paid partner messages;
  • authenticate accounts, apply access controls, and provide profile and participation features;
  • send requested newsletters and service communications;
  • provide discussion features, publish eligible comments, evaluate reports, enforce our rules, and review moderation decisions;
  • prevent abuse, including rate limiting public search;
  • comply with law and enforce our rights.

Our public rankings and AI-generated signals are editorial and product features. We do not use them to decide employment, credit, housing, insurance, or similar legal rights.

Where data protection law requires a legal basis, we rely on your consent for optional browser analytics, audience insights, and newsletter subscriptions; performance of our agreement with you for requested account and service features; our legitimate interests in operating, securing, and improving Digg, including cookieless audience measurement, and presenting public-source information; and legal obligations where applicable. You can decline optional cookies and still use Digg. Withdrawing consent does not affect processing that was lawful before withdrawal.

AI Processing

Digg uses AI services to classify public accounts, summarize public posts and linked articles, describe public media, generate topic labels, score public content, and power search. These services may include, but are not limited to, xAI, OpenAI, Anthropic, Google Gemini, Typesafe, and other AI providers.

Inputs to these systems can include public posts, public profile information, public GitHub information, linked article text, media metadata, and search queries. We also use safeguards to avoid sending secrets and to reduce unnecessary capture of raw prompts or outputs in our telemetry.

We also use AI service providers to screen comments and replies, including submissions and edits that have not been published. Screening inputs can include the submitted text, the post's context, relevant earlier comments, and the category of a report. Automated screening may affect whether text is published, held for review or removed. We retain screening results and operational records for moderation and reliability purposes as described below.

Cookies and Local Storage

Digg uses cookies and local storage for:

  • sign-in and session management;
  • security and rate limiting;
  • preferences such as theme, sidebar state, and view settings;
  • analytics, performance measurement, and error reporting;
  • advertising and sponsorship delivery, frequency management, measurement, fraud prevention, and reporting.

Our cookie notice lets you accept optional collection, use only necessary cookies, or manage two categories: Usage analytics and Audience insights. Until you opt in, including if you choose only necessary cookies, we count visits and activity on Digg with PostHog in the cookieless mode described below. All other optional browser analytics, and all recordings, stay off until you opt in. Audience insights requires Usage analytics. You can change or withdraw your choices at any time using Cookie preferences in the site footer. Withdrawing consent reloads the page to stop previously loaded measurement scripts.

We remember this browser's choices in the required digg_consent cookie for up to 180 days, without storing your name, email address, or account ID in that cookie. After it expires, we ask again. If you are signed in, we also save your choices to your Digg account and apply them on other browsers and devices where you sign in, so you are not asked again there; the most recent choice you make on any of them applies to all of them, including a withdrawal. Choices made while signed out apply only to that browser until you sign in. Choices saved to your account also expire 180 days after you make them, and are deleted with your account. You can also control cookies through your browser settings. Some features may not work correctly if required cookies are blocked.

Key browser storage used for these choices and optional measurement includes:

  • digg_consent — Digg’s required cookie for your choices; up to 180 days.
  • _ga and _ga_* — Google Analytics browser and session cookies, set only with Usage analytics consent. Google’s default is up to two years; browser limits may shorten this.
  • ph_* cookies and local storage — PostHog browser and session identity and analytics state, set only with Usage analytics consent. The cookie default is up to 365 days; local storage lasts until cleared.
  • __ph_opt_in_out_* — a PostHog local storage flag that keeps PostHog in cookieless mode until you opt in. It contains no identifier and lasts until cleared.
  • digg_last_session_at — Digg’s returning-visit measurement cookie, set only with Usage analytics consent; up to 30 days.
  • digg_sponsor_frequency — Digg’s optional sponsorship frequency cookie, set only with Usage analytics consent; up to 30 days.

Sign-in, security, and interface-preference storage also support the features you request. Browser cookie lifetimes are different from server-side data retention. Declining or withdrawing optional consent clears known first-party analytics storage, including the items above other than the required choice cookie and PostHog’s cookieless flag. Local storage has no automatic browser expiry, but Digg clears its known optional analytics entries when consent expires or is withdrawn. Google and other providers describe their own storage in their cookie information and browser-persistence documentation.

Analytics, Advertising Measurement, and Error Reporting

Without Usage analytics consent, PostHog measures page views and interactions in cookieless mode. Digg stores no PostHog identifier in your browser. PostHog counts visitors using a hash of your IP address, user agent, and a value that changes daily and is then deleted, so the same visitor appears as someone new each day. We do not identify you, record your session, or link this measurement to your Digg account. You can stop it with browser tools that block analytics.

With Usage analytics consent, we use Google Analytics, PostHog, Plausible, and Vercel Analytics/Speed Insights to understand traffic, performance, and product usage. This includes sampled session recordings through PostHog and Sentry, and optional sponsorship measurement and frequency cookies. Google Analytics may use first-party cookies such as _ga to recognize a browser and measure sessions, pageviews, interactions, referrers, browser and device information, and approximate network-derived location for product analytics. Basic error reporting, security, sign-in, contextual sponsor delivery, and service operations continue with only necessary cookies. Our error reporting setup is designed to avoid sending sensitive values like passwords, tokens, cookies, authorization headers, raw AI prompts, and raw AI outputs.

With Audience insights consent, we use Google Analytics Demographics and Interests reporting through Google signals to understand our audience in aggregate. For eligible visitors signed in to Google who have enabled Ads Personalization, Google may associate activity on Digg with Google account information, using first-party Analytics cookies or identifiers together with Google advertising cookies or identifiers. The resulting reports can include age ranges, gender, and interests; Digg does not receive individual Google account identities from these reports. Digg keeps advertising personalization disabled for its Analytics events. Google analytics storage and advertising-related collection remain denied worldwide unless you choose the corresponding optional category. You can control Google's Ads Personalization in My Ad Center, manage associated activity in My Activity, or use the Google Analytics opt-out browser add-on.

Sentry session replay, when enabled, masks text and inputs and blocks media by default.

If we use an ad server or sponsorship measurement provider, such as AdButler or a similar provider, that provider may process limited delivery and measurement data for Digg's ads and sponsored placements. Our current intent is to support contextual, placement-based, or sponsorship-based advertising rather than cross-context behavioral advertising. If we begin using personal information for cross-context behavioral advertising, sale, or sharing as those terms are defined by applicable privacy laws, we will update this policy and provide any legally required choices.

When We Share Information

We share information with:

  • service providers that help us run Digg, including Supabase, Vercel, Vercel Blob, Clerk, Trigger.dev, Resend for email delivery, Google Analytics, Google, PostHog, Sentry, OpenAI, xAI, Anthropic, Google Gemini, Typesafe, other AI providers, Upstash, Iframely, and ad-serving or sponsorship measurement providers such as AdButler;
  • public data sources and APIs, such as X and GitHub, when needed to fetch or validate public information;
  • the public, when we display public-source information or derived Digg signals on pages, APIs, feeds, or other product surfaces;
  • other readers and connected applications, when we display published comments, replies and associated public profile details on the Digg website or through Digg's public API and tools;
  • authorities or others when required by law, security, fraud prevention, or to protect rights;
  • a successor organization if Digg is involved in a merger, acquisition, financing, reorganization, or sale of assets.

Pending or held submissions and reports are not displayed publicly. Authorized personnel and relevant service providers may access them as needed to operate and moderate Digg. Copyright notices and counter-notices, including contact details, may be shared with the parties involved as described in our Terms of Service.

We do not sell personal information. We do not use personal information for cross-context behavioral advertising.

Retention

We keep information for as long as reasonably needed for the purposes above. Public-source content and derived Digg signals may be kept while useful for rankings, product history, research, debugging, or abuse prevention. Account information is kept while needed to provide your account and handle security, legal, or service obligations. Newsletter subscription information is kept while needed to deliver the subscription and maintain unsubscribe preferences. Telemetry and logs are kept for a limited period appropriate for security, debugging, and reliability.

Removing content from public display, closing an account and erasing personal information are different actions. When you delete a comment, its text is removed from public display, but a placeholder may remain to preserve replies. Account closure may leave published discussion text without account attribution. That text may still identify you if it includes personal information. Copies retained by other people are outside our control.

We may retain submissions and revisions, reports, screening results and moderation records for as long as reasonably necessary to investigate abuse, review decisions, prevent repeated violations, comply with legal obligations or resolve disputes, subject to applicable law. Retention depends on the record's purpose, whether a report or dispute remains open, applicable legal requirements and the continuing need to protect the service. Public hiding or suspension does not itself erase these records. You may request deletion of personal information using the contact information below. When we erase comment text on request, we remove it and its earlier versions from our database and blank report notes you wrote. Erasure does not reach copies in backups or evaluation records, copies already held by service providers or by AI tools our moderators use, copies others made, moderators' own notes, or text subject to a pending court action over copyright.

Google Analytics user-level and event-level data retention is set to two months, without extending user-data retention when you return. Standard aggregated reports are not governed by that setting. Withdrawing cookie consent stops future optional collection; it does not itself delete information already sent to a provider. You can request deletion through the contact below, subject to applicable rights and exceptions.

Some rate-limit records are intentionally short-lived. For example, story search rate-limit keys are designed to expire quickly.

Your Choices and Rights

You can:

  • use browser controls to limit cookies and local storage;
  • contact us to request access, correction, deletion, or removal of information you provided to us;
  • where applicable, request a portable copy of your information, restrict processing, or object to processing based on legitimate interests;
  • withdraw optional cookie consent through Cookie preferences and unsubscribe from newsletters using their unsubscribe link;
  • contact us if Digg shows a public profile or public-source item about you that you believe is incorrect or should be removed from Digg.

We may need to verify your identity before acting on a request. Removing information from Digg does not remove it from the original public source, such as X or GitHub. We may also keep limited records when needed for security, legal compliance, or to complete your request.

Send privacy requests to legal@digg.com. We will respond within the period required by applicable law. You may also lodge a complaint with your local data protection authority. Exercising applicable privacy rights will not result in discrimination.

California Privacy Note

California residents may have the right to know, access, correct, delete, or receive information about certain personal information, and to be free from discrimination for exercising privacy rights. California residents may also opt out of "sale" or "sharing" of personal information, but Digg does not sell personal information or share it for cross-context behavioral advertising.

You or your authorized agent can make a request using the contact information below.

Security

We use technical and organizational safeguards to protect information, including access controls, server-side secrets, row-level security where applicable, service-role restrictions, telemetry scrubbing, and limited admin access. No system is perfectly secure.

Children

Our Terms of Service require users to be at least 14 years old. Digg is not directed to children, and we do not knowingly collect personal information from children under 13. Contact us at legal@digg.com if you believe a child under 13 has provided personal information so we can investigate and take appropriate action.

International Users

Digg is operated from the United States. If you use Digg from outside the United States, your information may be processed in the United States and other countries where we or our providers operate.

Changes

We may update this policy from time to time. The effective date above shows when it was last updated.

A Friendly Note From the Team

We value your privacy. We do not sell personal information, and we use the information we collect to operate Digg, keep it reliable, understand what is working or breaking, and improve the product experience.

If you are reading this, privacy probably matters to you, and we understand that. We use analytics, error reporting, infrastructure, and AI service providers because they help us see where Digg can be faster, clearer, safer, and more useful. Our goal is to serve you the stories and product experience you are looking for, not to use your information in ways that are unrelated to Digg.

Contact

Digg Inc.
Registered in Delaware; offices in California
Email: legal@digg.com
Website: https://digg.com