Privacy

This site

Most of this site is static. The support form and TAMA validation features use Cloudflare Workers and Cloudflare D1. When you send a support message, the selected app, message type, message, optional email address, timestamp, browser user agent, and IP address are stored in D1.

Cloudflare Turnstile checks the submission, and Resend emails the message to me. There is currently no automatic deletion schedule for support submissions.

Images to Notes

When you process an image using the current bring-your-own-key or GitHub Copilot options, the Images to Notes Obsidian plugin sends the image and your configured prompts directly to the provider you select: OpenAI, Anthropic, Google Gemini, Mistral, an OpenAI-compatible endpoint, or GitHub Copilot. The selected provider’s terms and privacy policy apply. I do not receive your images or transcriptions through these modes.

API credentials and plugin settings are stored in the plugin configuration associated with your Obsidian vault. Where that configuration is copied depends on your Obsidian and sync configuration. The plugin has no analytics, tracking, or client-side telemetry.

The proposed managed transcription beta has not been built and there is no charge today. If you submit the beta-interest Google Form, your email address and form answers are sent to Google Forms and made available to me. I will use them only to evaluate demand and contact you about the beta. The form does not request payment information or create a subscription.

I will delete beta-interest responses within 90 days after making the final beta decision, or earlier if you ask me to. You can request access, correction, or deletion by emailing [email protected].

Effective date: August 10, 2026

Koku

Koku does not collect, store, or transmit any personal data. There are no accounts, no analytics, no tracking, and no network requests. All timer data stays on your device.

That’s the whole policy.

Effective date: May 8, 2026

Toki

Toki does not collect, transmit, sell, or share personal data. It has no accounts, advertising, analytics, tracking, third-party marketing SDKs, or network service.

Timer state and app preferences are stored locally on your device so Toki can restore your timer and settings. Toki uses Apple system features such as alarms and Live Activities to run timers and display their status, but the developer does not receive this information.

For privacy questions, email [email protected].

Effective date: August 16, 2026

Koe

Koe does not require a login or account. It stores entries on your device, and sharing only happens when you explicitly send content through the iOS share sheet.

Tama

Tama stores study data locally on your device, including sessions, quizzes, flashcards, persona chats, custom scenarios, and study plans. Account backups exclude secret API keys.

Conversation and speech data is sent to the AI, transcription, or voice providers you configure. Tama also supports local model, transcription, and text-to-speech options if you want to keep those workflows on your own computer.

The TAMA landing page records a first-party visitor identifier, page views, download clicks, managed-beta actions, referring page, and campaign parameters. These records are stored in Cloudflare D1 and used only to understand interest in TAMA and where visitors came from. The page does not use advertising trackers.

If you reserve a managed-beta spot, TAMA stores the email address, Japanese level, operating system, current speaking-practice method, and price confirmation you submit. This is used to evaluate demand and contact you about the beta. Joining the list does not create a subscription or charge you.

Managed AI has not been built. Before access opens, TAMA will publish what practice data is sent, which providers process it, and how long it is retained. Beta-interest records will be deleted within 90 days after the final beta decision, or earlier if you request deletion at [email protected].

Effective date: August 23, 2026

Pulse for Workflowy

Pulse accepts a Workflowy API key and uses it to request the content you choose to display. The API key is stored in the device Keychain. Saved locations, cached item content, completion state, reminder settings, and sync timestamps are stored locally in Pulse’s private App Group so the iPhone app and its widgets can share them.

Reminder hashtags and Workflowy date tags are processed on device, and notifications are scheduled locally by iOS. Pulse has no advertising, analytics, or tracking SDKs. The Pulse developer does not collect or sell personal data. Requests needed to read or update your account are sent directly to Workflowy and are subject to Workflowy’s own terms and privacy policy.

Disconnecting Workflowy in Pulse removes the stored API credential and locally cached Pulse data. Removing the app also removes its local data, subject to standard iOS and backup behavior.

Effective date: August 9, 2026