Kelpie

Privacy Policy

Effective 20 October 2026

The short version

Who we are

Kelpie ("we", "us") is a personal finance app for iPhone, run by an individual developer based in Singapore. This policy covers the website at kelpie.site, the waitlist, and the Kelpie iPhone app. It is written to meet Singapore's Personal Data Protection Act 2012 (PDPA).

Our Data Protection Officer can be reached at privacy@kelpie.site.

The website and waitlist

What we collect when you join the waitlist

Bot and abuse protection

The form uses Cloudflare Turnstile to check that a person, not a bot, is signing up. Turnstile runs in your browser and Cloudflare receives technical signals such as your IP address and browser details. When you submit, we pass the Turnstile result and your IP address to Cloudflare to verify it.

To limit repeated sign-ups we count attempts per IP address per hour. We never store your IP address: we store only a keyed one-way hash of it, which cannot be turned back into the address, and we delete these counters within two days. When many sign-ups come from the same address in one hour, the later ones are saved and their confirmation email is sent after the hour ends. While a sign-up waits, it keeps that hash so queued emails go out in order; we delete the hash as soon as the email is sent, and in any case within two days.

Why we use it

We rely on your consent, which you give by submitting the form. You can withdraw it at any time (see "Your choices and rights").

What we don't do

Kelpie's own pages set no cookies and use no advertising or cross-site tracking. The form keeps the campaign tags from your link in your browser's session storage until you close the tab, so they survive moving between our pages. Cloudflare Turnstile may store a short-lived token in your browser to do its check.

How long we keep it

In the Kelpie app

This section applies once you sign in to the Kelpie iPhone app, including during the TestFlight beta. The app is for people aged 18 and over.

What the app collects and stores

Why we use it

We do not sell this data, use it for advertising, or use it to train AI models.

Forwarded bank alerts

Kelpie does not connect to your mailbox. You set up a filter in your own email service that forwards only your bank's alert emails to your forwarding address. Cloudflare receives the email and passes it to our servers, which read it. Only alerts carrying a valid signature from the bank's own domain are saved as transactions. Anything else, such as an alert you forwarded by hand, is used at most to show you a preview during setup and is never saved as a transaction. Alerts we cannot read are discarded straight away unless you have opted in to 30-day retention, in which case we keep the email for 30 days and then delete it. You can pause forwarding, change your forwarding address (the old one stops working immediately), or turn the 30-day option off, at any time in the app.

AI features and your provider key

The AI advisor runs only on an AI provider key that you add yourself, and any charges are yours. When you ask the advisor something, the question and the parts of your financial records needed to answer it are sent to the provider you chose (for example OpenAI, Anthropic, Google or Groq), under that provider's terms. Kelpie does not use its own AI keys for your requests. You can remove your key in the app at any time.

Analytics

The app sends product analytics to PostHog's EU cloud. Events say what you did in the app, such as "finished the accounts step", and are tied to your Kelpie account ID. A filter in the app drops anything that looks like financial content, so events never carry amounts, merchants, descriptions, account names or email addresses. Screen recordings, where used, are limited to onboarding screens with text masked.

Exporting and deleting your data

Backups

We do not currently keep backups of the app database. When your scheduled deletion takes effect, your data is removed and cannot be recovered. We keep a log of deleted account IDs and deletion dates (nothing else) as a record that each deletion was carried out.

How long we keep it

Who processes your data

We use these service providers to run Kelpie. Each processes data only to provide its service to us, except your chosen AI provider, which acts under your own agreement with it.

ProviderWhat forWhere
SupabaseDatabase, sign-in and servers for the waitlist and the appSingapore
ConvexAI advisor data: conversations, memory and your encrypted provider keyEU (Ireland)
Amazon Web Services (SES)Sending our emailsMumbai, India
CloudflareHosting this website, Turnstile bot protection, receiving email sent to kelpie.site and to your forwarding addressGlobal network
PostHogProduct analytics from the app, without financial contentEuropean Union
AppleSign in with Apple, TestFlight and App Store distribution, push notificationsGlobal
Your chosen AI providerAnswers AI advisor questions, only if you add your own keyDepends on the provider you pick
Google (Gmail)Our inbox: email you send to kelpie.site addresses is forwarded hereGlobal

Some of these providers store or process data outside Singapore. Where they do, we rely on their contractual commitments to protect it to a standard comparable to the PDPA.

Your choices and rights

Email privacy@kelpie.site from the address you signed up with. We reply within 30 days. If you are not satisfied with our answer, you can contact Singapore's Personal Data Protection Commission.

Security

Your data travels over encrypted connections. Each person's app data is protected by row-level access rules in the database, so one account cannot read another's, and the waitlist can only be read by our own server code, not by visitors to the site. No system is perfectly secure; if a breach affects you, we will tell you and the authorities as the PDPA requires.

Age

Kelpie is for people aged 18 and over. The app asks you to confirm this the first time you sign in. We do not knowingly collect data from anyone younger. If you believe a minor has signed up, email us and we will delete their data.

Changes

We will update the date at the top whenever this policy changes.