TapToNote

이 문서는 영어로 제공됩니다.

TapToNote — Privacy Policy

Effective date: 13 November 2026

TapToNote is provided by Serhii Onenko, individual entrepreneur (FOP), Kyiv, Ukraine. Privacy contact: support@taptonote.app. The full App Store name is “TapToNote: Speak & Keep for AI”.

What the app handles

TapToNote creates a local record containing the text you type or dictate, a random entry ID, and creation and last-edit times. You may enter any kind of text, including sensitive information or information about other people. The app uses these records to display, edit, re-dictate, delete, export and, if you opt in, synchronise your log with connected copies and share it with AI assistants you connect. Local use needs no account. There is no advertising SDK. Usage statistics are off unless you turn them on, and problem reports are sent only when you tap Send (see “Problem reports and optional usage statistics”). If you explicitly enable optional cloud sync, we receive and store the text entries you synchronize, as described below.

On-device dictation

TapToNote transcribes speech entirely on your iPhone. By default it uses Apple's on-device speech recognition; if iOS needs recognition files for your language, it downloads them from Apple once. You can also download a more accurate Whisper model (large-v3-turbo, run through WhisperKit) in Account → Dictation or from the card on Home: about 630 MB from Apple's App Store servers, deleted in the same place. Where Apple's on-device recognition does not support your language, the app offers this download. Your recordings, transcripts and learned vocabulary are not sent to Apple, OpenAI, Argmax, Hugging Face or us for dictation; TapToNote does not use Apple's server-based recognition, and there is no server-based transcription fallback. Using Whisper does not connect the app to an OpenAI service.

When you dictate, the app records audio into a file in its own storage on your iPhone; the audio never leaves your iPhone and is excluded from backups. The app saves the resulting text, not the recording. It deletes the audio once the text is saved. If the app stops while you are recording a note, that recording is transcribed at the next launch, then its audio is deleted. If no speech is heard in a new note's recording, its audio stays on your iPhone so you can try again, until you delete it on Home, sign out, delete your account or remove the app. If a recording cannot be transcribed after three tries, its audio stays until you discard it on Home or remove the app. Microphone permission is required; Apple Speech Recognition permission is not. You can revoke microphone access in iPhone Settings and continue typing.

While dictation is still getting ready (recognition files downloading, or the Whisper model being prepared after a download or an update), a recording is kept in a protected file on your iPhone, excluded from backups, until it has been turned into text. Then the text is saved as a note, dated when you spoke, and the audio is deleted at once. This audio is never uploaded.

The app shows “Preparing dictation…” while dictation is getting ready. Speech recognition can still be inaccurate or fail. It does not identify speakers or guarantee separation of voices in a noisy environment.

When you correct a short word or phrase in an entry, TapToNote may store the corrected wording and the original misheard wording in a small, language-specific vocabulary on your iPhone. It uses the corrected wording as a local dictation hint and can replace the same misheard wording in a later transcript locally. This does not train a remote model. Corrections are not included in exports. Account → Delete all notes… also clears them. Open-source licenses are available in Account → Legal.

This section describes TapToNote's microphone feature. If you use iOS keyboard Dictation to fill a text field, that separate system feature is governed by your Apple settings and Apple's Siri, Dictation & Privacy notice; it may use Apple servers. TapToNote does not control that system feature.

Storage, backups and exports

The app stores entries in an on-device SwiftData database shared with its own app components through an iOS App Group. It does not use CloudKit. Without an enabled cloud connection, local capture does not upload entries. Optional cloud sync requires sign-in and TapToNote Plus. After you subscribe, the app asks separately (“Copy your log to the cloud?”) and copies nothing until you choose Agree. Your answer is kept with your account, so a new install or a new sign-in to the same account does not ask again. Signing out stops copying and removes that account's notes from this iPhone; signing in again downloads those in the cloud. Your iPhone's iCloud Backup or a backup on a Mac or PC may nevertheless include app data, depending on your device settings. Backup copies are managed by Apple or the backup destination, not by TapToNote. You can manage iCloud Backup in iPhone Settings.

TapToNote keeps no backups of its own on the phone. Export your log to a file when you want a copy.

You can export a copy as a JSON file and choose where to save or share it through the iOS share sheet. The temporary export file is removed when sharing ends or on a later app start; a saved, mailed or shared copy remains wherever you sent it. Other apps and recipients handle those copies under their own terms and privacy practices.

Using an AI tool to read or change entries can send selected entry text to that AI provider under its own terms and privacy policy; TapToNote does not send your entire log to ChatGPT, Codex or Claude automatically.

Optional cloud connection

Local capture and dictation work without an account. Sign-in uses Sign in with Apple through Clerk, which handles account sign-in, your email and account identifier; Apple may give us your real email or a private-relay address. TapToNote does not receive your Apple password. See Clerk's privacy policy. If you add a first and last name on your profile page, Clerk stores them with your account. Tokens are stored in this iPhone's Keychain, available only on this unlocked device. Signing in alone does not upload entries.

Clerk records the IP address, the browser or device type and the approximate location (city and country) of each sign-in to protect the account. When you sign in on another device by scanning its QR code, our server stores that device's browser and system name (for example Chrome on macOS) so your iPhone can show them before you confirm. It stores the code only as a hash and deletes the record about an hour later.

After you subscribe to TapToNote Plus and choose Agree, all local text entries and streams, their identifiers, timestamps, revisions and deletion metadata are synchronized to our server on Oracle infrastructure in Tokyo, Japan. Audio and learned dictation vocabulary stay on the iPhone. While the app is open and online it coalesces changes and checks for remote updates; it also uploads changes in the background when iOS allows, for example after a Shortcut saves a note. Offline changes remain local until a successful sync. Conflicts require your choice.

The server stores a random installation identifier and last contact/successful-sync times to report freshness. An old time means potentially stale data, not proof the phone is offline. We do not use this identifier for advertising or cross-app tracking.

HTTPS (TLS 1.2 or later) protects transport. The server's disks, the database snapshots and the off-site copies are encrypted at rest (AES-256). The cloud copy is not end-to-end encrypted. The server processes readable text; the operator and hosting administrators may have technical access. Clerk receives authentication information, not log text. Oracle hosts the server; see Oracle's privacy information. Providers receive network/security information such as IP addresses. Our application diagnostics use fixed error categories and do not intentionally log entries, audio, emails, passwords or tokens.

Before any AI assistant can read your notes, the app asks separately (“Share your notes with AI assistants?”), and our server gives no assistant any note until you choose Allow. You then choose which assistants to authorize: ChatGPT, Codex, Claude, Claude Code or another MCP-compatible assistant. An assistant you connect receives the text of your notes, their date and time, and your stream names, with the technical details it needs to work with them (entry and stream identifiers, revisions, your plan and trial, and a random identifier and the last sync time of each of your iPhones), and only when it asks for them. Tools can read, search, add and edit your cloud entries. Entry deletion requires a separate user-confirmation form; clients without that confirmation support cannot delete. AI tools cannot delete your TapToNote account. Notes an assistant reads are sent to the provider you chose: OpenAI for ChatGPT and Codex, Anthropic for Claude and Claude Code, or the provider of another assistant you connect. They are handled under that provider's terms, including OpenAI's and Anthropic's privacy policies, and the provider must protect them at least as well as this policy describes. We do not control or retract those copies. TapToNote itself does not analyze entries with AI. The server keeps which AI assistants are connected and when each last used your account; you withdraw an assistant's access in Account → AI assistants → Disconnect, and your Allow for all assistants with Disconnect all AI assistants; the app then asks again before an assistant can read your notes. Use the same TapToNote account on iPhone and in the assistant; your assistant's sign-in email can be different. When you connect an assistant, it may also receive the name and email address of your TapToNote account through the standard sign-in scopes (openid, profile, email) that assistants such as ChatGPT request; they give no access to your entries beyond what you authorize.

Where EU/EEA rules apply, we process account and sync data to provide the service you request (GDPR Article 6(1)(b)); security and minimal deletion records serve our legitimate interest in preventing unauthorized access and restoration (Article 6(1)(f)). Optional cloud transfer requires your affirmative choice. If your entries include health or other special-category data, choosing Agree in the app is your explicit consent to copying them (Article 9(2)(a), where applicable). Sharing them with AI assistants is based on your consent (Article 6(1)(a)): choosing Allow is that consent, and your explicit consent for special-category data (Article 9(2)(a), where applicable). Do not upload another person's sensitive data without a valid legal basis. You can stop future uploads by signing out (Account → Sign out) or delete the account (Account → Delete account…). Withdrawal does not undo earlier lawful processing or retract third-party copies. No cloud choice is required for local use.

Account deletion and server retention

Open Account → Delete account…. The app asks you to confirm with Sign in with Apple, then permanently deletes the account and its cloud data. Your notes and learned words on this iPhone stay. Cancellation deletes nothing. A failed or unconfirmed request pauses sync until its outcome is checked.

Once accepted, the server durably blocks that account's sync and AI access, removes active cloud entries, streams and device metadata, and requests deletion of the Clerk identity and revocation of the app's Sign in with Apple authorization. A temporary Apple token is kept with the pending record only until Apple revocation finishes or is abandoned. If the provider is unavailable, the account stays blocked and deletion is retried automatically; the app reports a pending operation and lets you check its status. Completion is shown only after the identity deletion succeeds or the provider confirms that the identity no longer exists. The phone keeps its notes and learned words, removes cloud conflicts, sync checkpoints and connection credentials, and removes any pairing secret left by an older version. It remembers which notes belonged to the deleted account, so they are never uploaded to another account without asking.

Our server takes one database snapshot a day and keeps it on the server for at most five days. An encrypted copy of each daily snapshot is also stored outside the server, in Oracle Object Storage in Tokyo, and deleted after six days. Oracle also backs up the whole server disk once a day and keeps each disk backup for one day. A small separate deletion ledger records deleted accounts. Pending operations keep the provider account ID until they finish. Completed records keep only hashed account and receipt identifiers and deletion times, for access blocking, safe restoration and completion checks, never entry text or email. The ledger is not in the database snapshots; an encrypted copy of it goes with each off-site copy, and Oracle's disk backups include it. After any restore, before the service is back, we re-apply every deletion recorded in the newest copy of the ledger.

Deleting the account does not remotely erase another phone's offline copy, a copy on another device, previous exports, AI-provider conversations, support correspondence or iCloud, Mac or PC backups. Manage those separately. Account deletion prevents those devices from using the deleted cloud account. Underlying device or infrastructure storage may retain remnants; active-database deletion is not a promise of forensic erasure.

Cloud data is processed outside your country, including in Japan. The European Commission has recognised that Japan protects personal data adequately (adequacy decision of 23 January 2019). For transfers to other countries we do not claim a specific transfer mechanism. Do not use the cloud for regulated information.

Problem reports and optional usage statistics

Contact us. Nothing is sent until you tap Send in the Contact us form. A report contains the type you choose (Bug, Idea or Feedback), the message you type, a rating if you give one for Feedback, a trail of the screens you opened in the last five minutes (fixed screen names only, never any text), and technical details: app version, build configuration, iOS version, device model, a few fixed labels about the app (plan, sync state, theme and language), the voice model’s last load time, the last dictation’s length, its transcription time and the app’s memory use at its end, and a random installation identifier. It never contains your log entries or stream names. It contains your email and your account identifier only if you switch on Email me when this is fixed: then the email address and the account identifier of that report are sent with it and used only to reply to you; you can request their deletion at support@taptonote.app. In builds distributed for testing (TestFlight), the account identifier, but not the email, is attached to every report from a signed-in account. Please do not write sensitive information in the message. If delivery fails, nothing is queued or sent later; you can retry from the open form. If you are not using optional usage statistics, a report uses a one-off random identifier, so separate reports cannot be linked to each other. We use reports to understand and fix problems. Where EU/EEA law applies, the legal basis is our legitimate interest in maintaining the app. We keep reports only as long as needed to resolve them and never longer than the event retention of our PostHog plan.

Optional usage statistics. These are off by default. On the first launch, the Terms screen has a separate switch, Share usage statistics. It stays off until you turn it on; agreeing to the Terms does not turn it on. You can turn it on or off at any time in Account. Nothing is sent before you turn it on, and the app works the same either way. When on, the app sends only these fixed event names: onboarding_started, mic_permission_granted, mic_permission_denied, model_ready, action_button_set, app_opened, terms_accepted, sign_in_started, sign_in_completed, cloud_consent_granted, cloud_consent_declined, first_entry_saved, connect_ai_opened, assistant_link_copied, subscription_opened, purchase_started, purchase_completed, purchase_cancelled, export_used, model_load_failed, dictation_transcribed, daily_metrics, crash_diagnostic. The only properties beyond the event name are the export file format (export_used), the voice model’s load time (model_ready), a fixed error category and the error’s domain and number, without message text or file paths (model_load_failed), the dictation’s length, its transcription time and the app’s memory use (dictation_transcribed), Apple’s daily MetricKit counts of how the app ended, by exit reason, and its peak memory (daily_metrics), and a crash’s exception type, signal and termination reason category, without stack or text (crash_diagnostic), plus the same technical details as above (app version, build configuration, iOS version, device model) and a random installation identifier. The app creates this identifier when you turn statistics on and keeps it on this iPhone until you turn them off, so events from one installation can be linked to each other. It is not linked to your name, email or TapToNote account. Events never contain entry text, transcriptions, stream names, search text, your account email or identifier, tokens or file contents. No person profile is created, IP-address geolocation is disabled, no advertising identifier (IDFA) is used and there is no tracking across other companies’ apps or websites. We use them to see where people stop in the app and to improve it; where EU/EEA law applies, the legal basis is your consent.

Processor and location. Reports and usage events are sent over HTTPS to PostHog (PostHog, Inc.), our analytics processor, through its host eu.i.posthog.com. PostHog’s EU cloud host stores this data in the European Union; PostHog acts as our processor under its data processing agreement. The network request necessarily reveals your IP address to PostHog’s servers; PostHog discards it and does not store it. See PostHog’s privacy policy.

Withdraw consent. Turn off Account → Share usage statistics. Sending stops immediately and the installation identifier is deleted from this iPhone. Because events are not linked to your name, email or account, and the identifier is gone, we cannot find and delete the events sent earlier; they contain no entry text. Turning the switch on again creates a new random identifier. Reports you already sent can be corrected or deleted on request at support@taptonote.app if you include the email address you gave in the report.

Beta sign-up on the website

If you ask to become a beta tester with the form on taptonote.app, we receive your name, the email you type, the AI assistants you choose (and the name you type under Other), your note if you write one, the phone you pick and the page language, and use them only to invite you to the beta and to write to you about it. The request reaches our mailbox through Cloudflare, which hosts the website and routes our mail. To invite you, we add your name and email to the tester list in Apple’s TestFlight, and Apple sends you the invite. We keep your request until you ask us to remove you or the beta ends. If you join with the public TestFlight link on the website instead, you give us nothing there: you join in Apple’s TestFlight, which Apple runs under its own privacy policy. Either way, feedback you send through TestFlight reaches us through Apple.

Visit counts on the website. The pages of taptonote.app count visits and button clicks anonymously, without cookies and without storing anything in your browser. Each event carries a random identifier that exists only until you reload or leave the page, the page language, the device type (phone, tablet or desktop), the campaign tags of the link you came with and the site you came from, and never your email, notes or anything you type. Events go over HTTPS to PostHog (PostHog, Inc.), our analytics processor, through eu.i.posthog.com, which stores data in the European Union; the request necessarily reveals your IP address to PostHog, which discards it and does not store it. Nothing is sent if your browser signals Do Not Track or Global Privacy Control.

Sign-in and consent pages. The pages where you sign in on another device (taptonote.app/sign-in) or allow an AI assistant to access your notes (taptonote.app/consent) load Clerk, our sign-in provider, from clerk.taptonote.app, and the bot check Clerk uses, Cloudflare Turnstile. Clerk and Cloudflare may store cookies or similar data in your browser that are needed to sign you in securely and to tell people from bots. We use them only for sign-in and security. Clerk records the sign-in as described in “Optional cloud connection”. These pages do not send visit counts.

Retention, deletion and your choices

Entries remain in the app's local database until you delete individual entries, use Account → Delete all notes…, sign out of the account they belong to, or remove the app. Deletion removes entries from the active app database; iOS controls underlying storage reclamation. Deleting from the app does not delete earlier exports, messages, recipients' copies or device backups. Manage those separately with the relevant service or backup settings. With cloud sync active, deleting an entry or all entries also deletes the cloud copy once your iPhone is online; only a deletion marker without text remains. You can review your entries in the app and export them before deletion.

You can revoke microphone access in iPhone Settings. This affects future dictation and does not delete existing text entries. If you used Apple speech recognition in an earlier version of TapToNote, use Apple’s privacy controls for any data already processed by Apple; this update cannot retract it.

Support email

If you choose to email us for support, Serhii Onenko receives your email address, message and any files you include. Please avoid sending sensitive log entries unless they are needed to explain your request. Providing support information is optional, but without a return address we cannot reply. We use it to answer and follow up on your request; where EU/EEA data-protection law applies, our legal basis is our legitimate interest in providing support. We do not use support messages for advertising.

Our Gmail service (Google) and your email provider handle the correspondence. Email providers may process data in other countries; see Google's privacy information and transfer information. We keep support correspondence while needed to resolve and follow up on your request, or for an applicable legal obligation or active dispute, and delete it when those reasons no longer apply. Support email contains only the information you choose to send. Entries separately uploaded through an enabled cloud connection are handled as described in the cloud-sync section.

Your rights

Depending on where you live, you can ask for access to your personal data, a copy of it, its correction or deletion, or the restriction of its processing; object to processing based on our legitimate interest; and withdraw consent at any time, without affecting earlier processing. Write to support@taptonote.app; we reply within one month. You can also complain to your data-protection supervisory authority; in Ukraine, the Ukrainian Parliament Commissioner for Human Rights. We cannot retrieve or erase entries from your device, device backups or copies you shared.

We do not sell personal information or share it for advertising. Apart from our service providers, your notes reach another company only when an AI assistant you allowed and connected reads them (see “Optional cloud connection”). Our service providers process personal information only on our instructions and protect it at least as well as this policy describes. We make no automated decisions and do no profiling.

Children

TapToNote is not directed to children under 13 (or under the age of digital consent in your country, up to 16). We do not knowingly collect data from them; if you believe a child has given us data, write to support@taptonote.app and we will delete it.

TapToNote Plus subscription and purchase records

Apple processes App Store subscriptions. We receive the subscription product, original/current transaction identifiers, validity, refund/revocation status and a random app-account token linked to your TapToNote account to verify access. We do not receive payment-card details or your Apple account password. These account-linked purchase records remain while the cloud account exists and are removed when account deletion is accepted, subject to 14-day server backup expiry. Apple retains its own records under its terms and privacy policy. We use this data for service performance and security, not advertising.

Expiry stops sync and authorized AI access, without deleting phone data. You can still export your log or delete the account without renewing; to receive a copy of your cloud data, email support. After 365 days without an active subscription, measured from its verified coverage end, a scheduled operation revalidates inactivity and removes cloud entries, streams and device metadata. If Apple is unavailable, removal is postponed. Server snapshots expire within 14 further days; restoration repeats the inactivity check. This does not erase phone entries, exports, AI copies or Apple's billing records. Signing out alone neither cancels billing nor immediately deletes the cloud journal. An account that never had a subscription holds no cloud entries; its sign-in identity, email, consent record and sign-in records are kept until you delete the account.

Changes

We may revise this policy as the app changes. The effective date identifies the current text. We will make a revised policy available before a material change in data handling takes effect and give any notice required by law. Questions: support@taptonote.app.