Starring Life Privacy Policy

Scheduled effective date: 2026-10-10

Document version: 2026-10-10-v2

Last updated: 2026-10-01 · (주)딥하이

DeepHigh Co., Ltd. (the Company) establishes this policy under the Personal Information Protection Act to protect the personal information of Starring Life users and handle inquiries and rights requests. Records are saved on the device first. Sign-in, AI and backup are separate choices. This policy discloses personal information processing and does not replace any required individual consent or device permission.

1. Scope and operator

• This policy applies to the Starring Life Android app offered in the Republic of Korea and its authentication, AI, backup, payment verification and customer support. The initial distribution country is the Republic of Korea.
• Operator: DeepHigh Co., Ltd. / Representative: Shim Chung-seop / Business registration number: 798-86-01094.
• Address: Unit 202, Building 110, 50 Geomdan-ro, Buk-gu, Daegu, Republic of Korea (Bokhyeon-dong, Bokhyeon Seohan Town). Telephone: 02-3443-1028. Contact: task@deephigh.ai.

2. Age and choices

• Starring Life is intended for users aged 14 and over, including minors aged 14 and over. Account registration and server processing services are not provided to children under 14.
• Before starting Google sign-in, users confirm that they are at least 14. We do not collect a date of birth or identity document for this purpose. This confirmation is not identity or age verification, or confirmation of a legal representative's consent.
• Legal representatives may contact us to exercise a minor's personal information rights. We request only the minimum information needed to verify identity and authority. Legal representative consent required for a minor's paid contract is separate from reading this policy.
• You can write on your device without signing in. Signing in alone does not send records to the server. Device recording features remain available without choosing AI help, backup or notifications.

3. Information processed on the device

• Writing, titles, event periods, photo links, book structure, edit history, chosen profile name, topics, text size, language and other settings are stored on the device for recording and reading. You enter or select each profile and setting item when using its feature.
• Photos link to originals in your gallery. The app does not delete those originals. If you choose backup or photo text recognition, the photo materials needed for that request may be sent to the server.
• Choosing “Keep original audio” retains the original recording in app-private device files until you remove the attachment, permanently delete the record, or clear app data. Original audio is excluded from server account backup and cannot be restored from the account after app removal or phone loss. Keeping original audio alone does not send it to AI. Temporary retry audio for speech-to-text is encrypted on the device and accessible for up to 24 hours. It is marked for deletion on successful transcription, cancellation or expiry, and files are cleaned up when the app runs. We do not guarantee that every file physically disappears immediately if the app is interrupted.
• When you choose PDF export, source export or phone sharing, selected materials are passed to device files or an external app you choose. Sharing destinations and file retention depend on your choices.

4. Server processing: information, purposes, routes and grounds

• Google account connection — Information: account identifier, email and authentication session data. Route: Google sign-in chosen by you and Supabase authentication. Purposes: maintaining sign-in, identifying your account and providing account features. This is optional, but the information is necessary when connecting an account. Ground: processing necessary to perform the requested account service contract (Personal Information Protection Act, Article 15(1)(4)); processing requiring separate consent is explained separately.
• Optional backup — Information: selected writing, titles, event periods, photos, edit history, book structure, transcribed text, owner identifier and sync version. Route: you select records to upload. Purposes: paid backup, restoration across devices and prevention of conflicts and duplication. Optional, but needed for the selected backup. Ground: processing necessary to perform the requested backup contract. Audio files themselves are not retained.
• Optional AI help — Information: writing, photos or audio selected for that request, task type, language and request identifier. Route: app to Company server to OpenAI API. Purposes: recall help, writing organization, transcription and photo text recognition. Optional, but needed for the requested feature. Ground: performance of the requested AI feature contract; requirements for separate consent for overseas transfers or sensitive information are considered separately.
• AI usage and duplication prevention — Information: account and request identifiers, material fingerprints, task type, execution and settlement status, date and cost. Route: a ledger generated by the Company server. Purposes: preventing duplicate requests, limiting usage and settling costs. Needed for the chosen AI request. Original content and AI results are not stored in this ledger. Identifiers and fingerprints are not assumed to be anonymous information.
• Paid plans — Information: purchase token and hash, product, plan, status, term, verification time, account link and available transaction records. Route: Google Play purchase and server verification. Purposes: providing plans, restoring purchases, checking transactions and statutory retention. Necessary if you choose to pay. Grounds: performance of the paid contract and applicable retention obligations. We do not ask you to enter card numbers or bank account passwords directly in the app.
• Deletion reminders — Information: selected phone notification token, account identifier, notification consent and delivery status. Route: your notification choice and server delivery. Purpose: upcoming deletion reminders for server copies. Optional; declining does not prevent device recording. Ground: consent to these reminders. Notifications do not include personal records.
• Customer support and rights requests — Information: reply email, inquiry, relevant transaction details and minimum identity or authority verification information. Route: email to task@deephigh.ai or telephone. Purposes: resolving inquiries, exercising privacy rights and handling disputes. Only information necessary to respond and process requests is collected. Grounds: request processing and applicable legal obligations. Do not unnecessarily send original personal records, passwords or full identity document copies.
• Service access and safety — Information: platform-generated security and operational logs, such as access time, request status, IP and client information. Company code is designed not to log personal records, authentication secrets or raw provider responses. [To be confirmed: actual platform log fields, collection grounds, necessity and retention periods].

5. Retention periods and starting points

• Device records, profiles and settings remain until you delete them or clear app data. Drafts remain until deleted. Device Trash items can be restored for 30 days after deletion, then are cleaned up while the app runs or on the next launch. Immediate permanent deletion is also available.
• Account information is processed while needed for account maintenance and authentication and deleted on account closure. Server copies remain while a plan is valid and are deleted after a 30-day grace period from expiry. A valid lifetime plan has no recurring expiry and inactivity alone does not trigger deletion. Permanent deletion and account closure requests take priority over the ordinary retention grace period.
• Device audio for transcription retries is accessible for up to 24 hours from normal recording completion (creation for interrupted recordings) and cleaned up earlier on successful transcription or cancellation. External AI retention is described separately in section 7.
• Notification tokens are processed while using reminders on that device and cleaned up when reminders are disabled, the token becomes invalid or the account is deleted. [To be confirmed: specific retention period for delivery status records].
• Minimal payment verification records after account closure: one year from removal of the account link. Fields include purchase token hash, product, plan, term, verification and closure times, without original personal records. Transactions subject to statutory retention are exceptions to this one-year policy, retained separately for the periods below and not reused to provide services.
• Under Article 6 of the Act on Consumer Protection in Electronic Commerce and Article 6 of its Enforcement Decree, applicable advertising records are kept for six months; contract and withdrawal records and payment and supply records for five years each; and consumer complaint and dispute records for three years. The statutory starting point for each record, such as creation, transaction completion or handling completion, applies. Account closure does not restart retention.
• AI request and usage ledger: [To be confirmed: period needed for duplication prevention and settlement, and removal or separation of account identifiers on closure]. General inquiries: [To be confirmed: specific period after resolution]; statutory consumer complaint and dispute records use the three-year period above. Operational backups and temporary caches: [To be confirmed: actual retention, replacement and final deletion cycles].

6. External services, processors and third-party disclosure

• We use external providers as needed for requested features. Contracted processing is distinguished from a provider's independent processing for its own services. We do not classify every activity of a provider uniformly as processing on our behalf or third-party disclosure.
• Supabase — The contracting entity in its standard service terms is SUPABASE PTE. LTD. We use it for authentication infrastructure, database, file storage and server functions. The project's primary storage region is Seoul, Republic of Korea (ap-northeast-2). This does not establish that overseas support or subprocessors operate only domestically.
• OpenAI — The standard contracting entity for customers in the Republic of Korea is OpenAI OpCo, LLC. It processes materials selected for AI help. Our server does not separately attach your sign-in email as AI input, but your selected writing, photos or audio may contain personal information.
• Google — We use Google account authentication, Google Play payment and purchase verification, and Firebase Cloud Messaging notifications. Independent Google account and Play processing follows their policies; processing of Company notifications through FCM follows the applicable processor terms. [To be confirmed: entities and roles under actual Google contracts, and required processor or disclosure details].
• Processor contracts address purpose restrictions, safeguards, oversight, subprocessors, rights assistance and deletion; actual agreements and acceptance records are checked. [To be confirmed: actual contracts and applicable subprocessor lists for each service]. We do not disclose personal information beyond specified purposes except as permitted by law or with required separate consent.

7. Overseas processing and AI data

• Overseas disclosure, access, outsourced processing and storage are described separately from domestic storage. Actual processing countries are not inferred solely from a provider's corporate address.
• OpenAI: transferred information consists of selected writing, photos, audio and request data; the purpose is generating the chosen AI result; timing is when you run AI; the method is HTTPS through our server. Standard contracting party contact: contract-notices@openai.com. [To be confirmed: actual destination countries, retention by material type, transfer grounds and provider data control settings].
• Supabase: account, backup and server processing information is transferred over HTTPS, with primary storage in Seoul. The standard DPA contact is privacy@supabase.io. [To be confirmed: countries, timing, purposes, retention and transfer grounds for overseas access, support and subprocessors].
• Google: authentication, transaction and notification processing takes place during sign-in, Play purchases and optional reminders. [To be confirmed: destination countries, information, recipient contacts, retention, timing, methods and grounds under actual contracts].
• You may decline AI, account connection, backup or notifications, or contact us to withdraw consent for processing based on consent. Refusing necessary transfers may prevent the relevant feature, but device records remain available. Information already transferred and statutory records follow separate deletion and retention rules.
• We do not use source materials to train our own models without authorization. OpenAI's standard API guidance states that data is not used for training without an opt-in, but actual organization settings must also be checked. Writing and OCR requests use store:false; this does not mean that no logs are retained. Provider retention for transcription, text and images depends on endpoints and settings and is not described as universally immediate, complete deletion.

8. Deletion procedures and methods

• We identify information for deletion when its purpose is fulfilled, retention ends, an account is closed or permanent deletion is requested. Information required by law is separated from service information, accessible only to staff who need it for that purpose, and deleted after the statutory period.
• Device deletion cleans up app storage rows and linked files without deleting gallery originals. Server deletion removes files, personal records, edit history, book structure, notification data and other related materials in stages, then deletes the authentication account. Failed stages are retried, and request acceptance is distinguished from completed deletion.
• Electronic information is deleted to prevent restoration or reuse; paper information, if any, is destroyed by shredding or similar methods. Operational backups and provider residual data follow confirmed retention and deletion cycles. [To be confirmed: final deletion timing and operating procedures for backup and external residual data].
• Closing an account does not delete your Google account or cancel a Google Play subscription. Cancel recurring payments separately in Google Play.

9. Access, correction, deletion, restriction and withdrawal of consent

• Users and legal representatives may request access, correction, deletion, restriction of processing or withdrawal of consent at task@deephigh.ai or 02-3443-1028. State your request and a contact method. Requests are handled after minimum identity and authority checks.
• Device records can be viewed, edited, deleted and exported in the app. Account and server deletion are provided through the account screen or account deletion request page. [To be confirmed: activation of actual deletion operations and completion verification before release]. Contact us if you cannot use the app.
• If legal retention or another legal reason prevents full compliance, we explain the reason and possible scope. Statutory data transmission requests are handled according to applicable entities, information and procedures. PDF and source export do not replace every statutory transmission request process.

10. Permissions, automatic collection and behavioral information

• The microphone is used when recording, the camera when taking photos, photo access when selecting or linking photos, and notification permission when choosing deletion reminders. Change permissions in phone settings; refusal limits the related feature. OS permission is separate from consent to personal information collection or overseas transfers.
• The app does not use advertising SDKs or advertising-identifier-based personalized advertising. Authentication sessions and server access logs may be processed to provide features, so we do not claim that no automatic information is collected.
• Cookies and account settings used by Google in its sign-in browser follow Google's policies and browser or Google account settings. Our legal document screens do not add external tracking scripts or fonts. Viewing the Privacy Policy does not send sign-in tokens or user records.

11. Sensitive information, others' data, AI results and sharing

• Writing, photos and audio may contain sensitive information, such as health or beliefs, or others' personal information. Do not enter or send unnecessary information, resident registration numbers or others' secrets. Where sensitive processing is needed, applicable separate consent and other requirements are checked; a single AI or backup confirmation does not replace them.
• Memories are not automatically posted to a public feed. You decide whether to share materials externally. AI suggestions enter your writing only when you review and apply them; they do not automatically overwrite originals.
• AI text generation is not used for automated decisions with significant effects on rights or duties, such as credit or employment. Contact us about feature access problems caused by plan verification errors or usage limits. Separate pseudonymized processing for statistics, research or model training is not currently provided.

12. Security safeguards

• We encrypt text databases and keep original audio in app-private files, with OS-protected credential storage, HTTPS, owner-based server access restrictions and private file access. Server administrator secrets are not included in the app, and code is designed not to log personal originals or secret keys.
• Administrator privileges and personal information access are limited to what is needed. Retention, deletion and processor operations are checked. We do not guarantee a particular security certification or that incidents or data loss are impossible.

13. Privacy officer and contact

• Privacy officer: Kim Pil-woo, Strategic Planning Department. Telephone: 02-3443-1028. Email: task@deephigh.ai.
• The same contact handles access requests, rights, complaints and remedies. For help from relevant Korean bodies, visit privacy.go.kr, privacy.kisa.or.kr or kopico.go.kr.

14. Effective date and changes

• Scheduled effective date: October 10, 2026. Revision: 2026-10-10-v2 (local original-audio disclosure). Initial jurisdiction: Republic of Korea.
• When this policy changes, the app and public page explain the effective date, changes and how to view earlier versions. Publishing a policy does not replace any additional consent required for a change.