1. Summary
Breakdown helps users understand whether connection problems appear to originate in the local network, the ISP/Internet path, or the application side. Most monitoring and troubleshooting data is generated locally on the device where Breakdown runs. Some features send data to Breakdown's cloud services so we can operate accounts, subscriptions, updates, enrichment, AI-powered troubleshooting, support, crowdsourced health data, and team/company functionality.
We do not sell personal information. We do not use personal information for targeted advertising. We use privacy-focused website analytics and first-party functional measurement for download and checkout flows.
2. Scope and controller
This Privacy Policy applies to Breakdown's public website, sign-up and dashboard pages, app, backend APIs, support and feedback channels, account and billing functionality, AI-powered Breakdown feature, crowdsourced network and app-health data features, and team/company functionality.
The data controller is PeaceCraft LLC, 2850 SW Cedar Hills Blvd #1551, Beaverton, OR 97005, United States.
3. Information we collect
Website, analytics, and marketing measurement
When you visit our website, we may collect page and performance analytics, referrer information, campaign parameters, download and checkout events, browser/device metadata, user agent, and source-IP-derived security or attribution hashes. We use privacy-focused analytics for baseline page and performance measurement. We also use first-party cookies and local storage to remember a website session, campaign parameters, download identifiers, and checkout attribution.
Account, dashboard, and billing information
If you sign in or subscribe, we collect account identifiers, email address, name where provided, organization or team membership, authentication state, dashboard session metadata, device-link records, entitlement and plan status, billing metadata, payment processor customer and subscription mirror data, invoice or checkout status, audit events, and account export/deletion request information. Our payment processor processes payment information; we do not store full card numbers.
App registration, entitlement, update, and security data
The app may register with Breakdown's API and send app version, build number, channel, platform, install or client identifiers, device metadata, entitlement checks, rate-limit information, source-IP hashes or source IP where permitted by the applicable route, and operational security data. These credentials identify an app install for service operation, abuse prevention, and rate limiting; they are not upstream provider credentials.
Local monitoring and troubleshooting data
Breakdown monitors network and app health from the device where it runs. Depending on settings and feature use, the app may process local network metadata, route and topology observations, public and private IP addresses, DNS and hostname information, TLS/SNI or service labels, app/service names, endpoint probe results, latency, jitter, loss, network interface metadata, local event snapshots, timeline data, graph history, and Evidence Reports. Breakdown does not monitor call audio/video, message contents, document contents, or the contents of encrypted application payloads.
Feedback, support, and uploaded materials
If you use the feedback form, email support, or otherwise contact us, you may provide contact information, free-text descriptions, screenshots, status snapshots, Evidence Report PDFs, attachments, logs, troubleshooting notes, or other information you choose to send. These materials may include personal information or sensitive network details, including hostnames, private IP addresses, service names, or employer/customer context if you include them.
The AI-powered Breakdown feature
When you use the Breakdown feature, the app sends your issue note, timezone, selected focus context, locally available evidence catalog, and user-authorized troubleshooting evidence to Breakdown's API. Depending on the request, this data may include app/service labels, hostnames, local network addresses, service IDs, route observations, event details, prompts, tool results, provider responses, token accounting, rate-limit metadata, and generated Evidence Report metadata. Breakdown's API sends relevant prompts and evidence to an AI service provider to generate the response.
Crowdsourced network and app-health data
When enabled, the app sends health measurements to Breakdown's cloud so we can produce broader ISP, Internet, App, and AppNet health insights. This may include timing, loss, jitter, endpoint or service classifications, path/topology attributes, ISP or ASN information, regional or coarse network context, app/service labels, and health-state observations. Section 5 explains how we treat this data.
Team and company functionality
If you use team, company, organization, or managed-device functionality, the app uploads data needed to provide those features. That data may include app details, hostnames, endpoint identifiers, local and public network observations, health history, Evidence Reports, device records, user/account identifiers, organization membership, and administrative audit information. This information is associated with your user account, device, and organization.
4. How we use information
We use information to provide, secure, support, improve, and bill for Breakdown. This includes operating the app and dashboard, registering app clients, delivering updates, processing subscriptions, enforcing plan and device limits, providing IP/ASN enrichment, running the Breakdown feature, generating Evidence Reports, receiving feedback, providing support, producing crowdsourced health insights, enabling team/company workflows, measuring website conversion, preventing abuse, debugging incidents, enforcing our Terms, and complying with legal obligations.
5. Crowdsourced health data
Crowdsourced health data is designed to help users understand whether a broader ISP, Internet, application network, or app-side condition appears to affect other Breakdown users. The crowdsourced health dataset is designed to be de-identified and/or aggregated, without storing raw source IP addresses or user account identifiers as part of that dataset. We may use coarse network, ISP, ASN, service, region, timing, and health attributes so the resulting insights remain useful without being tied to an identified user. We may generalize data, suppress small cohorts, or limit publication where we believe a combination of attributes could create re-identification risk.
We maintain de-identified data in de-identified form and do not attempt to re-identify it except to test de-identification methods or as permitted by law. We take reasonable measures to prevent re-identification, and we require recipients of de-identified data to maintain the data in de-identified form and not attempt to re-identify it except where permitted by law.
You may opt out of crowdsourced health data participation. If you opt out, Breakdown will stop sending your data for that feature, but you will lose access to crowdsourced health insights because the feature depends on reciprocal participation. Opting out of crowdsourced health data does not disable local monitoring, account services, billing, support, security, or team/company data processing.
6. Team and company data
Team and company functionality requires cloud processing because the feature is built around shared organization visibility, managed devices, administration, and collaboration. If you use these features, the necessary app data is uploaded to Breakdown's cloud and associated with your user account, device, team, company, or organization. This can include detailed app and network information such as hostnames, service labels, endpoint identifiers, local network context, health history, and Evidence Reports.
You cannot opt out of cloud processing required for team or company functionality while continuing to use that functionality. Your choices are to stop using the team/company feature, disconnect the relevant device or account where supported, or ask your organization administrator to change your access. Organization administrators may be able to view, export, retain, or delete organization-associated data according to their role and the applicable plan or agreement.
9. Retention
We retain information for as long as reasonably necessary for the purposes described in this Privacy Policy, including to provide the service, maintain local and cloud history, support users, meet legal and accounting obligations, resolve disputes, enforce agreements, preserve security, and prevent abuse. Retention periods vary by data type.
Typical retention examples include website growth and marketing events for at least five years to measure long-term acquisition and product trends, short-lived rate-limit counters, Breakdown feature records for operational support and abuse prevention, feedback submissions and attachments for support retention, account and billing records while the account or subscription remains active and as legally required, crowdsourced health data in de-identified and/or aggregated form, and team/company data for the period required by the organization plan or agreement. Website growth events can include pseudonymous session, visit, and download identifiers, referrer and campaign information, browser metadata, and source-IP-derived hashes as described above. Local app data remains on the device according to app settings and local retention rules unless you upload or sync it through a cloud-backed feature.
10. Your choices and privacy rights
You may choose not to provide optional support, feedback, or Breakdown feature inputs. You may opt out of crowdsourced health data participation, with the feature tradeoff described above. You may manage subscriptions and account information through the dashboard where available. You may request access, correction, deletion, export, or other privacy rights by contacting us.
Depending on where you live, including Oregon, you may have rights to confirm whether we process your personal information, access it, correct inaccuracies, delete it, obtain a copy, and opt out of sale, targeted advertising, or certain profiling. We do not sell personal information or use it for targeted advertising. We will not discriminate against you for exercising applicable privacy rights, but some choices may limit features that require the relevant data.
We may need to verify your identity before fulfilling a request. If we deny a privacy request, you may appeal by replying to our decision email or contacting us again with "Privacy Appeal" in the subject line.
11. Security
We use reasonable technical, administrative, and organizational safeguards designed to protect information. No system is perfectly secure. You are responsible for using Breakdown only on networks and devices where you have authority to monitor, and for avoiding unnecessary submission of secrets or regulated data through support, feedback, or AI features.
12. Age limit
Breakdown is intended for users who are at least 18 years old. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided information to us, contact us so we can take appropriate steps.
13. International processing
PeaceCraft LLC is based in the United States. We and our service providers may process information in the United States and other countries. If you use Breakdown from outside the United States, you understand that your information may be processed in countries whose data-protection laws differ from those in your location.
14. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new effective date. If changes are material, we will provide additional notice where required by law or where practical for the service.
15. Contact
PeaceCraft LLC
2850 SW Cedar Hills Blvd #1551
Beaverton, OR 97005
United States
Privacy requests: support@breakdown.live
General inquiries: info@breakdown.live