IYARAE
Privacy Policy
Effective date and version: 2026-11-05
IBRDOS Co., Ltd. ((주)아이비알도스, the “Company”) processes information for IYARAE accounts, AI fiction, reading, cash purchases, public story branches, reader reactions and comments, service-usage statistics and improvements. Contact dev@ibrdos.com for privacy questions, access, correction, erasure, restriction or consent withdrawal.
1. Information and purposes
| Information | Purpose | Retention |
|---|---|---|
| Email, verification data, account/session identifiers, display name, language, 18+ declaration and consent history | Authentication, account management and rights requests | Until account deletion; codes expire after 10 minutes and refresh sessions after 30 days |
| Story title, world, characters, fixed facts, choices and instructions, episodes, branches, visibility and reading entitlements | Writing, editing, reading and preserving branches | Until account or item deletion; previously acquired independent public-story copies follow section 4 |
| Read stories and episodes, text position, episode/story completion and last-reading time | Continue reading, reading history and position sync between devices | Until account deletion; guest reading history is stored on the device |
| Saved story identifiers and public story information; save times and account association for signed-in users | Saving/removing library items and syncing an account across devices | Until removal or account deletion; guest libraries remain only on the device |
| Search terms and filters such as genre, completion, order and language | Searching public stories and returning results | Used to process requests; no separate server-side search history is stored |
| Recent searches on the device, separated by account/guest scope (up to 10) | Repeating earlier searches | Until cleared or app data is deleted; new searches replace older entries. Signed-in device records are also cleared on that device at sign-out or account deletion |
| Account/installation identifier, IP address and server day in view requests; story view totals | View counting and duplicate/abusive-view prevention | No raw IP address or installation identifier in the view-deduplication store; account or IP HMACs: 2 days. Totals without individual associations remain until story deletion |
| Account/story identifiers, like status and last-change time | Showing, cancelling and counting likes | Until account deletion; an unliked state and last-change time remain after cancellation |
| Comment identifier, author account/public display name, text and posting/deletion times | Public comments, author deletion, reports, blocks and safety action | Text removed when the author deletes the comment; deletion metadata, including author association and times, until account or story deletion |
| Comment duplicate, rate-limit and retry-prevention hashes and processing records | Preventing repetitive posts, excessive requests and duplicate submission | Duplicate-text hashes: 24 hours; rate-limit records: 2 days; retry-prevention records: 90 days |
| Generation requests, status, usage and failure data | Queue processing, troubleshooting and cash reservations/refunds | Job status: 90 days; provider request/response and detailed failure records: 7 days |
| HMACs of random installation and account identifiers; random session identifier; type and time of app opens, return visits, completed sign-ups, story opens, choices, generation, purchases and refunds; related story, episode, job and product identifiers, entry screen, choice index, store platform and cash amount | Understanding the path from first use to reading a generated episode, return visits, purchases and refunds; service improvement | 30 days from server receipt. Account-associated records are removed on account deletion. On-device delivery queue: 7 days and at most 40 events; random installation identifier: until app data is removed |
| Store product/transaction identifiers, validation data, cash and reading ledger | Purchase verification, duplicate-credit prevention, balances and refunds | While the account is active, plus statutory transaction retention below |
| Push token, device/session identifiers, notification language/preferences | Requested episode-ready notifications | 90 days from registration/update; disabled or removed on opt-out, applicable sign-out or deletion |
| Report/block targets, reasons and details, support correspondence | Safety, rights complaints and support | Reports: 90 days; blocks until removed/account deletion; consumer disputes: 3 years |
| Minimal security/error records and rate-limit hashes | Security and incident handling | Server logs: 14 days; rate limits until their window expires |
We do not request identity documents or date of birth. The age confirmation is a declaration, not identity verification. We do not request contacts, precise location or health records. Do not include sensitive or unnecessary personal information about yourself or others in story prompts, display names or comments. Your device may retain sign-in tokens, reading preferences and recent content.
View deduplication uses the server day in Korean Standard Time (UTC+9) and distinguishes an account or a guest IP for each story. Account identifiers and IP addresses are transformed with a service-secret HMAC for deduplication. Shared IPs and excessive requests are subject to additional limits. These values remain protected information that may be associated with a person; they are not used to reconstruct the original identifiers.
Saved-story lists and recent searches are not public. For signed-in users, story identifiers and save times are associated with the account for synchronization; guest libraries remain on the device. A saved story’s public information is not displayed in the saved list when it becomes private or its author is blocked, deleted or restricted. The saved record can be removed by unsaving it or deleting the account.
Search filters are sent to the server to query the public catalog, not accumulated as a separate search history or sent to AI. Recent searches are saved on the device when you submit a search or select a search result and can be removed using “Clear all” on the search screen. The existing security/error-record retention in the table also applies to search use.
The Company processes service-usage statistics on its own server. The device stores a random installation identifier, first-open status, the most recent visit day and events waiting for delivery. The installation identifier is transformed with an HMAC before server storage, and a signed-in account is also distinguished by an HMAC. These statistics do not store raw installation or account identifiers, email addresses, fiction text, free-text choices, advertising identifiers, raw IP addresses or browser/device User-Agent strings. Choices are recorded only by their option index. We do not send these statistics to advertising platforms or external analytics services. Existing advertising-SDK processing follows the provider and advertising information below.
2. AI processing and separate consent
Before generation or comment submission, we separately request agreement to AI processing and overseas transfer to OpenAI. Fiction processing sends world settings, characters, fixed facts, earlier episodes and summaries, reader choices, writing instructions and results. Comment submission sends the public display name and comment text for prohibited-content safety checks. We do not automatically include your sign-in email, password or payment details in these requests. AI drafts, edits and checks continuity; its output is not a guarantee of accuracy, rights or literary quality.
Consent version 2026-10-28 applies only to the existing fiction-generation and editing scope. Comment safety checks require agreement to version 2026-10-29, which adds that scope; prior generation consent alone does not authorize sending comments to the provider. Under Article 28-8(1)(1) of South Korea’s Personal Information Protection Act and the notice and renewed-consent requirements in its paragraphs (2) and (3), we disclose the transfer details and purposes and obtain separate overseas-transfer consent.
Generation runs through a server queue. Inputs and jobs may be stored in OpenAI's Responses API. After completion or failure, we request deletion of stored provider responses and retry failures. Deletion can be delayed or fail, and does not erase the provider's security or abuse-monitoring logs. Standard API inputs/outputs are not used for model training unless the Company separately opts into data sharing. Abuse-monitoring logs generally last up to 30 days, subject to legal and safety exceptions. Undeleted stored responses follow the provider's default retention of at least 30 days. See OpenAI data controls.
Comment safety checks use the OpenAI Moderation API. Unlike stored fiction-generation responses, its inputs and results have no abuse-monitoring-log or application-state retention under the provider’s published API rules. The Company manages published comments, deletion, reports and duplicate-prevention records under the table above. See the API-specific rules in OpenAI data controls.
Refusing or withdrawing these consents disables new AI generation and comment submission. Guest access to available public opening episodes, free collections and basic reading remains available. Change consent in settings or contact support. Withdrawal alone does not erase existing public comments; delete the comment or request account deletion if you want it removed. Withdrawal does not undo prior lawful processing or statutory retention.
3. Providers and overseas processing
| Provider/contact | Data and purpose | Location, timing and method | Retention |
|---|---|---|---|
| Amazon Web Services, Privacy | Accounts, fiction, reading/saved libraries, search processing, cash/entitlements, views, likes, comments, jobs, safety records and service-usage statistics; hosting | Seoul, South Korea; encrypted service traffic | Company retention rules; recovery backups up to 35 days |
| OpenAI OpCo, LLC, privacy@openai.com | Creative inputs/context and results for writing, editing and safety checks; comment display name/text for safety checks | United States; encrypted API calls upon generation or comment submission. See subprocessors for additional locations | Fiction: AI retention above, including legal/safety exceptions. Comment Moderation API: no abuse-monitoring-log or application-state retention |
| Resend / Plus Five Five, Inc., Contact | Email address, verification email containing the code and delivery logs | United States; encrypted API calls upon email verification requests | Standard plans: mail/logs 30 days, backups 7 days; provider rules govern legal exceptions and termination cleanup |
| Expo / 650 Industries, Inc., Privacy, Apple APNs and Google FCM | Push token, generic completion message and opaque job/story/episode identifiers | United States and provider infrastructure; encrypted delivery after permission and completion | Expo holds content in delivery memory/queues; device, Apple and Google rules apply separately |
| Google AdMob, Privacy | IP, advertising/device identifiers, ad interactions, diagnostics and consent; ads | United States and other Google infrastructure; encrypted SDK ad requests | Provider policies and applicable consent/ad settings |
| Apple App Store / Google Play | Product, transaction and validation data | Store purchase/verification through global provider infrastructure | Store transaction/refund and legal retention rules |
Email authentication and overseas processing
Resend processes authentication mail as overseas outsourcing necessary to establish and perform the email sign-in service. Under Article 28-8(1)(3)(a) of South Korea’s Personal Information Protection Act, the Company publishes the transferred data, country, timing and method, recipient and contact, purpose and retention, and refusal method, procedure and effects in this Policy. You can review this information through the sign-in screen’s email-processing link or this Policy before requesting a code.
If you do not want this overseas processing, do not request a code; you can continue guest reading. Email sign-in, account-based cloud storage and cash purchases will not be available. To stop using email authentication and your account after registration, request account deletion in the app or contact dev@ibrdos.com. Previously processed authentication mail and delivery records remain subject to the retention periods above and applicable legal requirements.
OpenAI transfer consent is separate, before generation or comment submission. Notifications and personalized-ad/tracking choices are separate from AI consent.
We do not send fiction text or your email as advertising request data. Reader screens contain no ads. Where required, we present advertising consent; iOS tracking follows operating-system authorization. Use privacy/ad settings to revise choices. Basic reading remains usable when ads are unavailable.
4. Private stories and public branches
Stories are private by default. Publishing makes your display name, public story settings/episodes and branch details accessible to other readers, who may acquire reading copies or create branches under the Terms. We request specific confirmation before publishing. Email and sign-in data are not part of the public profile.
Selecting a name on a public story or comment opens an author page with the author identifier, display name, official editorial status and currently public stories. Email, private stories and reading history are not public. Author pages subject to blocking, account deletion or account restrictions are not provided to other users.
Unpublishing or deleting the source stops new access and branches. Independent snapshots already acquired by others may remain. On account deletion, source-author attribution is anonymized. Report or contact support about copies containing personal information or infringing material. Copies exported or shared outside IYARAE cannot be erased automatically.
Sharing images of public stories
You can create a share image containing a public story’s cover, title and author name and, when available, the public original’s title and branch episode. Account email and private manuscript text are not included. You choose an app and recipient through the operating system’s share screen. Processing after transfer follows the selected app’s privacy policy.
Temporary files created by IYARAE to prepare the image are cleaned up when you close the share screen in IYARAE. Manage copies you send to external apps or save separately within those apps or devices.
Views, likes and public comments
Other users can see a public story’s view, like and comment totals. Lists of individual viewers or accounts that liked a story are not public. Posting a comment displays your public name at the time of posting, its text and posting time to other users. Your email is not included in public comment information.
You can delete your own comments. Reported comments may be restricted or removed after review, and blocking an author also limits display of that author’s comments. Once an account-deletion request is verified, its comments stop being displayed. Erasure then removes their text and author associations and the account’s likes, updating the related totals. Report or contact support about personal information or rights violations in comments.
5. Erasure and statutory retention
Request deletion in Account or through the external deletion page. After verification we remove the account, email mapping, sessions, private stories, jobs, notification registrations, public comments, likes, saved-story records, account-associated service-usage statistics and public source visibility, retrying failed cleanup. Recovery backups may contain earlier data for up to 35 days; deletion requests are reapplied after a restore.
Under Article 6 of Korea's Electronic Commerce Consumer Protection Act Enforcement Decree, contract/withdrawal and payment/content-supply records are retained for 5 years; consumer complaints/disputes for 3 years. Minimal required records are separated from ordinary profiles/fiction and used only for the relevant legal or dispute purpose. Opaque purchase anti-reuse associations are retained with minimal transaction records for 5 years. Deletion markers and welcome-gift email HMACs expire on a 180-day threshold. They do not retain original emails or fiction. Expiry cleanup is asynchronous, not a promise of physical deletion at an exact instant.
6. Rights, safeguards and contact
Account exports include saved story identifiers, save times and account-associated service-usage statistics. Device-only recent searches and guest libraries are not part of server account exports and are managed on the relevant device.
You may request access/copies, correction, erasure, restriction and withdrawal. Rights to object, portability or supervisory complaints may apply where you live. We may ask for minimal account verification to prevent unauthorized changes. If a legal limitation applies, we explain its reason and scope.
We use encrypted transport, restricted storage access, authentication checks, minimized operational logging and backup access controls. Registration and generation require age 18+. Contact support if you suspect an underage account or improper collection.
Operator/privacy contact: IBRDOS Co., Ltd. · Representative Taewoong Ra · dev@ibrdos.com · +82-70-4589-9109. Address: Room 618A, 6F, 326 Wangsimni-ro, Seongdong-gu, Seoul, South Korea. Business registration 829-86-02325; mail-order business registration 2026-Seoul-Seongdong-0450. We announce policy changes and their effective date and request renewed consent where needed.