Privacy policy (draft)
Document version: draft-2026-10-28. The business operator, privacy officer, direct contact details and effective date remain undecided. This draft reflects the current implementation and has not completed legal review. The Korean text is authoritative.
1. Information and purposes
| Category | Information | Purpose | Retention basis |
|---|---|---|---|
| Waitlist | Email, language, source, registration and consent timestamps | Invitations and waitlist management | The existing draft proposes 90 days after invitation or until a deletion request; the operational cleanup procedure is not finalized |
| Registration and sign-in | Email, authentication records, consent types, versions and timestamps | Identity verification, account access and consent records | While the account is active; deletion procedures must remove other data promptly on closure while retaining legally required records separately |
| Profile | Optional display name, language and time zone | Personal display and settings | While the account is active or until removed |
| Connections | Connection and machine names, agent type, token identifiers and hashes, issue, expiry and usage timestamps | Agent authentication and connection management | As needed for connection and security management; cleanup periods for revoked connections are not finalized |
| Support | Email, subject, message, category, optional attachments, replies and handling records | Answering questions and resolving problems | Until the purpose is met; legally required complaint or dispute records are retained separately |
| Clone data | Source material, cases awaiting sorting (your words, the situation and choices sent by your AI agent, plus a hash of the conversation ID that tells conversations apart; conversation content is not received), pending proposals, confirmed memories and criteria, judgment context | Sorting cases and writing proposals, review, memory management, retrieval and judgments | Cases awaiting sorting are kept 10 days from when they were last seen, or 30 days once the server has sorted them and is holding them for the next sorting, up to 300 per person, then deleted (cases that back a proposal or memory are kept with it). Other data is subject to user retention and deletion policies; detailed periods for individual data types and backups are not finalized |
| Call history | Requests your AI agent made to look up memories or ask for a judgment and the answers the server returned, the calling connection and time, and, if you use the Clone-Me hook, the work folder path and a hash of the conversation ID (conversation content is not received) | Letting you review your AI agents' calls in the console | Deleted after the retention period you set in the console (1 to 3,650 days); if none is set (the default), kept while the account is active |
| Optional marketing | Email, consent status and timestamp | Product and promotional email | Until withdrawal or account deletion |
You may refuse consent. The current registration flow cannot be completed without its required consents. Display name, support attachments and marketing are optional. Do not include memory content or connection tokens in support messages. Do not submit another person's sensitive or confidential information.
2. Storage and access boundaries
The web database stores accounts, profiles, consent, waitlist, support and operational records. Attachments use private storage with authorized access. Connections, source material, memories and call history are managed by the Clone-Me server. The web server retrieves data to display your authenticated pages and does not retain personal memories or call history in its database, cache, analytics or error logs. Administrative screens do not provide access to users' raw memories or call history.
3. Processors and external AI
| Service | Role | Confirmed configuration |
|---|---|---|
| Vercel | Web hosting and public-page usage and performance statistics | Seoul functions; this does not establish that all processing remains in Korea |
| Supabase | Authentication, web database and support attachment storage | Production project in Seoul |
| Resend | Authentication, invitation and service email | Overseas processing conditions require confirmation |
| Amazon Web Services | Clone-Me server hosting | Lightsail in Seoul |
| OpenRouter and model providers | External AI for judgments, sorting cases into proposals and dreaming | The current production setting sends only to models from OpenAI and Anthropic; each provider's processing countries and retention periods require confirmation |
Read the overseas transfer notice for processing scope and refusal or withdrawal. Like judgments and dreaming, cases are sorted with external AI within the scope you agreed to at sign-up, and cases marked sensitive are never sent. You can turn off external AI for each memory. You can set retention periods for source material and call history under Settings > Data in the console. This policy does not guarantee exclusion from provider training, zero retention or processing in a specific country. Draft consent does not replace new consent required for additional external processing.
4. Cookies and access information
We use authentication cookies and display preferences such as language and theme. Restricting cookies in your browser may prevent sign-in. Public pages use Vercel usage and performance analytics; the console does not include analytics tools. Application error logging focuses on request IDs and error codes, not email, memory or token contents. Infrastructure providers' handling of access information must be confirmed against their contracts.
5. Access, correction, deletion and withdrawal
You can review and edit your profile and memories, review your call history, withdraw memories and disconnect connections in the console. Use the contact form below for account deletion, export, suspension of processing or consent withdrawal. Web account deletion and export controls are still being prepared. Requests require identity verification; their scope and results will be explained.
Deletion from active storage is distinguished from backup expiration. We do not claim that all backups are immediately erased. Legally required records are retained separately with their purpose and period identified. The finalized policy must specify deletion schedules and provider retention periods.
6. Safeguards and changes
We use HTTPS, account-scoped access controls, hashed connection tokens, restricted operational access and audit records. Changes to consent purposes, data or processing scope will be explained, and new consent requested where needed. The operator and privacy officer's direct contact details will be added here and to the footer once confirmed.
Contact and rights requests
Last updated Oct 28, 2026