Privacy Policy

In this policy, "collect" means sending data to a server the developer operates and storing it there. Oriha has no such server, so we collect none of your data.

Oriha stores your data on your device. It leaves the device only for destinations you connect or choose yourself — the calendar accounts you add in iOS Settings (iCloud, Google, Exchange, and so on), Google Calendar sync if you enable it, iOS backups, and wherever your notes go when you export them, back them up to a folder, or share them over Wi-Fi — and for the iOS features described under "Information passed through iOS" below. Nothing is sent to a server we operate.

None. There are no analytics SDKs, no tracking code, and no accounts.

We don't know who you are or how you use the app — there is simply no mechanism for it.

Calendars & Reminders: accessed to show, create, and edit your events and tasks. The contents are never sent to us.

Note that if you save an event to an account such as Google, iOS syncs it to that service — a separate path from the "Google Calendar sync" described below.

Microphone & speech recognition: used to turn what you say into event input. Conversion happens on-device.

Camera: used to read schedules and flyers into events. Recognition happens on-device. Once you save what was read as an event, it is treated like any other event — it goes to Google sync, or to the iOS calendar account you saved it to.

AI assistant: runs on Apple's on-device foundation models (Apple Intelligence). The model receives only what you type (or the text read from a photo, when you create an event from one) and minimal context such as the reference date — never the titles, locations, or notes of your calendar events. Apple's own processing is governed by Apple's policy.

Only if you enable it, the app talks directly to your Google account to read and write events.

The only server involved is Google's. We have no server — nothing passes through us or is stored by us. Auth tokens are kept in your device's Keychain.

You can disconnect any time in Settings. Google's handling of your data follows Google's own privacy policy.

We request only four permissions: sign-in identity (openid), your email address, read/write access to calendar events, and read-only access to your calendar list.

From events we read the title, location, description, start and end, all-day flag, recurrence, visibility, free/busy status, color, Google's own reminder settings, and — for syncing — the identifiers, the last-updated time, and the event's state (confirmed, tentative, or cancelled).

We do not read attendees, organizers, conferencing details (such as Meet), or attachments. They are not among the fields our requests ask for, so we can neither receive nor store them.

From your calendar list we read each calendar's name, color, time zone, access role, and default reminders. To identify the account, we also read your email address and display name.

You choose the time range (12 months back and 24 months ahead by default) and pick which calendars to sync, one by one.

When you create, edit, delete, or move an event in the app, we write it back to Google. We send only the title, location, description, start and end, recurrence, visibility, free/busy status, state, and identifiers.

Photos attached to an event, Oriha's own notes, and Oriha's own colors and reminder settings are never sent — those fields do not exist in the data we send.

Editing or deleting an event with guests never triggers notification emails from Google: we send updates with notifications turned off.

Oriha's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We use the data we receive only to provide the app's own features — showing, creating, editing, and syncing your calendar events.

No human reads this data, except where required by law, with your explicit consent, or where necessary for security purposes.

Every network request the app initiates through URLSession uses HTTPS, and we declare no App Transport Security exceptions. Auth credentials (access and refresh tokens) are kept in iOS Keychain, set to This Device Only so they're never shared with other devices or backups. Access tokens are short-lived by design.

Authorization uses the system browser with PKCE; the app holds no client secret. Responses from Google's APIs are fetched with an ephemeral session, so they are never cached to disk. Logs never contain personally identifying information.

Calendar events and the calendar list we read from Google are kept on your device — as a local copy for syncing — for as long as Google Calendar sync stays enabled. There is no server we operate, so nothing is retained server-side. Attached photos are not automatically deleted over time unless you set an auto-delete period in Settings.

See "Disconnecting and deleting data" below for what happens when you disconnect. Deleting the app from iOS erases everything stored on your device.

You can disconnect any time in Settings. Doing so removes your Google account details, calendar list, pending changes, and the imported Google events from your device. Nothing is touched in your Google calendars. If the same Google account is also connected as a calendar account in your iPhone's Settings, those events may reappear through iOS.

Some things remain on your device after disconnecting: Oriha notes (a note attached to an event keeps a copy of that event's title), photos you attached to events, events saved as templates, and your sync range settings. They remain even when they came from a Google event.

When you disconnect, the app asks Google to revoke its access. If that request fails, the token is held safely on your device and retried automatically later. To be certain it is revoked, also remove Oriha from "Third-party apps & services" in your Google account.

Deleting the app alone does not revoke Google's access — use the same step above. To erase the data held on your device, delete the app from iOS.

Event titles, locations, descriptions, times, and reminder settings are kept on your device as a local copy for syncing, along with attached images and theme settings.

Nothing is sent to a server we operate. If you have iOS backups enabled, however, this data is included in your backups through Apple's backup mechanism. Auth tokens are stored in the Keychain marked "this device only," so they are never restored to another device from a backup.

Information passed through iOS: notifications include event titles, and a combined notification lists that day's events with their times. If you place a widget, it receives the titles of every event in the period shown (up to six weeks), holiday names, and sticker text. Tapping an event's location opens Maps with that location string, and tapping a link inside an event's notes takes you to that destination.

When the app changes, this page is updated before the change ships. That includes any significant change to how data is handled.

support@oriha.jp — the developer answers personally.