Knock Knock

Privacy Policy

Last updated: [date you publish this]

Before you publish this page Legal name, contact email, domain, and country are filled in below. Still open: the "Last updated" date (set this when you actually publish), confirming no third-party SDK has been added, and the App Store age rating. Note: Iddaveru is not yet a registered business — the policy currently names Fabio Sebastiano Pulvirenti as the responsible person trading as Iddaveru; update this once KvK registration is complete. This draft assumes no analytics or crash-reporting SDK is in the app and that Apple's App Store / StoreKit handles all payment processing directly — if you add a CloudRelayTransport (server-based delivery) or any third-party SDK later, this policy needs a real update before that ships, not just a version bump.
01

Who this policy covers

Knock Knock is developed by Fabio Sebastiano Pulvirenti, trading as Iddaveru, based in the Netherlands. This policy explains what happens to your data when you use the Knock Knock app. If anything here is unclear, contact us at privacy@iddaveru.com.

02

The short version

Knock Knock is built to work without a server. When a visitor takes a photo and sends it to you, that photo travels directly from their device to yours over your local Wi-Fi or Bluetooth connection — it never passes through us, and we never see it, store it, or have the ability to access it. We don't require an account, we don't collect your name or contact details, and there's no database anywhere with your information in it.

03

What the app processes, and where it stays

Photos

When someone uses Knock Knock to let you know they're at your door, their device captures a photo and sends it directly to your device over a peer-to-peer local network connection. The photo is held in memory on your device for as long as it's on screen, and is discarded — not saved to disk, not backed up, not uploaded anywhere — once you respond or dismiss it.

Messages

If a visitor leaves a predefined message instead of a photo (for example, to say they'll come back later), that message is delivered the same way: directly between the two devices on the same local network, never through us.

Device identifiers

To connect two nearby devices, the app exchanges a device identifier and display name over the local connection. These stay on the two devices involved and are not sent to us.

04

Permissions the app asks for

You can decline or later revoke any of these in your device Settings; doing so may prevent parts of the app from working as intended.

05

Purchases

Knock Knock and its optional Pro unlock are sold through the Apple App Store. Apple processes payment and handles your billing information directly — we never receive or store your card details. We only know that a purchase was made, not who made it, through Apple's standard transaction receipt system.

06

Third-party services

[Confirm: as of this draft, the app does not use any third-party analytics, advertising, or crash-reporting SDK. If that changes — for example, if you add crash reporting — list the service here, what it collects, and link to its own privacy policy.]

07

Data retention

We don't retain your data because we never receive it. Photos and messages exist only in your device's memory for the duration of the interaction, and are cleared automatically.

08

Your rights

Because we don't collect or store personal data on our own servers, there is typically nothing for us to provide, correct, or delete on request. If you're in the European Economic Area, UK, or another region with data protection laws that grant you rights such as access, correction, deletion, or portability, you're still welcome to contact us at privacy@iddaveru.com with any question about how the app handles data, and we'll respond.

09

Children's privacy

Knock Knock is not directed at children and we do not knowingly collect personal data from children. [Confirm the App Store age rating you select and keep this line consistent with it.]

10

International data transfers

Since photos and messages travel directly between two nearby devices and never reach our servers, there is no international transfer of this data by us to disclose.

11

Changes to this policy

If we change how the app handles data — for example, if a future version adds an optional server-based delivery method — we'll update this page and change the "Last updated" date above. Material changes will be flagged in the app itself.

12

Contact

Questions about this policy: privacy@iddaveru.com