Privacy
Last updated 21 November 2026.
Your data lives on your devices. We never hold readable personal data.
Current is a family of apps made by Klare Inc. (a Delaware company; Klare's own site is a separate product). This page covers every Current app and the Current assistant.
Where your data lives
Everything you record sits in one vault on your phone, shared by the Current apps. If you turn on iCloud, it syncs through your own iCloud account, which we cannot read. There is no Current account and no login. Health, body, money, document, residency and journal data is encrypted in iCloud, and you turn Apple's Advanced Data Protection on or off yourself.
What we store
Only what is needed to run the paid plans and keep the service fair, keyed by an anonymous ID your devices make, never by your name or email:
- Purchases are handled by RevenueCat and Apple: the product, dates, price and storefront country, under a hash of your anonymous ID.
- One number per month: how much of your plan's model allowance you have used, under a hash of your anonymous ID. No messages, no models, no times. It expires five days after the month ends. The one-time free dollar of cloud models each device gets has its own counter, kept for as long as the service runs so the dollar is not given twice.
- Rate limits: how many messages you sent today, and, for protected catalogs, how many downloads, which expire by themselves.
- App Attest keys: the public key of each install, to check requests come from our apps, not linked to your anonymous ID, kept while the install is active.
- Purchase records at RevenueCat are kept as long as the subscription history matters, and are deleted on request.
What passes through and is not kept
When you use the assistant, your phone sends only the slice of your records that a question needs, together with your message, to our relay on Vercel and, through Vercel's AI Gateway, to an AI model provider. The slice can include the names, relations, birthdays and keep-in-touch rhythms of the people you keep in the app Pod, and when you were last in touch, never your notes about them or anything from your Contacts. The relay keeps nothing: no message bodies, IP addresses or anonymous IDs in logs, and no content in traces. Model providers are used only under zero data retention and no training on your data. Photos you attach go with that one message, downscaled and with no location or time, and your vault keeps a link into Photos, never a copy.
Sensitive records (health, body, money, documents, residency, journal) are not sent to a cloud model unless you consent. You are asked once, and you can revoke it on the Vault screen. Apple's on-device model never leaves your phone; Apple's Private Cloud Compute counts as a cloud model under the same consent.
If you connect your own API key (OpenAI, Anthropic or Google), it travels with each message, is held only for that turn and is never stored or logged. The turns you run on it go straight to that provider under its own terms, not ours, and the app tells you so when you connect it.
The web search the assistant can run (Perplexity, through the same gateway, under zero retention) sends only a short query it writes, never your records, and nothing sensitive, from our servers so the search provider sees no IP of yours. It is not used on turns that run on your own key.
The sensitive-data consent also covers Apple's Private Cloud Compute, if and when a feature uses it; Apple's terms say no prompt is stored. Our servers keep no message, photo, key or record from any of this: session state is short-lived and responses are never cached.
What your phone asks others for
- Tides and swell (Stormglass): your position rounded to about 5 km, with our key, no ID.
- Links you add: YouTube's public oEmbed for a video's title, and its privacy-enhanced player when you watch inside Channel; another page's first few kilobytes for its title; a recipe page for its recipe. Those sites see your IP and the link, as when you open it yourself, and nothing from your vault.
- Catalogs and the body's detail from our public file store: the same files for everyone, so a request never says which part you look at.
- Climate and soil data for Homebreak's land twin (NASA POWER, Open-Meteo, SoilGrids, Copernicus elevation): only the area rounded to about 11 km, never the plot. The twin itself keeps nothing, and those services keep their own request logs under their terms.
- Surf forecasts: our own scheduled job asks Open-Meteo for the public catalog spots only, never anyone's position or secret spot, and publishes the same files for everyone.
- Klare, if you choose to use it, is a separate product with its own login and database. Nothing is sent to it without a preview and your confirmation.
- Every one of these sees your IP address when your phone asks, as any website would, and our key where one is used. We add no ID of yours.
Every time something leaves, you can see it
Each outside request writes a line in an access log on your device, which the Vault screen shows. The assistant needs a grant to read anything and loses it when you revoke.
What we measure
Only event names, such as that a screen opened, through TelemetryDeck, which hashes its ID on your device. Never content and never joined to your anonymous ID. Apple also gives us App Store sales and crash reports under its own terms. No advertising, no tracking across apps or sites.
Your choices
- Export everything you hold, as JSON and SQLite, from the Vault screen.
- Delete your data by deleting the apps and your iCloud copy in iCloud settings.
- Ask us to delete the few server records above (purchases, allowance counters) by writing to the support address, which is published here before the first release; we need your anonymous ID, which Settings shows. Wherever you send an export is your choice and outside this page.
- Cloud features need none of these: the free plan runs on Apple's on-device models.
This website
These pages have no scripts, cookies, forms, analytics or third-party requests.
Changes and contact
If this page changes in a way that matters, the date above changes with it. Questions to the support address, which is published here before the first release.