Privacy Policy

Effective date:

Kairumo does not collect your data. No accounts, no analytics, and no server of ours that keeps your notes. This page explains how that claim holds up — and how Cloud sharing, the one feature that uses a relay, protects you.

Platform: iOS · iPadOS · macOS | Applies to: v7.2.6

In one sentence: your notes, recordings and handwriting stay on your own device. We have no server that keeps your notes and no account that could be linked to you; only when you choose Cloud sharing (any network) does end-to-end-encrypted content that no one else can read pass through a relay, kept for at most 1 day after the session ends.

What we do not collect

Kairumo never collects, transmits or stores any of the following:

  • Name, email, phone number or any account details — the app has no sign-up or login of its own; the optional Google Drive sync is authorised directly by Google and the credential stays on your device (see “Google Drive sync” below).
  • Note content, ink strokes, audio recordings or transcripts.
  • Location, contacts, calendars or advertising identifiers.
  • Usage analytics, crash telemetry or behavioural data — there is no analytics or advertising SDK in the app.

Where your data lives

Entirely on your device:

  • Notes, pages, ink, recordings and transcripts are written to the app's local sandbox folder.
  • Your display identity (the name and colour shown while collaborating) and language choice are stored in local preferences; multiple devices signed in to the same Google account automatically append a device tag (e.g. (Device A), (Device B)) on the canvas for clear real-time attribution, computed locally without collecting personal info.
  • If you choose to keep the folder in any cloud drive, that copy is governed by that provider's terms and privacy policy — a relationship between you and them, not us, and we cannot see its contents.
  • Storage uses local atomic writes and hardware disk synchronisation (fsync) to safeguard your notes and ink against unexpected power loss or crashes.
  • System diagnostic logs, main-thread stall monitoring, startup exit-reason diagnostics and cloud sync logs reside exclusively in device memory or the local sandbox, and are never uploaded automatically; they only leave your device if you explicitly choose to copy or save them as text files.
  • The app automatically cleans up its own temporary files, abandoned model-download leftovers and trash that has passed its retention period, so it does not take up space needlessly; your notes and recordings are never touched. The “Storage” and “Device self-check” sections in Diagnostics are computed on your device only and nothing is sent anywhere — a report reaches the clipboard only when you tap “Copy report”. The built-in manual and privacy policy display fully offline and load no web fonts or other external resources.

Permissions the app asks for

Each one can be denied; only the matching feature stops working.

  • Microphone — used in two cases only: while you record a lecture or meeting (audio is stored locally), or while you hold or tap the voice capsule during collaboration (your voice is encrypted and streamed live to teammates in the room — never recorded or stored).
  • Speech recognition (Apple): used only when you transcribe with Apple's system speech recognition; it runs on the device whenever possible — see “Handwriting recognition, transcription and translation” below for the exception.
  • Photos — read only for the image you pick when you tap “Insert Image”.
  • Local network — used only for collaboration, to automatically discover rooms on the same Wi-Fi or connect directly. If this permission is disabled in system privacy, Kairumo automatically falls back to pure local relay mode; you can still connect by typing the host's IP manually with no compromise on privacy.

How sync and backup work

Neither passes through us — we have no server that could receive it.

  • Syncing is file copying: you pick a folder in your own cloud drive, the app puts the notebook files there, and moving them is that provider's job.
  • Point two devices at the same folder and they see each other's content. The app neither needs nor obtains your cloud account.
  • A backup is a single file saved where you choose. It is not encrypted, because it sits on your own device — where it goes next is your decision.
  • We cannot see which folder you picked, or whether you sync at all.

Google Drive sync (optional)

You can choose to sync automatically between your own devices with your Google account. This is optional — everything in the app works without signing in; cross-network collaboration does not use Google Drive.

  • Signing in goes through Google’s own consent screen. Personal sync requests only an app-private folder (appDataFolder): a hidden area that does not appear in your file list and that other apps cannot read; we cannot see any other file in your Drive.
  • The authorisation token stays on this device. We have no server, so it never passes through us.
  • That copy is governed by Google’s terms and privacy policy — that is a relationship between you and Google.
  • You can sign out any time under “Cloud sync” on the home screen; to revoke the grant entirely, remove the app in your Google Account security settings.

How collaboration works

Whichever way you connect, only the participants in a room can read what is shared.

  • There are two ways to connect. With Same Wi‑Fi, the device that starts the session acts as the relay itself and teammates connect straight to it, so nothing leaves your local network. With Cloud sharing (any network), traffic goes through an encrypted relay on Cloudflare (see “Advanced collaboration and the cloud relay” below). When the host opens the same room both ways, the host's device also forwards the room's encrypted content to the cloud relay so members on other networks can take part; with Same Wi‑Fi alone, nothing leaves your local network.
  • All content (including ink strokes, stickers, images, text boxes, tables, shapes, connectors, link previews, 3D models and comments) is end-to-end encrypted with AES-256-GCM. The key travels in the fragment of the invite link (#key=...), so the relay only forwards ciphertext it cannot read, and all canvas objects are persisted locally.
  • One technical consequence: participants in a session see each other's local network or private VPN IP addresses, which is inherent to connecting directly; if Bonjour discovery is disabled, collaboration automatically falls back to local direct relay.
  • Edits made while offline are queued locally and sent automatically once the connection returns.

Handwriting recognition, transcription and translation

All of this runs on the device by default; the one exception is the third point below.

  • Handwriting recognition uses the operating system's on-device capability.
  • Whisper transcription runs against a model downloaded to the device; audio never leaves it.
  • (Apple) When the engine is set to “Auto” or Apple's system dictation, Apple speech recognition is tried first. It always runs on the device when the device supports it; if the device does not, or on-device recognition fails, the system sends that audio to Apple's servers for recognition under Apple's privacy policy. To keep audio on the device, set “Transcription Engine Preference” to Whisper.
  • When the transcript language differs from the audio, the transcript is translated on the device: using system-provided or on-device translation capabilities. Only the transcribed text is translated; no audio is sent, and none of our servers is involved.
  • Scan Translation Pen: when you swipe across text boxes, tables, images or handwriting on the canvas, structured text extraction, regional image and handwriting recognition, multi-line auto-stitching, blurry-text confidence safeguards, on-device translation and bilingual speech synthesis (TTS) all run strictly on your device without transmitting scanned notes or speech to any external server; language preferences and converted comment pins, note boxes, highlights and masking tapes are saved solely inside your local notebook file.
  • “Reduce noise before recognition” processes only the copy sent to recognition, locally; the recording always keeps the original sound.
  • Timestamps generated by audio-ink synchronisation are stored solely within your local note file, contain no biometric identifiers, and are never uploaded.

Model and language downloads

The app connects only when you choose to download:

  • Recognition models such as Whisper come from public model hosting sources such as Hugging Face.
  • Translation languages are provided by the operating system or component vendor: downloaded and managed by the platform (over Wi-Fi only where applicable).
  • As with any ordinary download, that host sees your IP address and applies its own privacy policy.
  • We receive nothing about these downloads.

Multiple users and the lock (PIN)

One device can have up to 5 users. All of it works on your device; again we have no server and cannot see any of it.

  • Each user’s notes, recordings, preferences and sync data are kept in separate places inside the app’s sandbox. When you switch users, the app first saves the previous user’s content and then replaces what is in memory with the next user’s.
  • A user’s name and colour exist only on this device and are never sent to us; they are shown to people in a room (end-to-end encrypted) only when you start collaboration yourself.
  • A PIN is never stored in clear text: the app adds a random salt, runs it through many rounds of computation (PBKDF2) and stores only the result in the system’s secure storage (for example a keychain or keystore). It is not part of any backup or cloud copy, and we cannot get it. Repeated wrong entries lock it for a while.
  • Biometrics (Face ID, Touch ID, fingerprint, face unlock) are handled by the operating system. The app only receives “success” or “failure”; it never receives or stores any biometric data.
  • The PIN and biometric lock only keep other people sharing the device from opening your user by accident; it is not encryption, and someone who can access this device’s files directly may still be able to read the data. A forgotten PIN cannot be recovered by us — we never had it; the only way out is to delete that user.
  • When each user signs in to their own Google account, the authorisation credentials are stored separately, and a Google account can be used by only one user. This mapping exists only on the device; we never learn it.
  • Deleting a user removes all of that user’s notes, preferences, sign-ins and PIN from this device; the copy in the cloud is not affected — remove it yourself in your Google account’s security settings if you want to.

No third-party tracking and In-App Purchase privacy

The app contains no advertising SDK, no analytics SDK, no A/B testing and no push tracking. Core features are free forever; if you choose the optional one-time Kairumo Pro upgrade, payment and receipt verification are handled directly by the official platform store (such as Apple App Store / StoreKit 2 or Google Play) — we never receive, collect or store your payment card details or billing information. If you redeem a VIP Gift Pass, signature verification runs entirely on-device offline using Ed25519 cryptography with no account sign-in or data transmission. The source code is public, so anyone can verify this.

Advanced collaboration and the cloud relay

Recent versions introduce advanced collaboration features (live cursors, voice rooms, and time machine) that strictly follow our local-first principles:

  • Live voice: when you hold or tap the voice capsule, your microphone audio is converted to 16 kHz mono on the device, encrypted with the room key (AES-256-GCM) and streamed live to the teammates in the room. The relay only forwards it and never stores it; no one records or keeps it.
  • Live cursors, typing status and collaboration relay: presence such as cursors, typing indicators and selection outlines is only forwarded while connected and is never stored. Same Wi‑Fi rooms use the relay on your own device and are cleared when the room closes.
  • Time machine rollback: Editing history is preserved strictly within your device's local Oplog; we cannot and do not upload it.
  • Cross-network collaboration (cloud relay): the room runs on a relay hosted on Cloudflare (or one you deploy yourself). The relay sees only the room ID and connection details; strokes, objects and the notebook content are encrypted on your device with AES-256-GCM, and only participants hold the key, so the relay cannot read them. So that people can join while the host is offline, the encrypted operations and an encrypted copy of the full state are kept in that room; after everyone leaves (or the host ends the session) they are kept for 1 day and then all of the room's data is deleted automatically. No account is needed and Google Drive is not used.

Children's privacy

The app collects no personal data from users of any age, and therefore none from children under 13 (or the age set by your local law).

Drafting tools and export

The drafting (engineering drawing) features run entirely on your device:

  • Rulers, protractor, alignment snapping, edit tools, the solid helper and the glass-box unfolding are computed locally and need no network.
  • The practice-problem bank ships inside the app; your answers, scores and hints stay on the device and are never uploaded.
  • Exported DXF, SVG, STL, OBJ, GLB and USDZ files are generated on the device and go only where you send them through the system share sheet or a file location you choose.
  • Where your device offers an augmented-reality (AR) preview of a 3D model, that is a system component: it uses the camera and asks you for permission, and the app itself never receives camera images.

Your rights and deleting data

Because we hold no copy of your data (Cloud sharing only keeps ciphertext we cannot read), deletion is entirely in your hands:

  • Deleting a note in the app removes it from the device.
  • Deleting the app removes everything in its sandbox.
  • If you kept the folder in your own cloud storage, delete it there as well.
  • We cannot delete or restore anything on your behalf — we never had it.
  • Cloud-sharing room data (encrypted operations and full state) is kept for 1 day after everyone leaves or the host ends the session, then deleted automatically; we cannot read it or retrieve it for you.
  • One thing to be aware of: the notebook file is append-only by design (that is what stops multi-device merges from losing data), and milestone snapshots deliberately preserve history. So text or strokes you delete in the app disappear from view but may still be inside the file until it is compacted automatically. Keep this in mind before sharing a .padnote file — someone opening it in Kairumo can roll back to a milestone taken before your deletion. If you need to hand something over without its history, export it as PDF or as an image instead.

Changes to this policy

If this policy changes, the effective date and applicable version at the top are updated and published with the new release.

Contact

Questions about this policy: [email protected]