HANCHAE · Review draft
Privacy notice
What we use, where it goes and when it is removed.
- Reviewed as of
- Effective date
- To be confirmed and announced before sales
1. Operator and scope
Hanchae’s current developer and operator is Soomin Park (박수민), an individual developer in South Korea. Privacy questions and rights requests can be sent to [email protected]. This draft prepares the personal web and desktop launch notice.
The final controller, privacy contact, operator address and effective date must be confirmed before sales. This page is not an effective policy until the open items below are resolved and a final document is published separately.
2. Information and purposes
Accounts, work storage and subscription checks provide the service you request. Optional Calendar access, activity collection and AI transfers require the relevant permission and consent. We do not sell personal information or share it for advertising. Legally required records are retained separately under the applicable obligation.
Data and drafts also remain on your device. Credentials use OS-protected storage and server Calendar credentials are encrypted, but workspace content is not end-to-end encrypted. This site adds no advertising or analytics tracking scripts or sign-up forms.
| Area | Information and purpose |
|---|---|
| Account | Account ID, email, sign-in provider ID, available profile and auth sessions: sign-in, identification and protection. We do not receive Google passwords. |
| Work and sync | Chae, resource references, tasks, notes, sections, dates, recurrence, sessions, completion/conflict records: storage, device sync and recovery. Device launch paths/arguments and original file contents are not automatically synchronized. |
| Optional Calendar | Account/calendar IDs, names and permissions; event titles, descriptions, times, locations, recurrence, attendees, responses and conference details; encrypted credentials and mappings: authorized viewing, changes and records. |
| Trials and billing | Account, product, transaction and subscription IDs, purchase/renewal dates, entitlement, trial start/end and usage: purchase checks, one-time trials and limits. Paddle handles full card data; Hanchae’s app/API do not receive it. |
| AI | Input reviewed for each request; request IDs, hashes, model, status, token/credit usage: requests, duplicate-charge prevention and usage checks. Input retention is distinguished below. |
| Support and operations | Emails and attachments you send, and technical details such as IP, request time, app version and errors: support, reliability and abuse prevention. |
3. Optional activity and AI transfers
Activity collection is off by default and runs only in sessions you enable. Supported-app window/material titles, addresses/paths, activity times and optional excerpts are stored per account on the device. Settings provide exclusions, pause, inspection and deletion. Collection permission is not permission to send data to AI.
Task recommendations send the reviewed chae, recent completion records, tasks, notes, observed material titles/addresses and retained excerpts to TypeSafe (Jev). Record summaries separately send reviewed evidence and recommended-task information to OpenAI. Imported Google Calendar event bodies are not included in this resume input.
Quick-capture classification sends the input sentence and chae/section candidates to TypeSafe (Jev), and note task candidates send the selected note title and body range there. Background generation sends reviewed purpose, time and mood descriptions to OpenAI. Each execution reviews its input, provider and cost; collection or background consent does not authorize other AI transfers.
Hanchae does not persist or content-log text AI inputs or recommendation/summary/candidate/classification outputs on its server. It keeps request IDs, hashes, model, status, token and credit usage for deduplication and usage checks. Generated background previews are separately retained for 7 days.
OpenAI API inputs and outputs are not used for model training by default. Default abuse-monitoring logs may retain content for up to 30 days, with legal/security exceptions. TypeSafe states it does not train or fine-tune models on input, but permits retention for processing and legal needs. Immediate deletion or zero provider retention is not promised.
4. Google data and disconnection
Google sign-in and Calendar access are separate choices. Data received from Google APIs is used for requested account and Calendar features, not advertising, resale, credit decisions or training general-purpose AI. We follow the Google API Services User Data Policy, including Limited Use.
Human access is limited to specific user permission, necessary security investigations, legal obligations and other situations that policy permits. Workspace notes and Calendar event bodies are not sent to billing providers for subscription checks.
Disconnect Calendar in the app or revoke access in Google account connections. Further connected access stops, but events already created at Google are not deleted.
5. Providers and international processing
Necessary information is transmitted over encrypted network connections when features, sync or checkout run. Processing and storage can occur outside your country. A production region alone does not establish every provider’s or subprocessor’s countries.
The final notice must identify each recipient entity/contact, country, data, purpose, timing/method, retention and legal basis. Transfers requiring separate consent will obtain it; disclosure requirements for contract-necessary outsourced processing/storage must also be checked.
Refusing or withdrawing optional consent can limit the corresponding Calendar, AI or collection feature. Refusing essential account/sync processing may prevent service use; export, account deletion and support remain routes to exercise your choices.
| Provider | Role and information | Location and retention checks |
|---|---|---|
| Supabase | Account auth/database: account and sync data, encrypted Calendar credentials, AI ledger | Production DB in US East, us-east-1. Confirm contracting entity/contact and detailed retention. |
| PowerSync | Device sync: account ID and synchronized data | Production instance in US East, us-east-1. Confirm replica and log retention. |
| Render | Hanchae API: information needed for authenticated, sync, Calendar and AI requests | Production API in Virginia, USA. Confirm detailed log and backup retention. |
| Sign-in and optional Calendar: profile and authorized event/account information | Global infrastructure. Confirm contract, actual processing countries and retention. | |
| OpenAI | Optional record summaries and backgrounds: input reviewed before execution | Provider infrastructure. Confirm exact transfer countries, entity and retention exceptions. |
| TypeSafe (Jev) | Optional recommendations, capture classification and note task candidates: reviewed input/candidates | Provider/subprocessor infrastructure. Confirm exact countries, duration and contracting entity. |
| RevenueCat | Subscription checks: account, product, transaction, subscription and entitlement | Confirm exact transfer countries, contracting entity and retention periods. |
| Paddle | Sales, payments, billing, cancellation and refunds: checkout data and transactions/subscriptions | Seller shown at purchase and provider infrastructure. Confirm countries and legal transaction retention. |
6. Retention and deletion
Information is removed when its purpose or legal retention period ends. Electronic records are deleted to make recovery difficult, and paper copies, if any, destroyed. Final cleanup schedules, backup expiry and provider retention need verification against production settings.
Individual deletion may leave sync deletion markers or conflict records. Account deletion removes cloud work data and Calendar credentials through the workflow; it does not erase all backup and transaction copies immediately.
Original files, exports, local unsent drafts, offline-device copies and Google events can remain separately. Export covers data downloaded to this device and pending state; check sync status first.
Account deletion and provider subscription cancellation are separate. Cancel and confirm automatic renewal before leaving. If deletion cannot be confirmed, verification state and data are preserved; follow the recheck instructions.
| Information | Retention and removal |
|---|---|
| Tasks, notes, sessions and account data | Kept for reading/export while the account remains open; subscription expiry alone does not delete it. Removed through account deletion. |
| Trial history and AI usage ledger | Used for trial/usage checks while the account is open, then removed with account deletion. No new permanent email/device fingerprint for re-sign-up tracking. |
| Local activity metadata / excerpts | Cleaned after 30 days / 7 days respectively; deletable in settings. Separate from copies already sent to providers. |
| Server AI background previews | Cleaned after 7 days; images already downloaded to a device are separate. Text AI input/output is not stored on the server. |
| Deletion-status verification record | Expires 30 days after the request, with completed-processing conditions, for minimal deletion recovery/verification. |
| Operational backups, sync replicas and technical logs | Production DB automatic backups had a confirmed 7-day retention on September 15. Confirm maximum retention/disposal for manual/old-environment backups, objects, logs and sync copies before sales. |
| Legally required transaction/dispute records | Separately retained if the applicable law requires it. Korean e-commerce rules specify 5 years for contracts/withdrawals and payment/supply, 3 years for complaints/disputes, 6 months for advertising. Confirm actual Hanchae/Paddle records and responsibilities. |
| General support inquiries | Kept as needed to handle the inquiry. Confirm a maximum general-support retention period, distinct from statutory dispute records, before sales. |
7. Rights, safeguards and contact
The app provides editing, export, individual/account deletion, optional disconnection and withdrawal of consent. Applicable law may also grant access, correction, deletion, restriction or portability rights. Contact support for requests through a representative as well.
Send requests to [email protected]. We request only verification needed to protect the account and confirm representation, and explain legal restrictions and available steps. Rights requests do not require full card numbers or passwords.
Safeguards include account-isolated stores, access controls, encrypted transport, OS-protected credential storage and encryption of server Calendar credentials. Use the same contact for security or privacy concerns.
In Korea, you can contact the privacy infringement reporting center (privacy.kisa.or.kr) or Personal Information Dispute Mediation Committee (kopico.go.kr). Elsewhere, you may contact your local data-protection authority.
8. Changes and final publication
Changes in information use, providers or retention require applicable advance notice and consent checks before an updated document is published. The final document will state its effective date and revision history.
Existing invitation-beta/sandbox policies and this launch draft have different scopes. Preparing this page does not open paid sales or complete final legal review.
Before publication
- Confirm operator, privacy contact, effective date, age eligibility and legal-representative procedures.
- Finalize each provider’s entity/contact, transfer countries, data, purpose, timing/method, duration, legal basis and refusal methods.
- Verify maximum retention/disposal for production/manual/old-environment backups, Storage objects, sync copies, logs and general support inquiries.
- Review statutory transaction retention and Hanchae/Paddle responsibilities, rights-request procedures/deadlines, and required notice/consent screens.