MarkMono

Privacy Policy

Privacy Policy

Monoshiri (operated by Makoto Kobayashi; the “Operator”) establishes this Privacy Policy regarding the handling of information in “MarkMono” (the “App”) — a Markdown editor for iPhone, iPad, Mac, Windows and the web — together with the servers the Operator runs for it (collectively, the “Service”). The Japanese text is the original; this page is a reference translation, and the Japanese version governs if the two differ.

Summary

There are three places your notes can live, and we only hold the third.

  • Your own Google Drive — we never receive the contents of your files.
  • A folder on your device (macOS / Windows) — nothing leaves your machine; no request reaches us at all.
  • Team collaboration — your documents are stored on servers we operate. This is the one case where we hold your content.

If you use only Google Drive or a local folder, sections 4 onward do not apply to you: nothing has changed. Team features become active only when you create a team or accept an invitation to one.

1. The Operator and how to reach us

  • Operator: Monoshiri (Makoto Kobayashi)
  • Address: 3-16-12 Roppongi KS Building 5F, Minato-ku, Tokyo 106-0032, Japan
  • Person responsible for personal data: Makoto Kobayashi
  • Contact: contact form (monoshiri.jp)
  • Representative in the EU / EEA (GDPR Article 27): none appointed at present

2. When you save to Google Drive

  • Google account information — At sign-in we obtain your email address, display name, profile picture URL and Google Drive user identifier (permissionId), for the purpose of showing the connected account and identifying you within a team.
  • Files on Google Drive — The permission the App requests is drive.file (a limited scope). The App reads and writes only files it created, or files you explicitly select. It never browses or lists your entire Google Drive.
  • Authentication tokens — In the desktop and mobile apps, the refresh token is stored only on your device and never sent to our servers. In the web version it is encrypted and kept in an httpOnly browser cookie; it is not stored on our servers, though it passes through them each time it is refreshed.
  • External access for link previews — When a document contains an external URL, the App fetches publicly available metadata from it to render a preview. In the apps this request comes from your device; in the web version our server makes it on your behalf, so that URL passes through us. We do not store what is retrieved.

The contents of files stored in Google Drive are never sent to our servers. Reading and writing happens directly between your device (or browser) and Google.

3. When you save to a folder on your device (macOS / Windows)

The App reads and writes inside the folder you pick. No request reaches our servers in this mode, and we receive nothing. On macOS, a security-scoped bookmark to that folder is stored on your device so it can be reopened next launch; it never leaves the machine.

4. When you use team collaboration

With team features, we store your documents on servers we operate. This is the most significant difference from the other two modes.

4.1 What we hold

  • Document contents — the text of documents created in a team space, the edit history used for real-time collaboration, and folder/document names and ordering. Edits are sent to the server as you type.
  • Attachments and images — the files themselves that you paste or attach to a document.
  • Account information — your email address, display name (both the one from the linked provider and any you set yourself), profile picture (a provider URL, or an image you upload), linked sign-in methods (Google: the provider’s user identifier and the email address, name and picture it returns; email and password: the password is stored only as a hash; Apple sign-in, coming soon: the identifier and email address Apple returns, which may be a private relay address), two-step verification (TOTP) secrets, stored encrypted, and recovery codes, stored as hashes, and creation / last-seen timestamps.
  • Document copies (history) — every 5 minutes we save a copy of a document’s text so that earlier versions can be restored. Up to 100 versions are kept, and each is deleted after 30 days (stored on Cloudflare R2).
  • Team and permission data — team name, members and their roles (owner / admin / member / guest), invitation records (the invited address, who invited, expiry, acceptance), allowed domains and email addresses, and per-document sharing settings.
  • Access logs — as a property of the hosting platform (Cloudflare), request timestamps, IP addresses and user agents are logged for a limited period. We use them to investigate faults and prevent abuse, and for nothing else.

4.2 Why we hold it

To provide collaboration, sharing and search; to decide who may read and write what; to answer your enquiries and investigate faults; to bill for paid plans and contact you about them; and to act on abuse or breaches of the Terms. Not for advertising. We do not analyse the contents of your documents either (for site analytics, see section 7-2).

4.3 What other members of your team can see

  • Your display name and profile picture — shown in sharing lists, as the last editor, and on your cursor while editing.
  • Your cursor position — anyone with the same document open can see, at all times, where in the document you are looking and typing.
  • Your email address — visible to team owners and admins, and in the sharing list of documents shared with you individually.

You can change your display name at any time from your profile page.

4.4 Invitations

A team administrator can create an invitation link by entering the invitee’s email address. That address is recorded on our servers at that point — entered by the administrator, not obtained by us from anywhere else. The address is not embedded in the invitation URL. Invitations expire after 7 days. We send the invitation email ourselves (from no-reply@markmono.app, delivered through Cloudflare’s email service); it contains the inviter’s name and email address, the team name and the invitation link. If it cannot be sent, the administrator can pass the link on themselves.

4.5 Relationship to Google Drive

Using team features never moves documents from your Google Drive or your local folder onto our servers. Only documents created inside a team space are held by us.

5. Paid plans and payments

Using the App on your own is free. The team plan is free for up to 3 people (the administrator included); from the 4th person it is charged per seat (JPY 480 per month or JPY 4,800 per year in Japan; USD 3 or USD 30 elsewhere), bought by the team administrator, who also takes one seat (all prices include tax). Contracts are entered into on the web (markmono.app) only; we do not use in-app purchases.

Payments are handled by Stripe.

  • Card numbers never pass through our servers. Card details are entered on Stripe’s own pages (Stripe Checkout and the customer portal). We neither receive nor store them.
  • What we send to Stripe: your team name, the billing contact’s email address, the team identifier, and the number of billable seats.
  • What we receive from Stripe: a customer ID, a subscription ID, and the subscription status (active, past due, canceled).
  • Stripe’s own handling is governed by the Stripe Privacy Policy.

6. Where data is stored, and transfers abroad

Data held for team features is stored on Cloudflare, Inc. services: documents and edit history in Durable Objects, account / team / permission metadata in D1, and attachments and images in R2.

The country or region in which it is stored is left to Cloudflare and is not specified by us. It may be stored and processed outside Japan, including in the United States and Europe. Payment data likewise goes to Stripe (United States and Japan), and Google account data to Google (United States and elsewhere).

For users in Japan, this constitutes provision of personal data to a third party in a foreign country under Article 28 of the Act on the Protection of Personal Information; the recipients are Cloudflare, Inc. (US), Stripe, Inc. (US) and Google LLC (US). Information about those countries’ data protection regimes is published by Japan’s Personal Information Protection Commission. Each recipient applies protective measures under its published data processing agreement and standard contractual clauses.

7. Sharing with third parties

  • We never sell personal data.
  • We do not provide personal data to third parties without your consent, except where required by law (including lawful requests from courts or the police).
  • The companies named in section 6 are processors engaged to provide the Service, and are supervised accordingly.

7-2. Site analytics (Google Analytics)

To see which pages are read and how often, we use Google Analytics 4 on our websites (monoshiri.jp and markmono.app) and in the App.

If you are in the European Economic Area, the United Kingdom or Switzerland, nothing is stored on your device until you agree. Consent Mode’s regional default is set to “denied” for those countries and we ask the first time you visit. Decline and everything works exactly the same. If you change your mind after declining, clearing your browser’s site data will bring the question back. Google determines the region from the IP address.

Elsewhere (including Japan) we collect the items below and store an identifier (a cookie). If you would rather we did not, disable cookies in your browser or install the Google Analytics Opt-out Add-on.

What we send:

  • The URL and title of the page viewed, the referrer, an approximate location (country or region), the kind of device and operating system, and the screen size.
  • If you have agreed, an identifier (a cookie) so that a returning visitor is counted as the same person.

What we never send:

  • The text, titles, file names or folder names of your notes. None of it reaches analytics.
  • Your email address, your name, or your account identifier.

Every advertising feature (ad_storage, ad_user_data, ad_personalization) is disabled, and IP addresses are anonymised at Google’s end. For how Google handles this data, see the Google Privacy Policy and How Google uses data when you use our partners’ sites or apps.

7-3. AI features (with your own API key)

The Mac, Windows, iPad and iPhone apps can send text to an AI service — OpenAI, Anthropic or Google (Gemini) — when you ask them to, using an API key you obtain from that service yourself. This is off until you add a key, and the web version does not offer it.

  • What is sent: only when you run an AI action, the text it needs — the selected text, or the open note — together with your instruction. It goes directly from your device to the service you chose; it does not pass through our servers and we do not receive or store it.
  • Before the first use of each service, the App asks for your permission and names the service the content will be sent to.
  • Your API key is stored only in your device’s secure storage (the Keychain on Apple devices, Credential Manager on Windows). It is never sent to us.
  • The service you choose handles the content and bills your usage under its own terms and privacy policy: OpenAI, Anthropic, Google.
  • Our analytics record only which kind of AI action was used and which service, never the text or the instruction.

8. Retention, deletion and leaving

What you can do in the App today: documents and folders you delete go to a trash state (hidden from view, but retained); you can delete your profile picture; and you can unlink a sign-in method, except the last one, which would lock you out.

You can delete your account in the App (My page, “⋯” → “Account…” → “Delete account”). Disbanding a team can also be done from the team administration screen. There is no bulk export: documents are downloaded one at a time with “Download”. For anything the App does not cover, use the contact form and we will act on it after verifying your identity.

  • Deleting your account — you are removed from the teams you belong to, and we delete your account information (email address, display name, profile picture, sign-in methods, password, two-step verification settings and recovery codes). If you are the only member of a team, that team is deleted together with its contents, after cancelling any contract. Documents you wrote in a team that has other members remain with that team, because those members are still using them. The owner of a team that has other members must first transfer ownership.
  • Disbanding a team — the owner cancels the team from the administration screen; the contract is cancelled and, 30 days later, the team’s documents, attachments and membership records are deleted.
  • Exporting — documents can be downloaded one at a time with “Download”. If you need more than that, contact us.

We respond to such requests within 30 days of receiving them. Data you delete is removed from our backups within 30 days.

Team data is retained for as long as the team exists. When the owner cancels a team (the “Cancel the team” button), the team is deleted, together with its documents and attachments, 30 days after that (30 days after the end of the paid period, if some remains); the owner can undo the cancellation before then. A contract ending on its own does not delete a team. Invitation records remain after their 7-day expiry. Access logs are retained for the period set by the hosting platform.

9. Your rights

You may request notification of the purpose of use, disclosure, correction, addition, deletion, suspension of use, or suspension of provision to third parties of your retained personal data (Articles 32–35 of Japan’s Act on the Protection of Personal Information). If you are in the EU / EEA or the UK, you have the rights of access, rectification, erasure, restriction, data portability and objection under the GDPR, and the right to lodge a complaint with a supervisory authority. Use the contact form; we act without undue delay once we have verified your identity, and charge no fee.

10. How we protect it

  • All communication is encrypted (HTTPS / WSS).
  • Documents kept in a team space are encrypted while stored. The keys are managed by us, and our servers process the content in order to provide simultaneous editing and search.
  • Only people granted permission in a team can read its documents; changing or revoking a role also invalidates sessions that are already connected.
  • An attachment can only be opened by someone who can read a document that references it, through a URL that expires after five minutes.
  • Refresh tokens are stored only on your device, or in an encrypted httpOnly cookie.
  • Servers run on Cloudflare; the country in which data is stored is determined by Cloudflare, not by us.

11. What we do not do

  • No advertising. There are no advertising tags in the App or on this site.
  • No tracking across other sites. We use Google Analytics for visitors who have agreed to it, with every advertising feature (ad_storage, ad_user_data, ad_personalization) switched off — see section 7-2.
  • The contents of your documents are never sent to analytics. We send which page was viewed, and nothing of the note itself — not its text, its title, or its file name.
  • We do not sell or otherwise provide your personal data to third parties.
  • We do not use the contents of your documents for anything other than providing the Service — and never to train machine learning or AI models.

12. Children

13. Changes

The Operator may revise this Policy as necessary. For significant changes we will give notice in the App or by email in addition to posting here. The revised Policy takes effect when it is posted on this page.

14. Contact

For inquiries regarding this Policy or the handling of personal data, use the contact form, or use the contact form.

Last updated: October 4, 2026