Privacy Policy

Localify does not collect request logs, project data, local paths, domain names, or information about the local services you run. Core proxy features work locally after setup. We use limited product analytics to understand broad app flows such as onboarding and project creation, and we process personal data when you visit the website, buy or activate a license, check for updates, or contact us for support.

Localify, Inc. is the data controller for information collected through the Localify website, the checkout flow, and the license system. You can reach us at support@localify.dev.

The Localify daemon, desktop app, and CLI run on your machine. DNS, TLS certificate issuance, routing, project configuration, and request logs are handled locally. We do not receive the hostnames you create, the requests you proxy, the logs shown in the desktop app, or the contents of the services you run through Localify.

The desktop app may send privacy-preserving product analytics events, such as onboarding step views, activation success or failure, navigation between app sections, and counts like how many domains or services were added. These events are used to understand product flows and do not include project names, domains, request logs, local paths, proxied URLs, or app traffic contents. Desktop autocapture is disabled. Session replay is disabled by default and only starts if you explicitly enable diagnostic replay in the app settings; replay masks text and inputs and does not record console logs or network timing.

If you check for updates, the app may fetch release metadata from our update endpoint. That request can create standard server log data, such as IP address, user agent, timestamp, and requested file. We use that data to deliver updates and troubleshoot delivery, not to build a usage profile.

Checkout is powered by Stripe. When you buy a license, Stripe collects your payment details directly. We do not store your card number. We receive and store purchase information such as your email address, billing country, name when provided, the plan you bought, payment status, Stripe checkout identifiers, and the license key or license identifier generated for your purchase. We use this to issue the license, deliver the key by email, answer support questions, handle refunds, keep accounting records, and prevent duplicate fulfillment.

Licenses are managed by our licensing provider, Keygen. When you activate Localify on a machine, the app sends your license key, a machine fingerprint, and basic machine metadata such as platform, hostname, and device name when available. The fingerprint is a non-reversible identifier derived from a stable machine identifier, used to count activations against your plan limit and support offline license validation.

The marketing site is deliberately light. We use Umami and PostHog to understand page visits, CTA clicks, checkout flow health, and product interest. We do not run advertising trackers or cross-site retargeting.

When you click a download button, the website may write a short Localify attribution token to your clipboard. If you open the desktop app afterwards, the app can read that token to connect the website visit to the first app open in our funnel analytics. The token contains a PostHog visitor identifier, an attribution id, a source label, and a timestamp. It does not contain project data, domains, local paths, or proxied traffic.

To run Localify we rely on a small number of providers:

• Stripe — checkout and payment processing.
• Keygen — license key issuance and activation tracking.
• Email providers — license delivery, receipts, and support-related messages.
• Hosting and storage providers — hosting the website, checkout endpoints, and update files.
• PostHog — website analytics and privacy-preserving product analytics.
• Umami — lightweight website analytics.
• Private operational tools — internal order traces and notifications used to support purchases and fulfillment.

We process purchase, license, activation, update, and support data because it is necessary to provide Localify, fulfill your license, maintain product security, comply with accounting and tax obligations, respond to support requests, and protect the service from abuse.

We keep purchase, invoice, and license records for as long as needed to provide the license, support the customer relationship, and meet accounting and tax obligations. License activation records are kept while they are needed to enforce device limits and support offline validation. Support emails and internal order traces are kept for as long as useful for support, fraud prevention, and business records, then deleted or archived.

You can ask us for a copy of the data we hold about you, have it corrected, or ask us to delete it. Where applicable under GDPR or similar privacy laws, you can also object to or restrict certain processing, request portability, or complain to your local data protection authority. Some records may need to be kept where required for legal, tax, security, or fraud-prevention reasons. Email support@localify.dev and we'll respond within a reasonable time.

We and our providers may process data outside your country, including in the United States. Where required, we rely on appropriate transfer mechanisms such as adequacy decisions, Standard Contractual Clauses, data processing agreements, or equivalent safeguards.

Localify is a developer tool aimed at adults. It's not intended for children under 16, and we do not knowingly collect personal data from them.

If we change how we handle data, we'll update this page and change the Last updated date at the top. If the change is significant, we'll flag it on the website.