1 Operator and scope
1.1 Your Neverland HK Limited is responsible for the InStory personal information processing described here and acts as the business or controller under applicable United States state privacy laws. State or country of incorporation: HONG KONG. Contact address: Suite 6503, 65/F, Central Plaza, 18 Harbour Road, Wan Chai, HONG KONG. This Policy applies to the app, website and story, AI interaction, creation, community, messaging and points services offered to United States users.
1.2 "Personal information" includes information that identifies you, relates to you or is reasonably linkable to you or your household, and personal data as defined by applicable law. We process necessary information only for functions you use and the purposes below. This Policy is not blanket consent to undisclosed uses. Independent third-party services have their own policies; our disclosures to them remain governed by this Policy.
1.3 This Policy distinguishes information you provide directly, information supplied automatically by devices, and information from sign-in, payment, other users and similar sources. A function not available to you does not result in collection merely because it is described here. New categories or incompatible purposes are specifically disclosed before processing, with required consent. You may request an accessible format by emailing chancechang000@gmail.com.
2 Information categories and purposes
2.1 Account and profile: depending on your chosen and available registration method, we process your email, verification-code result, Apple or Google sign-in identifier, identity token, and authorized name or profile information for registration, login and security verification. Nickname, avatar and biography identify or describe the account. We process your full date of birth; gender and interests support the profile and preference functions you choose. Additional identity information is requested only where legally required or necessary for verification, with an explanation before collection.
2.2 AI and person-to-person communications: for AI chats and resonance conversations, we process the text, images, audio, video, current scene and relevant history needed to generate replies and organize requested stories. For direct and group messaging, we process conversation identifiers, participants and membership changes, message content and attachments, timestamps, delivery and read status, unread counts, subscriptions, searches, highlights and message-clearing actions. Context sent to an AI model is limited to what is needed for the current request. Translation occurs only when you request or enable it.
2.3 Creation and materials: we process photos, audio, video, prompts, scripts, editing instructions, generation settings and results that you select and upload to generate, edit, save and publish works as instructed. Photo-library permission does not authorize us to read your entire library; we do not actively extract photo location metadata unrelated to the request. Without uploaded materials, the corresponding creation function cannot be completed, but other functions remain available.
2.4 Community, privacy settings and sharing: we process works, comments, likes, saves, following relationships, blocks, audience settings, follow-list visibility, discoverability and recommendation choices, and sharing actions for display, interaction and enforcement of your settings. Public content, nicknames and avatars can be viewed by the corresponding audience; private materials and private conversations are not automatically made public. When you share through an external platform, the content and necessary links you select are provided to that platform and may be saved or forwarded by recipients.
2.5 Points and transactions: we process order identifiers, products, amounts, currencies, point changes, transaction times, payment channels, payment status and refund records to deliver entitlements, reconcile accounts and resolve disputes. Payment credentials are handled by the relevant channel through its processes; we do not ask you to submit bank-card passwords, payment passwords or verification codes in chats. Specific payment recipients are listed in Appendix A.
2.6 Security, device registration and operation: we process IP addresses, device model, operating-system and app versions, language, time zone, identifier for vendor (IDFV), request times, necessary session identifiers, and error and security logs for connectivity, protection and troubleshooting. If you separately authorize tracking through iOS, the advertising identifier (IDFA) may be transmitted for authorized app measurement, attribution and fraud prevention; we do not use it to sell personal information or for cross-context behavioral advertising. To deliver notifications, we process an app identifier, device identifier and push token until the token is invalidated, notifications are disabled, or the account or device registration is removed. General product analytics, if enabled, excludes raw chats, original photos, prompts, precise location and payment credentials.
2.7 Support, reports and safety assistance: we process support requests and privacy requests, contact details, reported content identifiers, selected report reasons, descriptions, locale, client request identifiers and up to four evidence media items to investigate complaints, enforce rules, prevent abuse and respond to rights requests. When you block an account, the block request identifies your account and the blocked account so we can record and enforce that relationship. Blocking alone does not submit a particular post, comment, video or evidence as a content report. When you submit an in-app report, its content identifier, reason, description and evidence are sent to us for safety review; we may also use block records to identify potential abuse. We do not disclose the reporter's identity or private evidence to the reported user merely because a report was filed or an account was blocked. Safety systems may process relevant conversations and risk signals to limit harmful outputs, provide crisis resources or support necessary human review; this is not diagnosis and does not guarantee detection of every risk. We disclose only the minimum necessary information to assistance providers when you request it, validly authorize it, or an emergency disclosure is permitted or required by law.
2.8 We may receive account identifiers and authorized profile data from your chosen sign-in provider, payment, refund or fraud-review status from payment channels, and posts, mentions or complaints concerning you from other users. Receipt from a third party does not automatically authorize advertising, training or sensitive profiling. Nonusers may also make privacy or personal-rights requests concerning information about them on the platform.
2.9 Media processing may identify text, objects, scenes, speech or person locations needed for generation, captions and safety review. This is not equivalent to building an identity faceprint or voiceprint database. Biometric processing for identification occurs only when actually needed for the relevant function and after specific notice and authorization. We do not continuously read keystroke rhythms, contacts or unrelated files on your device.
2.10 The relevant saving or generation step explains whether drafts are stored on the device or in the cloud. Requesting cloud generation transmits the selected input even if it is never publicly posted. We do not treat other unsubmitted edits or the entire clipboard as default uploads. Feedback such as disliking content processes only the explained feedback data; if accompanying chat excerpts are sent for human review, their scope is explained.
2.11 Voice input and recording: when you record a voice message or video, the app temporarily stores the recording and uploads it only when you choose to send or submit it. When you use video-prompt dictation, microphone audio, selected language and partial or final transcripts are processed through Apple Speech Recognition. Cancelling an unsent recording removes the temporary recording from the app’s working storage, subject to operating-system temporary-file behavior.
3 Memory and personalization
3.1 When you enable long-term memory, we may create summaries from relevant conversations, facts you confirm and preferences for later interactions and story creation. Assessments of emotions, relationships and interests are potentially inaccurate inferences, not objective facts or evidence that you authorized disclosure. You may request access, correction or deletion of memories and disable future memory generation; disabling the function does not delete existing records. The scope of memory deletion and original-chat deletion will be explained separately, and you may request both.
3.2 If personalized recommendations are enabled, they may rank content or characters using selected interests and viewing, interaction, following and saving history. You may disable personalization, choose non-personalized content and manage tags; general recommendations may still appear. We do not exploit inferred emotional vulnerability to manipulate purchases or use story preferences or chat analysis for eligibility decisions in credit, employment, housing, insurance or other matters with legal or similarly significant effects. Statutory profiling and automated-decision rights are described in section 11.
3.3 We do not sell personal information, "share" it for cross-context behavioral advertising, or process it for cross-site or cross-app targeted advertising. "Sale" and "sharing" have the meanings given by applicable state law and are not limited to cash transactions. Private conversations, unpublished materials, long-term memories, consumer health data and biometric information are not provided to advertisers. Before changing these practices, we will update specific disclosures and choice mechanisms and obtain legally required consent, without retroactively expanding existing permissions.
3.4 Profiles, chats, memories and recommendation records may be linked through the same account to provide Services you choose, using only relevant and necessary data. Deleting an inaccurate memory does not automatically change a published work, and withdrawing a public work does not automatically delete its source chat. You may expressly request handling of these records together, and we explain scope and retention exceptions.
3.5 We do not build advertising audiences from private chats or sensitive inferences such as health, sexual orientation or religion. If creator analytics are offered, they generally show aggregate viewing and engagement metrics, without revealing viewers’ private chats or sensitive inferences. Statistics presenting identification risks remain protected as personal information and are not made public merely by being called “statistics.”
4 Sensitive information and device permissions
4.1 Chats and materials may contain sensitive information such as health, sex life or sexual orientation, religious beliefs, race or ethnicity. Facial geometry for identification, voiceprints, government identification numbers, account credentials or precise geolocation may also receive special protection. Before processing sensitive information for a purpose beyond providing the function you request, we explain the specific purposes, categories, recipients and retention and obtain affirmative, separate or written consent required by applicable law. Optional sensitive processing can be refused or consent withdrawn without limiting unrelated functions. Consumer health information voluntarily included in a chat or material is subject to the same purpose, disclosure, security, deletion and non-sale restrictions in this Policy.
4.2 If facial, voiceprint or real-person verification is enabled, specific written disclosures and legally required written releases must precede collection or derivation of biometric identifiers; uploading a photo or accepting this Policy does not replace that release. We do not sell, lease, trade or profit from biometric data itself, or use verification data for advertising, emotional profiling or model training. Data subject to Illinois BIPA is permanently destroyed when its initial purpose is satisfied or within 3 years of your last interaction with us, whichever occurs first; absent a valid court warrant or subpoena, we follow that deadline, with any shorter period under other law or Appendix B applying. Disclosures occur only under valid authorization or another statutory exception.
4.3 Photo-library or file access enables your material selection; the camera supports photo and video capture you initiate; the microphone supports voice messages, video recording and dictation you initiate; speech-recognition permission supports conversion of spoken prompts into text; notification permission supports messages or task alerts you choose; tracking permission controls access to the IDFA. Development or test builds may request local-network access to connect to an explicitly configured local chat server, but production services do not scan devices on your local network. Permissions may be withdrawn in system settings. Accepting this Policy does not grant access to contacts, precise location or continuous background recording.
4.4 Before supplying materials depicting another person, inform them and obtain required permission. Performance authorization records verify the permitted story, purpose and scope and do not automatically authorize collection of biometric identifiers. The person concerned may contact privacy or safety channels to request verification, correction or cessation of unauthorized processing. We do not reject applicable rights requests solely because another user uploaded the material.
5 Model processing and training
5.1 AI replies or works require relevant model providers to process necessary inputs and context. Appendix A identifies the current provider categories and named platform providers; the relevant feature notice identifies a contracted model provider, processing location and retention arrangement when applicable law requires that detail before use. Providers may not use entrusted data for unauthorized independent purposes. Sensitive information, biometric information and consumer health data must also meet applicable consent requirements and restrictions; sending an ordinary chat does not authorize other purposes.
5.2 By default, we do not use private conversations, uploaded materials, generated content or long-term memories to train or fine-tune general-purpose models, and we do not allow contracted providers to use them to train their own general-purpose models. Any optional training programme for non-sensitive content requires separate disclosure of the data, purposes, models, recipients, retention and withdrawal method and an independent affirmative choice; declining does not affect basic services. Consumer health data and biometric verification data are excluded from such training programmes. Processing context for inference is not training.
5.3 Necessary human access may support requested troubleshooting, safety review and lawful investigations, with role-based authorization and access records. Human review is not routine reading of all chats and does not automatically authorize adding content to training datasets. Identifiable quality-evaluation samples require disclosed purposes, necessary scope and any choices or consent required by applicable law.
5.4 If you join future optional training, you may withdraw from further participation. We will stop new training use and address retained source data. Applicable deletion or other rights concerning information in existing models must still be handled. We will neither promise item-by-item removal from model parameters without confirmed capability nor use that limitation to avoid legal duties. The specific arrangements must be explained before participation.
6 Storage technologies and privacy choices
6.1 Local storage and necessary session technologies retain account and onboarding state, encrypted session credentials, profile information, language and translation preferences, privacy settings, chat messages and delivery state, pending message attachments and uploads, creation entry settings, post drafts, recent creation records, image caches and video playback caches. These records support offline display, retries and playback. Clearing cache may remove downloaded media without deleting server content; clearing a conversation, signing out, deleting local drafts and deleting an account have different effects as explained at the relevant action. Account credentials are stored using protected device storage where available.
6.2 We process information according to the functions you request, your choices and applicable United States law, without treating acceptance of terms as unrestricted permission to use data. As required by law, we recognize and honor universal opt-out signals such as Global Privacy Control (GPC) as requests to opt out of sale, sharing or targeted advertising; although we do not currently conduct these activities, we do not circumvent such signals. Traditional Do Not Track signals do not trigger an additional mechanism, without affecting compliance with GPC or other recognized signals. Marketing emails may be stopped through unsubscribe links; necessary service and security notices are not marketing emails.
6.3 Necessary technologies support sign-in, network requests, security, media selection and caching, language, notifications and transactions. The current provider and SDK register appears in Appendix C. The app does not include a third-party advertising or general behavioral-analytics SDK. Refusing optional permissions does not affect unrelated services, but disabling necessary local storage may prevent sign-in, messaging retries or draft functions. Browser choices do not necessarily change settings on other devices or within the app.
6.4 You may separately manage follow-list visibility, discoverability, blocks, recommendations, notifications, tracking permission and other available choices in the app or iOS settings. You can block an account from its profile or conversation options and review blocked accounts in privacy settings. To ask us to investigate a particular post, comment or video, use the in-app Report option and provide the relevant reason and optional evidence. For abuse involving an account or content without an available Report option, contact chancechang000@gmail.com and identify the account or content. Blocking is a personal safety control; it does not by itself delete that user's content for everyone or remove copies already saved outside InStory. If an interface is unavailable, email the same address. We will lawfully honor requests and will not suspend your rights merely because a settings control is temporarily unavailable.
7 Processors and external disclosures
7.1 To provide the services, we disclose necessary information to providers performing hosting, content delivery, model inference, safety review, identity verification, payments, login, notifications or support, with categories and the specific register in Appendix A. Processors are contractually restricted as to purpose, confidentiality, security and retention and must assist with rights requests as required by law. Independent login or payment providers process necessary information for their disclosed purposes. We do not provide complete chats or materials to every provider; each receives only what its actual function requires.
7.2 Apart from public or external sharing you choose, we disclose necessary information only for purposes permitted by applicable law, including verifying valid legal process, protecting lawful rights, addressing safety or fraud incidents, and providing assistance in lawful and necessary emergencies. If a merger, acquisition or asset transfer involves data, recipients remain subject to applicable law and existing commitments; material changes in purpose require further notice and consent where required. Stricter rules for health and biometric information continue to apply.
7.3 Public disclosure follows your chosen audience; service-provider processing is not publication. If collaboration or external sharing enables others to access works, materials or specific profile information, we explain the scope at the action. Independently saved copies may be controlled by recipients; you may still request handling of information within our control and report unlawful recipient uses.
7.4 Disclosures within a corporate group must also have a specified purpose and necessary scope; affiliation does not automatically grant access to all information. Current recipient categories and known platform providers are listed in Appendix A. Consumer health information, biometric information and other sensitive information are not disclosed to affiliates for advertising or unrelated profiling. Deidentified information is handled under applicable law with safeguards against reidentification and corresponding recipient restrictions.
8 Storage locations and retention
8.1 Offering services in the United States does not mean that all information is processed only in the United States. Primary service storage, hosting and backup locations are in the United States. Remote support or model processing may occur in another jurisdiction where a contracted provider operates; the relevant feature notice identifies the location when applicable law requires disclosure before processing. Processing outside the United States may be subject to different privacy laws and lawful government access requirements; we apply contractual and security measures required by applicable law. We do not rely on this Policy or user consent to bypass United States data-access, national-security or other data-transfer prohibitions.
8.2 Information is retained for the shortest period necessary for its purpose, with category-specific periods in Appendix B. After account deletion, a deletion request or completion of a purpose, we delete or anonymize the corresponding information; legally required retention is limited to necessary records, with other processing restricted. Data that cannot immediately be deleted individually from backups is isolated and removed within the backup rotation period, without reuse in ordinary services; deletions are reapplied after backup restoration. De-identified data may still be personal information and is not equivalent to anonymized data.
8.3 Retention depends on functional needs, whether you retain content, dispute handling, legal retention requirements and security risks, rather than keeping data indefinitely because it “might be useful.” Legally preserved evidence is separated from ordinary-use data, used only for preservation purposes and subject to applicable deletion once the basis ends. Account deletion does not require erasing legally mandated transaction records, but does not permit continued recommendation or marketing use of them.
9 Security and your rights
9.1 We apply transmission protection, access controls, permission reviews and incident response measures appropriate to the risk; human access to content is limited to necessary support, safety or legal-duty scenarios and is logged. If a personal information security incident occurs, we take remedial measures and notify users and authorities as required by law, explaining the impact, response and available protective steps.
9.2 All United States users may request access, copies, correction or deletion of personal information, disable memory or personalization, withdraw relevant consent, or delete an account through the app’s account-security settings or by emailing chancechang000@gmail.com. Requests do not require a new account; existing account holders may use their account for appropriate verification. We verify only information proportionate to the request’s risk and do not request account passwords. Additional state-law rights and appeals are in section 11.
9.3 We respond to general rights requests within 45 calendar days, or a shorter period required by applicable law. If an extension is necessary and legally permitted, we explain the reason and new deadline within the original period. Opt-out requests follow any applicable shorter deadline. Ordinary reasonable requests are free; any legally permitted fee or refusal is explained. Deletion may not apply to limited records that must or may lawfully be retained; we explain exceptions and restrict later uses, with specific health-data rules taking precedence. Withdrawal does not affect prior lawful processing but may stop optional functions dependent on the information.
9.4 Request verification normally uses an existing account or contact information already held. High-risk access to specific information may require stronger verification to avoid disclosure to an impostor. Verification materials are used only for verification, security and legal obligations and deleted after the necessary period. If verification fails, we explain why and what appropriate additional information may help, without requiring unrelated sensitive details.
9.5 Portability requests provide data you are entitled to receive in a commonly used, machine-readable form where applicable, while protecting other people’s information and legally protected security information. Disabling a function, clearing device cache, deleting one item and deleting an account have different effects. We act on your actual request and do not require account deletion as a condition of correction, opting out or deleting an individual item.
10 Age restrictions and policy updates
10.1 The services are for users at least 18 years old who meet their state’s legal age for independent contracting and are not intended for minors. We process the date of birth supplied during registration or profile editing to enforce this requirement. If we discover that an ineligible minor’s information was collected, we promptly restrict the account, delete or otherwise handle the information as required by law, and provide a review channel. Parents or guardians may email chancechang000@gmail.com.
10.2 We review and update this Policy at least every 12 months and prominently notify you of material changes, explaining the changes and effective date; processing requiring new consent begins only after obtaining it. You may save and review policy versions. This published version governs the United States service in English; any translated convenience copy must provide protections consistent with this version and applicable law.
11 United States state privacy rights
11.1 Depending on your state of residence and whether the relevant law applies to us, you may have rights to confirm processing, access, copies and portability, correction, deletion, information about data recipients, and opt-outs from sale, sharing, targeted advertising and certain significant-effect profiling or automated decisions. Some states also require prior consent for sensitive processing or allow limits on its use and disclosure. We honor each applicable requirement in effect without reducing these rights through this Policy.
11.2 Where CCPA / CPRA applies, California residents may request the categories and specific pieces of information collected, used, disclosed, sold or shared, source categories, business or commercial purposes and recipient categories; request deletion and correction; opt out of sale or sharing; and, where applicable, limit use and disclosure of sensitive information. We do not unlawfully deny service, charge different prices or reduce quality because you exercise rights. Our commitments against sale, sharing and cross-site targeted advertising are in clause 3.3; we do not knowingly sell or share information of anyone under 16.
11.3 Submit a privacy request through the app’s available account or privacy controls, or email chancechang000@gmail.com with the subject "Privacy Request". Authorized agents may use the same channel with reasonable proof of authority; we verify directly with you when necessary. Opting out of sale, sharing or targeted advertising does not require the identity verification used for ordinary access requests. Recognized opt-out signals such as GPC are handled under clause 6.2 and apply to the relevant browser, device or linkable account as required by law.
11.4 If a request is denied, email chancechang000@gmail.com with the subject "Privacy Appeal". We provide a written outcome and reasons within 45 calendar days, or a shorter legally required period. If the appeal is unsuccessful, we explain how to complain to your state attorney general or other competent privacy regulator. This appeal channel is also available to United States users without a statutory appeal right and does not limit other legal remedies.
11.5 Privacy requests will not result in unlawful retaliation or differential treatment. If we offer a financial-incentive program in exchange for voluntarily supplied personal information, we provide a separate notice before enrollment describing categories, enrollment and withdrawal methods, material terms and any legally required data-value estimation method. Withdrawal may end the corresponding benefit without affecting other statutory rights.
11.6 California residents may also contact the privacy email about applicable direct-marketing disclosures. We do not provide personal information to third parties for their independent direct marketing. Applicable state rights may vary by residence, processing activity and legal exemptions. If we deny a request, we explain the actual basis rather than merely stating that “the law does not apply.”
12 Notice at collection and California category disclosures
12.1 This section must be available before or at collection. Depending on the functions used, we collect the following categories, with specific purposes in sections 2 through 7 and retention criteria in section 8 and Appendix B: identifiers and account contact information; voluntary profile information such as age and gender; commercial information such as orders; internet activity and device information; text, photos, audio and video you submit; and preference and memory inferences. Sensitive categories are processed only for enabled functions and where legal conditions are met, including sensitive chat content such as health information, account credentials and identity-verification information.
12.2 Sources include you, your device and service activity, login and payment providers you select, collaborators you authorize or other users who post content involving you, and system inferences from those sources. We do not purchase personal dossiers from data brokers or collect employment or education records for the services. If you voluntarily include such information in content, it is handled as user content subject to relevant sensitive-information restrictions.
12.3 Business disclosures follow the minimum necessary scope: account information to login, security, hosting or support providers; order information to payment, accounting and support providers; internet activity to operations, security and enabled analytics providers; content and inferences to model, storage, delivery and review providers needed for the request; and verification information only to necessary verification and security providers. Other users see only what you choose to post or share with them. Legal-disclosure recipients and transaction successors are addressed in clause 7.2. None of these categories is sold or shared for cross-context behavioral advertising.
Appendix A — Service providers and recipients
A.1 Apple Inc. and its affiliates provide Sign in with Apple, Apple Push Notification service, Apple Speech Recognition and App Store / StoreKit payment functions. Depending on the function you choose, Apple may process an Apple account identifier, identity token, authorized name, device push token, microphone audio and transcript, app and device information, product and transaction identifiers, purchase status and refund status. Apple acts under its own terms and privacy policy for its independent services and as a platform provider for functions integrated by InStory.
A.2 Google LLC and its affiliates provide Google Sign-In. Google-authorized profile information, Google identity and access tokens and sign-in status are processed to authenticate the selected Google account. Firebase Authentication, a Google service, exchanges the Google credential for a Firebase identity token that InStory sends to its account service. InStory does not receive the user’s Google password.
A.3 Cloudflare, Inc. and its affiliates may provide website hosting, delivery, DNS, network-security and content-delivery functions for InStory web properties. These services may process IP address, browser and device information, requested URL, request headers, timestamps and security events for delivery, abuse prevention and troubleshooting under configured retention controls.
A.4 InStory’s contracted infrastructure, storage, upload, content-delivery, customer-support, safety-review and AI inference providers receive only the account, request, content or technical data necessary for the enabled function. AI inputs can include prompts, selected conversation context and media you submit; outputs and task status are returned to InStory. The provider can vary by the model and feature displayed in the app. Before a new provider processes sensitive information or uses data for a materially different purpose, we provide specific notice and any required choice or consent. Contracted providers may not use entrusted private content to train their own general-purpose models.
A.5 Other users and external sharing recipients receive information only according to the audience or sharing action you select. Courts, regulators, law enforcement and emergency recipients receive information only when disclosure is lawfully required or permitted as described in section 7.
Appendix B — Retention schedule
B.1 Account, profile, settings, blocks and social-relationship records are retained while the account is active. Following a verified account-deletion request, ordinary-service copies are deleted or anonymized within 30 days, except for records subject to a legal hold, fraud investigation or legally required retention. Backup copies are isolated from ordinary use and expire through the backup cycle, normally within an additional 30 days.
B.2 Chats, message metadata, uploaded materials, saved creations and published content are retained until you delete the relevant item or account, the applicable conversation or feature expires, or the service no longer needs the record to provide the requested function. A cleared conversation stops ordinary display for the requesting account; recipient copies, lawful moderation records and backup copies may follow separate deletion timelines described at the action.
B.3 Pending uploads, unsent attachment files and creation or post drafts stored on the device remain until sent, deleted, cleared, replaced or removed during sign-out/account cleanup. Image and video playback caches remain until evicted by storage limits, cleared through app settings or removed by the operating system. Temporary cancelled recordings are deleted promptly from app-controlled temporary storage.
B.4 Push tokens and associated device registrations are retained until invalidated, replaced, notifications are disabled and the registration is removed, or the account is deleted. Authentication and active-session credentials remain until expiration, sign-out, revocation or account deletion. Operational, request, error, device and security logs are normally retained for no longer than 12 months unless a shorter period is sufficient or a longer period is necessary for an active security investigation or legal duty.
B.5 Payment, point-ledger, refund and tax records are retained for the period required by applicable accounting, tax, consumer-protection and anti-fraud laws, generally up to seven years. Report, moderation and safety records are normally retained for two years after resolution, and privacy-request verification and response records for 24 months, unless an active dispute, repeat-abuse prevention need or legal obligation requires longer preservation.
B.6 Data sent to an integrated platform or contracted provider follows the shorter of the provider’s contracted deletion period and the period needed for the requested function, subject to independent legal duties. We periodically review retained records and delete or anonymize information when the stated purpose and any lawful retention basis end.
Appendix C — App technologies and SDK register
C.1 Apple system frameworks: AuthenticationServices supports Sign in with Apple; APNs supports notifications; Speech and AVFoundation support dictation, voice messages and media capture; StoreKit supports point purchases. Data, purpose and retention are described in clauses 2.1, 2.5, 2.6 and 2.11 and Appendices A and B. These functions are necessary only when you choose the corresponding service.
C.2 Google Sign-In and Firebase Authentication support optional Google account login. They process login tokens and authorized profile information only when you choose Google login. Authentication state lasts until sign-out, token expiry, revocation or account deletion, subject to provider security records.
C.3 Alamofire and Moya perform app network requests; Kingfisher caches displayed images; KTVHTTPCache caches streamed video; ZLPhotoBrowser and YPImagePicker present device media-selection interfaces. These libraries operate within the app and do not independently receive personal information merely because they are included. Network destinations, selected uploads and local cache retention are controlled by InStory as described in this Policy.
C.4 The current app does not include a third-party advertising network or general behavioral-analytics SDK. IDFA is read and transmitted only when iOS reports that tracking permission is authorized, as described in clause 2.6. We will update this register before enabling a new SDK that independently receives personal information for analytics, advertising or another materially different purpose.