Teco G.K. ("we", "us") sets out below how we handle users' information in the iPhone app "Hachibu" (the "App"). We operate the App and handle users' information. Sales on the App Store (including Hachibu Pro subscriptions) are made by the seller listed in our legal notice.
This is a translation. If it differs from the Japanese original, the Japanese original prevails.
The App does not send your events, tasks or location to our servers. Calculating the time you have left, working out departure times and scheduling notifications all happen on your iPhone. The only information our servers receive is described in section 3: counts from the onboarding screens, problem reports and feedback that you send yourself, referral code records if you use referrals, and, if you create a booking link, the time ranges on the link and the booking requests sent to you, and, if you connect Claude or ChatGPT, the connection records and the answers your iPhone calculates when asked (removed as soon as they are passed on).
1. Information the App handles on your iPhone
The App handles the following information only on your iPhone and does not send it to our servers. Deleting the App removes it from your iPhone.
| Information | Purpose |
|---|---|
| Calendar events (title, time, location, notes, attendee email addresses, etc.) | Calculating your open time and counting travel and prep. Attendee email addresses are used only as the recipients of a message you send when you are running late (Hachibu Pro). Read from the iOS calendar (EventKit) |
| Events and travel blocks the App creates | Written to the iOS calendar when you choose to create them |
| Current location | Used as the start point for your first event of the day. Not kept; discarded when you close the App |
| Places saved as Home or Office, and places remembered for event titles | Deciding start points and destinations |
| Tasks (if you connect Todoist, Reminders, Microsoft To Do or Google Tasks) | Calculating the day's task load and reflecting new tasks, completions and new due dates. Connection keys (such as API tokens) are kept in the iOS Keychain. Reminders are read from iOS Reminders (EventKit) without any network connection |
| Record of completed tasks | Shown under "Done". The last 60 days |
| Measurement log | Records of travel-time lookups and the shape of events (without titles or place names), kept in a file on your iPhone. You can view, export, delete or stop it in Settings → Measurement |
| Settings | Working hours, notification times, etc. |
| Times you picked for a booking link, and booking requests you receive (the other person's name, contact and message) | Calculating the times on the link, deciding whether to accept or decline, and replying. Requests are also removed from your iPhone 30 days after you accept or decline them |
| Hachibu Pro subscription status | Deciding whether Pro features are available. Purchases and payments are handled by Apple; the App only reads the subscription information signed by Apple on your iPhone. It is not sent to our servers |
2. Information the App sends from your iPhone (external transmission)
The App sends information to the following companies to provide its features.
| Recipient | Information sent | Purpose | When |
|---|---|---|---|
| Apple Inc. (Maps) | Coordinates of the start point and destination, travel mode, departure time | Getting travel times | When an event has travel to count |
| Apple Inc. (Maps) | The text in an event's location field, or the words used to search for a place (initially the event title) | Searching for a place's coordinates | When an event has a location, and when you open the "Set place" screen |
| Apple Inc. (App Attest) | Proof that the App is genuine | Confirming that the transmissions in section 3 come from the App | Before the transmissions in section 3 |
| Apple Inc. (DeviceCheck) | Temporary values for reading and writing two per-device flags (passed from our servers to Apple) | Preventing the same device from using referral codes repeatedly | When you create or enter a referral code |
| Apple Inc. (push notifications, APNs) | A notice that a booking request has arrived (without the other person's name or time), and a signal to recalculate the link's times | Letting you know a booking request has arrived | Only if you have created a booking link (passed from our servers to Apple) |
| Apple Inc. (push notifications, APNs) | A signal to answer a question (the date and length asked about; no event names or places) | To answer questions from Claude or ChatGPT with a calculation on your iPhone | Only if you connect Claude or ChatGPT (sent from our servers to Apple) |
| Google LLC (Firebase) | The information we receive under section 3, and verification values derived from the proof above | As described in section 3 | As described in section 3 |
| Anthropic PBC (Claude), OpenAI, L.L.C. (ChatGPT) | The time left, open time ranges and leave-at times for the day you asked about, with a sentence explaining them | So you can ask Claude or ChatGPT how much time you have | Only when you have connected them and ask a question (sent from our servers) |
| GitHub, Inc. | The reports in section 3 (text and the attached table) | So that our developers can read reports (kept in a private place) | When a report reaches our servers (sent from our servers) |
| Doist Inc. (Todoist) | Your Todoist API token, and creating, completing or rescheduling tasks | Reading tasks, and reflecting new tasks, completions and new due dates | Only if you connect Todoist |
| Microsoft Corporation (Microsoft To Do) | The connection key from signing in with Microsoft, and creating, completing or rescheduling tasks | Reading tasks, and reflecting new tasks, completions and new due dates | Only if you connect Microsoft To Do |
| Google LLC (Google Tasks) | The connection key from signing in with Google, and creating, completing or rescheduling tasks | Reading tasks, and reflecting new tasks, completions and new due dates | Only if you connect Google Tasks |
Transmissions to Apple Inc. go through iOS's map features (MapKit) and are handled under Apple's privacy policy. We do not receive this information.
If you connect Google Tasks, the App's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Tasks received are used only on your iPhone; they are not sent to our servers or to any third party, and are not used for advertising or for training AI models.
Data is exchanged directly between your iPhone and Google over an encrypted connection (HTTPS). The connection key is stored in the iOS Keychain with a setting that keeps it from moving to other devices. Tasks received are kept only on your iPhone and replaced with the latest content at each sync. When you disconnect Google Tasks in the App, the tasks kept on your iPhone and the connection key are deleted. Deleting the App removes the tasks, but iOS may keep the connection key in the Keychain, so please disconnect before deleting the App. You can revoke the App's access at any time under "Third-party apps & services" in your Google Account.
Please see each company's website for its privacy policy.
3. Information our servers receive
3.1 Onboarding counts
On the first setup screens (onboarding), the App sends counts of which screens were shown and which actions were taken to our servers (Google LLC's Firebase, Tokyo region).
- The App only adds one to a count for each combination of date, screen and action (for example, one "Allow" on the "Location" screen on 2026-10-05)
- We do not send information that identifies you or your device (device ID, advertising ID, account, etc.). We do not send times either
- The number of events shown on the first screen is not sent as is; it is rounded to a range such as "10–29". Event titles and places are not sent
- The purpose is to learn on which onboarding screens people stop using the App, and to improve them
- Nothing is sent if you turn off Settings → Measurement
Because these counts are stored in a form that cannot identify individuals, we cannot retrieve or delete a particular user's counts.
3.2 Problem reports and feedback
Only when you tap "Send" in Settings → "Report a problem" or "Send feedback" do we send the following to our servers (Google LLC's Firebase, Tokyo region).
- The text you wrote (up to 1,000 characters) and the type and category of the report
- An automatically attached table: the App version, iOS version, screen and text size, the App's settings (working hours, travel mode, notifications, etc.), and that day's number of events and total time. It does not include event titles, places or task names (except what you write yourself in the text). You can check its contents on screen before sending
- We do not send information that identifies you or your device. We do not send screenshots either
Reports are moved to a private place that only our developers can read (a GitHub, Inc. service) and deleted from our servers when moved. We use reports only to investigate problems and improve the App. We do not reply individually. For enquiries that need a reply, please contact us at the address in section 8.
Because reports contain no information that identifies you, you cannot retrieve or delete a report you sent from within the App. To request deletion, send the date, time and content of the report to the address in section 8.
3.3 Booking links
Only when you create a "booking link" do we place the following on our servers (Google LLC's Firebase, Tokyo region) and show it to the person who opens the link (the "other person"). The purpose is to let the other person pick a time.
- The time ranges that are still open after travel and prep within the times you picked (start and end times only). We do not place event titles, places, attendees or notes. Times that later fill up disappear from the other person's page. Because open time ranges are shown, the other person can tell that the times outside them are taken
- The meeting length and how you will meet (online, they come to you, you go to them). We do not place the location for "they come to you" or "you go to them"
- The title, display name and company name you enter to show the other person (all optional, up to 40 characters), and the page color you choose
- The logo image you choose (optional, Hachibu Pro). Your iPhone redraws it at a small size before sending, so information in the photo such as where it was taken is not sent. It is deleted together with the link
- Your iPhone's time zone (for example, Asia/Tokyo), to show times in the other person's region as well
- Your iPhone's push notification value (Apple's APNs), to let you know when a booking request arrives. It is kept only while you have an active link and is not used for anything else
- A value used to confirm it is you (a non-reversible form of a string kept in your iPhone's Keychain), and a daily count of requests to prevent too many being sent
When the other person picks a time and sends it, we receive their name, contact (email address or phone number) and message, together with their time zone and display language. These are deleted from our servers as soon as they are delivered to your iPhone. They are not included in the push notification text. We do not store the other person's IP address. The other person's information is used by you to reply about the schedule, and we do not use it for any other purpose.
Records of links and requests (times, and states such as accepted or declined) are deleted within 10 days after the link's end date. When you revoke a link, the push notification value and any of the other person's information not yet delivered are deleted immediately. Even if Settings → Measurement is off, we handle these for the links you created yourself.
Booking page (Hachibu Pro): a booking link with no end date. It handles the same information as the links above, with these differences:
- For the period you choose (1 to 4 weeks), starting today, we store all of the time that is still open after travel and prep (not only the slots you picked). The other person can therefore tell that the time outside it in that period is taken
- We store a value for the page's short URL (10 random characters that don't identify you)
- For each way of meeting you allow (online, they come to you, you go to them), we store the open time. Because the time shown differs by way of meeting, the other person may be able to tell roughly how long you travel. For "you go to them", we store the time left after taking off travel before and after it up to the one-way limit you set, and the area you can visit that you entered (optional, up to 40 characters)
- When the other person chooses "you go to them", in addition to their name, contact details and message, we receive the place to visit that they wrote (an address or building name). Like the name and contact details, it is deleted from our servers as soon as it is delivered to your iPhone. Our servers do not look it up on a map (your iPhone looks up the place in Apple Maps and recalculates the travel time)
- We store a flag for whether the page is paused. We don't store why (you paused it, or Hachibu Pro ended), and we don't send your subscription status to our servers
- A page that hasn't been updated from your iPhone for 3 days stops taking requests. A page that hasn't been updated for 90 days is deleted entirely (Firestore's automatic deletion can take about one more day). When you revoke it, it stops taking requests at once and the URL value is deleted
3.4 Connecting Claude and ChatGPT
Only when a Hachibu Pro user connects Claude or ChatGPT under "Claude and ChatGPT", we handle the following information on our servers (Firebase by Google LLC, Tokyo region). The purpose is to answer questions such as "How much time do I have left today?" asked in Claude or ChatGPT, with a calculation made on your iPhone. We do not create an account.
- Connection records: the name of the connected service (Claude or ChatGPT), the dates you connected and were last asked, a value to verify the iPhone that answers (an irreversible form of a string kept in your iPhone's keychain), your iPhone's push notification value (Apple APNs) and display language. Keys given to Claude or ChatGPT (such as access tokens) are kept only in an irreversible form
- Questions and answers: when a question arrives from Claude or ChatGPT, our servers wake your iPhone with a notification, receive the answer your iPhone calculates from your events (the time left, open time ranges and leave-at times for that day, with a sentence explaining them) and pass it to Claude or ChatGPT. We keep an answer only for the few seconds until it is passed on, then delete it
- Event names, places, attendees and task names are never included in answers. We do not handle your name, email address or Apple ID
Answers passed to Claude or ChatGPT are handled under the privacy policies of those companies (Anthropic PBC and OpenAI, L.L.C.). Your iPhone may not be able to answer in Low Power Mode or after the app has been closed.
Connection records are deleted as soon as you disconnect on your iPhone (when you disconnect the last one, the push notification value is deleted too). Connections not asked anything for 90 days are also deleted. Connections do not carry over when you change iPhones or reinstall the app. We handle this information for connections you made yourself even if Settings → Measurement is off.
3.5 Referral codes
Only when you create a referral code with "Tell a friend" or enter one with "Enter a referral code" do we handle the following on our servers (Google LLC's Firebase, Tokyo region). The purpose is to check whether a referral has been completed (whether the person who entered the code opened the App on 3 of 7 days) and to give free Hachibu Pro periods to both the referrer and the person referred.
- The referral code, and a value used to confirm it is you (a non-reversible form of a string kept in your iPhone's Keychain)
- The dates the code was created and entered and the dates the App was opened (dates only; no times), and a record of the free periods given
- Flags for whether a device has "created" or "entered" a referral code. These are kept in Apple's DeviceCheck, and no information that identifies the device reaches us
- The App Store offer code given to the person referred
We do not handle users' names, email addresses, device IDs, events, places or tasks. We handle no information at all about people who do not use referrals.
Records of entered codes are deleted when the referral is completed or after 7 days. Records of created codes are deleted 400 days after they were last used. Even if Settings → Measurement is off, we handle these to complete the codes you entered yourself.
4. What we do not use
- Advertising, the advertising identifier (IDFA), tracking
- Usage analytics services (analytics SDKs)
- Sending events, tasks or location to our servers (except what you write yourself in a report)
5. Permissions
The App asks for the following permissions on the screen where each is needed, after explaining why. You can change each of them at any time in the iOS Settings app.
| Permission | Use |
|---|---|
| Calendar (full access) | Reading your events to calculate your open time. Writing when you create events |
| Reminders (full access) | Only if you connect Reminders. Calculating your task load, and writing new tasks, completions and new due dates |
| Location (while using the App) | Using your current location as the start point for your first event of the day |
| Notifications | Sending departure alerts and the night-before and morning-of summaries. These are scheduled on your iPhone and not sent from our servers. Only if you have created a booking link do we send, from our servers (via Apple's push notifications), a notice that a booking request has arrived |
6. Provision to third parties
We do not sell or provide to third parties the information we receive under section 3 (except the transmission to GitHub, Inc. for reading reports described in section 2, showing a booking link's time ranges, title, display name and company name, and its logo, to the people who open it as you choose, and delivering the other person's request to you, and passing the answers you ask for to Claude or ChatGPT that you connected), except as required by law.
7. Changes to this policy
We may revise this policy as the App's features or laws change. A revised policy takes effect when it is posted on this page. Changes that increase the information our servers receive will be announced on this page before the App update.
8. Contact
For enquiries about how the App handles information, please contact:
Email: info@tekot.jp
Contact form: https://tekot.jp/contact/
Established: September 28, 2026 (Japanese original). Last revised: October 20, 2026 (choosing how to meet on booking pages; how Google Tasks data is protected and deleted)
Operator
- Company
- Teco G.K.
- Address
- RM Bld. 701, 5-31-1 Minami 2-jo Nishi, Chuo-ku, Sapporo, Hokkaido 060-0062, Japan