Privacy policy

Information we handle

Account and developer details may include name, verified email, Clerk identifier, role, API-key metadata and security events. Reader services may include newsletter choices, comments, tips, alert-device tokens or browser push endpoints and encryption keys, saved preferences, approximate region, request logs and privacy requests. Audience totals use a random or app-scoped pseudonymous installation identifier, Web/iOS/Android/tvOS/Android TV/Roku platform, product, release channel, app version, build number, broad device and operating-system class, account link when authenticated, and first/last-active timestamps. With analytics consent, public page and story views are assigned a random event ID, installation ID and session ID so duplicate requests can be rejected and reported totals can be audited. Page-view events are not connected to a Clerk account and do not contain an advertising identifier, IP address or raw user agent. The referring page is reduced to a broad acquisition category such as Google, X, Facebook, Instagram, email, direct or other, and the raw referring URL is discarded. A broad device class such as desktop, phone, tablet or smart TV is retained with those event records and aggregate counters. Pre-audit aggregate statistics are retained as labeled legacy evidence and are excluded from verified totals. We do not store raw developer API keys after creation. Device sign-in handles short-lived pairing status, hashed sync codes and requester network information for abuse prevention. Apple TV, Android TV and Roku sessions retain account, device, expiry and last-active metadata; raw device tokens are not stored. Media press-kit requests may include the requester’s professional name, organization, role, work email, supplied websites, country or jurisdiction, project, intended use, publication destination and timing, requested materials, intake conversation, policy decision, review history, generated license and package/download events. The system stores hashed—not raw—request and download credentials and a keyed hash of the requester network address for abuse prevention.

Why and how we use it

We use data to deliver news, authenticate accounts, operate the newsroom, securely connect browsers and televisions, send requested alerts, moderate participation, prevent abuse, measure platform adoption and reliability, satisfy legal obligations and improve services. Production counsel must document the applicable legal basis for each market, including consent, contract, legitimate interests and legal obligation where relevant. Press-kit request information is used for package generation, abuse prevention and appropriate media-relations follow-up; it is not added to a marketing list without separate consent.

Processors and transfers

The planned service uses Vercel for hosting and media, Neon for Postgres and Clerk for identity. Upstash handles developer and Press Kit rate limits. When configured, Cloudflare Workers AI processes a minimized Press Kit intake prompt to extract professional request details; it does not receive storage credentials or authorization authority. When configured, Resend delivers transactional Press Kit status emails. Expo, Apple and Google may process mobile build or notification data. Third-party analytics, advertising and payment providers are disabled until separately configured and disclosed. Website notifications use the browser’s standards-based push service; the Courier stores only the endpoint and public encryption material needed to deliver a reader-requested alert. Notification campaigns may target all subscribers, selected accounts, newsroom roles or a separately defined NJC+ entitlement group. Cross-border transfer mechanisms must be reviewed for the final entity and audience.

Retention and security

Retention is limited to operational, editorial, security and legal needs. Unscanned pairing requests rotate after 60 seconds. A legitimate scan freezes the displayed code only for a short, server-controlled verification window. Television sessions expire after 90 days unless renewed and can be revoked by signing out. Revoked API-key records and security audit logs may be retained to investigate abuse. Audience installation, version-history and presence-event records are removed when a mobile reader disables measurement and the deletion request reaches The New Jersey Courier. Page-view events contain no account identifier; website records can be addressed through a privacy request. Evidence exports pseudonymize installation, session and account identifiers. Backups are encrypted and access-controlled; raw secrets and Press Kit access-token hashes are excluded or revoked on portable restore. Press Kit packages expire after a short access window; request and decision records are retained only for operational, security and authorization audit needs. Final retention periods, incident contacts and breach-response duties must be approved before production.

Your choices and rights

Depending on location, you may request access, correction, deletion, portability, restriction, objection, or an opt-out from certain sharing or targeted advertising. The New Jersey Courier does not activate targeted advertising or sale/sharing of personal information in this launch build. We verify identity before fulfilling requests and will explain lawful exceptions.

Browser notifications are opt-in. You can disable them from the Newsletters & alerts page or your browser settings. Signing out removes the browser subscription’s account association so later account-targeted alerts are not delivered to a shared browser.

Submit a privacy request or review measurement and cookie choices.

Children

Accounts and developer access are intended for people age 13 or older. The service is not directed to children under 13, and The New Jersey Courier does not knowingly collect their personal information through account features. Contact us to report a potentially underage account.

Updates and contact

Material changes will be dated and, when appropriate, notified in-product. A monitored privacy contact will be published after the operating entity and domain are established. Until then, use the privacy-request form.