PeekPilot App Privacy Policy

1. Scope and who we are

PeekPilot is operated and published by Hassan Raza. This policy applies to official PeekPilot desktop and mobile apps and to their connection with the PeekPilot service at peekpilot.com. It does not control the privacy practices of websites that you choose to monitor or of operating-system and app-store providers.

2. How the apps work

• Local or disconnected monitoring: where offered, the app can check websites directly from your device without a PeekPilot account. On Windows, local monitors and their history stay in the app's local database and are not automatically uploaded to PeekPilot.
• Connected account: if you connect the app to a PeekPilot account, it securely receives your account profile, cloud monitors, check history, incidents, and queued actions. Changes you explicitly make to connected monitors are sent to the PeekPilot service.
• Demo or guest experience: if offered, this uses fixed demonstration data. It does not provide anonymous access to run arbitrary checks through PeekPilot's servers.

3. Information processed on your device

The Windows app may store the monitor names and website URLs you enter; intervals, timeouts, expected HTTP status codes or keywords; SSL and notification preferences; check results; response times; status and error details; certificate-expiry information; resolved network addresses; incidents; and app preferences such as theme, startup, and tray behavior.

If you configure an expected keyword, the app reads a limited amount of the target page response in memory to look for that keyword. In local mode, it does not save the page body in monitoring history or send that page body to PeekPilot.

Credentials used to connect an account are kept in the operating system's protected credential storage (Windows Credential Locker on Windows), separate from the monitoring database.

4. Information used in connected mode

When you connect an account, the app and PeekPilot service may exchange your account profile and plan, cloud monitor configuration and status, check history, incidents, queued actions, and connection details such as a connection label, key identifier, permissions, last-use time, and revocation state.

Requests include security metadata such as a key identifier, timestamp, nonce, and cryptographic signature. PeekPilot's server may also process ordinary connection logs, including IP address, user agent, request time, and response status, for security, fraud prevention, reliability, and troubleshooting. The connection secret remains in protected credential storage on your device and is not transmitted with signed requests.

Connecting the app does not automatically copy locally created monitors into your PeekPilot account. Only actions you choose for connected monitors are sent to the service.

5. Network interactions and service providers

Local checks go directly from your device to the website you choose. That website and the DNS, network, TLS, hosting, or security providers involved in the request may receive your device's public IP address, the app's user agent, request timing, and other normal web-request information. Their own privacy policies apply.

For connected features, PeekPilot uses service providers for website and API hosting, transactional email, security, and encrypted backups, as described in our website and service Privacy Policy. Microsoft, Apple, and Google may independently process information related to app acquisition, updates, diagnostics, payments, or store use under their own policies. PeekPilot apps do not receive your full payment-card number.

We do not sell or rent personal information, use third-party advertising SDKs, or disclose app activity to data brokers.

6. Device permissions and features

The Windows app uses internet access to perform monitoring and connect to PeekPilot. It runs as a desktop application and can optionally start with Windows and show native notifications. Startup and notifications are controlled by you. The app does not require access to your contacts, precise location, camera, microphone, photos, or documents for its monitoring functions.

Future macOS, iOS, and Android releases will request only the permissions needed for their documented features. Their final permissions and store privacy disclosures will be reviewed before release.

7. Analytics, advertising, and automated decisions

The current Windows release does not send active product analytics or advertising telemetry. Its telemetry control is disabled and does not transmit data. The app does not use cross-app tracking, targeted advertising, or automated decisions that produce legal or similarly significant effects.

If a future release introduces optional diagnostics or analytics, we will update this policy and the relevant store disclosures before collection begins and provide any consent or control required by applicable law.

8. Why we process information

We process information to provide monitoring and account-connected features you request; display results and notifications; authenticate and protect app connections; prevent abuse; diagnose failures; maintain the service; comply with law; and respond to support or privacy requests. Depending on your location, our legal bases may include performing our contract with you, your consent for optional features, compliance with legal obligations, and our legitimate interests in operating and securing PeekPilot.

9. Retention, disconnection, and deletion

Local app records remain on your device until you delete them, clear the app's data, or uninstall the app, subject to how your operating system and any device backups retain data. Disconnecting a PeekPilot account removes the saved app connection credential from the device, but it does not by itself delete your PeekPilot account, cloud monitoring records, or unrelated local records.

For the connected service, detailed checks are normally retained for 30 days. Closed incidents are normally retained for 30 days on Free and Standard plans and 180 days on Pro plans; open incidents remain until resolved. Connection and queued-action records may remain while the account is active. Encrypted backup rotation normally retains the latest 60 daily backups (about two months), although failed backup runs can extend the calendar span.

To request access, correction, export, or account deletion, email we@peekpilot.com. We aim to acknowledge deletion requests within 48 hours and remove account data from active systems within 7 days after any required identity verification. Deleted data may remain in encrypted backups until those backups rotate out.

10. Security

We use measures designed to protect app and connected-service data, including HTTPS, signed requests, unique nonces and timestamps, platform-protected credential storage, access controls, limited logging of secrets, and encrypted backups. No storage or transmission system can be guaranteed completely secure.

11. Children's privacy

PeekPilot apps are not directed to children under 16, and we do not knowingly collect personal information from children under 16. If you believe a child has provided information to us, contact us so we can investigate and delete it where required.

12. Your privacy choices and rights

You can choose local mode where it is available, decide whether to connect an account, disable startup or notifications, remove local monitors, disconnect credentials, and request access, correction, export, restriction, objection, or deletion as applicable in your region. You may also have the right to complain to your local data-protection authority.

13. Changes to this policy

We may update this policy when app features, platforms, service providers, laws, or data practices change. We will post the revised date and version here. Material changes will be communicated through an appropriate channel, such as the app, website, account email, or store listing, when required.

14. Contact us

For privacy questions or requests, email we@peekpilot.com. You can also review the website and service Privacy Policy and Terms of Service.