Frequently Asked Questions

Yes. Saving to Obsidian without sending an email is a Premium feature. Select the destination folder and grant access before saving.

Syncing with other devices depends on your own sync service and settings. See the official App Store description for details.

Yes. The Free plan lets you send up to 3 memos a day, with no time limit. No credit card registration is required — you can start using it as-is from day one. If you want to send more, the Premium plan (monthly or annual) gives you unlimited sends.

We offer a monthly plan and an annual plan: $2.99/month or $29.99/year (¥500/month or ¥5,000/year in Japan). Please check the App Store in-app purchase screen for pricing in your region. The annual plan works out cheaper than paying monthly.

Tap "View Plans & Subscribe" in the "Premium" section of the Settings screen to open the plan details screen (Paywall). On the Paywall you can review:

• The name, duration, and regional price of the monthly and annual plans
• An explanation of auto-renewal and how to cancel
• Links to the Terms of Use and Privacy Policy
• A "Restore Purchases" button

You will also be offered an upgrade to Premium when you reach the daily send limit on the Free plan.

Yes. The Free plan requires no registration and has no time limit — you can send up to 3 memos a day for free from day one. No credit card is needed.

Purchasing is entirely optional. If you ever want to send more, upgrade to the Premium plan (monthly or annual) whenever you need it for unlimited sends.

You can cancel from your Apple ID's subscription management screen:

1. Open the "Settings" app on your iPhone
2. Tap your name at the top of the screen
3. Tap "Subscriptions"
4. Select your Simple Memo subscription ("Simple Memo Premium" or "Simple Memo Annual Premium")
5. Tap "Cancel Subscription"

After canceling, you can keep using Premium features until the end of the current billing period. After that, you can continue on the Free plan (up to 3 memos a day) for free.

Yes. In the Premium section of the Settings screen, tap "View Plans & Subscribe", then tap "Restore Purchases" at the bottom of the Paywall screen that opens. As long as you are signed in with the same Apple ID, your subscription will be restored.

This means product information could not be fetched from the App Store. Please try the following:

1. Check your network connection (Wi-Fi / cellular)
2. Tap the button labeled "Tap to load" to re-fetch the product information
3. Once the re-fetch succeeds, you can proceed straight to the purchase flow
4. If it keeps failing, check your sign-in under iOS "Settings > [your name] > Media & Purchases"

They are sent as emails to the destination email address you verified in the Settings screen. The sender is noreply@mail.simplememofast.com, shown as “Simple Memo” (as “シンプルメモ” when the app language is Japanese).

The subject is generated automatically using these rules:

• If a subject template is set: template + first line of the memo (e.g., "Simple Memo Today's shopping list")
• If the subject template is empty: the first line of the memo becomes the subject
• If the memo starts with blank lines: the first line containing text becomes the subject
• The subject is truncated at 60 characters
• With Obsidian integration and AI Auto-Tagging turned on: a short title made on the device replaces the first line (the first line is used if no title can be made)

Yes. Enter text in the "Signature" field of the Settings screen, and it will be appended to the end of every email you send, after a -- separator line.

An empty editor does not confirm that your email has arrived. A memo may be reserved while its recipient is unverified, or waiting in the Outbox when a connection is unavailable. Complete recipient setup and verification, then reopen the app when you are online and check for pending sends. Confirm arrival in the recipient inbox or spam folder. If you have chosen to save only to Obsidian, no email is sent; check the selected note instead.

Yes. However, a 1.5-second cooldown is in place to prevent accidental sends. Consecutive taps within 1.5 seconds are ignored, and a "Please wait a moment" toast is shown.

Yes. When you send a memo offline, the message is stored in the on-device Outbox (unsent queue), encrypted with AES-GCM. Once your network connection is restored, sending resumes automatically.

An orange banner appears at the top of the screen reading "Offline - will send when connected". When the network recovers, the banner disappears automatically.

Yes. Outbox messages are stored encrypted in the device's storage, so they are not lost when you close the app or even restart your iPhone. Resending is attempted automatically the next time the app launches, or as a background task.

Yes. The in-app send history screen lists sent, unsent, and failed memos. It keeps the 100 most recent memos (memos that haven't gone out stay regardless of the count).

The following is displayed for each memo:

• A preview of the memo body (up to 10 lines)
• Date and time sent
• For memos that haven't gone out, their status ("Pending" or "Failed"; for memos saved only to Obsidian, "Waiting to write" or "Write failed")

Yes, for a memo that hasn't gone out (unsent or failed): long-press it in the history screen and choose "Resend". Because the same message ID is used, the same memo is not sent twice within 24 hours (duplicate prevention at the email service). For a memo saved only to Obsidian, the option is "Write again" instead. Long-pressing a memo that has already been sent opens the share sheet.

Yes. Long-press a sent memo in the history screen to bring up the standard iOS share sheet. You can copy it to other apps, share via AirDrop or Messages, and more.

No. Memo bodies pass through the Relay API (Cloudflare Workers) and the delivery provider (Resend) at send time, but they are not persistently stored on our servers and are not written to logs. The Outbox and send history are stored only on your device, encrypted with AES-GCM. Ordinary email is not end-to-end encrypted.

Simple Memo encrypts all memo data stored on the device (Outbox, history and the auto-saved draft) with AES-GCM (256-bit).

• The encryption key is stored in the Keychain with a this-device-only setting that is readable after the first unlock (other apps cannot read it, and it does not move to another device through a backup)
• Files are covered by Apple's standard Data Protection (completeUntilFirstUserAuthentication)
• The encryption key is never sent off the device

The full route of a memo — local-only vault appends, on-device AI tagging, and why it is not E2EE — is mapped on the Privacy Architecture page.

Yes. All communication between the app and the Relay API (Cloudflare Workers) is encrypted with HTTPS (TLS). In addition:

• HMAC signatures: every request is signed with HMAC-SHA256 for tamper detection
• Static API key authentication: a dedicated API key is required to access the server
• Ephemeral URLSession: URLSession uses an ephemeral configuration, so no communication cache, cookies, or URL cache are ever stored
• Idempotency-Key: each memo gets a unique message ID that is reused on resends, so the same memo is not sent twice within 24 hours (duplicate prevention at the email service)

Memo bodies transit through our Relay API (Cloudflare Workers) and the delivery service (Resend) for sending; we do not persistently store them (as in the Privacy Policy). Verification codes disappear automatically when they expire after 10 minutes.

For email addresses, records do remain on our servers, for example (see the Privacy Policy for the rest):

• A mapping between send IDs and a hash of the recipient address (derived from SHA-256), on Cloudflare D1
• A record that the address was verified: the app's random per-device ID paired with the address hash, deleted automatically after one year (Cloudflare KV)

We do not treat these hashes and IDs as fully anonymous information.

On the device, Outbox and history data are AES-GCM encrypted, with the encryption key stored in the Keychain.

Yes, it can. The current app does not enable automatic hiding (the privacy overlay) when it moves to the background, so memo text that is on screen may remain in the app-switcher snapshot. See the Privacy-First Design dev log for details.

No. Sensitive information such as email addresses, memo bodies, verification codes, tokens, and URLs is never written to logs in any build, including DEBUG builds. Even error logs record only the kind of error (its type name), not detailed messages.

Yes. Like the Outbox, history data is stored on the device encrypted with AES-GCM. The encryption key is kept in the Keychain with a this-device-only setting that is readable after the first unlock, and the encrypted files use Apple's standard Data Protection (completeUntilFirstUserAuthentication).

Deleting (uninstalling) the app removes its data on the device (Outbox, history, and settings). However, items saved in the Keychain (such as encryption keys) can remain on the device after the app is deleted, because of how iOS handles the Keychain (the encrypted memo files are deleted with the app). Memos you have sent stay where they were delivered (your email inbox, your Obsidian vault, or Notion), so delete them there.

To prevent unauthorized sending to someone else's email address. Verification confirms that you are the owner of that email address. This is an important mechanism for keeping the app safe.

During voice input, Dialogue Memo asks brief follow-up questions in the same composer. Answer by voice, or tap the memo to stop and edit with the keyboard. Review the memo before tapping Send.

The questions and note organization use Apple Intelligence on iPhone. A compatible iPhone, iOS 26 or later, Apple Intelligence enabled, and a supported language model are required. Voice input also needs microphone permission. Dialogue Memo itself does not require Siri setup. See the official App Store description for details.

Simple Memo is a memo app dedicated to just three steps: launch → write → send. The memo you type is sent with one tap to the email address you set in advance. There are no complex features such as folder management, tagging, or sync settings. "Jot down what's on your mind right now and send it to your own email" — that is the one thing this app does.

• Emailing a shopping list to yourself
• Jotting down an idea that strikes you on the go
• Instantly recording something important you heard in a meeting
• Sending yourself work task reminders
• Noting things to do after you get home, while walking
• Temporarily capturing URLs, phone numbers, addresses, and other info you'll need later

To receive memos by email, complete recipient setup and verification by following the delivery setup instructions in the app. If you use email-code verification, enter the six-digit code you receive. If a memo is reserved, finish verification and then check its arrival in your inbox. To save to Obsidian as well, enable the integration, grant access to the vault folder and choose the destination note. Send a short memo and check that it appears in that note. For installation steps and plan details, see the download guide.

Yes. Tap "To" in the Settings screen, enter the new email address, and complete verification again. Once the new address is verified, all subsequent memos are sent to the new address.

Tap "Clear Recipient" (shown in red) at the very bottom of the "Email Settings" section of the Settings screen. When you tap "Clear & Restart" in the confirmation dialog, all of the following is deleted:

• The configured destination email address
• The verified status (the verified address stored in the Keychain)
• Past verification state (including legacy data)

After clearing, the app goes back to the first-run setup (tutorial). No memo is emailed until you set up and verify an address again. Use this when you want to start over with a different account or redo verification.

Yes. From the "How It Works" section of the Settings screen you can open an illustrated three-step guide:

1. Email setup: register and verify your destination email address
2. Write a memo: the keyboard appears right at launch, ready for immediate input
3. Send: one tap sends it to your destination email

It is translated into each of the 10 supported languages, including English and Japanese.

Any address that can receive email works — all email services are supported. Gmail, Outlook, Yahoo Mail, iCloud Mail, company email, custom-domain email, and more, with no restrictions.

Text that is prepended to the subject of each email you send. For example, if you set "Simple Memo" and the first line of your memo is "Today's shopping", the subject becomes "Simple Memo Today's shopping". Leave it empty and the first line of the memo becomes the subject as-is.

Yes. In the "Voice Input & Sound" section of Settings ("Sound & Haptics" on devices before iOS 26), you can toggle "Send Sound" on or off. Even with the sound off, haptic feedback continues to work. Note that in silent mode the sound is muted automatically regardless of the setting.

Yes. The app follows your iOS system setting and switches between light and dark mode automatically. There is no app-specific theme switcher; it always follows the system setting.

No. Simple Memo is an independent app inspired by the original Captio and has no relationship with Captio's developer. It aims to recreate and build on the experience Captio offered: launch → type immediately → one-tap send → instant clear.

No. Simple Memo - for Obsidian is an independent app developed by YURIKA, K.K. and is not an official Obsidian app or plugin. The Obsidian integration automatically appends your sent memos to a note in your own Obsidian vault and requires no Obsidian account or plugin. Obsidian is a trademark of Dynalist Inc. For how this compares with Obsidian 1.13's official share sheet, Shortcuts, and QuickAdd, see the honest comparison.

Yes. Basic Apple Watch support (quick capture) is available. You can send a memo to your own email from Apple Watch, with voice dictation and Smart Stack support (advanced Watch automation is not supported). Once setup is complete, opening the app brings up the standard watchOS input screen. The input method shown varies with the model, language and screen state; when dictation is ready to use, opening the app and pressing Done (as few as 2 taps) starts the send. See the Apple Watch page for details.

Simple Memo recreates the core experience of the original Captio while improving and extending it in the following ways:

• Outbox (unsent queue): unsent memos stay on the device and are resent automatically, even offline
• AES-GCM encryption: the Outbox and send history on the device are encrypted
• 10 languages: including Japanese and English (RTL supported)
• Email address verification: 6-digit code verification to prevent abuse
• Send animation: page-turn style 3D animation + haptics

No. There is no feature for importing data from the original Captio. Simple Memo is an app independent of Captio, so the data is not compatible.

No. Simple Memo specializes in sending text memos fast and does not support image attachments. To save photos, please use Apple's built-in Photos or Notes apps. Simple Memo is a dedicated tool for "capturing a thought as text, right away."

• iPhone (iOS 16.0 or later)
• Apple Watch (watchOS 9.0 or later)

The target for Time-to-Text — from launching the app to being able to type — is 500 milliseconds or less. In the developer's measurement (iPhone 16e, warm launch, median of 5 runs), it took about 0.4 seconds from the tap until the app accepted typing. The app skips Storyboards and builds its UI directly in UIKit to keep launch fast.

No external SDKs are used anywhere in the "primary data path" — memo encryption (CryptoKit), key storage (Keychain Services), and networking (URLSession / Network.framework) are built entirely on Apple's first-party frameworks.

Since v2.4, the app additionally uses the GoogleSignIn-iOS SDK and Firebase Authentication SDK for an optional onboarding shortcut (importing your email from a Google account), plus the Firebase App Check SDK to protect the backend API against unauthorized access. Usage analytics go to our own /v1/analytics/event endpoint, and the app also includes the AppsFlyer SDK for acquisition and usage analytics (how first-party analytics and AppsFlyer run depends on the app version and your analytics choices; see the privacy policy).

The following 10 languages are supported: Japanese, English, Spanish, French, German, Portuguese, Russian, Chinese (Simplified), Chinese (Traditional), and Arabic.

From the "Language" section of the Settings screen. Changes take effect across the entire app immediately (the screen reloads automatically).

Yes. When you select Arabic, the text direction, UI layout, and navigation bar button placement all switch automatically to RTL (right-to-left).

Simple Memo is built to keep background network activity low. Outbox resends happen when the connection returns, when you open the app, or in a background task scheduled with iOS's BGTaskScheduler (iOS decides when that task runs). The app does not run continuously in the background.

Please check the following:

• There are no typos in the email address
• It has not been filtered into your spam/junk folder
• The sender is noreply@mail.simplememofast.com (shown as “Simple Memo”)
• Verification codes expire after 10 minutes. If expired, request a new code
• You can enter the code up to 5 times. After 5 failed attempts, request a new code

Enter and verify a recipient email address from the Settings screen. No memo is emailed until the address is verified (a memo that shows "Send reserved" stays on the device and goes out once the address is confirmed).

Verification of the destination email address has not been completed. Tap the "Verify" button next to the email address in the Settings screen and complete the verification flow. If you changed the email address, the new address also needs to be verified.

This appears when many memos are sent in a short time. To prevent abuse, the sending server caps how many memos can be sent from the same IP address per hour (a separate cap from the free plan's 3 memos a day; it applies to Premium too).

If you reach the cap, wait a while and try again. Once the limit lifts, messages saved in the Outbox are resent automatically when the connection returns, when you open the app, or from a background task (automatic resends have a retry limit). Devices using the same Wi-Fi network may share this cap, so it can be reached even if you send only a few memos.

This appears when, for example, the sending server (Relay API) has a problem. Your memo stays in the Outbox and is resent automatically when the connection returns, when you open the app, or from a background task (automatic resends have a retry limit; once a memo reaches it, you can resend it manually from the history screen). If the problem continues, please contact support.

Please check the following:

1. The destination email address is correctly verified
2. Your network connection is stable
3. Check your spam/junk folder
4. Make sure your email service's filtering settings are not blocking mail from simplememofast.com

Please check the following:

• Your network connection is stable
• The destination email address is verified
• Each memo is retried automatically up to 5 times. After 5 failures, automatic retries stop and History shows it as "Failed"
• Long-press the memo in the history screen and choose "Resend" to send it again

Memos saved in the Outbox are not lost. A memo is encrypted and saved to the Outbox the moment you tap the send button, so after a crash, simply relaunch the app and resending is attempted automatically.

This happens when the server's response never reaches the device — due to a network timeout, backgrounding, or similar — so the app judges the send as "failed" even though it actually succeeded. The app currently handles this as follows:

• Immediate retry after 5 seconds: even when treated as a timeout, one automatic background resend is attempted right away
• Instant retry on app return: the moment you come back to the app from the home screen, any unsent messages are resent right away (automatic resends have a retry limit)
• Duplicate-send prevention: every send path uses the same Idempotency-Key, so even if the message had actually reached the server, the same email is not sent twice within 24 hours (duplicate prevention at the email service)
• Automatic history repair: when a resend succeeds, the corresponding history entry is automatically updated to sent

So even if "Pending" is shown for a while, it switches to sent and the "Pending" badge disappears once a resend succeeds, and a resend within 24 hours does not send the same email twice.

Yes. Each send is tracked individually by its history entry ID, not by its body text. Even if you send the same short message like "OK" three times in a row, each of the three history entries is correctly marked "Sent" (earlier versions could misjudge based on matching body text).