heyTobi Terms of Service (Beta)

These Terms govern the use of heyTobi (hereinafter "the Service") provided by the Company.

These Terms are supplementary to the myTobi Terms of Service (hereinafter "Base Terms"). Matters not covered herein are governed by the Base Terms.

heyTobi is an AI-powered automation service that directly controls Android mobile devices through voice commands.

The Service is currently in Beta. Features may be unstable or inaccurate until official release.

Due to the nature of device control, this Service requires additional consent separate from the myTobi Base Terms.

A consent process for these Terms is presented upon first activation of heyTobi. The Service cannot be used without consent.

Users may disable heyTobi at any time in Settings, which immediately stops all Service functions.

heyTobi is activated via a floating bubble or app shortcut, recognizing voice commands to perform device actions.

Voice is recorded via microphone and sent to the server for speech-to-text (STT) processing. Audio is deleted immediately after processing and is not permanently stored on the server.

heyTobi can perform the following device actions:

• Make phone calls and send text messages

• Search contacts

• Launch apps and perform in-app searches

• Web search and map search

• Launch camera

• Change device settings (Wi-Fi, Bluetooth, display, etc.)

• Set reminders

• Copy to clipboard and share

• Multi-step in-app automation (tap, type, scroll, etc.)

For complex tasks (e.g., searching for a product in an app and adding to cart), AI analyzes the screen and performs sequential actions.

During multi-step automation, screenshots of the user's screen are sent to the server for AI analysis. Screenshots are deleted immediately after analysis and are not permanently stored.

Multi-step automation is limited to 35 actions per session and a 5-minute time limit.

heyTobi may reference the user's Local Memory (preferences, physical info, schedule, etc.) to personalize commands.

Example: "Find sneakers" → automatically enhanced with user's shoe size and brand preferences.

This data is stored locally on the device and only sent to the server during command processing.

heyTobi requires the following Android permissions, requested only when the relevant function is used (Just-In-Time):

• Microphone (RECORD_AUDIO) — Voice command recording

• Phone (CALL_PHONE) — Making phone calls

• Contacts (READ_CONTACTS) — Contact search

• Camera (CAMERA) — Camera launch

• Display over other apps (SYSTEM_ALERT_WINDOW) — Floating bubble

• Accessibility Service — Reading app UI and performing automated actions

• Notifications (POST_NOTIFICATIONS) — Service status notifications

heyTobi's multi-step automation uses Android's Accessibility Service.

The Accessibility Service is a powerful permission that can read app UI structures (text, buttons, input fields, etc.) and perform actions such as tapping, typing, and scrolling.

This permission is used solely for heyTobi's automation functions and is NOT used to collect passwords, financial information, or other sensitive data.

Users can revoke Accessibility Service permission at any time in Android Settings.

Data collected and transmitted by heyTobi and its handling:

• Voice data: Deleted immediately after recognition, not stored on server

• Screenshots: Collected only during multi-step automation, deleted after analysis, not stored

• UI structure (accessibility tree): Used for action determination, not stored on server

• Contacts: Local device search only, not transmitted to server

• Installed app list: Sent to server for app routing, not permanently stored

• Memory context (preferences, schedule): Sent for command personalization, not permanently stored

heyTobi implements the following safety measures:

• Login screen detection: Automation pauses and requests user confirmation when a login screen is detected.

• Payment screen detection: Automation pauses and requests user confirmation when a payment-related screen is detected.

• Sensitive information detection: Actions are refused when sensitive keywords (passwords, SSN, card numbers) are detected.

• Action limits: Maximum 35 actions per automation session, 5-minute time limit.

• User confirmation popup: User confirmation is requested before critical actions.

⚠️ heyTobi is a Beta service with the following limitations. Users must be fully aware of these before using the Service:

1. Unintended device actions: AI judgment errors may cause unintended actions (phone calls, text messages, in-app purchases, settings changes, etc.).

2. Unintended payments: During multi-step automation, AI may tap payment buttons or complete purchase processes. While payment screen detection exists, keyword-based detection may not catch 100% of payment screens.

3. Wrong contacts: Speech recognition errors or contact matching errors may result in calls or messages sent to unintended recipients.

4. Data modification: App data may be unintentionally modified or deleted during automation.

5. Sensitive information in screenshots: Screenshots captured during multi-step automation may contain personal information, messages, or financial data. These screenshots are temporarily sent to the server for AI analysis.

6. Imperfect safety measures: Login/payment/sensitive data detection operates on keyword and pattern matching and cannot perfectly detect all situations.

The Company strongly recommends:

• Avoid using automation in payment or financial apps.

• Always review the confirmation popup before approving actions.

• Avoid using heyTobi when sensitive information is displayed on screen.

• If an unintended action occurs, immediately tap the screen or disable heyTobi to stop automation.

• For important calls or messages, always verify recipient information before execution.

① The Service is provided "AS IS" in Beta stage. The Company does not warrant its completeness, accuracy, stability, or fitness for any particular purpose.

② The Company shall not be liable for the following damages caused by AI judgment errors, speech recognition errors, or automation execution errors (except in cases of willful misconduct or gross negligence):

1. Damages from unintended phone calls, text messages, or other communications

2. Damages from unintended in-app purchases, payments, or financial transactions

3. Damages from unintended modification, deletion, or alteration of in-app data

4. Damages from unintended changes to device settings

5. Malfunctions or data loss in third-party apps during automation

① Users have a duty to verify results and stop automation immediately when necessary.

② When a user approves an action via the confirmation popup, responsibility for the outcome rests with the user.

③ The Company is not liable for damages resulting from user disregard of the recommendations in these Terms.

① The Company is not responsible for issues arising from violations of third-party app terms of service through heyTobi.

② Automation may not function correctly due to UI or policy changes in third-party apps, and the Company is not liable for resulting damages.

The Company's total liability related to this Service shall not exceed the total service fees paid by the user in the 3 months preceding the occurrence of damage. This limitation does not apply in cases of willful misconduct or gross negligence.

① The Beta period continues until separately announced by the Company.

② The Company may change, add, or remove features during the Beta period.

③ If the Beta transitions to an official release, a separate consent process for updated terms will be conducted.

Errors, issues, and suggestions discovered while using the Service may be reported to contact@mytobi.ai. User feedback will be used for service improvement.

Matters not covered by these Terms are governed by the myTobi Base Terms and the laws of the Republic of Korea.