Privacy Policy
Last updated: November 7, 2026
PingKit ("we", "our", or "the app") is committed to protecting your privacy. This Privacy Policy explains how we handle information when you use PingKit for iOS and PingKit Agent for macOS.
Information We Do Not Collect
PingKit does not collect:
- Personal identification information (name, phone number, or email address, unless you give one yourself, for email alerts, for a reply to a report you send, or for the launch email on our website)
- Device identifiers for tracking purposes (no advertising identifier). The identifiers PingKit does use, to enforce AI usage limits and to deliver monitoring alerts, are described below and are never used for tracking.
- Behavioural profiles, or any record of what an individual user did
- Advertising data
- Your browsing history, the contents of your traffic, or your diagnostic results
We do not operate any third-party analytics or tracking. There is no account system and no login, and nothing to sign up for to use PingKit; the one list you can join is the launch email on our website, described under Launch Email below. PingKit-operated services that do receive data are the anonymous feature counts described immediately below, the crash and hang reports described after them, the AI service at ai.pingkit.app when you have allowed it, the IP lookup service at geo.pingkit.app (see IP Geolocation below), Cert Monitor and Uptime Watch monitoring (monitor.pingkit.app), email or webhook alerts if you turn them on, your refund choice if you turn on Share Refund Facts with Apple, the reports you send through Report a Problem or Suggest Something, and the launch email list if you join it (both at feedback.pingkit.app). Some AI answers are produced by Apple Private Cloud Compute instead, which is Apple's infrastructure rather than ours; that flow is described under AI Features below.
Anonymous Feature Counts
To understand which parts of the app people actually reach, PingKit sends aggregate counts of in-app events (for example, that a subscription screen was shown, or that a free trial was started) to our own server at monitor.pingkit.app. This is the only usage measurement we perform, and it is deliberately built so that it cannot describe an individual. When PingKit tries two versions of a screen to learn which one helps people more, the counts also say which version was shown.
Each report contains only:
- The app version
- Your device language, without the region (for example "en", never "en-GB")
- Whole-number counts per event since the previous report
Each report deliberately excludes:
- Any identifier. No device ID, no account, no advertising identifier, no installation ID, no push token. The request is unauthenticated, so two reports from one device are indistinguishable from reports sent by two different devices. From version 3.1.3, each report carries one random number, made fresh for that report and never reused. It lets our server recognise the same report if your device has to send it twice, so it is counted once. It cannot connect one report to another.
- Any timestamp from your device. Our server records only when a report arrived.
- Any content. No addresses, hostnames, scan results, diagnostics, or purchase details.
Your IP address is used only to rate-limit abuse at the network edge and is never stored alongside these counts. Because there is no identifier, we cannot single you out, build a profile, or link these counts to anything else, and we could not delete "your" data on request because we have no way to tell which rows are yours. These counts are never sold or shared, and are not used for advertising or for tracking you across apps or websites. Reports older than roughly 13 months are deleted.
Crash and Hang Reports
From version 3.3.2, when Apple's MetricKit framework gives PingKit a report that the app crashed, stopped responding, used too much processor time or wrote too much to storage, PingKit sends a trimmed copy to our own server at monitor.pingkit.app, so that we can find the fault and fix it. Apple usually hands these reports to the app the next time it opens, and decides which reports it provides. PingKit has no switch of its own for them.
Each report contains only:
- What kind of problem it was and Apple's technical codes for it: for a crash, the exception type and signal, the name of any error (never its message) and the reason the system gave for ending the app, with any file path and identifier removed; for a hang, how long it lasted
- The PingKit version and build it happened on, the operating system version, the processor type, and whether the app came from the App Store or TestFlight
- Where in the program it happened, as the chain of calls that led there: for each call, the name of the part of the app or system it was in, that part's build identifier (the same for everyone using that version) and a position inside it
Each report deliberately excludes any identifier (no device ID, installation ID, account or push token), your device model, your region and language, any file path, and any timestamp from your device. As with the feature counts above, the request is unauthenticated, so a report cannot be linked to you, to your device, or to another report. Each upload carries one random number, made fresh for that upload, so that an upload sent twice is counted once. Your IP address is used only to rate-limit abuse at the network edge and is not stored. Reports are deleted after 180 days. Nothing is sent from development builds, screenshot runs or tests.
Report a Problem and Suggest Something
From version 3.3.2 both apps have a form for telling us about a problem or an idea: on iPhone and iPad under Info > Support (the gear at the top of Home), on a Mac under Settings > General > Feedback in PingKit Agent, and through a link at the foot of the subscription screen and after you give a reason for cancelling. Nothing is sent until you press Send, and the form shows you everything that will be sent first.
A report contains what you write (up to 4,000 characters), whether it is a problem or a suggestion, where you opened the form, the PingKit version and build, the operating system version, your device's model (for example "iPhone17,2") and your device language. You can also add:
- An email address, if you would like an answer. It is optional and used only to write back about that report.
- Diagnostics, off unless you turn them on: your device's address on your own network and your router's, your plan, whether PingKit's own AI service is allowed, and Low Power Mode on iPhone and iPad, or on a Mac whether it is on Wi-Fi and whether it is running on battery. Device and network names are replaced before you see them, and only private addresses stay.
Reports go to PingKit's own service at feedback.pingkit.app, a Cloudflare Worker, and carry no account and no device or installation identifier. Your IP address is not stored with a report: to limit abuse, the service counts reports per day under a one-way hash of the address and the day, never the address itself, and clears earlier days' counts every day. We read reports to fix problems and decide what to build, and delete each one, with any email address and diagnostics sent with it, 12 months after it arrives. They are never sold or shared, and are not used for advertising or marketing. To have a report deleted sooner, write to [email protected] with the reference the app shows after sending, or from the address you gave.
Local Data Storage
Both the iOS app and macOS Agent store data locally on your device using Apple's SwiftData framework:
- Diagnostic history: Results from ping, traceroute, speed tests, and other network tools are saved locally for your reference.
- Discovered devices: LAN scan results including IP addresses, MAC addresses, hostnames, and vendor information are stored on-device.
- Saved configurations: Wake-on-LAN devices, HTTP analyzer requests, and saved targets are stored locally.
- Keys you set up: the SSH key PingKit creates for sleeping, restarting and shutting down your own machines (Guardian Plus). It stays in this device's Keychain and never syncs or reaches us, and it only proves this device to the machines you add it to.
- Purchase status: Your subscription status is managed by Apple's StoreKit and stored securely on your device. If you use Cert Monitor or Uptime Watch, the monitoring backend also keeps the tier it grants you, as described under Monitoring below.
You can delete all local data at any time by uninstalling the app.
iCloud Sync
PingKit Agent for macOS keeps its monitoring data in your private iCloud database through Apple's CloudKit framework whenever iCloud is available, on every plan; with PingKit Guardian, PingKit on your iPhone reads it from there. Only devices signed into your Apple Account can access it.
Data synced via iCloud includes:
- Discovered devices: MAC addresses, IP addresses, hostnames, vendor names, open ports, the services and UPnP details each device announces, what kind of device PingKit takes it to be, custom names, device categories, online/offline status, and when each was first and last seen
- Alerts: New device notifications, outage alerts, latency warnings, and speed drop alerts (retained for 30 days, or 90 with Guardian or Guardian Plus)
- Agent status: Whether monitoring is active, device counts, gateway and internet reachability, and latency readings, and your Mac's name
- Latency history: Timestamped latency measurements (retained for 7 days)
- Speed test results: Download and upload speeds with timestamps (retained for 90 days)
- Network timeline: Event logs such as devices joining or leaving and outage events (retained for 30 days, or 90 with Guardian or Guardian Plus)
- Requests from your iPhone to your Mac: waking a saved device (with its hardware address and the address to watch), running a scan or a speed test, or changing a device's alert settings, and the result the Mac reports back. Each request is deleted a day after it has run
- Subscription status: Used to verify Guardian access across your devices
This data is encrypted in transit and at rest by Apple. It never passes through any server we operate. We cannot see, access, or retrieve your iCloud data. For details on how Apple handles CloudKit data, see Apple's Privacy Policy.
Monitoring (Cert Monitor and Uptime Watch)
Uptime Watch is available to everyone (one URL at no cost, up to ten targets with Guardian), and so is Cert Monitor (one domain at no cost, more with Guardian and Guardian Plus). Both are optional and neither sends anything until you add a target yourself. Uptime Watch checks your targets from a PingKit-operated backend (a Cloudflare Worker at monitor.pingkit.app), so it keeps checking while your devices are asleep; Cert Monitor's certificate readings are taken by your iPhone or Mac and sent to the same backend, which sends the alerts. When you add a domain or endpoint, that target and its check results are uploaded to and stored on this backend.
The backend holds only:
- The domains, URLs and host-and-port targets you choose to monitor and the names you give them, with the TLS port for certificate checks and any keyword or expected status code you set for an uptime check
- Your subscription tier (free, Guardian or Guardian Plus), which sets how many targets you may add and how often they are checked. For Guardian or Guardian Plus, the app sends Apple's signed record of your subscription, and the backend keeps from it the plan, when it renews or ends, whether it was a test purchase, and Apple's identifier for the subscription, so that the tier ends when the subscription does. It holds no payment details
- Their certificate and uptime check results (issuer, expiry, TLS version, status codes, response times, and availability)
- A random per-device identifier and your Apple Push Notification token, used solely to send you alerts
- If you turn on email alerts (Guardian Plus), the email address you give, whether you have confirmed it, and when the last weekly summary was sent; and, for seven days, a one-way hash of each address a confirmation link was sent to, used only to limit how many links one address can receive
- If you add a webhook (Guardian Plus), the web address you give for it, and, for email or webhook alerts, the language their messages are written in
- If you turn on Share Refund Facts with Apple, that choice, with Apple's identifier for the subscription it covers, as described under Refund Requests below
- To stop abuse, and for 30 days: the IP address each new registration came from, with a count per day, and the IP address of any request refused for a missing or unknown key. Neither is linked to your targets, your device's identifier or your email address
Uptime check results are kept for 30 days. Removing a target or a domain in the app deletes it with all of its results. A device that has made no request for 120 days and that Apple will no longer deliver notifications to is deleted with everything stored for it.
This data is limited to what is needed to run the monitor and notify you. It is never sold or shared, and it is not used for advertising or tracking. Your device inventory, scans, and general diagnostics are not sent to this backend: your iPhone's stay on your iPhone, and the Mac Agent's are kept in your private iCloud as described above.
PingKit Agent for Docker and Raspberry Pi
When you pair a PingKit Agent for Docker and Raspberry Pi, the agent sends PingKit's server alert events and a check-in every five minutes (the agent's version and whether its internet check passed). Alert events pass through PingKit's server to Apple's push service and are not stored; PingKit keeps only the kind of event, how many, and when. Device names never rest on PingKit's servers. Your iPhone reads your devices from the agent directly, on your network or over your own VPN.
To pair them, the same monitoring backend keeps a record of the agent bound to your iPhone's per-device identifier: a random identifier for the agent, its number on your iPhone, the keys the two use to recognise each other, the agent's version and kind of processor, and when it last checked in. The name you give an agent stays on your iPhone. The record of each alert event (its kind, when it happened, how many devices it covered and whether it was delivered) is deleted after 30 days. Removing the agent on your iPhone deletes its record.
Every agent, paired or not, also checks every five minutes that it can reach PingKit's server, as one of its internet checks. The request carries nothing about you, your devices or your network. Like any connection, it shows the server your public IP address; PingKit does not store it.
Email Alerts (Guardian Plus)
Guardian Plus can also send your Uptime Watch and Cert Monitor alerts, and a summary every Monday, by email. This is off until you enter an address in the app, and nothing but a confirmation link is sent to that address until you open the link and press the button on the page it shows. Anyone who never turns email alerts on gives us no email address for them.
The address is stored on the monitoring backend described above, beside your targets, and is used for nothing but these emails: no newsletters, no marketing, and no sharing. The emails are delivered by Resend, which receives the address and the text of each email only in order to deliver it; see Resend's Privacy Policy. Every email has a link to stop them, which works without signing in. Using that link, or removing the address in the app, deletes it from our backend straight away. If your Guardian Plus subscription ends, the emails stop.
Launch Email
The PingKit Agent page on our website has a form for asking for one email when PingKit Agent for Docker and Raspberry Pi is released, with a box, off until you tick it, for emails about testing it before release as well, and a question, unanswered until you choose, about which phone you would use it with. Nothing but a confirmation link is sent to the address you enter until you open the link and press the button on the page it shows.
We keep your email address, the time you confirmed it, the page's language, whether you ticked the box and, if you answered, which phone you named. We use them only for the launch email and, if you ticked the box, for emails about testing it before release; the phone answer only tells us which phones the agent should work with. Resend delivers them, and the confirmation link before them; see Resend's Privacy Policy.
All of it is deleted, and the testing emails end, when you leave the list, when the launch email has gone out, or 12 months after you confirmed, whichever comes first. Until you confirm, we store no address: only one-way hashes of it and of your IP address, cleared the next day, to stop abuse.
Webhook Alerts (Guardian Plus)
Guardian Plus can also send your alerts to a webhook: a web address you enter, such as a Slack or Discord incoming webhook. Each alert is posted to that address as a short message with its title, its text and what it concerns: a site or domain you monitor or, from the Mac Agent, the name and local IP address of a device on your network, with any description PingKit has for it. The address is stored on the monitoring backend described above and on the device where you entered it. The Mac Agent posts the Mac's own alerts to it directly, so the service at that address receives those from your own internet connection and can see its IP address, as any website can. Whoever runs that service receives the messages under its own terms, so choose one you trust. Removing the address in the app stops the messages and deletes it from our backend, and if your Guardian Plus subscription ends, they stop.
Refund Requests
When you ask Apple for a refund of a subscription, Apple may ask the developer about the purchase. From version 3.3.2 PingKit answers only if you have turned on Share Refund Facts with Apple, which is off unless you turn it on. It sits beside your subscription: on iPhone and iPad under Info (the gear at the top of Home), and on a Mac under Settings > General in PingKit Agent. It covers the subscriptions bought on that device, so turn it on where you subscribed.
If you turn on Share Refund Facts with Apple and later ask Apple for a refund, PingKit tells Apple that you agreed to this, whether your subscription was delivered, and that a free trial and free tier were available. Nothing else: no name, no email address, no usage, nothing about your network, and no view on whether the refund should be granted. Apple decides the refund either way.
To do this, the monitoring service described under Monitoring above keeps your choice with Apple's identifier for your subscription. Your device proves the subscription is yours by sending Apple's signed record of the purchase, so nobody can make this choice for someone else's subscription. If your device has not used the monitoring service before, turning the switch on registers it, as Cert Monitor and Uptime Watch do. The choice belongs to the subscription, not to the device, so it is not deleted with a device that stops using the service. Your choice is kept only while the switch is on: turning it off deletes it straight away, with the identifier stored with it, and PingKit stops answering.
Whether or not the switch is on, when Apple tells PingKit's service that a refund was asked for, the service records that it was asked, with Apple's identifiers for the purchase and the reason category Apple gives, and whether PingKit answered. These records are deleted three years after the request.
Apple keeps its own record of your purchase and of anything PingKit tells it. To access or delete the data Apple holds, use privacy.apple.com. For the data PingKit's service holds, write to [email protected].
Push Notifications
PingKit uses Apple Push Notification service (APNs) in two ways. Alerts from the macOS Agent reach your iPhone through CloudKit: when the Agent writes an alert to your private iCloud database, Apple's infrastructure delivers the notification, and none of it passes through our servers. Uptime Watch and Cert Monitor alerts are sent by the monitoring backend described above, which gives Apple the alert, including the name or address of the site or domain it concerns, to deliver to your device.
External Services Used by Diagnostic Tools
When you use certain diagnostic tools, the app connects directly to third-party services to perform the requested operation. These connections are made from your device, not through our servers:
Speed Test
Speed tests use Cloudflare's public speed test infrastructure (speed.cloudflare.com). Only bandwidth measurement data is exchanged - no personal information is sent.
IP Geolocation
Several features ask PingKit's own lookup service at geo.pingkit.app, a Cloudflare Worker, for your public IP address or for geographic and ISP information about an IP address, among them IP Geolocation and "Locate My IP", an IP address lookup in Whois Lookup, My Network, the Security Scan, and traceroute, which looks up each public hop. For your own address it answers from Cloudflare's connection data. For any other address it looks the address up in its own copy of MaxMind's GeoLite database; when that copy has no answer it asks ipwho.is, and only while the copy is unavailable does it ask MaxMind's GeoLite service first. If geo.pingkit.app does not answer, the app asks ipwho.is directly. A service it asks receives the IP address you are looking up; geo.pingkit.app itself stores neither the address nor the answer.
DNS Lookup and Security Scan
The DNS Lookup tool asks your device's own configured resolver. The Security Scan's DNS check also asks Google Public DNS (dns.google) and Cloudflare DNS (cloudflare-dns.com) to resolve a fixed test domain, apple.com, to see whether your network's answers differ. The domain name being queried is sent to these services.
Whois Lookup
Domain lookups query public RDAP servers operated by domain registries (such as Verisign, Public Interest Registry, and others), found from IANA's public list at data.iana.org. For a domain whose registry has no RDAP server, the app asks that registry's WHOIS server directly over port 43, and if IANA's list cannot be read it asks rdap.org. The domain being queried is sent to these services. An IP address lookup in the same tool goes to PingKit's lookup service, described under IP Geolocation above; a private address, such as your router's, is answered on your device and sent nowhere.
Security Scan
The external exposure check queries Shodan's InternetDB (internetdb.shodan.io), a public and free API that reports what is already publicly known about a given IP address, such as which of its ports answer. Your public IP address is sent to this service during this check, and probed from your device for open ports. On iPhone, iPad and in PingKit Agent for macOS both are off unless you turn on Check my router's exposure from the internet in Settings, and both are skipped when your router reports that its own internet address is private, shared or different from the one PingKit sees, because the address would then not be yours. The security scan also connects to captive.apple.com (Apple's captive portal detection endpoint) and may inspect TLS certificates on google.com to detect MITM interception.
Session Watch
Session Watch measures against a host on the internet: Cloudflare's 1.1.1.1 by default or, with PingKit Guardian, an Amazon Web Services endpoint in the region you choose. It opens a connection to that host and closes it again without sending anything, so the host sees your IP address, as any connection does. With Guardian, the lag-under-load test also downloads data from Cloudflare's speed test service (speed.cloudflare.com) for 15 seconds, so that service sees your IP address too. The list of regions is fetched from monitor.pingkit.app in a request that carries no identifier.
AI Features
PingKit's AI features include the assistant, security explanations, remediation guides, scan summaries and device identification. An answer can be produced in three different places, and which one produces it decides what leaves your device. PingKit tries them in the order below and stops at the first that succeeds, with two exceptions: with a PingKit Guardian or Guardian Plus subscription, the assistant tries Apple Private Cloud Compute first, then your device; and device identification, described below, uses PingKit's own service and neither of the other two.
- On your own device. Apple Intelligence's on-device model writes the answer on your iPhone, iPad or Mac. Nothing leaves your device, and neither PingKit nor Apple receives anything. This is free and needs no subscription. It requires hardware that supports Apple Intelligence (iPhone 15 Pro or later) and one of the languages Apple's on-device model covers, so it is not available on every device or in every language.
- Apple Private Cloud Compute. With a PingKit Guardian or Guardian Plus subscription, questions to the assistant go to Apple Private Cloud Compute first, with the last few turns of the conversation and a summary of your network that holds the same kinds of information listed below, and more of it. PingKit's other AI features, apart from device identification, go there when the on-device model cannot answer, carrying what that feature needs: the finding, the tool result or the device's details. PingKit does not ask a separate permission for this step. This is Apple's infrastructure, not ours: the data goes to Apple, PingKit never sees it, and Apple's own privacy terms govern it rather than this policy. Apple states that data sent to Private Cloud Compute is used only to fulfil the request, is not retained, and is not accessible to Apple. This step requires a PingKit Guardian or Guardian Plus subscription, and iOS 27 or macOS 27, or later, on a device Apple supports.
- PingKit's own AI service. If neither of the above can answer, PingKit can send a summary of your network to its own service at ai.pingkit.app, running on Cloudflare Workers AI. PingKit asks your permission before its own service ever receives anything, and it does not ask once and remember forever: you can withdraw that permission at any time, on iPhone and iPad under Info > AI (the gear at the top of Home) and on a Mac under Settings > General > AI in PingKit Agent, and the next request will ask again.
What is sent to PingKit's own service, when you have allowed it: your connection type, speed and local network settings (on a Mac, also the name of your internet provider), how many devices are on your network and what kind each one is, each device's address on your local network and, where PingKit has them, its open ports, services and risk score, what a security scan found, the hostname a device announces for itself, recent network events, and the websites, servers and certificates you monitor, by the name you gave them or by address, with their status and last error. On iPhone and iPad with PingKit Guardian, the cameras on your network and the ports your router forwards, with the description your router holds for each, are sent too. When you use the assistant, your question and the last few turns of that conversation are sent, with what the assistant measured during them. When you ask PingKit to explain a tool's result, that result is sent, including any host you typed. When you ask about a finding or a device, what PingKit knows about it is sent, which for a fix-it guide can include your router's make, model and address. The app's version and platform are sent too. Your preferred language is sent so the answer comes back in it. If a later version of PingKit sends more than this list, it asks your permission again before sending it.
What is not sent to PingKit's own service with these answers: the names you have given your devices in PingKit, hardware (MAC) addresses (device identification, below, is the one exception), your Wi-Fi network name, your public IP address, your browsing history, the contents of your traffic, or any name, email or account detail.
Device identification works slightly differently, and it is worth stating plainly. When PingKit's on-device classifier cannot confidently identify a device on your network, it can ask the AI service at ai.pingkit.app to help. That request carries what the device announces or answers with: its maker as far as PingKit knows it, the hostname it announces, its reverse DNS and NetBIOS names, its open ports, the Bonjour services and UPnP details it publishes, the server name and title of its web page, its SSH banner, every Bonjour TXT record it publishes (on some AirPlay receivers one of these is the device's hardware address), and the reply TTL with the operating-system family PingKit guesses from it. This uses the same permission as everything above and is refused outright if you have not given it, and unlike the assistant it is part of PingKit Guardian: without a subscription, devices are identified on your device only.
What is stored:
- AI response cache: Responses are cached temporarily (24 hours to 7 days) to improve performance and reduce cost. Cache keys are hashes of the request, not personal data.
- Usage counters: Per-device request counts, to enforce daily and monthly limits. On iPhone and iPad these use Apple's vendor identifier, which resets if you reinstall the app; on a Mac, a random identifier PingKit Agent creates for itself. Neither is linked to your identity.
- Feedback ratings: If you rate an answer with a thumbs up or down, the rating is stored anonymously by feature. No user identifier and no response content is stored with it.
What is not stored: your questions, your conversations, your scan results, your device names, your network configuration, or anything else that could identify you. Answers produced on your device or by Apple Private Cloud Compute are not recorded by PingKit at all, because they never reach us.
A change made on 19 September 2026, stated here because the previous version of this policy described something different. Until that date, device identification requests were written to a retained corpus intended for future model training, and that corpus included the hostnames devices announce. Hostnames frequently contain people's names. That collection has been stopped, the stored data has been deleted, and the code that wrote it has been removed from the service. No device identification data is retained today.
All Other Tools
Ping, MTR, port scanning, LAN discovery, Bonjour browsing, SSL inspection, HTTP analysis, Router mode, the SSH power controls and Wake-on-LAN operate entirely on your local network or connect directly to hosts you specify, with no third-party service involved. Traceroute does the same for the route itself, then looks up each public hop's address through PingKit's lookup service, as described under IP Geolocation above, to show where it is and who runs it.
Location Permission
PingKit for iOS asks for location permission only when you turn on Use the Wi-Fi name to tell networks apart in the History tab, a switch that stays off until you turn it on, because iOS shares the name of the Wi-Fi network you are joined to only with apps that have this permission. The iPhone app uses the permission for two things only: that name, and whether the network is open, uses WEP or is encrypted, which Security Scan and My Network show. It never reads, stores or sends your location, and the Wi-Fi name stays on your iPhone, where it names your remembered networks; PingKit does not send it to its own services or to anyone else. If you leave the switch off or decline, PingKit tells your networks apart by your router's address and the devices a scan finds, without the network name.
PingKit Agent for macOS asks for location permission once, because macOS shows the name of the Wi-Fi network you are joined to only to apps that have it. The Agent uses the permission for that name and nothing else: it never reads, stores or sends your location. If you decline, the Agent still shows your Wi-Fi signal, channel and security, just without the network name.
Third-Party Services
In-App Purchases
Subscriptions are processed entirely by Apple through StoreKit. We do not have access to your payment information. See Apple's Privacy Policy for details.
When a subscription starts, renews, changes, ends or is refunded, Apple sends PingKit's service a signed notice about it, including Apple's identifiers for the purchase, the plan and any offer used, its dates, its price and currency, the App Store country, whether it will renew, and why it ended. It never includes your name, your Apple Account or your payment details. We keep these notices to understand how our subscriptions perform. From version 3.3.2 a purchase made on iPhone or iPad also carries one of three fixed codes, saying which version of a screen PingKit showed after the first scan, or that it showed none. Every purchase in the same group carries the same code, so the code says nothing about who bought it.
Apple Private Cloud Compute
With PingKit Guardian or Guardian Plus, some AI requests go to Apple Private Cloud Compute, as described under AI Features above. It is Apple's infrastructure, and Apple's own privacy terms govern it.
Email Delivery
Email alerts, for Guardian Plus subscribers who turn them on, are sent through Resend, as described under Email Alerts above, and so is the launch email, with its confirmation link and any testing emails, as described under Launch Email above. No other PingKit feature uses email.
Crash Reporting
Apple collects crash reports for App Store builds from people who choose to share analytics with app developers, and shows them to us in Xcode. These contain technical diagnostic data (stack traces, device model, OS version) and no personal information or network diagnostic results. PingKit's own crash and hang reports are described under Crash and Hang Reports above. We do not use any third-party crash reporting services.
Children's Privacy
PingKit is not directed at children under 13. We do not knowingly collect information from children.
Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date.
Contact Us
If you have any questions about this Privacy Policy, please contact us at: