Inksight

Privacy Policy

Last Updated: August 15, 2026

Welcome to Inksight. Your privacy is critically important to us. This Privacy Policy explains how we collect, use, and protect your information when you use our application.

1. Information We Collect

To provide handwriting recognition, document export, and cross-device sync, we collect the following types of information:

  • Account Information: If you sign in, we collect your email address and basic profile information to sync your documents across devices.
  • Document Data: We store the images you capture and the resulting digitized text so you can access, edit, and export them in your library.
  • Account and device identifiers: We process your account ID, app installation or device quota identifier, locale, timezone, notification token, and authentication-provider identifiers to secure accounts, enforce allowances, sync your library, and deliver notifications you enable.
  • Purchases and support: We receive subscription status, product, transaction, price, currency, and store information, plus information you send when requesting support. We do not receive your full card number.
  • Usage and diagnostics: We collect first-party product interactions, app version, platform, session timing, and limited error details to operate and improve Inksight. Optional website advertising measurement is collected only after the choice described below.
  • Export-operation records: When a signed-in web user initiates a document export, we record the time, linked account and document identifiers, selected scope and page count, file format/extension, and that the browser download was initiated. We do not include document content, filenames, email addresses, acquisition data, or a browser measurement-session identifier in this record.

2. Data Processing

To provide the best possible handwriting recognition and document service, Inksight uses leading cloud AI providers selected for quality and reliability:

  • Recognition: Your selected scan is sent through OpenRouter to Google Gemini to extract text and document structure.
  • Document organization: Extracted text may be sent through OpenRouter to Anthropic to create titles and organize documents. Inksight may also use Qwen3 Embedding 8B through OpenRouter to create the numerical representations used by document search and related organization features.
  • Apple devices: The iPhone and iPad app asks for affirmative permission before the first scan is uploaded for this processing. You can review or withdraw that permission in Profile Settings; declining prevents cloud scanning and sends no selected document.
  • Inksight does not use your documents to train AI models. Document content is used to provide the feature you request, not for Inksight advertising. AI processors handle data under their own retention and training terms.

3. Permissions

The app requires the following permissions to function correctly:

  • Camera: To capture photos of your notes directly within the app.
  • Photo Library: To allow you to import previously taken photos for processing.

4. Data Storage & Security

We take data security seriously:

  • Data is encrypted in transit and stored using cloud infrastructure with encryption at rest.
  • Document records use account-based authorization. New and migrated scan objects use private storage with short-lived signed access; older objects are moved from legacy storage when the owning account uses a compatible app.
  • Operational access is limited to authorized services and personnel who need it to operate or support Inksight.

5. Third-Party Services

We use the following processors and platform providers to deliver Inksight:

  • Supabase: authentication, database, private file storage, server functions, and first-party product events.
  • OpenRouter, Google Gemini, Anthropic, and Qwen: handwriting recognition, embeddings, titles, and document organization as described above.
  • RevenueCat, Apple, Google Play, and Stripe: purchases, entitlement status, checkout, and subscription support, depending on platform.
  • Apple and Google Sign-In: authentication when you choose the corresponding sign-in method.
  • Firebase/Google and Apple Push Notification service: app installation tokens and notification delivery. Firebase Analytics advertising measurement is disabled in the initial iOS release.
  • Vercel Web Analytics and Google Ads: optional website measurement only after you allow it as described below.

These providers may process data in countries other than your own. We use contractual, technical, and organizational safeguards intended to provide protection appropriate to the data and applicable law.

6. Cookies, Browser Storage, and Optional Measurement

Inksight uses necessary cookies and browser storage to provide features you request, including authentication, account security, checkout continuity, language and privacy preferences, and restoring the document or plan you selected while moving between product screens. This storage is not used for advertising and cannot be disabled through the optional-measurement choice without breaking those requested features.

When you initiate a signed-in web export, Inksight also creates the minimal export-operation record described above. We use it to deliver and support the requested export, investigate export reliability, and keep a cross-platform record of the format used. It is not used for advertising and is not controlled by the optional measurement choice. “Download initiated” means the browser was handed the file; it does not prove that a file was saved, opened, or read.

If you choose Allow optional measurement, we store a first-touch acquisition record and a measurement-session identifier in session storage, which normally lasts until the browser tab or session ends. Our Supabase-backed analytics can then record limited page and product-action data. The acquisition record may include the landing path, campaign parameters, referring host, and Google click identifiers such as GCLID, GBRAID, or WBRAID. Vercel Web Analytics also records anonymized page views and product events. We do not include document images, document text, names, or email addresses in these measurement fields.

The Google Ads tag is not loaded before you allow optional measurement. If you allow it, Google can receive the ad visit and two defined outcomes: a successful scan followed by copy or export, and a completed web subscription purchase. Purchase events include the order value, currency, and a random checkout-attempt identifier used to prevent duplicate counting. Enhanced conversions, advertising personalization, and Google Analytics storage are disabled, and document content is never sent to Google Ads.

Your choice is saved in local storage so the banner does not keep returning. You can use necessary storage only without losing Inksight functionality, and you can withdraw or grant permission at any time. Changing your choice does not affect processing that occurred lawfully before the change.

Open all privacy choices

7. Google Drive Exports

When you choose to create a Google Doc or Google Sheet, Inksight asks you to connect a Google account and grant the drive.file permission. This permission is limited to Google Drive files that Inksight creates for you or that you explicitly open with Inksight; it does not give Inksight access to browse all of the files in your Drive.

  • Information accessed: We use basic Google account information to establish the connection, and Google returns limited metadata such as the identifier, name, type, and editor link for the file you asked Inksight to create.
  • How it is used: Inksight generates the requested export on your device and uploads it directly from your device to Google Drive solely to create the Google Doc or Google Sheet you requested.
  • Storage and retention: Inksight's backend does not receive or store your Google access token or copies of your Google Drive files. The temporary export file on your device is deleted after the upload attempt. The resulting file remains in your Google Drive until you delete it there.
  • Sharing: We do not sell Google user data, use it for advertising, use it to train AI models, or share it with third parties. Data is sent to Google only at your direction to provide the export.
  • Your control: You can revoke Inksight's Google access at any time from your Google Account's third-party connections page. Revoking access does not delete files already created in your Drive; you can delete those files directly in Google Drive.

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

8. Your Rights & Account Deletion

You have full control over your data. If you wish to delete your account and all associated data, you can do so through the following methods:

  • In-App Deletion: Go to Account > Profile Settings and select "Delete Account". The app rechecks account ownership, removes and verifies your stored files, deletes linked processor customer data, erases direct internal identifiers, and then deletes the authentication account.
  • Manual Request: If you cannot access the app, you can email us at inksight.notes.app@gmail.com with the subject line "Account Deletion Request". We will verify the request and begin deletion without undue delay.

What data is deleted: Upon account deletion, we permanently remove your email address, profile metadata, all uploaded images of notes, all transcribed text, notification tokens, local per-account search data, and processor customer profiles associated with your account. Deleting an account does not cancel an App Store subscription; manage or cancel it at Apple subscriptions.

Data Retention: Active document and profile data is removed through the deletion workflow. Infrastructure providers may retain encrypted backup copies for their limited backup lifecycle. Transaction facts may be retained when required for accounting, fraud prevention, disputes, or legal compliance, but Inksight removes the direct account and RevenueCat customer identifiers from its retained transaction ledger.

9. Free Web Tool (Handwriting to Text)

Our web tools at https://www.inksight-app.com/handwriting-to-text let you prepare up to ten free pages before choosing a plan:

  • Scans and documents are stored. Uploaded images, extracted text, edits, and document metadata are stored in our Supabase-backed library so previews, exports, and cross-device access work.
  • No raw IP addresses. To prevent repeated anonymous free batches, we store only a one-way salted hash derived from the network IP address — never the raw address — alongside daily free-page and locked-preview counters.
  • No email is required for the first upload. We create an anonymous technical session. If you sign in from that browser session, its documents and free-page usage move to your account.
  • Allowance decisions are server-side. Account, page-credit, subscription, and anonymous network ledgers determine whether a page is available. Locked transcription text is not returned to the browser until the page is unlocked.

10. Contact Us

If you have any questions about this Privacy Policy or our data practices, please contact us at:

inksight.notes.app@gmail.com