Privacy Policy

1. Operator

This Policy applies to “Todia,” an iPhone and Android application (the “App”), and this website, provided by MakeSomethingNew, Inc., represented by Eiichi Sugiyama, Representative Director.

2. Information handled by the App

The App handles the following information entered by you solely to provide its features:

• Calendar names, colors, and display settings
• Event titles, descriptions, start and end times, and reminder settings
• To-do list names, colors, and symbols
• Task titles, notes, due dates, times, priorities, completion status, and reminder settings
• Messages entered in Chat, generated responses, and action proposals
• A Groq API key optionally configured by you
• Calendar names, events, additional instructions, and an optional reference image selected by you for announcement-image generation
• A Gemini API key optionally configured by you and generated images
• A timetable photo you select or capture for timetable import, and the subjects, weekdays, and class times recognized from it
• When Gmail is connected, your Google Account email address, OAuth authorization information, and email drafts you create
• Your Firebase anonymous identifier, linked sign-in methods, and verified email address when Google is linked
• App language, time zone, and the versions of the Terms and Privacy Policy you accepted
• Cloud entitlements, usage, and account creation, update, and deletion status
• Shared to-do memberships, invitations, change history, and sync status

The App creates an anonymous Firebase account on first use. You may link it to a supported Google Account or another supported provider while retaining the same Firebase UID. Through the App, we do not collect your telephone number, precise location, contacts, or advertising identifier. A reference image you optionally select for image generation is sent directly to Google’s Gemini API without passing through our servers.

Firebase Analytics may automatically collect App usage such as launches and screen views, an app-instance identifier, device, operating system and App information, approximate region inferred from IP address, and diagnostic information. Events, tasks, Chat content, and your Groq and Gemini API keys are not sent to Analytics.

3. Storage and transmission

Ordinary events, tasks, calendars, lists, and Chat history are stored on your device using SwiftData on iPhone and Room on Android. When your data-sync entitlement is enabled after Google linking, copies of events, tasks, calendars, lists, Chat text, generated responses, and action proposals, including existing on-device data, are also stored in MySQL on our backend for cross-device sync. Calendar-share snapshots and shared to-do content are also stored in MySQL when you use those features. New calendar-share links display the calendar name, event count, and date range to people who know the link, and display the calendar name in social-media link preview images. Event titles and notes are not displayed on the web page or link preview image. The App uses Firebase Analytics but does not use an advertising SDK or cross-app third-party tracking.

Authentication is processed by Google LLC’s Firebase Authentication. Our backend stores the Firebase UID, authentication type, display name, verified email address, language, time zone, consent versions, entitlements, usage, and the AI history described above in MySQL. A Firebase ID token is used only to authenticate a request and is not stored in our database. Invite-link tokens and email lookup values are stored as digests.

When you use Chat, your message, app language and time zone, and the limited event or task information needed to answer your question or perform your requested action are sent through our backend to the API of Groq Technologies, Inc. The App does not routinely send all events or tasks. Information sent to Groq is processed under Groq’s terms and privacy policy.

When you use task AI, the task title, notes, due date, and meeting time candidates calculated on your device are sent to Groq. Availability is calculated on-device; event titles and your complete event history are not sent. To create a Gmail draft, the App requests only Gmail compose access through Google Sign-In and sends the recipient, subject, and message you reviewed to the Gmail API provided by Google LLC. Email is never sent automatically. OAuth authorization information is managed in the device Keychain by Google’s SDK and is not received or stored by our servers.

When you generate an announcement image, the calendar name, titles, notes and times of selected events, your additional instructions, and an optional reference image you select are sent to Google LLC’s Gemini API using your own API key. The request instructs the API not to store the interaction, but information sent to Google is processed under Google’s terms and privacy policy. Your Gemini API key is stored in the device Keychain, and generated images and generation history are stored on-device. The reference image is not retained in the App’s history.

When you use timetable import, after your explicit consent the timetable photo, App language, and time zone are sent through our backend to Google LLC’s Gemini API. We do not retain the original photo, recognized subjects, weekdays, class times, or analysis result in our database, AI history, or an on-device file. Only events you review and register are stored on-device as ordinary events. Information sent to Google is processed under Google’s terms and privacy policy.

Backups you enable on your device or Apple Account, including iCloud Backup, are governed by Apple’s settings and privacy policy.

You may save events, to-dos, and Chat history as an unencrypted JSON backup in a location you choose through the Files app. The file is not sent to our servers. It excludes API keys, sign-in information, share links, sync information, and generated images. You are responsible for protecting, sharing, and deleting the backup file.

4. Notifications

When you set a reminder, the App uses the iOS notification system to schedule a local notification for an event or task. Notifications require your permission in iOS. They are processed on your device and do not pass through a server operated by us.

You can change notification permission at any time in iPhone Settings. How notification content appears on the Lock Screen and elsewhere is also controlled by your iOS notification settings.

5. Purpose of use

Information on your device is used only to provide the following features on that device:

• Displaying, creating, editing, and deleting events, tasks, calendars, and to-do lists
• Creating and importing a shareable copy of a calendar you select
• Inviting members to, joining, and continuously syncing shared to-do lists
• Showing dated tasks on the calendar and moving them between dates
• Providing local notifications for events and tasks you configure
• Returning completed tasks in the “Daily” list on the next day
• Answering Chat questions, looking up events and tasks, proposing additions, and completing tasks
• Proposing task steps, calculating meeting candidates, and creating a reviewed Gmail draft
• Generating, storing on-device, and sharing social-media announcement images containing calendar events
• Analyzing usage, identifying issues, and improving the App

6. Disclosure to third parties

We do not sell App information. When you share a calendar, the shared copy is processed by our backend and provided at your direction to people who receive the link. When you use a shared to-do, the shared list and tasks are provided to invited or participating members. When you use Chat or task AI, the limited information described above is provided to Groq. When you generate an announcement image, the generation data and optional reference image are provided to Google’s Gemini API. Information processed through Firebase and Gemini is handled under Google’s privacy policy.

7. Managing and deleting information

After a cloud-account deletion request, your Firebase authentication record, backend user record, synced event, to-do, and Chat copies, AI history, calendar-share snapshots you published, and shared to-dos you own are deleted asynchronously. A shared-to-do owner can delete a list for all members, and an editor can leave it. The request cannot be canceled, and temporary failures remain pending and are retried. Data on offline devices, images saved to Photos, and calendar copies already imported by recipients may remain until the device reconnects or you delete them.

8. This website

The event-feed request form on this website collects the requested feed name, a description, an optional reference URL, and an optional reply email address. We store this information in MySQL on our backend to review the request, decide whether it can be supported, and contact you when necessary. Unresolved requests are retained for up to one year after submission. The request text and email address of accepted or rejected requests are deleted 180 days after resolution. Only authorized operations staff may access this information.

This website uses Google Analytics 4 to understand usage and improve the site. Google Analytics may use cookies and collect pages viewed, access times, browser and device information, referrers, and approximate location inferred from IP addresses. Share and invitation pages are excluded from analytics. Google LLC processes the collected information under its Privacy Policy. We do not send events, tasks, shared content, feed-request entries, or similar user content to Google Analytics.

The site stores only your Japanese or English language choice in browser local storage. Feed-request entries are not stored in browser local storage.

The hosting provider used when this site is published may process standard access logs for security and operational purposes, in which case that provider’s policy applies. Information handled by external websites linked from this site is governed by each website’s policy.

9. Changes to this Policy

We may revise this Policy to reflect changes to the App, our information practices, or applicable law. We will announce material changes on this website or in the App. A revised Policy applies when it is posted on this page.