AP Vault

AP Vault

Privacy & Security

↑

Privacy & Security

As of: November 2026

Local storage: Content you create in the app (for example documents, photos, videos, details of valuables, inventory and metadata) is stored on your device. We do not store this vault content on servers of Christiane Plander & Michael Meseke GBR and we do not analyse it there.

No central vault cloud of our own: We do not operate a cloud run by us for storing your vault data, and we do not evaluate your vault content on a server for our own purposes. In the circumstances described there, technical connections to the infrastructure of other providers can still arise — set out under “Transmission to third-party networks”. The other exceptions are the points named below (in particular email contact with us, and Apple and system services).

Note on the word “local”: It means that we do not store or evaluate your vault content centrally; processing takes place in principle in the app environment on the device. Independently of that, the app may still open HTTPS connections to third-party servers, for example when fetching an embedded model or when using other optional functions. Which data is transmitted in that case (for example public model files and, as with any web request, connection data) is named for each service in the following section — without claiming that your documents or photos are placed there “for storage with the provider” where the technical design does not provide for that.

This information applies to the native app AP Vault and the bundled web preview (together, the “application”). Christiane Plander & Michael Meseke GBR (address below) is the controller within the meaning of the GDPR for any personal processing that takes place with us (for example when you contact us). Vault content created in the application is processed on your device within the distinction above. Those contents are not transmitted to us for our own purposes, and we do not run a central user-account system for vault data — subject to the exceptions described below (email, Apple / App Store / system, and the connections to other providers named under “Transmission to third-party networks”).

Controller

Christiane Plander & Michael Meseke GBR

Managing directors: Christiane Plander and Michael Meseke

Kantstraße 13

37120 Bovenden

Germany

Telephone: +49 551 / 3810 3954

Contact

Support and general enquiries: support@ap-apps.net

Enquiries from authorities and enquiries by data subjects / data-protection rights (for example access, erasure, complaint): support@ap-apps.net

Privacy contact: For enquiries by data subjects and in proceedings with authorities, Christiane Plander and Michael Meseke (managing directors) can be reached through the contact routes above. The separate role of a data protection officer under Article 37 GDPR does not automatically attach to the managing directors. It requires that the statutory conditions of Article 37 GDPR are met and that a formal appointment is made. Independently of that, your rights as a data subject are owed by the controller (Christiane Plander & Michael Meseke GBR) and can be exercised through the addresses named above.

Applicable data-protection law

Our business is established in Germany. Where we process personal data that arises with us (for example when you contact us), we observe the General Data Protection Regulation (GDPR) of the European Union and the applicable German data-protection law. If you use the application outside the European Union, the data-protection rules of the country concerned may also apply to you where mandatory rules exist there — without changing the fact that, as stated above, we do not store your vault content centrally for our own purposes and that connections to third parties are limited to the cases named under “Transmission to third-party networks”.

Privacy (overview)

We develop the application with the GDPR in mind. Unless you contact us or expressly send data to us, we do not process your vault content on our servers, and we do not carry out profiling, advertising use or marketing of that content with us.

Place of storage: Vault data remains in the local environment provided by Apple, the system or the web runtime (including the secure app or WebKit environment). There is no permanent storage of this content on servers of Christiane Plander & Michael Meseke GBR. The app does not run a synchronisation of your vault content between devices that we operate, and it does not use a cloud of our own for that purpose. To change iPhone or to back up data, use the backup and device-transfer options offered by Apple. Which data is included in iCloud or local backups depends on your settings and on Apple’s terms.

App permissions

Depending on the function, the app may need the following access: camera (for example photos of items, document capture), access to photos / the media library (saving and choosing images), and the microphone if you deliberately use functions with voice input or video/sound. Permission is given through the relevant system dialogues.

Purposes of processing

Processing takes place in order to provide the functions of the app and to store and manage your content on the device.

Tracking and analytics

The app does not use tracking by us and does not use analytics or statistics services to evaluate how you use it.

Text recognition (OCR) and local analysis

No external OCR providers or specialist cloud services are used for text recognition and similar analysis of images or documents. Text recognition takes place on the device with components supplied in the app. Your images or documents are not transmitted to third parties for this purpose. Note: this statement applies to OCR separately from the optional object detection (machine learning / TensorFlow) described under “Transmission to third-party networks”.

Transmission to third-party networks

The following list names connections to servers that are not operated by Christiane Plander & Michael Meseke GBR, when the function described is used or a corresponding technical configuration is in place. The controller for processing that takes place there is the provider concerned, under that provider’s privacy notice. We list which categories of data are typically transmitted — not every connection contains personal content from your vault.

Google — delivery of the TensorFlow.js object model (COCO-SSD)

If you use functions that load the embedded COCO-SSD model through TensorFlow.js, the library, when the model is first loaded, fetches publicly provided files over HTTPS from the domain storage.googleapis.com (infrastructure: Google LLC / Google Cloud). What is transmitted is the requested model and helper files as a download. Your own photos or documents from the vault are not uploaded as the payload of that download request for the purpose of providing the model. After the model has loaded successfully, object detection runs on the device. As with any request for an internet resource, connection data can arise at the host and be processed there (for example the IP address of the device, the time, and the user agent). Whether and for how long the operator stores such data is set out in Google’s privacy policy. We have no access to that. Transfer to a third country (USA): Google LLC is established in the USA. Connection data can be transferred to the USA. Google LLC states that it is certified under the EU-US Data Privacy Framework (DPF). In addition, the standard contractual clauses provided by Google (Article 46(2)(c) GDPR) apply.

CDN (jsDelivr) — only if expressly enabled

If the application is configured so that helper libraries cannot be loaded from the bundled package, scripts from cdn.jsdelivr.net may be loaded under an express developer or test setting. Public program files are fetched. Your vault content is not transmitted for evaluation as such. When the files are fetched, technical connection data arises at the CDN operator (IP address, time, user agent, requested file). Legal basis: Article 6(1)(f) GDPR (legitimate interest in secure delivery). Where possible, libraries are provided locally.

Configurable endpoint for unlock codes

If a URL for sending an unlock code (meta configuration) is set in your installation, the app sends an HTTPS request to that endpoint. The content can include, for example, the email address you entered, the one-time code and a language identifier — depending on the backend chosen and its operator.

Speech recognition (Web Speech API)

If you use a function with speech recognition through the Web Speech API provided by the browser or the web view (currently intended only in a limited context), audio processing may, depending on the platform, take place through infrastructure of the browser or device manufacturer, not through servers of Christiane Plander & Michael Meseke GBR. Scope and storage are those of the provider concerned.

Legal basis (GDPR)

Where processing of personal data is necessary, it takes place under the GDPR, in particular for performance of a contract or steps prior to a contract (Article 6(1)(b) GDPR) when the app is used, and on the basis of your consent (Article 6(1)(a) GDPR) where you give it, for example for access through the system settings.

Email to us: If you contact us by email, we process the personal data contained in the message to the extent necessary to deal with your request. Legal bases can in particular be Article 6(1)(b) GDPR (contract or steps prior to a contract) and/or Article 6(1)(f) GDPR (legitimate interest in answering factual enquiries). Storage period: we keep contact requests until they have been finally dealt with. We then delete the message unless a statutory retention duty applies (for example commercial or tax periods of up to 10 years). Other enquiries with no retention duty are as a rule deleted at the latest 6 months after they have been finally dealt with.

iCloud, the system, the App Store and backups are operated by Apple or by the device. We have no access to them and no influence over that infrastructure. Apple’s current privacy notice applies, and, where relevant, paid in-app handling through the App Store under the terms there. Additional protection in the application requires that decryption information remains with you (app/device).

Helper libraries and opening connections

The application is designed to load helper libraries (for example for exports or embedded web content) predominantly from the package supplied with it, so that no internet connection is required. In narrowly limited technical circumstances (for example if bundled files are missing), individual program code can be loaded from external sources. Your vault content is not transmitted for evaluation in that process. For model downloads (TensorFlow) and the optional CDN, see “Transmission to third-party networks”.

Your responsibility, availability

You are responsible for the contents of your vault (recording, completeness, accuracy, organisation) and for suitable backups — for example through the options offered by Apple. We are not the owner of your records and in principle have no view of your local vault content. We therefore also cannot judge whether or when you created, changed or deleted an entry.

For data that is processed only locally on your device, we give no guarantee of availability at all times or of permanent availability. Impairments can arise from software faults, operating errors, device defects, updates, lack of storage, and from infrastructure and services of Apple or third parties over which we have no control. Legal consequences are governed — subject to mandatory statutory liability — by the legal notice (short form of use and liability).

Security (note)

The camera and microphone are used only after a deliberate action by you (photo, scan, video). The security mechanisms offered by Apple apply to the device and the app (for example Face ID, Touch ID or the device passcode). Close the application if the device is left unattended. On shared devices, use the system lock in particular.

Data portability and full export (Article 20 GDPR)

Under Article 20 GDPR (right to data portability) you have the right to receive the data stored in AP Vault in a structured, commonly used and machine-readable format. AP Vault implements this right through a built-in full-export function (Settings → My data → Full export as ZIP).

Contents of the export: All entries, photos, scans, documents, notes and metadata from your vault are saved as a ZIP archive on your iPhone. The archive contains a readable index.json for each folder, so that you can open and continue to use your data without AP Vault.

Decryption on export: The exported ZIP file contains your data unencrypted, so that you can read it, back it up, print it or transfer it to other systems directly. You alone are responsible for keeping the exported file secure.

Availability after the subscription ends: This export is available at any time regardless of subscription status — including if your subscription has expired or you no longer pay. AP Vault never locks you out of your own data completely. After the subscription ends, the app switches to data-access mode: reading and exporting remain possible; creating new entries and capturing new photos or scans is disabled.

Emergency-contact export (separate process): The export for emergency contacts (Settings → Emergency contacts) is a separate process and is distinct from the full export. It serves only the Apple legacy workflow (Apple Legacy Contact / death function) and contains only the contact and legacy data intended for that purpose, as a vCard file. Neither export is transmitted automatically to third parties — you choose the recipient and the means of transfer yourself.

No transfer to us: None of the exports described transfers data to servers of Christiane Plander & Michael Meseke GBR. The file remains on your device. You decide on your own whether and how to forward it (for example by AirDrop, iCloud or USB).

Your rights

Where we process personal data about you, you have the following rights under the GDPR: access (Article 15), rectification (Article 16), erasure (Article 17), restriction of processing (Article 18), data portability (Article 20), objection (Article 21, including direct marketing) and a complaint to a data-protection supervisory authority (Article 77). For data that is processed only locally in the application and is not made known to us, these rights are in practice as a rule not directed at us, but exercised in the app. You can delete content there or remove the application (note any system and cloud backups by Apple). Enquiries to us: see Contact (authorities / data-subject rights).

Withdrawal of consent (Article 7(3) GDPR): Where we process personal data on the basis of your consent, you may withdraw that consent at any time with effect for the future. The lawfulness of processing until the withdrawal is unaffected.

Right to lodge a complaint with the supervisory authority (Article 77 GDPR): You have the right to lodge a complaint with a data-protection supervisory authority. The authority responsible for us is in particular:

The State Commissioner for Data Protection of Lower Saxony (LfD Niedersachsen)

Prinzenstraße 5, 30159 Hannover, Germany

lfd.niedersachsen.de

No automated decision-making (Article 22 GDPR): Automated decision-making, including profiling within the meaning of Article 22 GDPR, does not take place.

Objection (Article 21 GDPR): Where processing is based on Article 6(1)(f) GDPR (legitimate interest) or Article 6(1)(e) GDPR (public interest), you have the right to object on grounds relating to your particular situation.

We do not process personal data for direct marketing. The statutory notice under Article 21(2) GDPR is set out below. Where personal data is processed for direct marketing, you have a right to object at any time. This also applies to profiling insofar as it is related to such direct marketing.

Changes

We update this notice when the product, the technology or the legal position changes. The version at the time you open it in the application / web preview is the one that applies.

As of November 2026 — additions: right to complain to the LfD Niedersachsen (Article 77 GDPR), withdrawal of consent (Article 7(3) GDPR), storage period for email contact, third-country transfer Google/USA (EU-US DPF), Article 22 GDPR (no automated decision-making), Article 18 GDPR stated expressly, legal basis for jsDelivr. This does not replace a version individually reviewed by a lawyer.