Veiler Privacy Policy

Effective: 15 July 2026 Last revised: 1 September 2026

This Privacy Policy (the “Policy”) describes how Hiroki Kataoka (“we”, “us”) handles user information in the iOS application “Veiler” (the “App”). Please read it before using the App.

The App keeps photos and videos on your device and locks them behind a passcode or biometrics (Face ID and similar). It requires no account, and we operate no server that holds what you store. What you store stays on your device. For vaults with iCloud sync switched on under the paid “Veiler Pro” plan, an encrypted copy is also kept in your own iCloud (see section 5). On the free plan, the App displays advertising (see section 2.3).

This Policy is a translation provided for convenience. The Japanese version is the original and governs in the event of any discrepancy: プライバシーポリシー.

1. Who we are

We are an independent developer and provide the App as a personal development activity.

2. Information we collect

2.1 What you store — never sent to us

The App stores the photos and videos you keep in it, together with their titles, albums and other organising information, on your device. We operate no server for the App, and none of this is ever sent to us.

Only for vaults where you have switched iCloud sync on under the paid “Veiler Pro” plan, an encrypted copy of their contents (photos and videos, and their titles, albums and other organising information) is stored in the App’s own area of the iCloud account tied to your Apple ID. Sync is chosen by you, per vault, and is off by default. See section 5.

We never collect or hold what is inside a vault — the photos and videos themselves, their filenames, album names, or how many there are. The App does use the SDK for billing (2.2), the SDK for advertising on the free plan (2.3), the SDKs for usage records and crash information (2.4), and the SDK for sending feedback (2.5). For what each provider obtains under its own terms, see the relevant section.

2.2 Exception — subscription purchases

The App uses the SDK of a third-party service, RevenueCat (RevenueCat, Inc.), to manage purchases. It is initialised when the App starts and asks RevenueCat which plan you are on, whether or not you have bought anything. The following is sent to and held by RevenueCat:

This is used to provide the paid features, to restore purchases, and to prevent fraud. We do not use it for advertising or profiling. RevenueCat’s handling of information is governed by its own privacy policy (https://www.revenuecat.com/privacy/).

Payment itself is processed by Apple (the App Store). Neither we nor RevenueCat receive your credit card number or any other payment details.

The free plan displays advertising in the App. Advertising is delivered using the SDK of Google’s advertising service “Google AdMob” (Google LLC), and the following is sent to Google to deliver ads, measure impressions and prevent fraud.

Google handles this under its own privacy policy, and may use it for delivering and measuring advertising and for personalised advertising by Google and its advertising partners. See Google’s privacy policy (https://policies.google.com/privacy) and “How Google uses information from sites or apps that use our services” (https://policies.google.com/technologies/partner-sites).

The advertising SDK does not read the photos or videos you keep in the App, nor their titles or album names. What we receive about advertising is aggregate figures only — impressions, revenue and the like — never anything that identifies an individual user to us.

Your choices about advertising are as follows.

2.4 Usage records (measurement for improving the App)

The App records which of its features are used (for example, that an import completed, or that the settings screen was opened), using a fixed set of event names only. This is sent using Google Analytics for Firebase and Firebase Crashlytics (both Google LLC, USA). If the App fails to work correctly, the kind of failure and where in the program it occurred are recorded as well.

Nothing from inside a vault is ever sent — no file names, no album names, no counts. These records are not linked to anything that identifies you, nor to the advertising identifier (IDFA). You can stop this recording at any time from the App’s settings (“Share usage data”, under About).

2.5 Feedback submissions

When you write in through the App’s feedback screen, what is sent is the kind you picked (bug, request or other), the text you wrote, plus the app version, iOS version and device model — nothing else. Because nothing identifies you, we cannot reply. Submissions are stored in Google Cloud Firestore (Google LLC, USA).

3. Why we use it

We use the purchase-related information described in 2.2 only for the following purposes.

The advertising-related information described in 2.3 is used by Google to deliver, display and measure advertising and to prevent fraud, so that the free plan can be funded by advertising revenue. We do not use it to identify you, nor do we cross-reference it against any other information.

4. Disclosure and processors

We do not sell or rent the information we receive to third parties, and we do not disclose it to third parties except as required by law.

We engage the following providers to process information for the purposes of the paid plan and advertising. They handle it within the scope we specify.

The servers of these providers may be located outside Japan, including in the United States. They handle information under their own privacy policies and applicable law.

5. Where data is kept, and for how long

On protection: the current version of the App does not encrypt files on the device with its own encryption. It stores them in a dedicated area, behind the App’s passcode and biometric lock, and relies on the standard device protection iOS provides, such as protection by the device passcode. For stronger protection, set a passcode on the device itself.

The contents of files uploaded to iCloud, on the other hand, are always encrypted. However, so that a vault can be restored after changing phones or reinstalling, the key needed to decrypt them is stored unencrypted in the same iCloud area. This encryption therefore does not guarantee that the contents are hidden from someone with access to your iCloud account.

6. Your rights and choices

7. Biometrics (Face ID and similar)

The App can use your device’s biometrics (Face ID, Touch ID and similar) to unlock. Biometric matching is completed entirely within the device’s OS; the App never obtains, stores or transmits the biometric information itself — no face and no fingerprint. The App receives only the result of whether authentication succeeded.

8. Use by minors

Minors should use the App with the consent of a parent or guardian. We do not collect identification documents, photographs or anything similar for the purpose of age verification.

9. Changes to this Policy

We may revise this Policy in response to changes in law or in the App’s features. Where a change is significant, we will announce it in the App or where this Policy is published. Continuing to use the App after a revision constitutes agreement to the revised Policy.

10. Governing law

The interpretation and application of this Policy are governed by the law of Japan.

11. Contact

For questions about this Policy or about how the App handles information, please contact: