Monoshiki
privacy policy.

Last Updated: August 17, 2026

This Privacy Policy explains how Monoshiki handles your information. Monoshiki is a privacy-focused iPhone personal assistant for daily planning, workout logging, and viewing Apple Health metrics in one place. The app is developed by MGD Infrastructure, based in Philipsburg, PA, USA.

1. The short version

Monoshiki has no backend. MGD Infrastructure operates no servers that store your data, no user accounts, and no analytics tied to your identity. We never receive your tasks, workouts, calendar events, or health readings.

Your data stays on your iPhone unless you switch on one of the optional features below. Each of them is off until you turn it on, each one names what it sends and where, and each one can be turned off again:

None of these is required. Monoshiki is fully functional with all of them off.

2. Information we collect

MGD Infrastructure collects nothing. We do not operate servers that store your personal data, we do not maintain user profiles or accounts, and we do not collect analytics tied to your identity.

Data you enter or view in the app — tasks, habits, workouts, exercise library, preferences, and Apple Health metrics — is stored on your device. It leaves the device only through the optional integrations described in Sections 3 through 6, each of which you enable yourself.

If you use Sign in with Apple to identify yourself in the app, the name and email address Apple returns are stored locally in your app settings on the device. They are not transmitted to MGD Infrastructure. If you have enabled iCloud backup for Preferences, they are included in that backup to your own iCloud account.

3. Apple Health

Monoshiki can read from Apple Health to fill your metrics screens and daily summaries — steps, energy, exercise time, heart rate, sleep, body measurements, and nutrition, depending on what you authorize.

• Access is read-only. Monoshiki does not write to Apple Health. (iOS requires the app to declare a write permission string because of a framework dependency; the app does not use it.)
• Reading requires your explicit consent through the Apple Health permission sheet, where you choose exactly which data types to allow. You can change or revoke this at any time in iOS Settings → Health → Data Access & Devices. Monoshiki also has its own in-app switches per category in Settings → Health access.
• Readings are held in memory while the app is open and are not written to a Monoshiki server, because there isn’t one.
• Health data is never used for advertising, marketing, or data mining, and is never sold or shared with data brokers.

Health data can leave your device in three ways, all of which you control:

1. A workout you save. The heart rate and calories Apple Health measured during that workout are stored alongside the saved workout. If you have switched on iCloud backup for Fitness, those readings are included in that backup to your own private iCloud database.
2. The AI assistant. If you enable the assistant and switch on a health-related scope (activity, heart, body, sleep, or nutrition), summaries of that data are sent to Anthropic when you ask a question that requires them. See Section 5.
3. An export you create. If you include health categories in an export and send it to Google Drive or Google Sheets, that file contains the health metrics you selected. See Section 6.

Outside of those three, Apple Health data does not leave your iPhone.

4. iCloud backup

iCloud backup is off by default and is chosen during first-run setup or later in Settings → Sync & data. Backup is per category:

• Preferences — theme, units, and app settings
• Planner — your tasks, habits, and their completions
• Fitness — workout templates, exercise library, and saved sessions, including the heart rate and calories Apple Health measured during those workouts
• Health layout — which metrics appear on your dashboard, never the health data itself

Some data does not fall under one of the categories above — for example your logged food entries — and is included in the backup whenever backup is switched on at all.

What you turn on is mirrored to your own private iCloud database in your Apple account. It is visible to you on your devices, and not to MGD Infrastructure — we have no access to it. This uses the iCloud account signed in on your device; it is not related to Sign in with Apple.

Turning a category off stops future syncing and leaves your data on the device. Delete all data (Section 8) removes the iCloud copy as well.

Apple’s handling of iCloud data is governed by the Apple Privacy Policy.

5. AI assistant (Anthropic Claude)

The AI assistant is optional and off until you enable it, and it requires your own Anthropic API key, which you enter in the app. The key is stored in your device’s secure keychain and is never transmitted to MGD Infrastructure. Monoshiki ships no API key and has no server between you and Anthropic — requests go directly from your device to the Anthropic API.

• You choose what the assistant can see. Data reaches Anthropic only through scopes you switch on (for example activity, heart rate, sleep, nutrition, fitness, or planner), and only when you send a message that requires it.
• Every lookup is shown to you in the conversation, so you can see exactly what was shared.
• Actions that change your data — adding, completing, or rescheduling a task, or importing a workout template — pause and ask you to approve them first.
• Conversations are not saved. They exist only while the app is open.
• Your messages and any scoped data you send are processed by Anthropic under the Anthropic Privacy Policy. Monoshiki does not use these interactions for advertising, and does not sell this data.

6. Google services

Connecting a Google account is optional. Monoshiki uses Google OAuth; your Google credentials are entered with Google and are never visible to or stored by MGD Infrastructure. Access tokens are stored in your device’s secure keychain. You can disconnect at any time in the app, or revoke access from your Google account permissions page.

• Google Drive — Monoshiki requests the drive.file scope, which grants access only to files this app itself creates. It cannot see the rest of your Drive. Used to deliver exports you generate.
• Google Sheets — used to write exported data into a spreadsheet you generate from the app.
• Google Calendar — requested separately, only when you switch the calendar feature on, and read-only (calendar.readonly). Monoshiki can display your events; it cannot create, edit, or delete them. Events are shown on-device and are not uploaded to MGD Infrastructure.

Exports are always user-initiated: a file is generated on demand from the categories and date range you pick, and goes only where you send it — the iOS share sheet, Files/iCloud Drive, or your Google Drive. If you include health categories, that file contains those health metrics.

Google’s handling of data is governed by the Google Privacy Policy.

7. Device calendar, notifications, and advertising

Device calendar (Apple Calendar). With your permission, Monoshiki can read events from the calendars you choose on your device, to show them beside your tasks. This is read-only — Monoshiki does not add or edit events — and the events are displayed on-device and never uploaded.

Notifications. Task reminders are scheduled on your device as local notifications. Nothing is sent to a push notification server.

Advertising. Monoshiki includes the Google AdMob SDK so that a limited advertising slot can be supported in the app. Where ads are served:

• Requests are non-personalized only. Monoshiki does not request App Tracking Transparency permission, does not track you across apps or websites, and does not build an advertising profile of you.
• No Apple Health data, planner data, workout data, or calendar data is ever used in an ad request or shared with any advertising network. Ad code in Monoshiki is structurally isolated from your health and personal data.
• To serve an ad, Google AdMob may receive device and network information such as IP address, device type, and OS version, under the Google Privacy Policy and Google’s advertising terms. Where your jurisdiction requires it, you will be shown a consent form before any ad is requested.
• Ads are never shown in demo mode, and are not present on the web version of the app.

8. Data retention and deletion

Because MGD Infrastructure stores none of your data, there is nothing on our side to retain or delete.

• On your device: your data stays until you delete it. Settings → Privacy & data → Delete all data erases everything Monoshiki holds — planner, fitness, logged food entries, preferences, connected accounts and their stored tokens, scheduled reminders, and your Anthropic API key — and removes the iCloud copy for any categories you had backed up.
• Deleting the app removes its local data from the device. If you had iCloud backup on, use Delete all databefore uninstalling to remove the iCloud copy as well.
• In iCloud: data remains in your own iCloud database until you turn the category off and delete it, or use Delete all data.
• With third parties: files you exported to Google Drive or Sheets remain in your Google account until you delete them. Data you sent to Anthropic through the assistant is retained under Anthropic’s own policy; consult the Anthropic Privacy Policy and your Anthropic account settings.
• Revoking access: Apple Health in iOS Settings → Health; calendar and notifications in iOS Settings; Google in the app or at your Google account permissions page; the assistant by disabling it or removing your API key in the app.
• Your rights: if you are in a jurisdiction granting rights of access, correction, portability, or erasure (such as the EU/UK GDPR or the CCPA/CPRA), those rights apply to data a company holds about you — and MGD Infrastructure holds none. You can export all of your own data from the app at any time in open formats, and delete all of it from the app. Requests or questions can be sent to the address in Section 11.

9. Data security

Your data is protected by iOS platform security: device encryption, your passcode and Face ID/Touch ID, Apple’s HealthKit protections, and the iOS keychain, where Monoshiki stores your Anthropic API key and any Google or Apple sign-in tokens. Monoshiki does not log your health data, the contents of assistant requests, or your API key.

Where your data reaches a third party you have connected — Apple iCloud, Google, or Anthropic — it is protected by that provider’s own security measures. We select integrations from providers that commit to protections at least equivalent to those described in this policy, and we do not share your data with any third party beyond what is necessary to operate the feature you enabled.

We recommend protecting your device with a strong passcode and keeping iOS up to date. No system can be completely secure, but Monoshiki is designed to minimize risk by collecting nothing and keeping your data on your device by default.

10. Children’s privacy

Monoshiki is not directed to children under 13, and we do not knowingly collect personal information from children. Because the app collects no personal data on our servers, we maintain no accounts or profiles for children. If you believe a child has used Monoshiki in a way that raises a privacy concern, please contact us using the details below.

11. Changes to this policy

We may update this Privacy Policy as the app evolves or as legal requirements change. When we do, we will update the Last Updated date at the top of this page, and for material changes we will provide an in-app notice. Your continued use of Monoshiki after a revised policy is posted means you accept the updated terms.

12. Contact us

Questions about this policy, how Monoshiki handles your data, or any privacy-related request:

MGD Infrastructure
Philipsburg, PA, USA
Email: contact@mgdinfrastructure.com

We take privacy seriously and will answer your questions clearly and promptly.