Privacy policy

Machine inventory from MCP

Who we are

Patch Next is published by PixelVent, which is operated by The Huggable Corporation Incorporated, a Delaware C Corporation, at 1301 Mistletoe Lane, Kingwood, TX 77339, USA. Legal notices: support@pixelvent.com.

PixelVent (The Huggable Corporation Incorporated) is the controller of the personal data described in this policy. When a company uses a team organization, the company decides what its team uploads, and PixelVent processes that workspace data for the company under our data processing addendum.

In short: we collect only what we need to sign you in, save the software stacks you want checked, let the coding agents you approve read them, and send email updates if you ask for them. The only paid content is the labelled sponsor cards, the same for every visitor: no ad network and no targeted or personalised advertising. We do not sell personal data, and we do not use tracking or analytics cookies. Every choice in this policy is a control in the app: as an account holder you never need to write to anyone to see, export, correct or delete your data.

What we collect

• Google sign-in. When you sign in with Google we receive your Google account identifier, email address, name and profile picture link (the OpenID, email and profile scopes). Our authentication service also keeps your sign-in sessions and a security log of sign-in events.
• Your profile. The display name and time zone you set.
• Machine inventory. MCP checks provide each machine’s latest package snapshot, as described above. Backing stacks keep organization linkage and revision metadata for matching and triage. There is no manual lockfile upload or package setup.
• Machines and products. The machines a stack runs on, by the name you or your agent give them (often a hostname), with the packages seen on each, and the products and vendors you list.
• Triage history. For each finding: its status on each machine, notes, reasons, evidence links and snooze dates, and who or which agent changed it and when.
• Organizations. Each stack belongs to an organization: your personal one, or one you create and name, for example your company. We store each organization’s name, its members and their roles, and, when you or your agent set one, the code repository a stack tracks (for example github.com/acme/api). Members and viewers of an organization see each other’s display name, email address and role there. An invite link carries a random code: we store only its SHA-256 fingerprint, the role, who created it, when it expires and, if set, the one email address that may accept it.
• Inventory consent. We record the owner’s inventory-saving permission, consent statement and time for each approved OAuth app or personal token. This permission is independent of read access and finding marks. Legacy inventory replacement also records its per-update consent and resulting revision.
• Agent access. For personal agent keys we store only a SHA-256 hash of the key, never the key itself, plus its label, short prefix, scopes, the stacks you selected, expiry and revocation times, and when it was last used. For apps you connect through OAuth we store the app’s client identifier and registered name, the stacks you granted, grant and revocation times, last use and rate-limit counters.
• Email updates (opt-in). Email updates are off unless you tick the box at sign-in or turn them on in your account. We record each choice (the wording version you saw, where you made it and when) and send updates to the email address of your Google account. For each message we keep a delivery record: status, the email provider’s message ID and timestamps. Unsubscribes are recorded the same way.
• Community votes. If you vote an advisory or news item up or down, we store your vote, the item and when you last changed it, plus a per-account counter that limits how often votes can change. Your votes are private: other users never see them, and administrators see only the totals for each item.
• Sponsor bookings. If you apply for a sponsor placement we store the company name, contact email, destination link, ad text, requested week, our review notes, the booking status, the price and Stripe Checkout and payment identifiers. You pay on Stripe’s own checkout page: Stripe handles your card and billing details and we never see or store card numbers.
• Technical data. Our providers process your IP address and request details (such as browser type and the page or endpoint requested) in routine server and security logs.

Before 23 October 2026 an earlier version of this site offered a “Get notified” email form and counted visits with a random code stored in your browser. Both features have been removed and the records they created have been deleted.

Purposes, legal bases and how long we keep data

“Contract” means we need the data to provide the service you asked for. “Legitimate interests” means running Patch Next securely and well, which we weigh against your interests and keep to the minimum needed. “Consent” means you switched the feature on and can switch it off at any time.

Account deletion removes your personal data and follows workspace ownership. Sole owners of shared workspaces must transfer ownership first; surviving shared team inventory remains. Account-linked do-not-email records are erased with the account. Provider log and backup retention periods remain NEEDS-FROM-OWNER; database deletion does not establish when independent provider copies are erased.

How we use Google user data

We use information received through Google sign-in only to authenticate you and operate your Patch Next account, and, if you opt in, to send the email updates you asked for to your account’s email address. We do not request access to Gmail, Google Drive, Contacts, Calendar or any other Google service.

We do not use Google user data for advertising, we do not sell it, and we do not use it to train AI or machine-learning models. We transfer it only to the service providers listed below to run Patch Next, or when the law requires it. People at PixelVent look at it only to investigate security or abuse, or to comply with the law.

Patch Next’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The policy is available at developers.google.com/terms/api-services-user-data-policy.

Anonymous statistics

To decide what to build and which ecosystems to cover, we count how many saved stacks include a given public package. A package is counted only when it appears in at least 5 stacks belonging to at least 5 different accounts. These statistics never include versions, private packages, stack names or account details, and we do not share them with sponsors.

To learn whether people find the agent install useful, we keep daily totals of clicks on “Add to your agent”, copies of the install commands and one-click installs, by page area and agent (Claude Code, Codex or Cursor). A click only adds one to a total: no cookie, identifier, IP address or browser detail is stored with it, and browsers that send Global Privacy Control or Do Not Track are not counted. We also count, per day, how many agents were connected, from the agent access records described above.

Who processes your data

We use these service providers to run Patch Next:

• Supabase: Database, sign-in and backend functions. Where: European Union: our project runs in AWS eu-west-1 (Ireland).
• Cloudflare: DNS for patchnext.com and the mcp.patchnext.com endpoint that forwards agent requests. Where: Global network.
• Lovable: Hosting of the patchnext.com website. Where: May process data outside the EU, including the United States.
• Google: Google sign-in. Where: May process data outside the EU, including the United States.
• Stripe: Payments for sponsor placements. Where: May process data outside the EU, including the United States.
• Resend: Delivery of email updates, only to people who opted in. Where: United States.

Our web fonts are served from patchnext.com itself, so loading a page does not contact Google or any other font service. When you connect a coding agent, the results it requests are sent to the agent and host you chose, under their own privacy terms. We do not sell or rent personal data, and we never give sponsors or advertisers your identity, email address or stacks. We may disclose information if the law requires it, or to protect the service and its users.

International transfers

Our database and sign-in service run in the European Union. Some providers above process data in other countries, including the United States. Where personal data leaves the European Economic Area or the United Kingdom, we rely on the safeguards in each provider’s data processing terms: the European Commission’s Standard Contractual Clauses or, for providers certified under it, the EU-U.S. Data Privacy Framework and its UK extension.

Cookies and browser storage

Patch Next does not use advertising or analytics cookies and loads no third-party trackers, so there is no cookie banner. Your browser stores only what the site needs to work:

• your sign-in session, in local storage, until you sign out;
• short-lived values in session storage, cleared when you close the tab: where to return after sign-in, an invite you are accepting, an authorization you are approving, your email-update choice at sign-up, and how far you had scrolled on each page, so Back returns you to the same place;
• two technical cookies that our hosting network sets on patchnext.com: __cf_bm, which Cloudflare keeps for 30 minutes to tell people from automated traffic, and __dpl, which Lovable keeps for one day to hold the identifier of the site version you were served, the same for every visitor.

The install counts described above are cookieless daily totals. Stripe’s checkout page sets its own cookies under Stripe’s policy. Your coding agent reads lockfiles on your machine and sends only the normalized snapshot fields described above through MCP.

Your rights and how to use them

Under the GDPR, the UK GDPR and similar laws you can access, correct, delete, restrict, object to and port your data, and withdraw consent. Each right is a control in Patch Next:

• Access. The app shows what you saved in your account: your profile, organizations, stacks, machines and products, the Patch report with its history, your agents, email choices and sponsor bookings. Download my data in Account settings provides a private JSON copy, including community votes, safe sign-in metadata, machine snapshots and inventory consent.
• Portability. Download the Patch report as CSV. For a private JSON account export, including machine snapshots and inventory consent, use Download my data in Account settings.
• Rectification. Edit your display name under Account, and edit your stacks and products where they are shown. Your email address comes from your Google account.
• Erasure. Delete a stack (with its machines and their history) or a product, clear a vote by clicking it again, or delete your account and everything linked to it under Delete account on your account page.
• Restriction and objection. Turn email updates off under Email updates or with the unsubscribe link in any email (no sign-in needed), limit or revoke each agent’s access on your agents page, or stop all processing by deleting your account. Browsers that send Global Privacy Control or Do Not Track are left out of the install counts.
• Withdraw consent. Switch email updates or agent stack updates off at any time. Withdrawing consent does not affect processing that happened before.

Deleting your account takes effect immediately and cannot be undone. If a sponsorship is on hold for payment, withdraw it on Sponsorships first. A paid booking stops blocking deletion once its week has ended or it has been refunded, and you can cancel and refund a paid week yourself there before it starts. You can also remove Patch Next’s access to your Google account at myaccount.google.com/connections. We do not sell personal information or share it for cross-context behavioral advertising.

Complaints

You have the right to lodge a complaint with a data protection supervisory authority, in particular in the country where you live or work or where you believe your rights were infringed.

Automated decisions

We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Matching your stack against advisories is automated, but it only tells you what may need patching.

Security

Every private table is protected by access rules in the database, so other people cannot read your stacks, and website sessions and agents are kept apart. Agent keys and invite codes are stored only as SHA-256 hashes, every connection uses HTTPS, and Supabase states that it encrypts stored data. Agents see only the stacks you choose and can change nothing unless you allow it. Database permissions are checked automatically on every change. No system is perfectly secure.

Children

Patch Next is a tool for software teams. It is not directed at children under 16, and we do not knowingly collect their personal data. An account holder can delete their account at any time under Delete account. A parent or guardian without access to the account can send a notice about a child’s data to our legal-notice address, which is only for notices that cannot be given in the app.

Changes

We will post updates on this page and change the effective date. We will tell signed-in users about material changes before they apply.