Aperture

Privacy policy

Aperture runs on your own machine. Cameras, recordings, events and accounts stay there; I have no access to them.

Last updated November 2026. This is a translation; the German version is the one that applies.

Who is responsible

Philipp Henning Buß
c/o Farma-Plus Apotheke Briseck
Jupiterstraße 1
28816 Stuhr
Germany

E-mail: contact@aperturenvr.com
Phone: +49 151 29404362

In short

These websites (aperturenvr.com, docs.aperturenvr.com and get.aperturenvr.com) have no accounts, no analytics and no tracking, embed nothing from third parties and set no cookies of their own. Fonts, images, videos and scripts come from the same server. Personal data is processed only because a server has to answer requests, when you write to me, and when you turn on notifications in the app.

Hosting and delivery

The websites and downloads are delivered by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare processes what every request carries: your IP address, the date and time, the address requested, the referring page and your browser’s identification (user agent). This is necessary to deliver the pages and protect them from attacks and abuse (Art. 6(1)(f) GDPR). Cloudflare acts as my processor (Art. 28 GDPR). Data may be transferred to the USA; Cloudflare is certified under the EU-U.S. Data Privacy Framework, which is covered by an adequacy decision of the European Commission (Art. 45 GDPR). I do not analyse this data in relation to persons. Only when a request looks suspicious may Cloudflare set a technically necessary cookie after a security check (§ 25(2) no. 2 TDDDG).

Stored in your browser

If you switch between the light and dark design, your browser remembers the choice (in localStorage, under “theme”). It is not transmitted and only serves to show the page the way you chose (§ 25(2) no. 2 TDDDG). You can delete it at any time in your browser’s settings.

Installation and updates

When you install Aperture with the command on this website, or update it with aperture-setup update, your machine downloads the setup program and the program files from aperturenvr.com and get.aperturenvr.com. Only the access data described above is processed, with no identifier of your installation and no account (Art. 6(1)(f) GDPR). Aperture never checks for updates on its own. I do not count downloads.

Aperture itself

Aperture runs on your own machine. Everything it records and stores (video, snapshots, events, detection results, user accounts and settings) stays there and on the storage you connect to it. I receive none of it: no recordings, no settings, no usage statistics. The connections your Aperture server makes by itself when you turn a feature on (for example weather data or downloading a recognition model) are described in the documentation under What leaves your network.

The app for iPhone and iPad

The app connects directly to the Aperture server you sign in to; your password goes only to that server. On the device it keeps the server’s addresses, your sign-in and the notification key (in the system keychain, on this device only and not backed up to iCloud) and your settings. It does not store video or pictures, unless you save a snapshot to your Photos yourself. The app contains no analytics, no advertising and no tracking, and apart from your server it contacts only the relay (when you turn notifications on) and Apple’s services. It uses the camera only to read a pairing code (frames are processed on the device and neither stored nor transmitted), the local network only to find and reach Aperture servers near you, and Face ID or the device passcode only for the optional app lock, which the system checks; the app never receives biometric data. If you agree in your device’s settings to share crash reports with app developers, I receive them through Apple without information about your person; Apple’s privacy policy applies to that.

Notifications through push.aperturenvr.com

Apple’s push service delivers notifications to iPhone and iPad. Because your Aperture server cannot reach Apple itself, it sends each notification to a relay at push.aperturenvr.com that I operate, and the relay passes it on to Apple.

When you turn on notifications, the app registers the push address Apple assigned to your device with the relay, together with the app’s identifier. The relay gives it a random device identifier and a secret, which the app passes on to your own server. Your server encrypts each notification with a key that only your device knows. The relay therefore receives only the random device identifier, the encrypted message and a random event identifier that Apple uses to merge duplicate alerts. Neither the relay nor I can read which camera, what was detected or when; it never receives pictures, accounts, e-mail addresses or passwords. Your device decrypts the message and loads the picture directly from your own server.

The relay runs at Cloudflare (see above), which acts as my processor. For each device it stores the random device identifier, the secret, Apple’s push address, the app’s identifier, whether it is Apple’s test or production environment, when it was registered and when a notification was last delivered; no accounts, no address of your server and no IP addresses. The entry is deleted when you turn notifications off in the app or sign out (if no other Aperture server on the same device still uses notifications), when your device registers again, when Apple reports the push address as invalid, and at the latest after 180 days without a delivered notification. A deleted entry leaves the database at once; in its automatic backup at Cloudflare it stays restorable for up to 30 days. The relay does not store messages; it only passes them on. Its logs contain no IP addresses, push addresses or messages, only the time, kind and result of a request and the start of the device identifier; they are deleted after seven days. Separately, for the statistics of its network Cloudflare keeps samples of individual requests to push.aperturenvr.com, with IP address, address requested and user agent, for about 30 days; this cannot be turned off. To limit abuse, Cloudflare counts registrations per IP address, for about a minute each time; the relay itself does not store IP addresses.

The legal basis is that you turn notifications on yourself (Art. 6(1)(b) GDPR), and my legitimate interest in protecting the relay from abuse (Art. 6(1)(f) GDPR). Delivery to your device is handled by Apple (Apple Inc., or for users in the EU Apple Distribution International Ltd., Ireland); Apple’s privacy policy applies to that. You can turn notifications off at any time in the app or in your device’s settings.

Contact

Cloudflare forwards e-mail sent to contact@aperturenvr.com to a mailbox at Google (Gmail). If you write to me or call me, I use your details only to answer your request (Art. 6(1)(b) and (f) GDPR). I delete them once the request is settled, unless statutory retention obligations require otherwise.

GitHub

The source code is hosted at GitHub (GitHub, Inc., USA). If you follow a link there, open an issue or report a vulnerability, GitHub’s privacy policy applies; issues and contributions are public there, vulnerability reports are not.

Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). You may object to processing based on Art. 6(1)(f) GDPR on grounds relating to your particular situation (Art. 21). Write to contact@aperturenvr.com. You can also lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), for example the Landesbeauftragte für den Datenschutz Niedersachsen, Prinzenstraße 5, 30159 Hannover, Germany.

There is no automated decision-making. You do not have to provide any data to use the websites.