Yourkive

Privacy Policy

Last updated: 2026-09-20. This policy covers the app, the optional Automations subscription, and the hosted helpers that automations use. Material changes will be surfaced in the app.

The short version

Your journal is yours. We never see it. Your entries live on your device as plain Markdown files. If you turn on sync, a copy goes to your own cloud (e.g. your Google Drive) — not to us. You never need an account to write, and no server of ours stores your writing.

Nothing leaves your device unless you switch something on. The only data we keep about how you use the app is anonymous product usage, and only if you opt in — it is about the app and your device, never your content. If you have an Automations account there is also a small account — a scrambled form of your email address, your plan, and the devices you’re signed in on — and, if you pay, a purchase record held by our payment provider. Neither is linked to anything in your journal. Two more things pass through us without being kept: anything you deliberately send (feedback, a code), and the small request an automation makes on your behalf once you add it. All of it is detailed below.

What we collect (only after you choose “Share anonymous usage”)

Nothing is collected until you opt in on first run (or in Settings → Your data & privacy). When enabled, we collect:

A pseudonymous device id — a random value generated on your device so we can count distinct devices without an account. It is hashed before we store it, is tied to nothing about your identity, and you can reset it anytime in Settings.

Device / environment basics:

device class (mobile/desktop), operating system + major version, browser
screen size, window size, device pixel ratio
CPU core count and a coarse memory tier (e.g. “8 GB”), reported by your browser
language, time zone, network type (e.g. “4g”)
whether the app is installed (standalone) or running in a browser tab
approximate on-device storage used (rounded)
notification-permission state
your approximate country (derived at our edge from your IP; your IP itself is not stored)

Feature-usage events (what you do, never the content of it):

app opened; which views you open (entries / calendar / stats / automations)
an entry was created; an attachment or link was added
an automation was enabled or ran (and for which connector), and whether it succeeded
a search happened (with a count bucket of results — never the query text)
export used; theme, detail level, or lock mode changed; sync enabled
errors (an error type — never content), app version, and a rough bucket of how long the app is open in the foreground

That is the complete list. Events are structurally restricted to a fixed catalog and to primitive, length-limited values, so free text or content cannot be transmitted.

What we NEVER collect

Your entries, titles, tags, search text, file names, precise location, attachments, your Google/Drive tokens, or any content of your journal. Ever. (If you switch on an automation, it may need to send a small detail such as coordinates to answer a question — see “Automations you turn on” below. We still don’t collect it.)

Automations you turn on

This is separate from the usage data above, and it is worth stating plainly. Automations are off until you add them. When you add one, it asks a question on your behalf, and that question passes through our Cloudflare worker to reach the service that can answer it. We do not store what passes through. Specifically:

Weather sends the entry’s coordinates and date so a weather provider can say what the weather was. This means precise location does transit our worker while this automation is on — it is used to answer the request and is not written down anywhere on our side.
On this day sends only a month and day — no year, no location, nothing tied to you.
Workouts (Intervals.icu) sends the API key you entered and a date range, so your workout data can be fetched from your account there. The key is stored encrypted on your device, passes through in transit only, and we do not log or store it.

No entry text, title, or filename is ever included in an automation request. Each automation states what it shares before you add it, and removing it stops the requests. We do count how many requests a device makes, because the free tier has a daily cap and the helpers cost us money to run — a number, with no request details attached.

Where it goes and how long we keep it

Anonymous usage is sent to our Cloudflare worker and stored in our Cloudflare account: an aggregate dashboard (Analytics Engine) and a raw, de-identified event archive (R2). We use it solely to understand which features are useful and on what devices, so we can improve Yourkive. We do not sell it or share it with advertisers.

Feedback you send

If you use the contact form or “Send feedback,” we receive what you write, an optional contact you provide, and (if you leave the box checked) basic diagnostics: app version and device basics as above — never your entries. We use it only to fix problems and improve the app.

Your Automations account

The Automations account is the one place Yourkive handles ordinary personal data, so it is worth being exact about the shape of it. You sign in with your email address and a one-time code. The account holds:

A scrambled form of your email address (a keyed hash), not the address itself. It is how we recognise you when you sign in again and how a payment finds your account. We can’t read your address back out of it.
Your plan: which plan, until when, whether it renews, and any codes you’ve redeemed.
Your signed-in devices: a label such as “Chrome on Android,” when each signed in, and roughly when each was last used — so you can see them and sign them out in Settings.

When you ask for a sign-in code, your address is used once to send that email, through our email provider, and not stored by us. Your IP address counts toward a limit on how many codes can be requested per hour and is discarded within two hours. The account is never joined to your journal or your usage data: the anonymous device id above is deliberately not connected to it, and no entry, title, tag or file name is involved in any way. We use your address only to send sign-in codes — no marketing list, no sale or sharing with advertisers.

Delete the account anytime in Settings → Automations account. That removes it and every device session at once.

If you subscribe

Your payment goes to our payment provider, not to us. They act as the merchant of record, take the card details, and issue your receipt. We never see or store your card number. Their own privacy policy governs what they hold.
The purchase record — your email address, the amount, date and status of the subscription, and the country the provider reports for tax — is kept by the provider, where we can look it up to answer a billing question or issue a refund. Tax law requires a record of the sale, so it is kept for as long as that law requires, typically several years, even after you cancel.
When a payment, renewal, cancellation or refund happens, the provider tells our worker, which updates your plan. Our own database keeps only the scrambled address and the plan, not the purchase details.

Your choices

Opt out anytime: Settings → Your data & privacy → turn off “Share anonymous usage.” Nothing further is sent.
Reset your device id anytime in the same place.
We hold none of your content, so there is nothing of your journal for us to export or delete.
Delete your Automations account anytime in Settings → Automations account.
If you have subscribed, email [email protected] to see or delete your purchase record. We will delete what the law lets us — the record of the sale itself has to be kept for the tax retention period.

Contact

Questions: [email protected]

← Back to Yourkive