Privacy Policy

ProjectRadar processes personal data for these 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. We do not sell private intake records, 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.

After you submit a project, or after its Project Note is published, ProjectRadar may offer a private link to a few optional questions, such as why you built the project and who uses it today. The link may appear on the submission confirmation screen or in an email to the address you submitted with. ProjectRadar sends at most one separate invitation email per project, plus a fresh link if you reply about the questions.

Answers are saved in a protected admin record with the date you gave permission. They are used only if you agree that ProjectRadar may quote or summarize them in the public Project Note, and your name is shown only if you choose that option. Quotes use your exact words.

Links expire after 30 days and work once; the raw link token is not stored. To stop further requests, open the link and choose "No thanks, don't ask me again." You can also ask for a correction or deletion of your answers through the contact details below.

Replies to submissions@getprojectradar.com reach the ProjectRadar inbox. When a reply comes from the address a project was submitted with, a copy is also kept in the protected admin record so a request, such as not being asked again, can be acted on. Answers sent by email are not quoted; the private link is where quoting permission is given.

If you enable 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.

Optional analytics helps us understand which pages and features are useful and where the site needs work. Choose Allow analytics or No thanks in the first-visit request. Neither is preselected, and either choice leaves the site available. Privacy choices remains available above page content and through the footer. It includes a direct Turn analytics off action after an opt-in.

An opt-in also permits Google Analytics to measure page use and selected interactions. Google may use cookies or similar identifiers and receive device and ordinary request information, including your IP address. See how Google uses data from partner sites. Our application sends coarse page locations without query strings or fragments, a fixed site title and an empty referrer. This describes our explicit event payloads; it does not remove the information Google receives when its script loads.

Advertising choices are separate. Google consent alone does not enable our optional analytics. A fresh Allow analytics action here supplies analytics permission independently of advertising-message startup. Missing or unknown Google advertising readiness is not an analytics grant. We also preserve observed Google analytics refusals. A retained Google analytics refusal needs a current Google analytics grant and a fresh Allow analytics action here before analytics can start.

Google AdSense loads on eligible public pages to provide its published regional privacy message and manage advertising consent. Google and its disclosed advertising partners may process IP addresses, browser information, page addresses, and cookie or similar identifiers under the choices you make in that message. Non-personalized advertising may still use cookies.

Use Privacy choices to change optional analytics. Its Advertising cookie choices button reopens Google's applicable message. We keep Google Analytics advertising signals off. We do not use session replay. Journey/Grow is currently not loaded while its serving and consent integration is reviewed.

Global Privacy Control keeps both the Google advertising loader and optional analytics off on this site. A saved advertising refusal from our previous settings keeps the Google loader off for the rest of its original 180-day period. A rejection fallback saved when browser storage failed keeps advertising and analytics off. Changing analytics does not remove those restrictions. Optional vendors stay off private workflow and transaction routes; advertising also stays off intake forms.

An analytics opt-in lasts up to 180 days. No thanks, previous local analytics refusals and observed Google analytics refusals remain off without another automatic request while their browser records remain. Older opt-ins do not become permission for this new choice: a fresh Allow analytics action is required. You can deliberately change a local refusal through Privacy choices. Google manages storage for its own consent message; changing analytics here does not grant advertising consent. Withdrawing active analytics permission immediately disables our dispatchers and reloads the page to stop its running code. Changing a choice does not erase data a provider already received; contact us or the provider to request deletion where available.