Ponchos

Privacy Policy

Last updated August 2026

This Privacy Policy describes what information Ponchos collects, why, and how it is used. Ponchos is currently an invite-only product for a small number of users; this policy describes the product as it exists today, not future plans.

1. Information we collect

Account information. When you’re given access to Ponchos, we store your email address (via our authentication provider, Supabase) and, if you provide them, your first and last name.

Onboarding information. As part of a short onboarding flow after your account is created, we ask about your current job-search situation and, on your Search Profile, your product-type and target-buyer preferences.

Search Profile. To personalize company matches, we store the preferences you provide: target role/title, seniority, preferred company stages and categories, preferred locations, work preferences, compensation target, risk appetite, GTM motion preferences, companies to avoid, and a free-text background summary you write about yourself.

Favorites and watchlist. Which companies you mark as a favorite or add to your watchlist, and when.

Feedback. If you indicate you want to see more or fewer companies like a given one, or hide a company, we store that signal against your account and the relevant company.

Evaluation and research activity. When Ponchos evaluates a company for you or you request a research report, we store the result (scores, narrative text, verdicts, timestamps) tied to your account so it can be shown back to you later.

Credits. If credits have been granted to your account, we keep a record of each grant for bookkeeping. Ponchos does not currently process payments — see “Payments” below.

2. Public company, workforce, funding, developer, and job information

Separately from your account data, Ponchos collects and stores information about companies from public sources: company facts and descriptions (from public web search), public funding announcements, public GitHub activity (aggregate statistics such as stars, commits, and contributor counts — not individual contributor identities), and job postings sourced from the same public APIs that power a company’s own careers page (Ashby, Greenhouse, Lever).

Ponchos may also collect and maintain structured information from publicly discoverable professional profiles associated with a company. This may include a person’s name, current or listed job title, employer, general location, public profile or source URL, and publicly listed role start or end dates. Ponchos uses this information to build factual company workforce observations, such as observed functional composition, geography, tenure, and changes between collection dates. These observations are estimates from public sources, not a verified employee directory or authoritative company headcount.

Ponchos stores when an observation was collected, its source and provider identifiers where available, the collection methodology, coverage and confidence information, and estimated collection cost. Historical observations may be retained so Ponchos can show how publicly observed company composition changes over time.

3. How your information is used

  • To show you personalized company matches and evaluations based on your Search Profile.
  • To generate research reports and written rationale about why a company may or may not fit your stated preferences.
  • To remember your favorites, watchlist, and feedback so the product reflects your prior activity.
  • To assemble and compare factual, publicly observed company workforce information over time.
  • To operate, maintain, and improve the product.

4. Third-party services we use

Ponchos relies on a small number of third-party service providers to operate:

  • Supabase — our database and authentication provider. Your account credentials, profile, and activity data are stored here.
  • Vercel — hosts the Ponchos web application.
  • Modal — runs backend processing, including generating personalized research and evaluation narratives.
  • OpenAI — Ponchos uses OpenAI’s API to generate personalized company evaluations, research narratives, and match rationale. This means your Search Profile information, including the free-text background summary you write about yourself, may be sent to OpenAI’s API as part of generating this content. OpenAI processes this data to return a generated response; Ponchos does not use your data to train any model.
  • Exa — used to search public web and professional-profile information for company, funding, and workforce research. Queries are built from company names, roles, and other public company details, not from your private Search Profile information.
  • GitHub — Ponchos reads public repository and organization data from GitHub’s public API to compute developer-activity signals. Ponchos does not access your own GitHub account and has no GitHub login integration.
  • Mapbox — powers location maps shown in the product. Viewing a map causes your browser to request map tiles directly from Mapbox, which will see your IP address as part of that request.
  • Umami — limited analytics on Ponchos’s public landing and demo surfaces. It does not run inside the authenticated product.
  • Mixpanel — optional product analytics used only after you explicitly allow analytics. Ponchos sends a stable internal account identifier after authentication plus a small set of event properties needed to understand signup and whether a personalized Radar loaded. Ponchos does not send Mixpanel your email address, name, free-text searches, or Search Profile text. Session Replay, automatic page-view tracking, and autocapture are disabled.

Ponchos does not sell your data to any third party, and does not share it for advertising purposes.

5. Payments

Ponchos does not currently process payments. Credits shown in the product are an internal bookkeeping mechanism only; no payment processor is integrated, and no card or payment information is collected.

6. Job listings and third-party links

When you view a job listing through Ponchos, the link takes you directly to that employer’s own job-application page on their careers site or applicant-tracking system. Ponchos does not process job applications, is not involved in the hiring process, and is not responsible for the content, accuracy, or availability of third-party job listings once you leave Ponchos.

7. Cookies and sessions

Ponchos uses cookies to keep you signed in (managed by our authentication provider, Supabase). If you explicitly allow analytics, Mixpanel stores an analytics consent choice and an anonymous device identifier in your browser’s local storage so activity before and after login can be connected. Declining or withdrawing analytics consent disables that tracking and clears Mixpanel’s stored analytics identity. Ponchos does not use advertising or cross-site tracking cookies.

You can allow or withdraw Mixpanel analytics consent at any time:

8. Data retention

Ponchos does not currently have an automated data-retention or deletion schedule. Account and activity data is generally kept for as long as your account exists, unless you request deletion (see below).

Public company and workforce observations may be retained as historical records even when no user currently watches the company, because longitudinal comparison is part of the product. We may correct, restrict, or remove a named-person observation when we learn it is inaccurate or receive a valid privacy request.

9. Account and data deletion, and data export

Ponchos does not yet offer a self-service “delete my account” or “export my data” feature within the product. If you would like your account or personal data deleted, or a copy of your data exported, please contact us at support@ponchos.io and we will handle your request manually. We do not currently commit to a specific automated turnaround time, but we will respond to your request.

A person whose public professional information appears in a Ponchos workforce observation may also contact us to request access, correction, or deletion of that information. Please include enough detail for us to identify the relevant record and source without sending sensitive documents unless we request them.

10. Security

Your account data is stored in Supabase and protected primarily through authentication and access controls that restrict most tables to your own rows or to service-level access. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.

11. Changes to this policy

We may update this Privacy Policy as the product changes. We will update the “Last updated” date above when we do.

12. Contact

Questions about this Privacy Policy or your data can be sent to support@ponchos.io.

Privacy PolicyTerms of Service