Privacy Policy
How PortLark uses information to operate its service. Updated October 26, 2026.
Privacy questions
For questions about how PortLark handles your information, or to make a privacy request, contact support@portlark.com.
Account and service data
We store your email address, password hash, verification and reset records, session records, tunnel configuration, client credential hashes, trial permissions, and subscription access records.
Billing and payments
Stripe processes payments and manages payment methods through its hosted checkout and billing portal. We share your account email and an internal account identifier with Stripe to associate billing with your PortLark account. We store Stripe customer, checkout, subscription and invoice identifiers, billing events, payment status, refund status, and paid access periods. PortLark does not collect or store full payment card numbers or card security codes. Stripe processes payment and billing information under its own privacy policy at https://stripe.com/privacy.
Operational records
We process connection status, traffic counters, request metadata, client versions, and security audit records to operate the service and investigate problems. Do not include secrets in tunnel names or support messages.
Network traffic
Traffic passes through PortLark infrastructure to reach your local service. Public HTTPS is terminated at our edge, so this is not end-to-end encryption between the browser and your local application. Use application-level authentication for sensitive services.
Cookies and analytics
Session cookies keep you signed in. PortLark does not require advertising cookies. Stripe checkout and billing pages may use their own cookies to process payments and prevent fraud. With your permission, we store a random browser ID and collect page paths, referrer origins, browser information, approximate country/region/city and visit times. Signed-in visits include your account ID. Location is resolved locally using DB-IP; raw visitor IP addresses are not stored in analytics. For product analytics, we send page paths, referrer origins, the allowlisted campaign labels utm_source, utm_medium and utm_campaign, download clicks, successful registration and the first confirmed tunnel connection to PostHog in the United States. Consenting signed-in activity uses an internal account ID; we do not send your email, raw visitor IP, form contents, tunnel addresses or other URL parameters to PostHog. Session replay is disabled. You can accept, decline or withdraw using Analytics preferences. Do Not Track and Global Privacy Control are respected.
Infrastructure and service providers
We use hosting and infrastructure providers to run the service. Cloudflare provides DNS and incoming email routing; Resend delivers account emails; Stripe provides payment processing and subscription billing. These providers process information needed for their services and may process it outside your country. We do not sell personal information.
Retention and requests
Account data is retained while needed to provide the service. Operational traffic samples are retained for 30 days. Local optional page-view records are retained for 90 days and pruned hourly. PostHog product events use a one-year project retention setting. Our delivery queue retains pending events for at most seven days and delivered events for one day. Withdrawing consent stops future collection and clears pending events for the current browser and signed-in account; contact us to request deletion of previously delivered data. Billing records may be retained as needed for accounting, refunds, dispute handling, and applicable legal obligations. Backup copies may persist for their configured retention period. Contact support@portlark.com to request access, correction, or deletion of account data.