プライバシーポリシー

English version

Google user data that Autask accesses

Only if you choose to link your Google account, Autask accesses the following, and nothing else:

• Calendar event start time, end time, all-day flag, and cancelled status — used solely to determine when you are already busy.
• Your calendar list (identifier, name, and whether it is your primary calendar) — shown to you so you can choose which calendars count as busy.
• OAuth tokens (access and refresh tokens) — used to maintain the connection to Google Calendar.

Autask does not read event titles, descriptions, attendees, locations, or attachments. They are never read into application logic, never displayed, never stored, and never transmitted. Autask does not collect or store your name or email address.

How Autask uses Google user data

Event times are used to compute free slots inside your working hours. All computation happens on your device. Autask then writes your tasks into a single dedicated calendar named "オータスク" that it creates. It does not request permission to modify or delete the events you created yourself, and therefore cannot.

How Autask shares, transfers, or discloses Google user data

We do not share, transfer, or disclose Google user data to any third party, for any purpose.

• We operate no server. Google user data travels only between your device and Google. There is no path by which it could reach us.
• We do not sell it and do not use it for advertising. The app contains no analytics SDK and no advertising SDK.
• We do not use Google user data to develop, improve, or train generalized or non-generalized AI and/or ML models.
• Autask's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How Autask protects Google user data

• OAuth tokens are stored in the iOS Keychain, encrypted by the device and inaccessible to other applications.
• All network communication uses HTTPS (TLS). No unencrypted transport is used.
• On-device data is protected by the iOS application sandbox and iOS Data Protection, encrypted at rest while the device is locked and unreadable by other apps.
• Authentication uses OAuth 2.0 with PKCE and no client secret, so there is no shared secret on the device that could be extracted and abused.
• We hold no copy of your data. Because we run no server, there is no central store that could be breached.
• Unlinking revokes the tokens with Google and deletes them from the device.

Data retention and deletion

Events read from Google Calendar are used to compute free time and are then discarded; they are never stored. OAuth tokens remain on your device until you unlink your account or delete the app. Deleting the app removes all local data — tasks, settings, run logs, and credentials. Events already written to your Google Calendar remain and can be removed in Google Calendar.

Children

Autask handles work scheduling and is not directed to children under 13.

Contact

takec02.oniwaban@gmail.com