Skip to content

Apple has approved code signing for our macOS app, and we’re still securing it for Windows. In the meantime, follow the Windows guide to open Pip.

Pip
ServersShareAgentsGitNetworkStoragePrivacyMemoryGame mode
PricingPluginsChangelogDocsSupport
DownloadBuy Pip

Features

ServersShareAgentsGitNetworkStoragePrivacyMemoryGame mode

More

PricingPluginsChangelogDocsSupportDownloadBuy Pip — $29
All legal documents

Privacy Policy

How we handle personal information when you use Pip, its website, and related services.

Last updated
21 October 2026
Effective date
21 October 2026
Terms of ServiceLicence AgreementPrivacy Policy

ON THIS PAGE

  1. 01Who This Policy Applies To
  2. 02Summary
  3. 03Information Pip May Process Locally
  4. 04Information We May Collect
  5. 05Information We Do Not Intentionally Collect Through Local Scanning
  6. 06How We Use Information
  7. 07Legal Bases for Processing
  8. 08Local Scan Data
  9. 09Device ID and Licence Validation
  10. 10Cookies and Similar Technologies
  11. 11Analytics and Telemetry
  12. 12When We Share Information
  13. 13Third-Party Providers
  14. 14International Transfers
  15. 15Data Retention
  16. 16Security
  17. 17Your Responsibilities
  18. 18Your Privacy Rights
  19. 19Marketing Communications
  20. 20Children
  21. 21Business and Workplace Use
  22. 22Sensitive Information
  23. 23AI Features
  24. 24Changes to This Privacy Policy
  25. 25Contact Us
  26. 26Australian Privacy Notice
  27. 27Plain-English Summary
On this page
  1. 01Who This Policy Applies To
  2. 02Summary
  3. 03Information Pip May Process Locally
  4. 04Information We May Collect
  5. 05Information We Do Not Intentionally Collect Through Local Scanning
  6. 06How We Use Information
  7. 07Legal Bases for Processing
  8. 08Local Scan Data
  9. 09Device ID and Licence Validation
  10. 10Cookies and Similar Technologies
  11. 11Analytics and Telemetry
  12. 12When We Share Information
  13. 13Third-Party Providers
  14. 14International Transfers
  15. 15Data Retention
  16. 16Security
  17. 17Your Responsibilities
  18. 18Your Privacy Rights
  19. 19Marketing Communications
  20. 20Children
  21. 21Business and Workplace Use
  22. 22Sensitive Information
  23. 23AI Features
  24. 24Changes to This Privacy Policy
  25. 25Contact Us
  26. 26Australian Privacy Notice
  27. 27Plain-English Summary

This Privacy Policy explains how New Horizon Code PTY LTD (we, us, or our) collects, uses, stores, discloses, and protects personal information when you use Pip, including the Pip desktop application, website, licensing services, billing services, support services, updates, and related features.

Pip is a desktop utility that scans certain technical information on your local computer to help identify locally running development servers, ports, processes, folders, and related metadata. This Privacy Policy is written to reflect that Pip's core scanning functionality is designed to operate locally on your device.

By using Pip, you agree to the collection and handling of information as described in this Privacy Policy.

  1. 01Who This Policy Applies To

    This Privacy Policy applies to users of Pip, including:

    1. users of the Pip desktop application;
    2. users who purchase a licence or subscription;
    3. users who contact us for support;
    4. visitors to our website;
    5. users of trial, beta, preview, or paid versions; and
    6. business or organisational users who use Pip internally.

    If you use Pip on behalf of a company, employer, client, or organisation, you are responsible for ensuring that your use of Pip complies with that organisation's privacy, security, and device-use policies.

  2. 02Summary

    Pip is designed to scan technical information on your own computer so it can show you what local development servers, ports, processes, and projects are running.

    In general:

    1. local scan information is intended to be processed on your device;
    2. Pip does not intentionally upload your full local process list, project folder paths, Git metadata, or local scan results to us as part of ordinary scanning functionality;
    3. Pip has no user accounts or passwords; you use it with a licence key that is linked to the email address you bought it with;
    4. we may collect billing, licence, activation, support, update, crash, diagnostic, and security information;
    5. our licensing database stores IP addresses only as salted one-way hashes, but the providers that host our website and our licensing, recovery, and support services record IP addresses in their own request logs for a limited period (about 7 days for our licensing, recovery, and support services);
    6. if you send us screenshots, logs, support requests, or diagnostic files, those may contain information about your device, projects, folders, processes, or development environment; and
    7. we use personal information to provide, secure, support, bill for, maintain, and improve Pip.
  3. 03Information Pip May Process Locally

    Pip may process certain information locally on your device to provide its core features.

    Depending on your operating system, permissions, settings, and enabled features, this may include:

    1. listening network ports;
    2. localhost or local network URLs;
    3. running processes;
    4. process names;
    5. process identifiers;
    6. executable paths;
    7. process working directories;
    8. project folder names;
    9. Git repository metadata, where available;
    10. CPU usage;
    11. memory usage;
    12. runtime or process start-time information;
    13. local development server information; and
    14. other similar technical information required to display and manage local processes and development servers.

    This information is referred to in this Privacy Policy as Local Scan Data.

    Local Scan Data may include sensitive technical information, such as project names, folder names, repository names, internal development URLs, or information that identifies your development environment.

    Unless we expressly state otherwise, Local Scan Data is intended to be processed locally on your device and is not intentionally transmitted to us as part of Pip's ordinary scanning functionality.

  4. 04Information We May Collect

    We may collect the following categories of information.

    4.1No user accounts

    Pip does not have user accounts. You do not create a username or password, and you do not sign in to use Pip. Your licence is linked to the email address used to purchase it, as described in section 4.3.

    4.2Billing and payment information

    If you purchase Pip, we or our payment processor may collect:

    1. billing name;
    2. billing email;
    3. billing address;
    4. payment method details;
    5. subscription status;
    6. invoice details;
    7. transaction history;
    8. tax information;
    9. refund or chargeback information; and
    10. plan or licence details.

    Payment card details are usually processed by our payment processor. We do not intend to store full payment card numbers unless expressly stated.

    4.3Licence and activation information

    To activate, validate, renew, or enforce access to Pip, we may collect:

    1. licence key;
    2. the email address used to purchase the licence;
    3. subscription or plan status;
    4. Device ID;
    5. a device public key generated on your device;
    6. device name;
    7. activation date;
    8. activation status;
    9. device count;
    10. app version;
    11. operating system type and version;
    12. the IP address used for activation, licence checks, and licence recovery, which our licensing database stores only as a salted one-way hash;
    13. records of support lookups and actions taken on your licence;
    14. validation logs; and
    15. information required to prevent licence abuse, fraud, or unauthorised sharing.

    The Device ID is a salted, shortened one-way hash of an identifier your operating system assigns to your computer (or, if that cannot be read, of a random value). The identifier itself is not sent to us. The device name is the name your computer reports.

    The purpose of a Device ID is to help confirm that a licence is being used within the permitted device limits.

    In our licensing database, we store your licence key only as a keyed one-way hash, together with its last four characters, and we store IP addresses only as a salted one-way hash. We use the IP address hashes to limit repeated attempts and to detect a licence key being shared. This hashing does not apply to the request logs kept by our hosting providers, described in section 4.8. After activation, the Software confirms your licence with the device public key rather than the licence key.

    When the Network tool measures regional latency or runs a speed test, the Software sends its signed licence token, which contains identifiers for your licence and device, the Device ID, your plan, when the token was issued and when it expires, and an identifier for the key that signed it, to our network test servers to show that it is licensed.

    If you request licence recovery, we collect the email address you enter and send a single-use confirmation link to the purchase email address. We also email the purchase email address when your licence is activated on a new device, moved to another device, or replaced.

    4.4Website and online service information

    Our website does not use analytics, advertising, or tracking cookies, and does not run analytics scripts. When you visit it, our hosting provider records each request as described in section 4.8, including your IP address and the page requested, and possibly details your browser sends, such as its type and the referring page. The website stores your choice of light or dark theme in your browser's local storage; it is not sent to us.

    Unless you turn update checks off in its settings, Pip checks our website for updates 30 seconds after it starts and then every six hours, or an hour after a check fails. Each check sends the app's operating system, processor architecture, and version. An update is downloaded from our file storage provider.

    4.5Support information

    If you contact us for support, we may collect:

    1. your name and contact details;
    2. licence details you choose to include, such as an order number;
    3. device and operating system details;
    4. app version;
    5. issue description;
    6. support messages;
    7. screenshots you provide;
    8. logs or diagnostic files you provide;
    9. attachments you submit; and
    10. any other information you choose to include.

    If you use the support form on our website, the name (if you give one), email address, subject, and message you enter are sent through our email provider to our support inbox, with your email address as the reply address. Our database does not store your message or your email address. To limit repeated submissions, it keeps a salted one-way hash of the IP address the form was sent from and of your email address, together with the time and whether the message was sent, for 30 days.

    You should not send us source code, passwords, API keys, secrets, private repository information, sensitive project information, client data, health information, financial information, or confidential business information unless it is necessary and you are authorised to share it.

    4.6Crash reports and diagnostics

    Pip does not send crash reports, diagnostics, or usage data to us automatically. If you send us crash reports, diagnostics, or technical logs, for example with a support request, we use them to identify errors, improve reliability, and maintain the Software.

    They may include:

    1. app version;
    2. operating system version;
    3. device type;
    4. error messages;
    5. stack traces;
    6. crash timestamps;
    7. performance data;
    8. memory or CPU-related information;
    9. feature usage leading up to an error; and
    10. limited technical context needed to troubleshoot the issue.

    Where practical, diagnostics are designed not to include full Local Scan Data, project contents, source code, passwords, secrets, or private files.

    However, technical logs may sometimes include incidental information, especially if you manually submit logs or screenshots to us.

    4.7Communications information

    If we communicate with you, we may collect:

    1. email messages;
    2. support conversations;
    3. feedback;
    4. survey responses;
    5. product enquiries;
    6. marketing preferences; and
    7. records of notices sent to you.

    4.8Hosting and email provider records

    Our website and our licensing, recovery, and support services run on third-party hosting providers. These providers record requests in their own logs, including the IP address a request came from, the time, and the address requested. This applies to requests from your browser and from the Pip app. Supabase, which hosts our licensing, recovery, and support services, keeps these logs for about 7 days. Vercel, which hosts our website and update downloads, keeps its request logs for a limited period set by its service plan.

    The test servers used by Pip's Network tool run on Fly.io. Our test server software does not log individual requests; it logs a summary when a server starts and after each speed test (a random test identifier, the amount of data transferred, and the speed). Fly.io may keep its own technical records of the connections it carries, under its own retention.

    Our email provider, Resend, delivers the emails we send, including emails that contain your licence key, recovery links, device notices, and messages sent through our support form. Resend keeps its own records of these emails for a period it sets.

    We may view these logs and records to operate, troubleshoot, and secure our services. Our own services also add short technical messages to the logs, such as the order number of a purchase or a licence identifier, and never keys, tokens, or email addresses.

    4.9Claude plan usage

    In versions of Pip that show Claude plan usage, if Claude Code is signed in on your computer, Pip sends the sign-in token Claude Code has stored to Anthropic (api.anthropic.com) to read your plan's usage limits. This request goes directly from your computer to Anthropic; we do not receive the token or the usage information. Codex usage limits are read from files Codex stores on your computer, without a network request.

  5. 05Information We Do Not Intentionally Collect Through Local Scanning

    As part of ordinary local scanning functionality, Pip is not intended to collect or transmit to us:

    1. your full source code;
    2. private project files;
    3. passwords;
    4. API keys;
    5. environment secrets;
    6. database contents;
    7. browser history;
    8. personal documents;
    9. emails;
    10. photos;
    11. private messages;
    12. full local process history; or
    13. complete file system contents.

    Pip's purpose is to detect and display relevant local development server and process information, not to read or upload the contents of your files.

    However, some project names, folder paths, repository names, local URLs, or technical identifiers may be visible in the Pip interface and may be included if you voluntarily send screenshots, logs, recordings, or support materials to us.

  6. 06How We Use Information

    We may use information for the following purposes:

    1. to provide Pip;
    2. to activate and validate licences;
    3. to manage subscriptions and billing;
    4. to process payments, invoices, refunds, and taxes;
    5. to provide support;
    6. to troubleshoot bugs and crashes;
    7. to improve product reliability and performance;
    8. to provide updates and security patches;
    9. to prevent fraud, abuse, licence sharing, and unauthorised access;
    10. to enforce our Terms of Service and EULA;
    11. to communicate with you about your licence, subscription, product updates, or support requests;
    12. to send service notices;
    13. to send marketing communications where permitted;
    14. to comply with legal obligations;
    15. to protect our legal rights; and
    16. to maintain the security and integrity of Pip.
  7. 07Legal Bases for Processing

    Where privacy laws require us to identify a legal basis for processing personal information, we may rely on one or more of the following:

    1. Contract: to provide Pip, manage your licence, process payments, and deliver support;
    2. Consent: where you agree to optional features, marketing, cookies, beta testing, or optional diagnostics;
    3. Legitimate interests: to secure Pip, prevent fraud, improve the product, and operate our business;
    4. Legal obligation: to comply with tax, accounting, consumer law, regulatory, or legal requirements; and
    5. Vital or public interests: where required by applicable law, though this is not expected to be common for Pip.
  8. 08Local Scan Data

    Local Scan Data is primarily used to display information inside Pip on your device.

    We do not claim ownership over Local Scan Data.

    You are responsible for ensuring you are permitted to process Local Scan Data on the device where Pip is installed.

    If you use Pip on a work, client, school, managed, or shared device, you should confirm that you have permission to scan local process, port, and project information.

    You should also consider whether Local Scan Data may reveal confidential information, such as internal project names, client names, repository names, or development URLs.

  9. 09Device ID and Licence Validation

    Pip may use a Device ID for licence validation, activation limits, fraud prevention, and subscription enforcement.

    A Device ID is a salted one-way hash of an identifier your operating system assigns to your computer, as described in section 4.3. The identifier itself is not sent to us.

    We use Device IDs to:

    1. bind a licence to a device;
    2. prevent licence sharing;
    3. manage device limits;
    4. identify suspicious activation activity;
    5. enable offline or grace-period validation; and
    6. help you manage legitimate reactivations.

    Depending on applicable law, a Device ID may be considered personal information because it can relate to a specific licence or device.

  10. 10Cookies and Similar Technologies

    Our website does not use cookies, pixels, or similar technologies for analytics, advertising, marketing, or attribution. It uses your browser's local storage only to remember your choice of light or dark theme.

    Our hosting provider may use strictly necessary cookies to protect the website from abuse. You can usually manage cookies and local storage through your browser settings.

  11. 11Analytics and Telemetry

    Neither Pip nor our website uses analytics or telemetry. Pip does not send usage events, crash reports, or performance data to us.

    Pip does send the technical information described in section 4 where necessary for licence validation, updates, Network tool measurements, security, fraud prevention, or legal compliance.

  12. 12When We Share Information

    We may share personal information with:

    1. hosting providers;
    2. database providers;
    3. payment processors;
    4. billing and invoicing providers;
    5. support and helpdesk providers;
    6. email and communication providers;
    7. fraud prevention and security providers;
    8. professional advisers, such as lawyers, accountants, and auditors;
    9. regulators, courts, law enforcement, or government agencies where required; and
    10. buyers, successors, or parties involved in a merger, acquisition, restructure, financing, or sale of business assets.

    We do not sell your personal information to advertisers.

    We do not intentionally share your Local Scan Data with third parties as part of ordinary local scanning functionality.

  13. 13Third-Party Providers

    Pip may rely on third-party providers for services such as:

    1. payments;
    2. hosting;
    3. database storage;
    4. email delivery;
    5. support management;
    6. update distribution; and
    7. fraud prevention.

    Third-party providers may process information according to their own terms and privacy policies.

    We use reasonable efforts to work with reputable providers, but we are not responsible for the privacy practices of third-party websites, services, or platforms that we do not control.

  14. 14International Transfers

    Your information may be processed or stored in countries other than the country where you live.

    These countries may have privacy laws that differ from your local laws.

    Where required, we will take reasonable steps to protect personal information transferred internationally, including through contractual safeguards or other lawful transfer mechanisms.

    If you require a specific data residency arrangement, you should contact us before using Pip in a regulated or enterprise environment.

  15. 15Data Retention

    We retain personal information only for as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.

    Retention periods may vary depending on the type of information.

    For example:

    1. your licence record, including the purchase email address, order id, plan, the hash and last four characters of your key, and the devices that hold it, is retained while the licence exists;
    2. hosting providers' request logs, which include IP addresses, are kept for a period each provider sets: about 7 days for our licensing, recovery, and support services, and a limited period set by the service plan for our website;
    3. our email provider keeps its own records of the emails we send and the support messages it delivers, for a period it sets;
    4. hashed records of support form submissions are deleted after 30 days; the messages themselves are kept in our support inbox as support records;
    5. billing records may be retained as required for tax, accounting, and legal compliance;
    6. licence activation records may be retained to manage licensing, security, and fraud prevention; activation and validation events and records of purchase notifications (including the order id) are deleted after 90 days, hashed records used to limit repeated attempts and recovery links after one day, licence transfer records and the name and operating system of a released device after one year, and records of support actions on a licence are kept as its history;
    7. support records may be retained to provide ongoing support and maintain a history of issues;
    8. crash reports or logs you send us may be retained for troubleshooting and product improvement; and
    9. backups may retain information for a limited period before deletion or overwrite.

    When information is no longer required, we will delete, de-identify, or securely archive it where reasonable.

  16. 16Security

    We take reasonable steps to protect personal information against misuse, interference, loss, unauthorised access, modification, or disclosure.

    Security measures may include:

    1. access controls;
    2. authentication systems;
    3. encryption in transit where appropriate;
    4. hashed or transformed identifiers where appropriate;
    5. restricted access to production systems;
    6. monitoring and logging;
    7. secure third-party providers;
    8. staff or contractor access controls; and
    9. operational security practices.

    No software, network, system, or method of transmission is completely secure.

    You are responsible for securing your own device, licence key, local development environment, source code, secrets, and backups.

  17. 17Your Responsibilities

    You are responsible for:

    1. only installing Pip on devices you own or are authorised to use;
    2. complying with workplace, client, school, or organisational policies;
    3. reviewing what information is visible before sharing screenshots or logs;
    4. not sending us source code, secrets, credentials, or confidential information unless necessary and authorised;
    5. keeping your licence key secure;
    6. keeping your device secure;
    7. maintaining backups of your work; and
    8. ensuring your use of Pip complies with applicable law.
  18. 18Your Privacy Rights

    Depending on where you live, you may have rights to:

    1. access personal information we hold about you;
    2. request correction of inaccurate information;
    3. request deletion of certain information;
    4. object to certain processing;
    5. restrict certain processing;
    6. request a copy of certain information in a portable format;
    7. withdraw consent where processing is based on consent;
    8. opt out of marketing communications; and
    9. make a complaint to a privacy regulator.

    To exercise privacy rights, contact us at privacy@newhorizoncode.io.

    We may need to verify your identity before responding.

    Some information may need to be retained for legal, billing, security, fraud prevention, dispute resolution, or legitimate business reasons.

  19. 19Marketing Communications

    We may send you product updates, launch notices, educational content, offers, or marketing communications where permitted by law.

    You can opt out of marketing emails by using the unsubscribe link or contacting us.

    Even if you opt out of marketing, we may still send service-related communications, including billing notices, licence notices, security alerts, support messages, legal notices, and important product updates.

  20. 20Children

    Pip is not intended for children.

    You must not use Pip if you are under the age required to consent to these terms and privacy practices in your jurisdiction.

    We do not knowingly collect personal information from children.

    If we become aware that we have collected personal information from a child without appropriate consent, we will take reasonable steps to delete it.

  21. 21Business and Workplace Use

    If Pip is used in a business, workplace, client, school, or managed environment, the relevant organisation may have its own rules, monitoring practices, security policies, and privacy obligations.

    You are responsible for ensuring that:

    1. you have permission to install Pip;
    2. your use complies with internal policies;
    3. local scanning is permitted;
    4. any support materials you send us are authorised; and
    5. you do not disclose confidential, client, employee, regulated, or sensitive information without permission.

    If an organisation purchases or manages Pip for its users, that organisation may control access, billing, licence status, licence assignment, and related administrative information.

  22. 22Sensitive Information

    Pip is not designed to collect sensitive personal information, such as health information, biometric information, racial or ethnic origin, religious beliefs, political opinions, union membership, criminal history, or sexual orientation.

    You should not provide sensitive personal information to us unless it is necessary and you are authorised to do so.

    If you include sensitive information in support requests, screenshots, logs, attachments, or communications, we may process it only as needed to respond, comply with law, protect rights, or maintain records.

  23. 23AI Features

    If Pip later includes AI-powered features, such as process explanations, project summaries, error analysis, or support automation, additional privacy terms may apply.

    Such features may require sending selected information to an AI provider or processing service.

    We will aim to provide notice before enabling AI features that transmit user-selected information outside your device.

    You should not submit source code, secrets, credentials, confidential client information, or sensitive personal information to AI features unless you are authorised and understand how the information will be processed.

  24. 24Changes to This Privacy Policy

    We may update this Privacy Policy from time to time.

    If we make material changes, we may notify you by:

    1. posting the updated policy on our website;
    2. showing an in-app notice;
    3. sending an email; or
    4. using another reasonable method.

    The updated Privacy Policy will apply from the effective date stated above.

    Your continued use of Pip after the updated Privacy Policy takes effect means you acknowledge the updated policy.

  25. 25Contact Us

    For questions, requests, or complaints about this Privacy Policy or our handling of personal information, contact us at:

    Company
    New Horizon Code PTY LTD
    Trading name
    Pip
    Privacy email
    privacy@newhorizoncode.io
    Support
    support@getpip.dev
    Website
    getpip.dev
    Address
    Suite 121 Level 14, 167 Eagle Street, Brisbane QLD 4000 Australia
  26. 26Australian Privacy Notice

    If we are subject to the Privacy Act 1988 (Cth) and the Australian Privacy Principles, we will handle personal information in accordance with those requirements.

    You may contact us to request access to or correction of your personal information.

    If you have a privacy complaint, please contact us first using the details above. We will take reasonable steps to respond.

    If you are not satisfied with our response, you may be able to contact the Office of the Australian Information Commissioner.

  27. 27Plain-English Summary

    Pip scans your computer locally so it can show you running development servers, ports, processes, and project information.

    We do not intend to upload your full local scan results to our servers during normal use.

    There are no user accounts or passwords. We may collect information for billing, licence activation, updates, support, crash reports, diagnostics, security, and legal compliance.

    Our licensing database keeps IP addresses only as salted one-way hashes. The providers that host our website and our licensing, recovery, and support services still record IP addresses in their own request logs for a limited period: about 7 days for our licensing, recovery, and support services.

    Be careful when sending screenshots or logs to support, because they may include project names, folder paths, repository names, local URLs, or other technical information.

    Only install Pip on computers you own or are authorised to use.

Questions about this document? Contact support.

Back to top
Pip

Manage your dev servers and Git. Test your connection, free up memory, and clean up project files.

Made formacOSandWindows.

Product

  • Download
  • Pricing
  • Community plugins
  • Changelog
  • FAQ
  • Brand resources

Support

  • Help centre
  • Status
  • Contact support
  • Recover key
  • support@getpip.dev

Legal

  • Terms of Service
  • EULA
  • Privacy Policy

© 2026 New Horizon Code PTY LTD. All rights reserved.

Made in Brisbane, Australia.