← Groundkeep

Privacy Policy — Groundkeep

DRAFT — have a lawyer review before publishing or relying on this. This document is a starting point written to match how the product actually works as of 2026-07-27. It is not legal advice.

Effective date: 2026-07-27 Legal entity: Yaroslav Serhiienko, carrying on business as DriveVision, a sole proprietorship in the Province of Ontario, Canada ("DriveVision", "we", "us") Contact: hello@groundkeep.app

The short version

Groundkeep is a local-first app. The version you run on your own machine does not send your data to us, does not phone home, and does not collect telemetry or analytics of any kind. Your tasks, calendar, finances, journal, health data, and everything else live in one SQLite file on your own disk, under your control, for as long as you keep it.

This policy explains the few places where anything *does* leave your machine. Exactly one of them goes to us, and only when you press Send on a bug report you wrote and can read first (section 8). Of the rest, all but one are things you turn on yourself; the exception is a weather lookup that ships on and takes one toggle to turn off.

1. The local app: no data collection

When you install and run Groundkeep locally (the standard, one-time-purchase product), the app:

• Stores all data in a single SQLite file on your own computer.
• Does not transmit usage data, crash reports, analytics, or telemetry to DriveVision or anyone else.
• Does not require an account or login to use.
• Does not include third-party trackers, ad SDKs, or analytics scripts.
• Does not check your license or look for updates over the network.

DriveVision runs no license server and no update server. The license key you paste during setup is written to a file next to the app for your own records only — nothing reads it back, nothing validates it remotely, and your copy runs the same whether that file is there or not. You find out about new versions by looking at the release notes; the app never asks anyone.

Nothing the local app does in the background reaches a server we operate, so there is nothing for us to collect. The one thing that can reach us is a bug report or suggestion you write and press Send on yourself (section 8) — it happens only on that click, carries only what the dialog showed you, and is not part of running the app.

The sections below list every network connection the app can make. All but one are off until you switch them on; the exception is the weather lookup in section 4, which ships enabled and is a single toggle to disable.

2. Optional: the AI agent (Claude Code / Anthropic)

Groundkeep's agent features work by letting a Claude Code session — running under your own Anthropic/Claude subscription — read and write your Groundkeep data through a local, documented API on your own machine.

• This is BYO: you provide your own Claude Code account and pay Anthropic directly. We do not have access to your Anthropic account or billing.
• When you use the agent, the data it reads or writes (e.g. "summarize my week," "add these tasks") is sent to Anthropic as part of that conversation, under Anthropic's own privacy policy and terms, not ours. We do not see this traffic and it does not pass through any server we operate.
• If you don't use the agent feature, no Groundkeep data is ever sent to Anthropic.
• Review Anthropic's privacy policy directly for how they handle data sent to Claude: https://www.anthropic.com/legal/privacy

Groundkeep is an independent product and is not affiliated with, endorsed by, or sponsored by Anthropic. "Claude" and "Claude Code" are trademarks of Anthropic. The subscription is bought from and billed by Anthropic, and is not included in the price of Groundkeep.

3. Optional: Oura ring integration

If you connect an Oura ring, Groundkeep uses OAuth to request your authorization, then syncs sleep, readiness, and HRV data directly between your machine and Oura's API.

• This data flows machine-to-Oura and back; it does not pass through or get stored on any server we operate.
• The connection is entirely opt-in — Groundkeep has no health-tracking features that require it.
• You can revoke access at any time from your Oura account settings, which stops the sync immediately.
• Oura's handling of your data is governed by Oura's own privacy policy: https://ouraring.com/legal/privacy-policy

4. On by default: the weather lookup

The Today page and the morning-brief notification show a one-line weather summary. To build it, your machine requests a forecast from Open-Meteo, a keyless public weather API.

• The request carries the latitude and longitude set in Settings → Weather and nothing else — no name, no account, no license key, none of your Groundkeep data. There is no API key, so nothing in the request identifies you. As with any web request, Open-Meteo can see the IP address it came from.
• Those coordinates are whatever you typed into Settings (they start at a default city). The app never reads your device's location.
• This is the one connection that is enabled out of the box. Turn off Settings → Weather → "Show weather on Today + morning brief" and the app stops contacting Open-Meteo entirely.
• Open-Meteo's handling of the request is governed by its own terms and privacy statement: https://open-meteo.com

5. Optional: push notifications

If you enable push notifications (Settings → Notifications), your browser registers a subscription with its vendor's push service — Google, Mozilla, Microsoft, or Apple, depending on which browser you enabled it in — and Groundkeep sends the morning brief and habit nudges through it.

• Delivery follows the Web Push standard: your machine posts the notification to that vendor's endpoint and the vendor relays it to your device. The payload is encrypted to keys held by your browser, so the relay service can see that a message passed through but not what it said.
• Notification text can quote small pieces of your own data — a routine name, today's intention, the weather line — so this is the one optional feature where content, not just metadata, leaves your machine.
• It is off until you turn it on and accept the browser's permission prompt. Switching the same toggle off unsubscribes the device and delivery stops.
• No server DriveVision operates is involved at any point.

6. Optional: hosted Cloud / Backup tiers

If you subscribe to a Groundkeep Cloud or Backup tier (a paid add-on, separate from the one-time local license), your data is encrypted and stored on infrastructure that DriveVision operates or contracts with (e.g. Amazon Web Services, Inc. (AWS), in the US East (Ohio) region) so it can sync across your devices or be restored after loss.

• This only happens if you actively opt in and configure a Cloud/Backup tier. The default, one-time-purchase product never does this.
• Encryption. The storage volume holding your hosted instance's database is encrypted at rest with an AWS-managed key, as are the backup copies in Amazon S3. Traffic between your browser and your instance is HTTPS end-to-end.
• Sub-processors. Amazon Web Services, Inc. (AWS) — hosting, storage and outbound email, in the US East (Ohio) region. Stripe, Inc. — payment processing; Stripe receives your billing details directly and we never see or store your card number.
• Retention. Daily backups of your instance are kept for the period your plan includes (30 days on Cloud, 365 days on Cloud Pro), and at least the three most recent are kept regardless of age. If you cancel or delete your instance, your data is kept for 30 days so you can change your mind, and is then permanently destroyed along with every backup copy of it.
• Deletion. You can export your full SQLite database and/or delete your cloud data at any time. The procedure, and what cannot be undone, is at https://groundkeep.app/data-deletion.

7. The hosted demo (demo.groundkeep.app)

The public demo at demo.groundkeep.app runs against fictional, seeded sample data, not real user data.

• Anything you type or edit in the demo is discarded — writes are not persisted beyond the demo session and are never associated with a real identity.
• We may log basic, aggregate web-server traffic (e.g. request counts, IP address, standard HTTP logs) for abuse prevention and uptime monitoring on the demo site itself, the same way any web server does. This is operational logging, not a profile of you, and it's unrelated to the data you'd store in your own local instance.

8. When you send a bug report or suggestion

Settings has "Report a bug" and "Suggest something". Both open a dialog that builds a draft, shows it to you, and does nothing else until you choose one of three ways out: Send, which posts it to DriveVision; Open mail app, which hands the draft to your own mail client; or Copy, which puts it on your clipboard. Closing the dialog sends nothing.

• Nothing is collected in the background. There is no crash reporter and no error beacon. The only way anything here leaves your machine is you pressing one of those buttons, on a message you have already read.
• What is in it is what you saw. A bug report includes the app version, your browser's user-agent string, your OS label, whether the app can reach its own local bridge, and the NUMBER of rows in each collection — never their content. A suggestion carries less: no row counts at all. The whole draft is an editable text box; delete any of it before sending and the deleted version is what goes.
• The screenshot is opt-in and yours to check. You can attach one image, by picking a file or pasting it. It is shown at full width in the dialog before you send, and one click removes it. Nothing captures your screen — the app only ever sees a file you handed it. The image is re-encoded on your machine, which strips any EXIF metadata (timestamps, camera details, and on phones often GPS coordinates) the original carried. Whatever is visible in the picture is what you are sending, so look at it first.
• Send goes to DriveVision, and nowhere else. The report is posted to Groundkeep's own server, which emails it to the support address and stores no account, cookie, or identifier for you — the request deliberately carries none. As with any web request, the receiving server sees the IP address it came from.
• The other two exits involve us not at all. "Open mail app" and "Copy" are entirely local; a screenshot cannot travel by either, since neither a mail draft link nor the clipboard carries an attachment.

9. What we never do

• We never sell your data. We don't have your data to sell — the local app doesn't transmit it to us in the first place, and the one thing you can send us (section 8) is a message you wrote and read first.
• We never share data with advertisers.
• We never build user profiles from local-app usage, because we don't receive local-app usage.

10. Your choices

• Don't want any of the optional integrations? Don't enable them. The local app functions fully offline with none of them turned on.
• Want it fully offline from day one? Switch off the weather toggle in Settings (section 4) — it is the only thing enabled by default that makes an outbound request.
• Want to see or export everything? Your data is a single SQLite file you already have full access to; Groundkeep also includes a built-in export function.
• Want to delete everything? Delete the SQLite file (and, if you used Cloud/Backup, request deletion per section 6).

11. Children's privacy

Groundkeep is not directed at children and we do not knowingly collect data from children, consistent with section 1 (we don't collect local-app data from anyone).

12. Changes to this policy

If this policy changes — for example, if a new optional integration is added — we'll update the effective date above and post the revised version at https://groundkeep.app/privacy. Material changes affecting the optional Cloud/Backup or integration features will be noted in release notes.

13. Contact

Questions about this policy or your data: hello@groundkeep.app.