Privacy Policy

Effective date: November 16, 2026

Kour is an app for reading, writing and keeping everything you work with, for Mac, Windows, Linux, iPhone, iPad and Android, operated by ParkourLabs, Inc., a Delaware corporation (“ParkourLabs”, “we”, “us”). This policy describes what we can and cannot see when you use the Kour apps and getkour.app (together, the “Service”), what we collect, how we use it, and the choices you have.

Questions or requests: privacy@parkourlabs.io.

Your library is end-to-end encrypted

Everything in your library — notes, documents, spreadsheets, handwriting, canvases, files you import, their titles, tags and folders, your annotations, your conversations with Kour’s assistant, your browsing tabs and reading settings — is encrypted on your devices before it is sent to our servers, with keys that only your devices hold. Our servers store and relay that encrypted data so your devices stay in sync; we cannot read it, and neither can anyone who obtains a copy of our servers.

Searching your library, indexing it and extracting its text happen on your devices, and so does recognising text in images and handwriting where your device can do it. Feeds you follow are fetched by your devices directly from the sites that publish them; which feeds you follow is part of your encrypted library. Your mail accounts are read and sent from your devices, which connect to your mail provider directly. Looking up a reference sends its DOI, arXiv number, ISBN or title from your device to the service that holds it (doi.org, arXiv, Open Library or Crossref). Kour’s assistant runs its steps on your devices, but the AI model it uses runs in the cloud: what the model needs is sent through our servers to a model provider, unless you connect your own provider. Some other features send content too, and a page you choose to publish is stored unencrypted. Those are the exceptions to this section; “Pages you publish” and “When content leaves your device” list them.

Your recovery key. When you set up your first device, Kour shows you a recovery key and asks you to save it. Your other signed-in devices can also let a new device in. If you lose your recovery key and every device that holds your keys, your library cannot be recovered — not by you and not by us. We do not hold a copy of your keys, and we cannot reset them for you.

What our servers can see

To run the Service, our servers keep some information unencrypted:

Pages you publish

When you publish a note or document as a public page, it leaves end-to-end encryption: its title, its text and a picture of it are stored on our servers unencrypted, so that anyone with the page’s address can read it, and search engines may list it. It stays there until you unpublish it or delete your account; after that, a copy can remain in our file storage’s recovery copies for up to 30 days, and its title in database backups for up to 14 days.

When content leaves your device

Some features need a server or a provider. When you use one of them, only what that feature needs is sent, it is processed to give you the result, and we do not keep it. The providers are named on our Subprocessor List.

On-device recognition on phones and tablets

Kour uses Google’s ML Kit to recognise handwriting on iPhone, iPad and Android, and on Android also to recognise text in images, identify languages, translate on the device and scan documents. Your images and text are processed on the device. ML Kit itself sends Google diagnostics and usage data about its own work — the device and app, performance, the size of its input and output, errors, and the languages recognised or configured — under a per-installation identifier. Google states that it does not pass this data to third parties. It is the only third-party SDK in the apps that sends data of its own.

What we collect about how the Service works

There are three kinds, kept apart:

Diagnostics. When something breaks, the apps send an error report: what kind of error, a technical stack trace, which part of the app, the app version and the kind of device and operating system, the last 30 steps before it (the screens you moved between, the requests made and the names of the controls you used), and figures such as memory in use and, for a failed assistant step, the model and tool. An error’s own message is kept only where the programming runtime wrote it; a message the app wrote, which could quote a title, a file name or other text of yours, is reduced to the kind of error. Before a report is stored we also remove email addresses, keys and long numbers, text in double quotation marks, the name of a server a failed connection mentions (unless it is Kour’s), every file path on your device, and addresses outside Kour beyond their site name. When an app crashes, the crash is analysed on your device and only its outline is sent: which functions were running in each thread, and which code modules were loaded; the crash file itself never leaves your device. If you share crash reports with app developers in your device’s settings, Apple or Google may also send us the crash logs they collect. Error reports and performance measurements (how long things took, in the apps and on our servers) are not tied to your account: they are sent without it and carry only identifiers made at random for each request, and one for your device that changes every day, so no two days can be joined. Error reports are kept for 90 days; performance traces for 14 days and performance metrics for 30 days. To group repeated errors, an error’s scrubbed message and its counts are kept while the same error is still being reported. You can turn diagnostics off in Settings → Privacy → Share diagnostics.

Product analytics (de-identified). If analytics are on, the apps send which screen you were on and which action you took (for example “opened a note”, “used the search”), whether the window was visible and in focus, timestamps, a random identifier for each time the app is opened with the order of its events, the platform, and, when you pick a row in the entry, its place in the list and the kinds of rows above it. They never contain titles, text, file names, addresses or search terms, and they are not tied to your account: each device sends them under a random identifier that it changes every month, and our servers record only the country the request came from, not the address. In the United States and Singapore analytics are on by default; elsewhere the app asks you once. You can turn them off at any time in Settings → Privacy → Share usage data, and when you do, what those identifiers sent is deleted. Analytics are kept for 13 months. We keep diagnostics and product analytics in this de-identified form, we do not try to tell who sent them, and we require the same of any provider that stores them for us.

Billing and metering: as described under “What our servers can see”.

We use no third-party analytics or advertising SDKs, no advertising identifiers and no tracking pixels. Google’s ML Kit, described above, is used for recognition on the device, not for analytics or advertising.

Our website

getkour.app shows our product pages, blog and legal pages. When you visit them, we record which page you viewed or which button you clicked, the referring website (its domain only) and any campaign parameters (utm_*), sharing code (ref) and offer in the address. A visit carries the random visitor identifier from a first-party cookie the page sets (30 days), and a code computed from your IP address, your browser and the date with a key only our server holds, so codes from different days cannot be joined. We look up on our own servers the approximate location your IP address indicates and keep the country with the visit; cities are only counted per month, with the city’s region and approximate coordinates and without identifiers, and cities with fewer than five visitors are merged into their country. Your IP address is not stored. Visits by search-engine crawlers are kept apart and not counted.

If you join a waitlist on the site, we keep your email address, what you are waiting for, the site’s language and when you joined, to tell you when it is available.

How we use information

We do not sell or share your personal information (as California law defines those words), and we do not give it to advertisers or data brokers. Our website and apps do not respond differently to a browser’s Do Not Track signal; they do not track you across other companies’ sites or apps in the first place. For the same reason, a Global Privacy Control signal changes nothing: there is no sale or sharing to opt out of. We do not use your content to train AI models, and we ask the model providers we route through not to collect it.

Google Calendar

If you connect a Google account, Kour asks Google for your email address, to read your calendars and events, and to create, change and delete events, answer invitations and invite guests. You see this on Google’s consent screen first, and nothing is read until you agree.

Kour’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who can see your content

Nobody at ParkourLabs can see your library: it is encrypted with keys we do not have. We see content only when you send it to us yourself — in feedback, in an email to support — when you publish a page (see “Pages you publish”), and, for the moment a feature needs it, what is listed under “When content leaves your device”.

Providers

The providers that process data for the Service, and what each receives, are listed on our Subprocessor List. AI providers process what you send them under their own terms; the list states what each has published about keeping or using inputs. “We do not keep it” above is about our servers: a provider may keep what it receives for a while under its terms — OpenAI, for one, keeps API requests in its abuse-monitoring logs for up to 30 days, and Anthropic, which runs parts of Kour’s assistant, deletes what it receives within 30 days, or keeps it longer when it is flagged under its usage policy.

Where your data is

Our servers, database and file storage are on Amazon Web Services in the United States (N. Virginia). Diagnostic telemetry is also stored in a ClickHouse database hosted on AWS in the same region. Requests pass through Amazon CloudFront, which has locations worldwide. Email is sent through Amazon Web Services in the same region. Our AI providers are mainly in the United States and Europe; some speech and recognition providers do not publish where they process data. By using the Service you understand that your information is transferred to and processed in these places.

Retention

Your rights

You can see, correct, export and delete your data. Your library is on your devices: notes, documents, spreadsheets, handwriting and canvases can be exported from the app in their own formats. You can delete your account in the app (Settings → Account & plan → Delete account); this deletes your encrypted library, your devices, your sessions, your published pages and links, your feedback, and your plan, credits and receipts. What is kept after that is listed under “Retention”, including usage records without your account, Apple’s and Google’s payment notifications for 13 months, invitations you were sent until they expire, the fingerprints described there, and the copies of your feedback in the team’s mailbox; Stripe, Apple and Google keep their own payment records as the law requires them to. For anything else, email privacy@parkourlabs.io from your account’s address and we will answer within 30 days, wherever you live. Because your library is encrypted with your keys, we cannot export it for you or read it to answer a request.

Children

The Service is not directed to children under 13, and you may not use it if you are under 13. The apps do not ask your age. If we learn we have collected personal information from a child under 13, we will delete it.

Changes

We will post any changes to this policy on this page and update the effective date. For material changes we will tell you in the app or by email before they take effect.

Contact

ParkourLabs, Inc. privacy@parkourlabs.io (privacy requests) · support@parkourlabs.io (general support)