Horology Vault Privacy Policy

Last updated: 11 November 2026

This policy explains what Horology Vault does with information about you. In short, your collection stays on your iPhone and in your own backups (section 4.4). A few things leave your iPhone only when you send them yourself, and, apart from Apple's own services (section 4.6), one kind of small request happens on its own once you allow it: a download of public exchange rates, repeated whenever the app's rates are missing or more than 12 hours old (section 4.3). All of them are listed here.

This website

This website is hosted on Google Cloud Run in its us-central1 region in the United States. Google processes technical request information, which can include your IP address, the requested page, request time and browser details, to deliver the website and support its security and operation. Google Cloud may retain these technical logs under the hosting account’s logging settings and its applicable service terms. We have not yet completed a review of the configured retention period.

This hosting information is separate from the app data described below. Browsing this website does not give us access to your watch collection.

1. Who we are

Horology Vault is made by EndKai: Endkai SA, c/o Kellerhals Carrard Genève SNC, c/o Kellerhals Carrard Genève SNC Rue François-BELLOT 6, 1206 Genève, Switzerland, CHE426322163 ("we", "us"). We are responsible for the information described in this policy.

2. The short version

3. What stays on your iPhone

If you delete the app, iOS deletes its data from your iPhone, with two exceptions:

4. What leaves your iPhone, and when

Every connection the app opens itself, and every hand-off to Mail, the share sheet or a web search in your browser, is listed in the app's code, and a test checks the code against that list. The encrypted iCloud Drive backup (section 4.4) and the install check (section 4.6) go through iOS and Apple's services instead, and the links of section 4.8 carry nothing from your vault. These are all of them.

4.1 Email to support

Some buttons open your own email app with a prepared support message. Use contact@horologyvault.app as the recipient; if your test build fills in a different address, change it before sending. You can read and change the message, and you send it yourself; the app opens no connection of its own.

4.2 AI providers you choose

Horology Vault is private by default: Watch Expert answers on your iPhone (section 3). In Settings › AI Services you can also choose a cloud AI provider, OpenAI's ChatGPT, Google's Gemini, Anthropic's Claude or xAI's Grok, and add your own API key for it. If you do, you decide what it gets, the way you decide what goes into a PDF report you share with a friend:

4.3 Exchange rates

To convert between currencies, the app downloads public exchange rates from fxratesapi.com. If that fails, it uses the European Central Bank's daily feed (ecb.europa.eu).

4.4 Backups

4.5 Catalog suggestions

In Settings › Data & Sharing › Suggestions to Horology Vault you can review a suggestion for the app's watch catalog and send it to us from your own email app. The email holds the catalog details you reviewed: the brand, model or catalog option (such as a case material or a complication) as you entered it for one of your watches, with a model's brand, and a brand's country and founding year when you gave them. As the review lists under Technical Metadata, it also holds the app's language and region, the catalog's version and a duplicate-prevention key made from the suggestion itself; part of that key is also in the email's subject. Nothing else from your vault is added: no watch ID, serial number, value, location, note, photo or document. We receive your email address and the name your email app sends with it, and section 4.1 applies.

4.6 Apple, and testing with TestFlight

4.7 Things you share yourself

4.8 Links and web searches

5. Who processes data for us, and where

Who Role Data Where
Proton AG (Proton Mail) Stores support email for us, under its data processing agreement Your email address and the name your email app sends with it, your message and its attachments Switzerland, Germany or Norway
Apple TestFlight, App Store Connect and the crash reports it shares with us As described in section 4.6 Under Apple's own terms
OpenAI (ChatGPT and Codex) and Anthropic (Claude and Claude Code) Help us find and fix problems in the app, on our computer What sections 4.1 and 4.6 say they read: the technical details of the reports and crash data we receive, the short notes we write about the problems your emails report, and what we keep of App Store reviews; never the text of your emails, your TestFlight comments or screenshots, your email address, or the name your email app or TestFlight gives us; of a review, they read the text as section 4.6 says we keep it, with any name you wrote in it OpenAI: processing can take place in the United States and other countries where OpenAI and its service providers operate; choosing a storage region does not restrict inference to that region, and business safety and abuse-monitoring data is stored in the United States. Anthropic: data is stored in the United States; its default processing can route through the United States, Europe, Asia and Australia, with other processing where Anthropic or its affiliates operate. These are the providers’ published business-service practices; no exclusive Swiss or EU processing location is claimed.

Each provider in this table other than Apple processes data only for us, under terms that protect it at least as well as this policy. The AI providers you choose (section 4.2) aren't our processors: you choose them, you add your own key, and they handle your requests under your agreement with them.

fxratesapi.com and the European Central Bank aren't our processors. The app asks them for public rates directly, and they receive nothing about you beyond what any internet request shows (section 4.3).

When data goes to a country that Switzerland, the EU or the United Kingdom doesn't consider to protect it adequately, we rely on safeguards: the EU Standard Contractual Clauses, with the changes Swiss or UK law requires, or the Swiss-US or EU-US Data Privacy Framework, with its UK extension, where the provider is certified. You can ask us for a copy of these safeguards.

6. How long we keep it

What How long
Support emails, and anything attached to them 12 months after the last meaningful exchange.
Anonymous ideas and themes on our list for future versions Kept for planning without the sender's identity. The original email follows the support-email retention period above.
Copies on our computer of crash reports, screenshots and logs from Apple and TestFlight, and of the emails that report a problem (your message with email addresses removed, what you attached and the app's report) Until 90 days after we close the issue they belong to, or 180 days after they arrive if that comes first. A file from such an email that our tools can't read, or an email they can't file, is kept as it came, email addresses included: it goes with the email's copies, and at the latest 180 days after we set it aside.
A short record on our computer of each email that reports a problem (when it came, the app's build and version, the iPhone model, the report's code and the name of the folder we saved it as, and the issue we file it under, with our notes about it), and a fingerprint of the email that stops it from being filed twice The record: with the copies above. Our notes: until every report filed under that issue has reached the limits above. The fingerprint: until 180 days after the email arrives.
Crash logs that Xcode downloads from Apple when we open its list of crashes, on our computer Until 180 days after the newest log of the same crash arrives: our clean-up deletes each crash's logs once the newest of them is more than 170 days old.
The text of TestFlight feedback, with email addresses removed, and a short record of each report (when it came, the build, the iPhone model, the iOS version and a coded tester ID) The text: the same limits as the copies above. The record: the same limits as the copies above, except a coded reference that stops the same report from being downloaded twice, kept until 180 days after the report was made.
App Store reviews, on our computer: the title and text, without email addresses or @handles, and without your nickname if it is three characters or longer; the star rating, country and date; your nickname as a code The text: until 180 days after we download it. The code: with our copy of the review, until 90 days after we close the issue it belongs to, or 180 days after we download it if that comes first. The rating and the country: with our copy of the review, as the code. The date and Apple's ID for the review: with our copy too, then only as a reference that stops the same review from being downloaded twice, until 180 days after you wrote the review.
Our notes and emails for inviting testers (section 4.6) 12 months after the testing round ends.
Our list for telling writers and people we know about the release, and those emails (section 7) 12 months after our last exchange.
Requests about your data, and how we answered them In our support mailbox, for 12 months after the last meaningful exchange.
What our AI coding tools keep on our computer of what they read for us (section 5) Local conversation records remain until deleted or cleaned up by the tool. We have not adopted a fixed automatic deletion period for these records.
What the makers of those tools keep of it Saved conversations and coding sessions can remain until deleted or removed under the workspace's retention settings. OpenAI and Anthropic describe deletion periods and exceptions in their current business-service terms: deletion generally completes within 30 days after a saved conversation is deleted, with exceptions for legal obligations, security or misuse prevention. Provider feedback submissions and some service-specific records have different periods. This is not a promise that every record is deleted 30 days after it is created.
On your iPhone: your vault Until you delete it, or delete the app (section 3)
On your iPhone: claim packets (Tools › Claim Packet, under Recent Packets) The newest packet of each kind (Insurance Claim, Proof of Ownership and Policy Review) for each set of watches, until you delete it there, make a new one of that kind for the same watches, or delete the app. A packet keeps what it holds about a watch after you delete that watch, until you delete the packet, and packets are in your backups (section 4.4).
On your iPhone: the technical event log Two small files, the newest events replacing the oldest
On your iPhone: problem records 30 days, at most 50

7. Why we're allowed to use it

The Swiss Federal Act on Data Protection (FADP) applies to us. The EU General Data Protection Regulation (GDPR) also applies when you're in the EU or EEA, and the UK GDPR when you're in the United Kingdom.

You don't have to send us anything. If you don't, the app works the same.

8. Your rights

You have the right to:

How to use them. Write to contact@horologyvault.app. We answer within 30 days.

What we hold. We hold only what you or Apple sent us, our notes for inviting you to test and about the problems your emails report, our list for telling writers and people we know about the release, and a record of any request you make about your data: support emails, the details of your invitation, your name and email address, with a writer's publication, if we told you about the release (section 7), and, from Apple, crash data, your TestFlight details (name, email address, device details, installs and sessions) and feedback, and App Store reviews (sections 4.1 and 4.3 to 4.6). Your vault on your iPhone and your encrypted iCloud Drive backup are yours alone: we can't see them, and you can delete them yourself (sections 3 and 4.4). We never receive what you send to an AI provider you chose: for those requests, contact that provider (section 4.2).

9. Security

10. Children

Horology Vault is meant for adults and isn't directed at children. If you think a child has sent us information, write to us and we'll delete it.

11. Changes to this policy

When we change this policy, we update the date at the top. Before a significant change takes effect, for example a new kind of data leaving your iPhone, we say so in the notes of the app update that brings it. Earlier versions are available on request.

12. Contact

EndKai: Endkai SA, c/o Kellerhals Carrard Genève SNC, c/o Kellerhals Carrard Genève SNC Rue François-BELLOT 6, 1206 Genève, Switzerland, CHE426322163. contact@horologyvault.app.