Privacy Policy
What Qind collects, which providers process it, what AI sees and when, and how to get it deleted.
Last updated
This policy explains what the Qind apps, web app, browser extension and this website collect, why, who processes it on our behalf, and how to get it deleted. It is written to be read, not skimmed past: the summary is first, the detail follows.
The short version
- Your content is yours. We store what you save so Qind can be your library. We do not sell your personal information and we do not use it for advertising.
- AI is opt-in. Qind asks before sending your content (text, images, questions) to OpenAI or Anthropic, or your recordings and voice notes to ElevenLabs to transcribe them. Until you allow it, nothing goes to them, and saving and search still work. You can turn it off again at any time.
- We name every provider and what it receives, below. Our analytics and crash tools know you by your account id, so we do not call that data anonymous.
- On this website and in the web app, optional tools wait for your choice. We count visits to this website without cookies. Google Analytics, Microsoft Clarity, Google’s advertising measurement and the web app’s product analytics run only after you accept them. One choice covers both, and “Privacy choices” at the bottom of every page, or in the web app’s Settings, changes it.
- Location: the apps never ask for your location. Providers that receive your IP address can derive an approximate location (country or city) from it. We say more under “Location and your IP address”.
- You can delete your account from inside the app. Some copies age out on a schedule rather than instantly; see “Deleting your account”.
What we collect
Every category below is linked to your account. We say that plainly rather than describing our analytics as anonymous, because it would not be true: our analytics events are identified by your Qind account id.
| Data | Why we collect it | What it actually is |
|---|---|---|
| Email address and name | Signing you in, showing your name, and contacting you about your account. | Held by our authentication provider. If you sign in with Apple or Google we receive the name and email they share. |
| Account ID | Running the service, and product analytics, crash reports and subscription state. | Your Qind account id. It is the identifier our analytics, crash reporting and subscription providers know you by, which is why we do not call that data anonymous. |
| Push token and device details | Delivering notifications, and diagnosing problems. | A push token per device, plus device model, operating system and app version when you report a problem or when an error is reported. |
| Photos, videos, files and audio | Saving what you capture or import, and transcribing voice notes. | Only what you capture, record or pick yourself. Stored in your account; processed by AI providers only if you allow AI processing. |
| Notes, saved pages and everything you create | Being your knowledge base. | Notes, saved pages and links, collections, tags, tasks, transcripts and chat messages. |
| Search queries | Returning results from your own library. | Searches run on our servers, so the query text reaches us. |
| Messages you send us | Answering support requests and bug reports. | The text you write, your email address and basic device and app details. Reports sent from the app reach us by email. |
| Purchase history | Unlocking the plan you paid for. | Subscription and entitlement state. Never card numbers. |
| Product interaction | Understanding which features are used. | Analytics events that name a screen or an action, never your content. In the web app they are off until you allow Analytics, one choice shared with qind.ai. In the iPhone and Android apps you can turn them off with Share usage data (see Advertising and tracking). |
| Crash and performance data | Finding and fixing crashes and slowness. | Crash reports, error reports, network failures and timing measurements from the app, with your account id. |
| IP address | Delivering the service, preventing abuse, and as a side effect of every provider you reach. | See “Location and your IP address”. Our application logs keep only the network part of it. |
Location and your IP address
The apps never ask for your location. There is no location permission and no GPS or Wi-Fi positioning anywhere in the iOS, Android or web apps.
Your IP address is different. Every time your device connects, the address it connects from reaches the services involved: our hosting and delivery network, our servers, and the analytics, crash-reporting, push and sign-in providers listed below. Some of them can work out an approximate place, such as a country or city, from an IP address. We do not ask for that and we do not use it to track where you are or for advertising.
- Our servers use your full address in memory to limit abuse. Our application logs keep only the network part of it (for IPv4, the first three groups of numbers). The full address is stored in two places: the records of command-line (CLI) sign-ins, where the sign-in request and each CLI session keep the address it was made from and last connected from (deleted with your account), and the records of actions by our own administrators.
- Hosting and delivery: the web-server access logs of our hosting and of Cloudflare see the full address of every request, under those providers’ own retention.
- Product analytics (PostHog) may derive an approximate location from the address of the device sending an event.
- Crash reporting (New Relic) and the other providers below see the address their requests come from and handle it under their own policies.
We have not found an IP-derived location to be needed to run Qind, and we may switch it off where a provider lets us. If we do, this section will change.
What we deliberately do not collect
These are decisions, not oversights. Changing any of them would require updating this policy and our App Store privacy disclosures first.
- Your device location. No GPS, no location permission. (IP addresses: see above.)
- Your contacts. We never read your address book.
- Health or fitness data. We do not request or receive any.
- Your calendar contents. On iPhone, Qind asks for write-only calendar access: it can add a task block you asked for and cannot read what else is in your calendar. Android has no write-only calendar permission, so Android asks for both read and write; Qind uses it to list your calendars and add the event you chose, and does not read your events.
- Card or bank details. Payments are handled entirely by Apple (App Store), Google (Google Play), or Stripe. Card numbers never reach Qind.
- Your browsing history. We only receive a page you deliberately saved. We have no view into what else you browse.
Advertising and tracking
Qind does not track you in the sense Apple defines: we do not link what we collect with data from other companies’ apps or websites, and we do not share it with data brokers.
- We do not sell your personal information.
- There is no advertising identifier (no IDFA), no ad network SDK, and no attribution SDK in the apps.
- This is why the iOS app never shows you an App Tracking Transparency prompt — there is nothing to ask permission for.
- Analytics is first-party. PostHog runs on EU infrastructure and receives interaction events, never the contents of your notes.
- In the web app, nothing is measured in your browser until you allow Analytics. It uses the same Privacy choices as qind.ai, and one choice covers both in that browser: a choice you make on qind.ai applies in the web app, and the other way round. Once you allow Analytics, PostHog receives product analytics events, tied to your account id after you sign in, and keeps an identifier in your browser’s storage. You can change or withdraw your choice at any time from Privacy choices in the web app (Settings → Preferences → Privacy & data) or from Privacy choices at the bottom of every page on qind.ai. A withdrawal stops product analytics and removes PostHog’s storage.
- In the iPhone and Android apps, product analytics has its own switch, under Settings → Privacy & Data → Share usage data. Turning it off stops product analytics and session replay there.
- Error reports differ by platform. In the web app, error reports and diagnostic logs go to PostHog, and only while you allow Analytics. In the iPhone and Android apps, crash, error and performance reports go to New Relic, and Share usage data does not turn them off. None of these choices changes the AI processing choice.
How AI processes your content
Qind’s AI features — Ask Qind chat, summaries, tags, organizing into collections, document review — work by sending the relevant parts of your content (text, images, transcripts and your questions) to an AI provider: OpenAI or Anthropic. That includes, where the feature is available to you, the transcript and notes of a meeting recording that Qind summarizes into a brief.
Transcripts of recordings, voice notes, uploaded audio and the sound of saved videos are made by sending that audio to ElevenLabs. OpenAI and Anthropic receive the transcript, never the audio.
We ask before any of it is sent. When you set up the app, and whenever you ask for an AI feature before deciding, Qind shows what would be sent, why, and to which providers, and names each one. Until you choose “Allow AI processing”, nothing is sent to them: saving, browsing, and search keep working, and the AI features stay off. Your answer is kept on your account, so it applies on every device.
If you decline, everything you save stays in Qind, search keeps working, and the AI features stay paused until you allow them. Declining is not an error and nothing is sent in the background.
You can change your mind. In the app under Settings → Privacy & Data → AI processing, or on the web under Settings → Account → Privacy. Turning it off stops new AI processing at once, including work that is already waiting. Summaries, tags, and transcripts made before you turned it off stay with your content until you delete them, and what a provider already received is covered by that provider’s own retention rules, linked below.
Search embeddings are generated on our own infrastructure, not by a third party, and Qind’s document, OCR and image-caption processing also runs on our own servers.
Model training is a separate question
Allowing or declining AI processing decides whether your content is sent to OpenAI, Anthropic and ElevenLabs at all. It is not a model-training setting, and turning it off is the only thing in Qind that stops content going to them.
We do not use your content to train models of our own. What OpenAI, Anthropic and ElevenLabs may do with data they receive, including whether it can be used to improve their models, is set by their own terms and by our accounts with them, which their privacy policies (linked below) describe. We do not promise more than they do.
Because content is processed on our servers, Qind is not end-to-end encrypted. We would rather say that plainly than imply a protection the architecture does not provide.
Notifications
If you turn on notifications, we store a push token for each device so a reminder can reach that device. On mobile a notification passes through Expo’s push service and then Apple’s or Google’s push service (browser notifications go through Google’s Firebase Cloud Messaging), so each sees the token and the notification text. What the text shows follows your preview setting (Settings → Notifications): you can choose a generic message, the title only, or the title and due time. Tokens are removed when you sign out or delete your account. Notification permission is optional — declining it does not restrict anything else in the app.
Notices about new Qind apps
If you ask to hear when Qind for Android or desktop is ready (the “Notify me” form on the download page), we store, on the basis of your consent, your email address, the platforms you chose (and Mac or Windows, if you said), whether you also asked for product news, when you asked, the version of the wording you agreed to, and the page and campaign tags of the visit that brought you there. We first email you a link to confirm the address (sent through Resend); nothing else is sent until you confirm, and we email a confirmation at most once a day. We use the address only to tell you about those platforms. Product news is a separate choice: we send it only if you ticked that box as well. The request is kept on Qind’s own servers. Your email address is never sent to our analytics providers; if you allowed Analytics, PostHog receives which platforms and options you chose and whether the request went through, without the address.
Every email we send about it carries an unsubscribe link, which deletes the request and our record of the emails we sent about it; you can also ask us to delete it at any time (see Contact). A request you never confirm is deleted 30 days after you last made it, and our record of the confirmation email 30 days after we sent it; a confirmed request is deleted 24 months after you last made or confirmed it.
Optional permissions
Each of these is requested only at the moment you use the feature, and each can be declined without losing access to the rest of the app.
- Camera — to capture an image or document you want to save.
- Photo library — to import images and files you pick, and to save exports back.
- Microphone — to record voice notes. The app does not record in the background.
- Calendar — to add a task block you scheduled; write-only on iPhone (see above for Android).
- Notifications — to deliver reminders.
Subscriptions and payments
Subscriptions bought inside the mobile apps are processed by Apple (App Store purchases in the iPhone app) or Google LLC (Google Play purchases in the Android app). Subscriptions bought on the web are processed by Stripe. In both cases the payment processor handles your payment details — Qind receives only the resulting subscription state (which plan, active or not, when it renews), which we use to unlock the features you paid for. RevenueCat tracks that state for the mobile apps.
Who processes data for us
We use a small number of service providers. Each receives only what its function requires, and each acts on our instructions. The links go to each provider’s own privacy policy.
AI providers
| Provider | Role | What it receives |
|---|---|---|
| OpenAI | AI processing (only after you allow it) | Receives the text of what you save, your questions to Ask Qind, documents you ask Qind to review, transcripts, and in some chats up to two images from your library, to write summaries, tags, organization suggestions and answers. |
| Anthropic | AI processing (only after you allow it) | Receives the text of what you save, your questions to Ask Qind, documents you ask Qind to review, transcripts, and in some chats up to two images from your library, to write summaries, tags, organization suggestions and answers. |
| ElevenLabs | Audio transcription (only after you allow AI processing) | Receives the audio of your recordings and voice notes, audio files you upload, and the sound of videos you save, to turn them into transcripts. It does not receive your text, images or questions. |
Everything else
| Provider | Role | What it receives |
|---|---|---|
| Supabase | Authentication | Stores your login identity (email, sign-in method) and issues your session. |
| Cloudflare | Delivery, hosting and file storage | Serves this website and stores the files you upload (Cloudflare R2). Sees the IP address of anyone who requests those services. |
| Resend | Delivers account emails, reminders, digests, sharing emails and the emails about new Qind apps you asked for. Receives your address and the email’s text, which can include item titles, summaries and task text. | |
| Expo, Apple and Google | Push notifications | In the mobile apps, Expo’s push service passes notifications to Apple’s push service (iPhone) or Google’s Firebase Cloud Messaging (Android); browser notifications go through Firebase Cloud Messaging. They receive your device’s push token and the notification text, which follows your notification preview setting. |
| PostHog | Product analytics | Hosted on PostHog’s EU infrastructure. In the apps it receives events identified by your account id, device and app details, and, from the device’s connection, an IP address it may use to derive an approximate location. On this website it receives cookieless page counts and basic clicks, plus usage events and diagnostics if you allow Analytics. Website events have no account id (see “On this website”). |
| New Relic | Crash reporting and performance monitoring | Receives crash and error reports, network failures and timings from the app, and logs and performance data from our servers, with your account id. Our server logs hold only a coarse network address, not your full IP address. It can see the IP address of a connecting device. |
| RevenueCat | Subscription state | Tracks which plan you are entitled to on mobile, using your account id and store receipts. |
| Apple and Google | Sign-in and in-app payment | Apple processes App Store purchases in the iPhone app, and Google (Google LLC) processes Google Play purchases in the Android app. They also provide, if you use them, Sign in with Apple and Google sign-in. We never see your card. |
| Stripe | Web payment | Processes subscriptions bought on the web. Receives your email and billing details; card numbers never reach Qind. |
| Google Drive | Only if you connect it | Qind asks it, with read-only access, for the files you choose to import, and stores the sign-in token encrypted. |
| Notion | Only if you connect it | Qind asks it for the pages you choose to import, and stores the sign-in token encrypted. |
Our own servers run Qind’s databases, queues and the embedding, OCR, image-caption and document processing. We do not send your content to any other third party for advertising, and we do not sell it.
On this website, and the same choice in the web app
The first time you visit qind.ai, a card asks for your privacy choices. It offers “Accept all”,
“Reject all” and “Customize” with equal weight, and nothing optional runs until you choose. The
web app shows the same card and reads the same choice, so one answer covers qind.ai and the web
app in that browser. You
can change or withdraw your choice at any time from
Privacy choices, at the bottom of every page;
a withdrawal takes effect at once, without reloading the page. Your choice is kept in your
browser’s local storage, which is needed to remember it: the entry qind.consent.v1,
plus two copies of the Analytics answer, qind.google-measurement-consent.v1 and
qind.analytics.consent, that older parts of the web app still read.
Your language. If you pick a language, in the list at the bottom of a page, in
the menu or by accepting an offer to read a page in your browser’s language, this browser keeps
your pick in local storage as qind.language.v1, so a later offer never overrides
it. If you turn the offer down, it keeps that answer as qind.language-suggestion.v1.
Your browser’s list of preferred languages is read only on your device, to make that offer.
While you allow Analytics, we count when you pick a language or when an offer is shown or
turned down, with the languages involved, never the list itself. Nothing is written until you
pick or decline.
Your account has an Analytics setting too. It decides whether our servers send events about your account to product analytics, such as onboarding and subscription steps. It turns on only when you allow Analytics in the web app while signed in, or when you create an account after allowing Analytics. Allowing Analytics on qind.ai does not turn it on for an existing account. A choice carried over from older settings does not turn it on, for an existing account or a new one. A refusal always reaches your account: when this browser’s choice is a refusal, the web app turns the account setting off at once if it is open and you are signed in, and otherwise the next time you open it here while signed in. That holds whether you refused on qind.ai, in another tab or in the web app. Your browser never copies the account setting: a permission given elsewhere never turns Analytics on in this browser, and a refusal elsewhere does not change this browser’s own choice. This means an older refusal in one browser turns the account setting off again when you next open the web app there while signed in. Our servers also send these events only while Share usage data is on. It is on unless you turn it off in the iPhone or Android app, and turning it off stops them.
There are two categories:
- Analytics loads Google Analytics and Microsoft Clarity on these pages, and turns on the web app’s product analytics with PostHog (see “Advertising and tracking”). Google Analytics measures visits with its own cookies. Clarity records heatmaps and session replay of these pages, does not record passwords, payment fields, or inputs marked sensitive, and can see your IP address; see the Microsoft Privacy Statement. None of them loads before you accept, and if you withdraw, Clarity is told consent is denied (it erases its cookies) and stops recording, Google Analytics is switched off, and the web app stops its product analytics.
- Advertising measurement lets Google Analytics use Google’s advertising signals (advertising storage and ad user data) to tell us which Google ads led to a sign-up. It works only together with Analytics. Ad personalization is always off: we never let Google use this to target ads at you. See the Google Privacy Policy.
Whatever you choose, we count visits to these pages with PostHog in cookieless mode: it sets no cookie and stores nothing in your browser, and the site never tells it who you are. PostHog works out a one-way identifier on its own servers from your connection’s IP address and browser details, which it describes as changing every day. We count page views and clicks on signup, sign-in and store links. A page address is sent without its query, apart from the campaign tags described below, and a referring site only by its name. These counts are not linked to a Qind account, and they are separate from the web app’s product analytics, which waits for your choice. We rely on our legitimate interest in knowing how the site is used; you can object by emailing us, and a browser setting or extension that blocks PostHog also stops it.
If you allow Analytics, PostHog also receives website usage events, such as page exits, video progress and FAQ opens, and technical diagnostics, such as warning logs and script error reports. These also use cookieless mode. If you turn Analytics off, only page views and basic link clicks continue.
How you found Qind. When you follow a link from this website to sign up, the
link carries a few facts about the visit: the campaign tags in the address you arrived with
(utm_source, utm_medium, utm_campaign,
utm_content, utm_term), the first page you opened here, and the name of
the website that sent you, without the rest of its address. On qind.ai, nothing is stored on
your device for this; the facts travel only in the links. In the web app they are always held
in the page’s memory. While you allow Analytics, the web app also keeps a copy in this browser
tab’s session storage for up to two hours, and turning Analytics off removes that copy at once.
Nothing is written to your device before you choose. An email sign-up happens on the same page,
so it keeps these facts. A sign-up through a sign-in provider such as Google or Apple leaves the
page for that provider, so without Analytics the facts are lost on the way and the account is created without
them. When they do arrive with a new account, Qind keeps them once on the account, so we can see
which channels bring people who go on to use Qind. We do this
for every new account, on the basis of our legitimate interest, and it is shown to our product
analytics only if you accepted Analytics. Advertising click identifiers (such as Google’s or
Meta’s) are never carried.
These pages host their own fonts, so no font request goes to Google. The signed-in web app is not a marketing page, but it shares the same choice: if you accepted Analytics, it sends Google a single sign-up event when you create an account, with advertising signals only if you also accepted Advertising measurement. Nothing is sent if you rejected or never chose. The web app also loads a font from Google Fonts, which tells Google your IP address. None of these tools runs inside the mobile apps.
Session replay in the app
Product analytics can include session replay, which records the shape of your interactions — what you tapped, how you navigated. Where it is switched on, it is configured to mask all text, all text inputs, all images and all sensitive views, and it captures neither logs nor network payloads. It is designed to show us how the interface behaves, not what you wrote. Turning off “Share usage data” stops it. In the web app, session replay can run only while you allow Analytics, and withdrawing your choice stops it.
How long we keep things
Your content stays until you remove it or delete your account. Deleting an item removes it from your library. Deleting your account starts erasure of the account and its associated data.
Some records are kept for a limited time on their own schedule: a technical record of recent Ask Qind conversations is kept by our chat service for up to 30 days, temporary chats for 24 hours, data export archives for 24 hours, and a request to hear about a new Qind app 30 days after you last made it if you never confirmed it, or 24 months after you last made or confirmed it. Backups and operational logs persist for a limited period after deletion before they age out, and we may retain records we are legally required to keep, such as transaction records for tax purposes. Providers keep what they received for as long as their own policies say.
Deleting your account
You can delete your account from inside the app, without contacting us: Settings → Delete account, then type DELETE to confirm.
Deletion is processed asynchronously. You are signed out immediately and your account stops working straight away, but the erasure itself completes in the background — we will not tell you the data is already gone at the moment you tap the button. You can also export your data before you go.
Erasure removes your library, files, search data, devices and push tokens, and your sign-in identity from our systems, and cancels a web subscription. It does not on its own remove what providers already hold under their own policies: payment and subscription records, analytics events, emails already sent, and what AI providers received. The technical record of recent Ask Qind conversations described above ages out on its own schedule rather than at the moment of deletion. Email us if you want us to follow up with a specific provider.
If you would rather have us do it, or you want a copy of your data, email support@qind.ai from the address on the account.
How we protect it
- Everything travels over encrypted HTTPS connections between the apps and our servers.
- Your session credentials are stored in the operating system’s secure storage — Keychain on iOS, Keystore on Android — not in plain application storage.
- Access is scoped to your account, so one account cannot read another’s data.
- Files you upload (Cloudflare R2) and sign-in data (Supabase) are encrypted at rest by those providers.
We will not tell you your data is perfectly safe, because no online service can honestly promise that. If we ever discover a breach affecting your data, we will notify you.
Your rights
You can, at any time:
- Access the content stored in your account.
- Export it.
- Correct your profile details.
- Delete individual items, or your entire account.
- Allow or withdraw AI processing, and turn off product analytics and notifications.
- Object to or ask us to restrict a particular use of your data.
Depending on where you live, data protection law may give you additional rights, including the right to complain to your local supervisory authority. Email us and we will help.
Children
Qind is not directed at children. If you believe a child has created an account, contact us and we will remove it.
Changes to this policy
When this policy changes materially, we will update the date at the top of this page and notify account holders by email before the change takes effect.
Contact
Questions about this policy, or about your data, go to support@qind.ai. See also our security practices and Terms of Service.