Privacy Policy
Effective from November 15, 2026.
This English translation is provided for convenience. The Japanese version is the official text and prevails if the two differ.
Noop, LLC. (“we”, “us” or “our”) handles the personal information processed in Mockedule (the “Service”) and on the website mockedule.com in accordance with this Privacy Policy.
1. Information we collect
We collect the following information.
Registration and sign-in
- Your email address and name
- When you sign in with Google: your Google account’s identifier, name, email address and profile picture. We store the access token we receive from Google in encrypted form, and we do not store the ID token
- The versions of the Terms of Service and the Privacy Policy that you agreed to, and the date and time you agreed
- Where you came from when you signed up (one of the categories we define, such as mockedule.com, a view link page or an exported PDF)
- Information used to keep you signed in (the session identifier, the IP address you connect from and your browser type)
Use of the Service
- Information you enter (such as sticky notes, shapes, images and screen designs on boards, tasks, comments, work logs and notes on shared pages)
- Records of actions (such as who changed which board or task and when, and who added whom as a member or participant). The email addresses of the people invited are also kept in these records
- View records for the client shared page (who viewed which page and when)
- The number of times a view link has been opened and when it was last opened. We do not collect any information about the people who open it
- When you connect an AI client such as Claude Code or claude.ai: the client’s name and the date and time it was last used
- When you connect GitHub: your GitHub account name, repositories, and records of pushes and pull requests (commit hashes, messages and URLs; the sender’s account name; and pull request numbers, titles and URLs). We do not collect the names or email addresses of commit authors
- When you connect Figma: your Figma account name and email address, and the names, thumbnails, last-modified times and named versions of the files that are read. We store the access token and refresh token we receive from Figma in encrypted form
- When you connect Slack or Chatwork: the name of the destination channel or room, the name of the Slack workspace, and the user who connected it. We store Slack and Chatwork tokens in encrypted form
Payment
- When you subscribe to a paid plan: the Stripe customer and subscription identifiers, the plan, the subscription status and the billing period
- We do not receive card numbers; Stripe collects them directly
Inquiries
- What you send through “Support” in the Service, and the information sent with it (your account, the workspace you selected, the display language and your browser type)
- The name, email address and message you enter in the contact form on mockedule.com, and the information sent with it (the display language and your browser type). When you send it from “Report a problem” on a view link, the identifier of that link
- Records used to limit how often the form can be submitted (the IP address you connect from, converted into a value that cannot be reversed)
- The content of our replies
Suspension and termination of registration
- Records of when we suspend use or terminate a registration (the date and time, the category of reason, and the member of our staff involved)
- For accounts whose registration we have terminated: the email address and Google account identifier, converted into values that cannot be reversed. We do not keep the email address itself
- Records of our staff viewing user and workspace information (email address, name, affiliation, and plan and subscription status) to respond to inquiries and for similar purposes, and records of the actions they take
Website
- mockedule.com does not use cookies. To learn how many visits each page gets and where visitors come from, it uses cookieless analytics (Cloudflare Web Analytics). This analytics collects the URL of the page you open, where you came from, loading speed and similar data, and does not collect information that identifies visitors
- To pass on where you came from when you go from mockedule.com to sign up for the Service, mockedule.com keeps that category in your browser’s sessionStorage until you close the tab
- The contact page uses bot protection (Cloudflare Turnstile)
2. Purposes of use
We use the information we collect for the following purposes.
- To provide the Service and verify who has signed in
- To show boards and shared pages to project participants according to their roles
- To send emails such as invitations, mentions and sign-in links
- To send mentions and the weekly activity to Slack or Chatwork when users connect them
- To bill fees and confirm payments
- To prevent misuse and keep the Service secure (such as by limiting sign-in attempts and protecting against bots)
- To investigate issues and improve the Service
- To understand how many people mockedule.com and our announcements about the Service reach, and to improve how we announce it
- To respond to inquiries and keep a record of the correspondence
- To deal with use that violates the Terms of Service, and to prevent accounts whose registration we have terminated from registering again with the same email address or Google account
Our staff may view user and workspace information (email address, name, affiliation, plan and subscription status, and usage) to respond to inquiries, payment problems and use that violates the Terms of Service. They do not view board contents, comments or tasks, except on boards that users have made public with a view link.
The Service does not run AI on your information and does not use it to train AI. Progress summaries are written by an AI client that you connect yourself; the Service itself does not write summaries.
3. Disclosure to third parties and use of service providers
Except as required by law, we do not provide personal information to third parties without your consent. To provide the Service, we entrust the handling of information to the following companies or use their services.
| Company | Purpose | Information sent |
|---|---|---|
| Cloudflare, Inc. | Servers, database, image storage, email delivery, bot protection (Turnstile), logs and analytics for mockedule.com (Web Analytics) | All information handled in the Service (including the content of inquiries and our reply emails). Turnstile receives the result of the bot check and the IP address you connect from. Web Analytics receives the URL of the page you open on mockedule.com, where you came from and loading speed |
| Stripe, Inc. | Payments, invoices and receipts | Email address, workspace identifier, the plan you subscribe to, and card details (which you enter on the Stripe page) |
| Google LLC | Sign-in with Google | The sign-in request |
| GitHub, Inc. | GitHub integration | The integration request. From GitHub, we receive repository records |
| Figma, Inc. | Figma integration | The integration request and the identifiers of the files to read. From Figma, we receive file names, thumbnails and versions |
An AI client that you connect (such as Claude by Anthropic PBC) receives, as you instruct it, the information that you can view with your own permissions. How that information is handled is governed by the terms and privacy policy of the client’s provider.
When a user connects Slack or Chatwork to a project, mentions in comments on shared boards (the names of the author and the people mentioned, the beginning of the comment, and links to the board and comment) and the weekly activity (task titles and a link to the shared page) are sent, according to the user’s settings, to the channel or room the user chose. How that information is handled is governed by the terms and privacy policies of the providers of Slack and Chatwork.
Transfers to companies outside Japan
All of the companies above are incorporated in the United States, and information may be handled on servers outside Japan. We entrust information to these companies after confirming, through each company’s contract and privacy documentation, that it has in place a system conforming to the standards prescribed by the rules of the Personal Information Protection Commission, and we periodically check that the system remains in place. On request, we will inform you of the measures we take for this purpose.
4. Retention periods
| Information | Period |
|---|---|
| Sign-in state (session) | 30 days after last use |
| Sign-in links | 15 minutes |
| Records used to limit sign-in attempts (per IP address) | 24 hours |
| Records used to limit form submissions | 24 hours |
| Records of AI client connections | 30 days after last use |
| View records for the client shared page | 90 days |
| Records of payment notifications | 30 days |
| Account (email address, name, connections to Google, GitHub and Figma, and where you came from when you signed up) | Until you delete your account. It is deleted immediately when you do, and is removed from backups within 30 days |
| Connections to Slack and Chatwork | Until the connection is removed or the project is deleted |
| Boards, comments, work logs, records of actions, notes on shared pages, and reports created so far | For as long as the workspace exists. They are not deleted when you delete your account; the author is shown as “Deleted user” |
| The content of inquiries and our replies | 2 years from the date the inquiry is marked as resolved. They are kept for this period even if you delete your account (the link to the account is removed) |
| Records of suspensions and terminations of registration, and records of our staff viewing information and taking actions | For as long as we provide the Service |
| Values used to prevent re-registration of accounts whose registration we have terminated | For as long as we provide the Service. They are deleted if a registration was terminated in error |
| Payment records (Stripe customer and invoices) | As accounting records, for the period required by law |
5. Security
We take measures to protect personal information, such as encrypting communications, checking access permissions and encrypting tokens for external services.
6. Requests for disclosure, correction and deletion
If you request that we disclose, correct, stop using or delete the personal information we hold about you, we will verify your identity and then respond in accordance with the law. To make a request, use “Support” in the Service, the contact form on mockedule.com, or email hello@mockedule.com. The content of inquiries is kept for the period above even if you delete your account. If you want it deleted sooner, please tell us.
You can delete your account at any time from the account settings in the Service. When you do, we immediately delete the account and any workspaces that have no other members. Boards, comments and other content that you used together with other people remain, and the author is shown as “Deleted user”. Email addresses are deleted, including those left in records of actions and in invitations. An account whose use we have suspended cannot be deleted from the Service; please contact us by the methods above.
7. Cookies and information stored on your device
The Service (app.mockedule.com) uses cookies to keep you signed in. Display settings (such as appearance) are stored in your browser’s localStorage. We do not use cookies for advertising or analytics. View link pages do not use cookies.
8. Changes to this Policy
We may change this Policy. If we make important changes, we will give notice on our website and in the Service.
9. Contact
Noop, LLC.
Contact form: https://mockedule.com/en/contact
Email: hello@mockedule.com
We will provide our address and the name of our representative without delay on request.
Supplementary provisions
This Policy is effective from November 15, 2026.