Privacy Policy
This is a translation for reference. The Korean version is the official text and prevails in case of any difference.
This Policy takes effect on November 9, 2026.
isollet Inc. (주식회사 아이솔렛, the "Company") processes the personal information of people who use the isollet app and website (the "Service") in accordance with applicable laws, such as the Personal Information Protection Act (Korea) (「개인정보 보호법」, the "PIPA"). This Policy explains what personal information the Company processes, why, for how long, and how, and the rights users can exercise.
isollet is a service where parents who live apart (co-parents) record their child's parenting schedules, costs, and conversations together. Because these records may be used as materials that users submit to courts and other bodies, the Company processes them so that they are not arbitrarily changed or erased. For this reason, some information remains in the other party's records even after account deletion (Article 3). If all co-parents consent, an attorney, a family court investigator, or the judge in charge (a "Professional") can view records within the consented scope (Article 4), and all co-parents can check in the app what a Professional viewed and when.
Article 1 Purposes of Processing Personal Information
The Company processes personal information only for the following purposes. If a purpose changes, the Company informs users in advance and obtains consent again where necessary.
- Sign-up and account management: identity verification (email verification), sign-in, confirming age 19 or older, preventing misuse (preventing re-registration by permanently restricted members), processing account deletion
- Providing co-parenting features: connecting co-parents and third parties (grandparents, caregivers, etc.) by invite code; storing and syncing across devices child information, parenting schedules, schedule change requests, expenses and receipts, cost-sharing requests, settlement payment records, and messages
- Preserving and verifying records: keeping change records (event logs) of who did what and when, verifying record integrity with message signatures and server receipts, generating record documents (PDF) and verification data, and letting recipients check the original through a document check link (QR)
- End-to-end message encryption and recovery: distributing message public keys, keeping key backups and recovery information, transferring keys to a new device
- Providing the paid service (Plus): checking subscription eligibility, applying the Together Plan pass, providing AI wording refinement and receipt auto-fill, deciding on withdrawals and refunds and handling disputes
- Service operation and safety: detecting abuse and abnormal use, managing usage limits, responding to outages, answering customer inquiries
- Professional access: displaying records to a Professional within the scope requested by a co-parent and consented to by all co-parents; processing and recording consent, refusal, and withdrawal; keeping access logs and showing them to co-parents; issuance records for documents (PDF) for Professionals
- Managing professional members: professional sign-up and identity verification (qualification check), sign-in and keeping a single browser signed in, preventing misuse, processing account deletion
Article 2 Personal Information Processed and How It Is Collected
1. Information members enter themselves
| Category | Items | Notes |
|---|---|---|
| Required | Email address, password | For email sign-up. Passwords are handled by Google Firebase Authentication and are not stored on the Company's servers |
| Required | Sign-in identifier and email address of the Apple or Google account | Provided by Apple or Google when you sign in with them. If you use Apple's "Hide My Email," a relay address is provided. The account name is not stored even if received |
| Required | Title (e.g., "Minji's mom") | Shown to co-parents and third parties |
| Required | Child's name | When registering a child |
| Optional | Child's date of birth, sex, school, grade, class, notes | Notes are not visible to third parties |
| Optional (separate consent) | Child's blood type, allergies | This is health information (sensitive information), and separate consent is obtained when it is first entered. All other features remain available without this consent |
| Created during use | Parenting schedules (period, person in charge, notes), schedule change requests and their approval or rejection | |
| Created during use | Expenses (amount, date, category, description, merchant), receipt photos, cost-sharing requests (amount, reason) and their approval or rejection | Receipt photos are optional |
| Created during use | Settlement payment records (settlement month, amount, date sent, note) and their confirmation of receipt or withdrawal | Notes are optional. Do not enter financial information such as bank account or card numbers in notes |
| Created during use | Messages | Content is stored on the server only in end-to-end encrypted form (Article 6) |
| Created during use | Child deletion requests (reason) and responses |
The Company does not collect bank account information for exchanging child support or payment card information.
2. Information generated or collected automatically while using the Service
| Item | Details |
|---|---|
| Internal user ID | An internal number linked to the sign-in account. The server stores this number and the sign-in identifier |
| Device ID | A random number the app creates at installation. Stored with change records to record where a record came from |
| Push notification information | The push token of the device that receives notifications, device type (iOS or Android), enabled notification types, app language. Notifications contain only the type, such as "You have a new message," and not message content, names, amounts, or dates |
| Change records | Who created or changed a record, when, the target, and what changed |
| Message metadata | Sender, recipient, related child, time sent, time received by the server, time read, conversation sequence number, approximate ciphertext size, signature and receipt |
| Message encryption information | Message public key, encrypted key backup, encrypted recovery information, key transfer session (short-lived) |
| Recovery information unlock logs | Time, IP address, app name and version, success or failure |
| Key backup access logs | Time |
| Message key change logs | Type and time of key backup deletion, backup overwrites that discard old keys, public key replacement, and revocation of previous keys; part of the IP address |
| Consent records | Documents consented to (Terms of Service, collection and use of personal information, age (19 or older), health information), document version, time of consent |
| Subscription information | App market transaction identifier, product, plan, status, expiration time, terms agreed to at purchase, holder of the Together Plan pass |
| Paid feature usage records | Feature name (document export, wording refinement, receipt auto-fill), date, count, first and last use time, the subscription at that time. The content of exported documents or refined text is not recorded |
| AI usage counts | Usage counts by user and feature. Text, photos, and results are not recorded |
| Invite code records | Creator, assigned role and title, who used it and when, number of failed code entries (IP addresses only as irreversible values), number of codes created |
| Inquiry records | The content of inquiries and requests received through Contact us in the app and by email, the Company's responses, account identifier (in-app inquiries), email address, app version and device type (in-app inquiries; message contents are not included), and the times received and answered |
| Professional access requests | Child, requesting co-parent, designated Professional (name, role, and organization at the time of the request), record types (schedules, expenses, messages), record period, number of access days, status (pending, open, refused, expired, withdrawn, cancelled, ended) and its time and reason |
| Professional access consent records | The consenting co-parent and time; the person and time for each request, consent, refusal, withdrawal, expiry, and end |
| Professional access logs | Professional, child, type of records viewed, on-screen viewing or document download, record period, time. The content of the records is not kept |
| Message keys for Professionals | For each message within the consented scope, the key that opens that message wrapped with the public key of the Professional's browser, and who wrapped it. The Company cannot open messages with these |
| Document check link (QR) information | An encrypted copy of a document (PDF) that includes a QR check link, the document identifier, who issued it, the document type, creation and expiry time, and the number and times of views (IP addresses are not stored), and the fingerprint (SHA-256 — not content) of the original PDF file signed in the issuance seal. The copy is encrypted on the user's device and the key to open it is only in the QR address, so the company cannot see its contents |
| Server processing logs | Logs created when the server processes a request: request time, request method and path, response status, processing time, error text (request contents such as schedules or messages are not included). The server platform (Cloudflare) keeps them for 7 days, and a copy for troubleshooting (without IP addresses or device information, with identifiers in the path and query strings removed) is kept on Microsoft Azure for 30 days |
3. How it is collected
- When members enter it themselves in the app or choose photos
- Automatically when the app syncs with the server
- From Apple or Google when signing in with them
- From transaction information the app passes on when paying in an app market
- When a Professional signs up for and uses pro.isollet.com
- By checking against public sources, such as Korean Bar Association registration information and office websites, when verifying a Professional's identity
4. Information processed only on the device
The following is processed on the device and not sent to the Company's servers:
- Message temperature (tone) analysis
- Recognizing expressions of self-harm or suicidal thoughts while a message is being written and showing crisis hotline information (the result is not kept, and such text is not sent to the external AI for wording suggestions)
- On-device text recognition (OCR) of receipt photos
- Notification settings, notification display history, and app settings
- Camera video used to scan the QR code for transferring keys between devices
5. Information about professional members
| Category | Items | Notes |
|---|---|---|
| Required | Name, role (attorney, family court investigator, judge), organization (law office or law firm, or the court they belong to), email address, password | Passwords are handled by Google Firebase Authentication and are not stored on the Company's servers. Family court investigators and judges are accepted only with a court email address (@scourt.go.kr) |
| Required (attorneys) | Korean Bar Association registration number | For identity verification |
| Generated automatically | Internal ID, connection code, verification status (unverified, verified, rejected, suspended) and time of verification | The connection code is used by parents to find the Professional. The parent's app shows the name, role, organization, and whether the Professional is verified |
| Generated automatically | Sign-in records: ID of the signed-in browser, time the browser was changed, time of last activity, session information | Used to keep a single browser signed in and to sign out after 30 minutes of inactivity. Firebase Authentication sign-in records and server processing logs (Article 2, 2) are also kept |
| Generated automatically | Browser public key | The private key that opens messages is made so that it cannot be exported from the browser; it exists only in the browser and is not sent to the server |
| Created by operators | Records of identity verification, rejection, and suspension (type, reason, operator, time) |
Article 3 Retention Period and Destruction
1. General rule
Member information is kept until account deletion and destroyed without delay upon deletion, with the exceptions below.
2. Retention period by type of information
| Information | Retention period |
|---|---|
| Account (internal ID, sign-in identifier, title), consent records, failed invite code entry records, unused invite codes | Destroyed upon account deletion |
| Firebase Authentication account (email, password, etc.) | The app requests deletion upon account deletion |
| Child information and that child's schedules, expenses, cost-sharing, settlement payment records, messages, change records, and receipts | As long as at least one co-parent who manages the child together remains. Destroyed when the last co-parent deletes their account, or when the child is deleted with the consent of all co-parents |
| Health information (blood type, allergies) | When the field is cleared or the child information is deleted, or at the same time as the child information above |
| Receipt photos of deleted expenses | Deleted immediately when the expense is deleted. However, for an expense with a pending or approved cost-sharing request, the photo is kept for the same period as the child information, because the other party relied on it as evidence |
| Message key backup, recovery information, recovery information unlock logs, message key change logs, key transfer sessions | Destroyed upon account deletion |
| Recovery information unlock logs, message key change logs (before account deletion) | Destroyed after 3 years |
| Key backup access logs | 30 days |
| Key transfer sessions | Destroyed by scheduled destruction within 1 day after their short validity period ends |
| Message public key | Kept even after account deletion (see 3 below) |
| AI usage count records | Daily counts: destroyed by scheduled destruction within 1 day after 7 days. Monthly counts: destroyed by scheduled destruction within 1 day after 40 days from the end of that month. Destroyed immediately upon account deletion |
| Invite code creation count records | 1 day |
| Failed invite code entry records | Destroyed by scheduled destruction within 1 day after the misuse-assessment period ends. Destroyed immediately upon account deletion |
| Invite codes that expired unused | 7 days after expiry |
| Used invite codes | Same period as the child information, because they are the basis for the other party joining |
| Together Plan notifications (e.g., payer's account deletion) | 90 days after being viewed |
| Subscription information | Upon account deletion, separated from the account and moved to the transaction records in 5 below, then destroyed |
| Hashes of the email and sign-in accounts (Apple, Google) of permanently restricted members (to prevent re-registration; the original values are not kept) | After account deletion, for the re-registration restriction period set by the Company according to the reason for and severity of the restriction (up to 3 years) |
| Records of usage restrictions and their lifting (internal ID, type, reason, and time of action, operator who took it) | 3 years after the action (dispute-handling records; kept even after account deletion) |
| Professional account (name, role, organization, email, registration number, connection code, verification status, sign-in records) | Until the Professional deletes their account. Destroyed upon deletion |
| Professional's Firebase Authentication account | Deleted upon account deletion |
| Records of Professional identity verification, rejection, and suspension | 3 years after the action (kept even after the Professional deletes their account) |
| Re-registration block information for suspended or terminated Professionals (name, role, organization, email, registration number, sign-in account identifier, reason for the action) | 3 years after the action (kept even after the Professional deletes their account; used only to block re-registration and handle disputes) |
| Professional browser public key | While in use. Revoked when the browser is changed or withdrawn, and destroyed 3 years later |
| Message keys for Professionals | Destroyed immediately when access ends (withdrawal, cancellation, expiry, end of period, change of co-parents, Professional's account deletion, etc.) or when the browser key changes |
| Professional access logs | 3 years from when they are recorded |
| Professional access requests and their consent records (including the Professional's name, role, and organization at the time of the request) | 3 years after the request ends. They remain as the co-parents' records even if the Professional deletes their account |
| Professional document issuance permits | 1 day |
| Document check link (QR) information | The encrypted copy is destroyed within 1 day after 90 days from creation. The issuance record without content (document type, issue time, original file fingerprint) and view records are kept for 3 years so authenticity can be checked in proceedings, then destroyed. All of it is destroyed immediately if the issuer cuts the link or withdraws, or if the child's records are destroyed |
| All of the above records related to professional access | Destroyed immediately together with the child when the child is destroyed (Article 3, 4; child deletion) |
3. Information that remains in the other party's records after account deletion
Messages and shared records (schedules, expenses, cost-sharing, and their approval history, as well as settlement payment records and their confirmation history) in this Service are records created jointly by co-parents and may serve as grounds for the other party's submissions to courts and other bodies. If one party's account deletion erased these records, the other party's records would disappear, and deletion could become a way to erase unfavorable records. The Company therefore informs users of this at sign-up and handles it as follows:
- In the records of a child who has another co-parent, only the departing member is removed, and messages already sent and shared records remain as the other party's records. The other party's screen shows the member as "Former co-parent" (이전 공동양육자).
- Only the internal ID remains in the author field of the remaining records. Because the account information is erased, even the Company cannot identify the person from that number.
- The departing member's message public key is also kept, because the other party needs it to open past messages and verify their signatures. A public key cannot be used to open messages.
- These records are destroyed when the other party also deletes their account or the child is deleted.
- Third parties invited by the departing member are removed along with them.
- Professional access requested by the departing member ends. The departing member's consent records are erased, and in the access logs and consent records that remain, the person who acted is shown only as a deleted user, without a name.
4. Records of children managed alone
- For a child whose only co-parent is the departing member, the child information, all records, and receipt photos are destroyed immediately and cannot be restored.
- No option is offered to preserve these records after account deletion, and no email address or its hash is kept for that purpose. If you need the records, please export them as a PDF in the app before deleting your account.
5. Retention required by law
| Legal basis | Items | Period |
|---|---|---|
| Act on the Consumer Protection in Electronic Commerce (Korea) (「전자상거래 등에서의 소비자보호에 관한 법률」): records of contracts or withdrawal of offers, and records of payment and supply of goods | Transaction identifier, product, plan, status, payment and expiration times, terms agreed to at purchase, summary of paid features used under that subscription (days and counts per feature, first and last times) | 5 years from account deletion. Kept separately with the internal user ID removed (the transaction identifier can be matched against app market records) |
| Same Act: records of consumer complaints or dispute handling | Inquiries, requests, and how they were handled | 3 years (on account deletion, the account identifier and email address are erased and only the content is kept) |
6. Destruction procedure and method
- Procedure: Information whose retention period has ended or whose purpose has been achieved is destroyed by a daily scheduled job, and account deletion and child deletion are destroyed immediately when the request is processed. Information that fails to be destroyed is destroyed again.
- Method: Information in electronic file form is deleted in a way that cannot be recovered. When destroying a child, the related records are deleted all at once so that no partial records remain. Records on the device and message keys (including keys stored in iCloud Keychain or Google Block Store) are erased by the app upon account deletion.
- Deleted information may remain in the platform's data recovery records and backups for up to 30 days.
- Past schedules previously received may remain on the device of a third party removed by a co-parent.
- If the Company ends the entire Service (Terms of Service, Article 6-3), personal information and records on the servers are destroyed without delay after the end date, and only information that must be kept by law is stored separately for the required period.
Article 4 Provision of Personal Information to Third Parties
The Company processes users' personal information only within the scope of the purposes in Article 1 and does not provide it to third parties except in the following cases:
- The user has consented in advance
- It is unavoidable under special provisions of law or to comply with legal obligations (lawful requests from investigative agencies, court orders, etc.)
Co-parents and third parties invited by a user viewing that child's records is a feature the user initiated. What they can see is as follows:
- Co-parents: all records of that child and the messages they themselves sent and received
- Third parties: child information (excluding notes, including health information) and parenting schedules (including schedules entered by the other co-parent and their notes). They cannot see expenses, cost-sharing, settlement payment records, or messages. A third-party invitation is shown only to the co-parent who sent it, and the other co-parent is not notified
- Professionals: records of the types and period consented to by all co-parents (table below)
Provision through professional access (optional). Only when a co-parent requests access for a Professional and all co-parents of that child consent does the Company show the records within the consented scope to that Professional. Each co-parent's information is provided on the basis of that person's own consent (the request or the consent). If even one person does not consent, nothing is provided. Not consenting does not limit use of the rest of the Service, and consent can be withdrawn in the app at any time after it is given. On withdrawal, provision stops immediately.
| Recipient | Purpose | Items | Retention period |
|---|---|---|---|
| A Professional consented to by all co-parents together (an attorney, family court investigator, or judge in charge whose identity the Company has verified; name, role, and organization are shown on the request and consent screens) | Attorney: work on the case concerned entrusted by the requesting co-parent / Family court investigator or judge: duties in the family case concerned | Of the following, the types consented to, within the consented record period: schedules (period, person in charge, notes, status, schedule change requests and their approval or rejection) / expenses (amount, currency, date, category, description, and merchant of expenses, whether a receipt exists, cost-sharing requests and their approval or rejection, settlement payment records with notes and confirmations) / messages (content, sender and recipient, time sent and read, signatures and public keys for verification). People are shown by title (or "Co-parent 1·2" if none), and the child by name. The child's date of birth, sex, school, grade, class, notes, and health information, information about third parties (grandparents, etc.), and receipt photos are not provided. If the requesting co-parent has Plus, the Professional can receive records within the consented scope as documents (PDF) | The Company shows records until access ends (the consented number of access days from when access opens, 90 days by default and up to 365 days; immediately upon withdrawal or a change of co-parents). Content a Professional has already viewed and documents already received are handled by the Professional in accordance with their own obligations, such as under the Attorney-at-Law Act, laws applicable to public officials, and the Personal Information Protection Act, and with the Professional Terms of Use (confidentiality, no use for other purposes, destruction when the purpose ends) |
- Messages remain end-to-end encrypted. For each message within the consented scope, the co-parent's device wraps only the key that opens that message with the Professional's browser key and sends it, and it can be unwrapped only in the Professional's browser (Article 6). The Company cannot open messages with the wrapped keys.
- Before access opens, the Professional sees only the request status and the requested record types and period. The requesting co-parent's title, the other co-parent's information and records, and the child's name are shown only after all co-parents have consented.
- A Professional receiving a document (PDF) is recorded in the professional access log and is not recorded as the requesting co-parent's paid feature usage.
- The rights and obligations of professional members are governed by the Professional Terms of Use.
Provision with the user's consent (optional). If a user who consented through the optional checkbox shown just before purchase, or through "Tell Apple whether I used the service when I request a refund" on the subscription management screen, requests a refund from the App Store, the Company provides the following to Apple at Apple's request. Not consenting does not limit use of the Service, and consent can be turned off at any time on the same screen. After it is turned off, nothing is provided.
| Recipient | Purpose | Items | Retention period |
|---|---|---|---|
| Apple Inc. | Review of an App Store refund requested by the user | Transaction identifier, an opinion based on whether paid features were used in that billing period (recommend declining the refund, recommend a full refund, or no preference), whether content was delivered. What the user did and how many times they used features are not provided | According to Apple's policy |
| Google LLC | Processing a Google Play refund requested by the user | Transaction identifier, payment information needed to process the refund | According to Google's policy |
Article 5 Outsourcing of Processing and Overseas Transfer
1. Outsourcing of processing
| Processor | Outsourced work |
|---|---|
| Cloudflare, Inc. | Server operation (including operation of the professional web, pro.isollet.com), data storage (database, receipt photos and encrypted document check copies), AI request relay and AI model execution, network security, website visit statistics |
| Google LLC (Firebase Authentication) | Sign-up and sign-in (including professional members), sending verification emails |
| Google LLC (Firebase Cloud Messaging) | Delivering push notifications (on iOS, delivered via the Apple Push Notification service) |
| Google LLC (Firebase Crashlytics) | Collecting and analyzing app error (crash) records |
| Apple Inc. (Apple Push Notification service) | Delivering iPhone push notifications |
| Microsoft Corporation | Managing the encryption key that protects message recovery information |
| Microsoft Corporation (Azure OpenAI) | Plus AI wording refinement and receipt auto-fill |
| Microsoft Corporation | Storing data backups, processing service statistics |
| Apple Inc. | Sign in with Apple, App Store payments, message key sync through iCloud Keychain (depending on user settings) |
| Google LLC | Google sign-in, Google Play payments, message key sync through Google Block Store |
| Slack Technologies, LLC | Receiving operational alerts |
| Kakao Corp. (주식회사 카카오, Daum Smartwork) | isollet.com email (receiving and replying to inquiries and requests) |
In its outsourcing contracts, the Company sets out the prohibition of processing beyond the outsourced work, measures to ensure security, restrictions on sub-outsourcing, management and supervision, and liability for damages. The Company may change or add processors to operate the Service; in that case, it will announce the change through this Policy and an in-app notice at least 7 days before it takes effect. Changes that significantly affect users' rights, such as a new overseas transfer of personal information, will be announced at least 30 days in advance under Article 13. The Company entrusts personal information only to processors and service plans whose contracts or terms state that they do not use the entrusted personal information to train their own AI models.
2. Overseas transfer
To provide the Service (perform the contract), the Company transfers personal information overseas as follows (PIPA Article 28-8(1)3). Transfers take place as needed while the Service is used, over an encrypted network (HTTPS).
| Recipient (contact) | Country | Items transferred | Purpose | Retention and use period |
|---|---|---|---|---|
| Cloudflare, Inc. ([email protected]) | U.S. company. The primary storage location of the database and photo storage is the Asia-Pacific region; requests are processed at Cloudflare locations worldwide | All items stored on the server under Article 2, connection information from request processing, website visit statistics (aggregates that do not identify individuals) | Server operation and storage | The retention periods in Article 3. Server processing logs 7 days; other processing logs follow the provider's policy |
| Google LLC (Firebase) | United States | Email, password (handled by Firebase), sign-in identifier, Apple or Google account information, connection information at sign-in (including professional members' email, password, and connection information at sign-in) | Member authentication | Until account deletion |
| Google LLC (Firebase Crashlytics) | United States | Error records when the app crashes (crash location and code path), device model, OS, app version, app installation identifier (Firebase installation ID). User IDs, email addresses, and record contents are not included | Fixing app errors | According to the provider's policy |
| Google LLC (Firebase Cloud Messaging), Apple Inc. | United States | Push token, notification type and generic text, internal IDs of the related child and target | Delivering push notifications | The Company does not keep them after delivery; the provider's processing logs follow the provider's policy. Tokens are deleted when notifications are turned off or the user signs out or deletes their account |
| Microsoft Corporation (encryption key management) | Republic of Korea | Only at recovery: locked recovery information (including the internal user ID). The provider keeps a record of unlock requests | Message key recovery | Audit logs follow the provider's policy |
| Microsoft Corporation (Azure OpenAI) | The resource is in the Republic of Korea; processing may take place in other countries | Message drafts for which a Plus user tapped refine, and receipt photos chosen for receipt auto-fill | AI wording refinement and receipt recognition | Not stored under the Company's settings. Retention for the provider's abuse monitoring follows the provider's policy |
| Microsoft Corporation (data backup and statistics) | Republic of Korea (disaster-recovery copies are also kept within the Republic of Korea) | All items stored on the server under Article 2 (messages remain end-to-end encrypted), server processing logs | Database backup, service statistics, keeping server processing logs | Backups 30 days; statistics replica 1 day; server processing logs 30 days |
| Cloudflare, Inc. (Workers AI) | Cloudflare locations worldwide | Same as Azure OpenAI above (fallback route) | Same as Azure OpenAI above | According to the provider's policy |
| Apple Inc. | United States | Sign-in identifier and email, payment information (collected directly by Apple), message key bundle (iCloud Keychain, end-to-end encrypted by Apple) | Sign-in, payment, key sync | According to Apple's policy |
| Google LLC | United States | Sign-in identifier and email, payment information (collected directly by Google), message key bundle (Block Store; cloud backup only on devices with a screen lock) | Sign-in, payment, key sync | According to Google's policy |
| Slack Technologies, LLC | United States | Operational alerts: part of the internal user ID, usage figures. Text, photos, and email addresses are not included | Detecting abuse and outages | According to the provider's policy |
- The internal user ID is not sent to AI providers. The Company connects only providers and plans whose terms state that they do not use submitted text or photos for training, and configures the relay of AI requests so that request content is not logged.
- The server chooses the AI provider based on usage and outages; users cannot choose the provider.
- How to refuse and consequences: Overseas transfer is necessary to provide the Service, so to refuse it you must delete your account. Transfer to AI providers does not occur if you do not use Plus AI refinement or receipt auto-fill. Receipt photos are sent only if the app asks the first time you send one and you choose “Allow” (if you choose “Read on device only” or turn off “Read receipts with AI” in Settings, receipts are read only on your device). In that case, on-device features and the rest of the Service remain available.
Article 6 End-to-End Message Encryption and Storage of Recovery Information
Message content is end-to-end encrypted in transit and at rest. So that you can recover even if you change or lose your phone, recovery information is kept in encrypted form.
- Scope of encryption: Message content is encrypted on the sending device and decrypted only on the recipient's device. Only ciphertext is stored on the Company's servers. Schedules, expenses, child information, receipt photos, and change records are not end-to-end encrypted; they are protected by encryption in transit (HTTPS) and the platform's encryption at rest.
- Information that stays on the server: The sender, recipient, related child, time sent, time received by the server, time read, conversation sequence number, approximate length, and the signature and server receipt stay on the server.
- Recovery information: The app stores message keys in iCloud Keychain or Google Block Store and, separately, entrusts an encrypted key backup to the server. The information that opens this backup is locked again with a key in a key management service separate from the database, so it cannot be unlocked with the database alone. When you sign in on a new device without the key, this information is unlocked after identity verification to recover it.
- Limits of the recovery information: Under this method, anyone with access to the Company's systems could technically unlock the recovery information. The Company limits unlock permission to the minimum, records every unlock request in two separate places, and monitors unlocks with rate limits and alerts for abnormal requests.
- AI refinement: When you tap Plus AI wording refinement, the draft is sent to the Company's server and the AI provider before it is encrypted, to be refined (it is not stored). The message you send is end-to-end encrypted.
- Device and account security: If someone else uses an unlocked device, they can see the conversations on that device. iCloud Keychain and Google Block Store depend on the security of your Apple or Google account (two-factor authentication, device passcode).
- Court submission: When a user exports conversations, a document (PDF) and verification data are created, and only the keys that open the exported messages are included in the verification data.
- Document check link (QR): When a check link is added to a document (PDF), the app encrypts the document on the device and stores it on the server, and puts the key to open it only in the QR address printed on the document. The company cannot open the stored copy. Anyone who has the QR code or address can view the whole document for 90 days from creation (for 3 years after that, only the fact of issue and the original file fingerprint can be checked, without content), so please note that handing over only part of a document still opens all of it if the QR code is on it. The issuer can cut the link at any time in the app and see how many times and when it was viewed.
- Professional access: When all co-parents consent to access to messages, the device of the co-parent who sent or received a message wraps, for each message within the consented scope, only the key that opens that message with the public key of the Professional's browser and entrusts it to the server. The key that opens the whole conversation is not handed over. The private key of the Professional's browser cannot be exported from the browser, and the Company cannot open messages with the wrapped keys. When access ends, the wrapped keys are erased. If a co-parent's device is off, keys for new messages may be delivered late, and content a Professional has already viewed cannot be recalled.
- Upon account deletion, the key backup, recovery information, unlock logs, and key change logs are destroyed, and the keys on the device are erased. The public key remains as described in Article 3, 3.
Article 7 Rights of Data Subjects and How to Exercise Them
- Users may at any time request access to, correction or deletion of, or suspension of processing of their personal information, or withdraw consent.
- Directly in the app: Your title and child information can be edited in the app, and the health information fields are deleted immediately when cleared. You can delete your account under Settings (설정) > Edit my info (내 정보 수정) > Delete account (회원 탈퇴). Consent to professional access can be withdrawn at any time on the professional access screen in Child sharing management (자녀 공유 관리) in the app, and provision stops immediately upon withdrawal. On the same screen you can see the professional access log (who, when, which types, which period) and the records of consent, refusal, and withdrawal.
- By request: You can send a request from your registered email to the Chief Privacy Officer (Article 11). The same applies if you cannot use the app. After verifying your identity, the Company informs you of the result within 10 days.
- You may also make requests through a representative (a legal representative or a person you have authorized), in which case a power of attorney must be submitted.
- Cases that may be limited: Due to the nature of the records, the following cannot be corrected or deleted, or such requests are limited. If the Company declines, it informs you of the reason and how to object.
- Messages already sent (there is no edit or delete feature, and they are the other party's records)
- Change records and approval and rejection history
- Records managed together with another co-parent (Article 3, 3)
- Records kept as required by law (Article 3, 5)
- Only your own information: Requests for access, correction, deletion, or suspension of processing can be made only for the requester's own personal information. Other users' (the other co-parent's, a third party's, or a Professional's) personal information, records, or access logs are not provided through such requests (Terms of Service, Article 7-3). However, the professional access logs and consent records for a child are shown to all of its co-parents in the app. Shared records you can see may be viewed and downloaded directly in the app and as documents (PDF).
- Limits under law: The Company may limit or refuse requests in the cases set out in the Personal Information Protection Act of Korea, for example where access is prohibited or limited by law or where it may harm another person's life or body or unfairly infringe another person's property or other interests (Article 35(4)), requests to delete information that another law specifies as subject to collection (Article 36(1)), and requests to suspend processing where a law has special provisions or it is unavoidable to comply with a legal obligation (Article 37(2)).
- If a child has two or more co-parents, deletion of the child information and its records proceeds with the other party's consent.
- Account deletion does not cancel an app market subscription. Please cancel your subscription in the App Store or Google Play before deleting your account.
- Professional members: Professional members can request access to, correction or deletion of, or suspension of processing of their own information, and account deletion, from the Chief Privacy Officer as in item 3, and can also do so using features the professional web provides. The name, role, and organization at the time of the request and the access logs that remain in co-parents' apps are the co-parents' records and remain for the periods in Article 3, 2.
Article 8 Personal Information of Children Under 14
- Only people aged 19 or older can sign up, and age 19 or older is confirmed at sign-up. The Company does not accept sign-ups from minors, including children under 14.
- The Service contains information about children (including children under 14). This information is not collected directly from the child but entered by a member who is the child's guardian. The Company processes child information only for the purposes of co-parenting records (Article 1).
- Child information processed: name (required); date of birth, sex, school, grade, class, notes (optional); blood type and allergies (optional, separate consent); and the child tag on schedules, expenses, receipts, and messages related to that child.
- Child information can be seen only by that child's co-parents and by third parties invited by a co-parent (excluding notes). A Professional consented to by all co-parents sees only the child's name and the records of the consented types and period, and does not see the date of birth, sex, school, grade, class, notes, or health information (Article 4).
- The Company does not use child information for advertising, analytics, or AI training.
Article 9 Installation, Operation, and Refusal of Automatic Collection Tools
- The app has no advertising SDK or usage-behavior analytics SDK (e.g., Google Analytics for Firebase), does not use advertising identifiers, and does not track users across other companies' apps or websites. Only app error (crash) records are collected through Firebase Crashlytics (Article 5).
- The app stores sign-in status, settings, and notification history on the device. This information is not sent to the Company's servers and is erased when you delete the app, sign out, or delete your account.
- The website (isollet.com) does not use cookies for advertising or usage-behavior analytics. It collects visit statistics (number of visits, referrers, country and device type, page speed) without cookies through Cloudflare Web Analytics, and does not identify individuals or track them across other websites.
- The professional web (pro.isollet.com) stores the sign-in state only in that browser tab, and keeps the browser ID and the browser key that opens messages in that browser's storage. It does not use cookies for advertising or usage-behavior analytics.
Device permissions
| Permission | Purpose | If refused |
|---|---|---|
| Notifications | Notifications for new messages, requests, and schedule reminders. The app shows them on the device after syncing | You only miss notifications |
| Camera (iPhone) | Scanning a QR code when moving message keys to a new device | Only QR transfer is unavailable |
| Photos | The app receives only the receipt photos you choose in the system photo picker (it does not request access to your entire photo library) | Only attaching receipt photos is unavailable |
On Android, QR scanning is handled by the Google Play services code scanner, and the app does not request camera permission.
Article 10 Measures to Ensure the Security of Personal Information
- Administrative measures: The number of people who handle personal information is kept to a minimum.
- Technical measures
- All communication is encrypted with HTTPS, and message content is end-to-end encrypted (Article 6).
- Passwords are handled by Firebase Authentication and are not stored on the Company's servers.
- The server verifies the sign-in token and then issues a short-lived session. New accounts must complete email verification before using the server.
- Child-level permissions apply to all records, so people who are not members of that child cannot receive its records. The same permission checks apply to receipt photos.
- Email addresses used to restrict re-registration are stored as hard-to-reverse values instead of the original.
- Encryption keys and secrets are kept in a secure key management service with restricted access.
- Operational logs and alerts keep only the minimum necessary information and do not contain text, receipt contents, or email addresses.
- Message keys on the device are protected with the iOS Keychain and Android Keystore, and message plaintext is not stored in device storage.
- Rate limits apply to key features to prevent misuse.
- Professionals can view records only after the Company has verified their identity, and the server does not send records outside the types and period consented to by all co-parents. A professional sign-in is kept in only one browser and signs out after 30 minutes of inactivity, and the professional web uses a separate origin, strict security settings, and rate limits. Professional sessions are signed with a different key from app sessions, so one cannot be used in place of the other.
- Physical measures: Servers and storage follow the data center security of the processors (Cloudflare, Microsoft, Google).
Article 11 Chief Privacy Officer
The Company designates the following Chief Privacy Officer to oversee the processing of personal information and to handle users' complaints and damages.
Company information: isollet Inc. (주식회사 아이솔렛) · Representative: 김민경 · Address: 경기도 화성시 동탄구 동탄대로 595, 203-115호(영천동), Republic of Korea · Business Registration No.: 207-88-04100
Article 12 Remedies for Infringement of Rights
If you need counseling or relief for an infringement of personal information, you can contact the following organizations (in Korea):
- Personal Information Dispute Mediation Committee (개인정보분쟁조정위원회): 1833-6972 (www.kopico.go.kr)
- Personal Information Infringement Report Center, Korea Internet & Security Agency (개인정보침해신고센터, 한국인터넷진흥원): 118 without area code (privacy.kisa.or.kr)
- Supreme Prosecutors' Office (대검찰청): 1301 without area code (www.spo.go.kr)
- Korean National Police Agency (경찰청): 182 without area code (ecrm.police.go.kr)
If your rights or interests have been infringed by the Company's disposition or omission regarding a request for access, correction or deletion, or suspension of processing of personal information, you may file an administrative appeal with the Central Administrative Appeals Commission (중앙행정심판위원회, www.simpan.go.kr, 110 without area code) under the Administrative Appeals Act (Korea) (「행정심판법」).
Article 13 Effective Date and Changes
- This Policy takes effect on November 9, 2026.
- When content is added, deleted, or modified, the Company announces it in the app and on the website from 7 days before it takes effect. Changes important to users' rights, such as to the items collected, purposes of use, provision to third parties, or overseas transfer, are announced 30 days in advance, and consent is obtained again where necessary.