Privacy Policy

ProjectRadar processes personal data only for limited purposes: running the site, handling voluntary newsletter subscriptions, checking voluntary project submissions, managing correction requests, managing sponsor inquiries, preventing abuse, and keeping basic private workflow records.

The main personal data ProjectRadar may receive is an email address, optional founder or requester name, submitted project details, temporary access instructions, correction-request details, security-screening metadata, and privacy preference storage.

ProjectRadar uses this information for the purpose it was provided. It is not sold, and private intake or correction details are not published unless a human deliberately approves public-safe content.

ProjectRadar collects email addresses only when users voluntarily subscribe to the newsletter.

Newsletter emails are managed by Buttondown. When you submit the newsletter form, your email is sent to Buttondown so it can manage the subscription.

Subscribers can unsubscribe using the unsubscribe links included in newsletter emails.

ProjectRadar does not sell newsletter email addresses.

If you submit a project for project note consideration, ProjectRadar uses the submitted information to evaluate fit, understand the project, and contact you if follow-up is needed.

Project submissions are validated server-side, may be screened for security issues, saved in a private intake queue, and sent to ProjectRadar by email using Resend. Submission details are not published unless a human approves public project note content.

Developers may optionally provide temporary access, such as an invite link, demo account, free trial instructions, or promo code. ProjectRadar uses that access only to evaluate the submitted project for project note consideration, and access details are not published.

ProjectRadar may screen submitted URLs for security, spam, phishing, or malware. Screening may use third-party security providers such as VirusTotal. A clean scan is not a guarantee that a submitted site is safe.

ProjectRadar does not download submitted files or execute submitted code as part of normal intake.

Developers should not submit sensitive credentials, personal credentials, or personal passwords.

Submission does not guarantee publication or coverage.

Private submission details are kept only as long as they are useful for project note evaluation, corrections, abuse prevention, or basic recordkeeping. Builders can ask ProjectRadar to delete private submission details that are no longer needed.

If you request a factual correction, ProjectRadar collects the email address, page URL, correction request, and supporting details you voluntarily provide.

Correction requests are saved privately and emailed to ProjectRadar’s editor using Resend. They are used to check potential updates and do not automatically change public content.

Correction request details may be retained so ProjectRadar can understand what changed and avoid repeating factual mistakes. You can ask for private correction-request data to be deleted when it is no longer needed for request history.

If you ask about a Sponsored Spotlight or Launch Asset Pack, ProjectRadar collects the name, email address, project details, preferred timing, budget-and-scope choice, goals, and attribution details you voluntarily provide.

Sponsor inquiries are validated, rate-limited, screened for URL safety, and saved in a private workflow queue. ProjectRadar uses Resend to notify the editor and send the requester a confirmation. Submitting an inquiry does not accept payment, reserve a placement, or change editorial Project Note decisions.

Inquiry details are retained only as long as useful for follow-up, pilot planning, abuse prevention, or basic business recordkeeping. You can ask ProjectRadar to delete a private inquiry when it is no longer needed.

Eligible makers can request private access using the email attached to a published submission. ProjectRadar stores the ownership claim, hashed single-use login tokens, subscription status, Stripe Customer and Subscription identifiers, and the structured status, pricing, and project-button choices a maker saves. Raw login tokens are not stored.

Stripe hosts checkout and billing management and processes payment details under its own privacy terms. Stripe collects the billing address required for Pro eligibility. ProjectRadar uses the billing country to enforce the current U.S.-only launch policy but does not store the street address. ProjectRadar does not receive or store complete card numbers. Signed Stripe webhooks update subscription status and recurring-revenue totals.

Maker routes are no-store, noindex, no-referrer, and excluded from public advertising and optional analytics scripts. Ending a subscription removes the paid maker-confirmed block after entitlement ends; it does not remove or rewrite independent Project Note content.

After a visitor accepts optional analytics, their browser may add one to a daily aggregate for an active Pro profile view, official-project click, maker-button click, or a successful local save. The event uses a random public routing identifier and is stored by ownership claim, date, metric, and count. It does not store a visitor identity, IP address, project slug, referrer, typed text, or individual browsing history. Makers see only directional, non-unique, unverified aggregate totals for complete UTC days. These signals can undercount real use and do not prove individual visitors or outcomes.

Paid makers may publish a short, plain-text project update no more than once every 30 days. These updates are labeled as maker-provided, appear only on that project's profile, and can be archived by the maker or hidden by ProjectRadar for safety or policy reasons.

Founder Story questionnaires are invitation-only. ProjectRadar keeps the founder email, interview answers, permission records, accuracy confirmation, editorial draft, and private workflow notes in a protected admin record.

A submitted questionnaire is not published automatically. A human editor may lightly edit interview answers for clarity, length, and house style, then deliberately publish a separate public-safe export containing only the approved byline, role, bio, answers, project details, and optional social links.

ProjectRadar may use Resend to notify the editor after answers are saved. Invitation links expire, work once, and are shared manually; the raw link token is not stored. Founders can request a factual correction or deletion of private Founder Story records.

If you choose Accept analytics, ProjectRadar counts a strict set of monetization-intent actions such as a Fresh Eyes option selection, Project Radar Pro offer click, or sponsor-inquiry click. The first-party event record contains only the event name, page surface, fixed label, and daily count.

ProjectRadar does not store an IP address, cookie identifier, user agent, referrer, query string, project slug, newsletter email address, project submission description, founder name, feedback-focus text, or other user-entered text in its first-party analytics table. It does not keep raw visitor-level event rows.

Analytics is optional and stays off unless a visitor chooses Accept analytics. ProjectRadar may also configure a supported external analytics provider for basic site usage; that provider is governed by the same ProjectRadar analytics choice.

Grow loads on public pages as part of ProjectRadar's Journey by Mediavine setup. Grow helps Journey evaluate site traffic and engagement and may support audience features or advertising. Journey and Grow may use cookies or similar technologies under their own notices. ProjectRadar keeps those vendor scripts off private workflow and transaction routes.

ProjectRadar is also being connected to Google AdSense for account and site review. A publisher meta tag, public-page verification script, and ads.txt seller record identify the AdSense account. Manual AdSense ad units remain disabled, and Google must approve the account and site before ads can serve.

ProjectRadar's analytics choice does not turn Grow on or off. It controls only the separate optional first-party analytics and any optional analytics provider configured by ProjectRadar. Those analytics stay off unless you choose Accept analytics.

Journey, Grow, or Google may provide separate privacy choices, including a consent-management interface in locations where it applies. Those vendor controls are separate from ProjectRadar's analytics setting.

ProjectRadar stores a small browser preference after you choose Accept analytics or Reject analytics. You can reopen privacy settings and change that analytics choice at any time.