Privacy Policy

Reaktif LLC, a Delaware limited liability company, is the controller of the personal data described here. The founder is resident in the United Kingdom. In your interactions with Markwise, the controlling entity is Reaktif LLC.

Markwise is the product: the website at markwise.app, the Chrome extension, and the iOS app. "We", "us", and "our" mean Reaktif LLC.

This policy describes what we actually collect and use. It does not invent features. There is no client-side encryption passphrase, no cookie-preference dashboard, and the Chrome extension does not ship an analytics SDK.

What we collect

Category	What	Why
Account	Email, name if you give it, hashed password for email sign-up, Google account identifiers if you use Google sign-in	Create and secure the account
Library	URLs, titles, extracted page text, highlights, notes, YouTube timestamps, tags, Spaces, Focus Sessions, reminders	Provide the product you signed up for
Billing (web)	Subscription status, plan, and limited Stripe metadata (we do not store full card numbers)	Charge Pro and manage the trial
Billing (iOS)	Apple transaction identifiers and subscription status	Entitlements for App Store purchases
Usage (web)	Pages in the app, feature events, a PostHog identifier	Understand how the product is used
Attribution (web)	First-touch referrer and campaign parameters under a random visitor id (motif)	Attribute sign-ups to a channel
Technical	IP address, browser or device type, and logs needed to run and secure the service	Operate, debug, and prevent abuse
Support	Whatever you send to joseph@markwise.app	Answer you

We do not sell your data. We do not buy advertising lists. We do not run a survey product.

How we use it

• Provide, operate, and maintain the web app, Chrome extension, and iOS app
• File, search, summarise, and answer questions about the library you saved
• Process payments (Stripe on the web, Apple on iOS)
• Send transactional mail (sign-up, password reset, reminders, weekly digest if you enable it) via Resend
• Understand product use on the website via PostHog
• Attribute first visits via motif
• Detect abuse and keep the service up

Lawful bases for UK and EEA residents:

Basis	What it covers
Contract	Account, library, search, Copilot, billing, export, deletion
Legitimate interests	Security, error logs, anti-abuse. Minimum data, no marketing
Consent	Optional product analytics and first-touch attribution on the website. Marketing mail if we ever send it (you can unsubscribe)
Legal obligation	Billing records we must keep for tax

What we send to AI

When you save a page, highlight text, add a note, or ask Copilot a question, we send the relevant library content (URL, title, extracted text, your note or highlight, your question) to our language-model provider so it can summarise, tag, embed, or answer.

That provider currently is Doubleword. It receives the content of the request, not your password, and not your card number. Embeddings for Pro semantic search are generated the same way and stored in our search index.

AI output can be wrong. Treat summaries and Copilot answers as starting points, not ground truth.

Public Spaces

Spaces are private by default. If you turn a Space public, its name, description, and the bookmarks in it become visible at a public URL and may be listed on /explore and in the sitemap. You can unpublish it. Do not put secrets in a public Space.

Chrome extension

The extension reads a page only when you save it, highlight it, or otherwise trigger a capture. It does not collect browsing history in the background.

The shipping extension does not include PostHog or any other analytics SDK. Chrome Web Store policy forbids remote script injection, so we do not ship one.

Auth uses a short-lived code exchanged with markwise.app. The extension talks to our API with your session cookies. It does not request the Chrome cookies permission.

You stop all extension collection by uninstalling it.

iOS app

The iOS app uses the same account and library as the web app. Purchases go through Apple. Apple's privacy policy covers App Store payments. We see subscription status so we can grant Pro.

Processors

Each of these acts on our instructions for the purpose listed. We share the minimum needed.

Processor	Role	Sees
Google	Sign-in (optional)	Email and Google account identifiers if you choose Google
Stripe	Web payments and the Pro trial	Name, email, billing details, payment method
Apple	iOS payments	App Store transaction data
Doubleword	Language-model inference and embeddings	Library content and Copilot questions in the request
Resend	Transactional and digest email	Email address and message content
PostHog	Product analytics on the website	Pseudonymous id, in-app paths, feature events. Not in the extension
motif (Reaktif LLC)	First-touch attribution on the website	Referrer and campaign parameters under a random visitor id
Cloudflare	Pages hosting, DNS, Turnstile bot check	Request metadata, Turnstile tokens on sign-up
Hosting / database	API, Postgres, Typesense, and job queue on a VPS we operate	Account and library data needed to run the product

We do not host Markwise on Amazon Web Services. An older version of this page said we did. That was wrong.

Cookies and similar tech

There is no in-app cookie dashboard today. An older version of this page claimed there was. That was wrong.

Kind	What	Required?
Session	HttpOnly auth cookies so you stay signed in	Yes. The app does not work without them
Analytics	PostHog on the website	No. Email joseph@markwise.app and we will stop associating events with your account. You can also block the script in the browser
Attribution	motif first-touch script on the website	No. Same as analytics. It does not run if you have declined analytics cookies

We do not run advertising pixels. We do not sell cookie data.

Google Search Console is a tool we use on our own site. It is not a processor of your library.

Retention

Data	Kept
Account and library	While the account is open. Deleted when you delete the account or all data from Settings
Billing records	As long as tax and accounting law require (typically six years in the UK, seven in the US)
Email logs	Short operational window, then dropped
Aggregated analytics	May be kept longer; it is not tied back to you

Export and delete live in Settings. Export downloads your bookmarks. Delete account or delete all data is permanent.

Your rights (UK / EEA)

You can ask us to access, correct, delete, restrict, or port your personal data, or object to processing based on legitimate interests, or withdraw consent.

Email joseph@markwise.app. We reply within 30 days, free unless the request is manifestly unfounded or excessive.

You can also complain to the UK Information Commissioner's Office (ico.org.uk) or your local supervisory authority.

Transfers

Reaktif LLC is a US company. Several processors (Google, Stripe, Doubleword, PostHog, Apple, Resend) are also outside the UK / EEA. When we transfer personal data of UK or EEA residents, we rely on the mechanisms available at the time: the UK IDTA, the UK Addendum to the EU SCCs, and the EU-US / UK-US Data Privacy Framework where the recipient is certified.

Ask us for a copy of the relevant mechanism.

Children

Markwise is not directed at children under 13. We do not knowingly collect personal data from anyone under 13. If you think a child has signed up, email us and we will delete the account.

Security

Traffic is encrypted in transit (TLS). Passwords are stored hashed. Access to production is limited. No system is perfectly secure. If a breach affects your personal data, we will notify you and the relevant authority in the time the law requires.

We do not offer a user-controlled client-side encryption passphrase. An older marketing line said we did. That was wrong.

Changes

We may update this policy. The "Last updated" date on this page will change. Material changes will be announced on the service or by email before they take effect.

Contact

• Email: joseph@markwise.app
• Controller: Reaktif LLC, Delaware, USA

---