Qoril logoQoril
Updated 22 October 2026
Edition 04
Cord craft · Maker care

Privacy Policy

How sign-in, craft records, connected services and Thread Token purchases use your information.

User Agreement
THREAD 01

Who is responsible

This Privacy Policy explains how Qoril handles information for sign-in, cord-craft lessons, maker profiles, craft notes, Circle interactions, Thread Tokens and connected web features. “Qoril,” “we” and “us” refer to the publisher identified on Qoril’s App Store product page. For privacy questions or requests, contact support@qoril.app.

This policy covers Qoril’s app and connected services. Apple, your email provider and external websites also apply their own privacy policies to their services.

THREAD 02

Sign-in and account identity

For quick sign-in, the app generates and persists a random UUID. It sends this same app-generated identifier for authentication and request identification. This identifier is not your advertising identifier or a hardware serial number.

When you choose Sign in with Apple, the app receives and sends your Apple identity token, authorization code and Apple user identifier to the authentication service. It does not receive your Apple password and does not request your name or email address from Apple.

The app stores the resulting account identifier and session credential to keep you signed in. Authenticated requests use these credentials, with application, channel, platform and version configuration where required. Account requests to the auxiliary data service also include your account identifier and session credential.

The app’s sign-in requests do not include IDFA, IDFV, device model, operating-system version, system language or time zone. The app’s language preference is used locally.

THREAD 03

Profiles, craft notes and Circle

You may provide a maker name, biography, avatar and profile voice recording. When you create or edit a craft note or Circle post, the app handles its title, text, selected image or audio, tags and category. Replies, likes and favorites are associated with your account.

Profile changes, posts, replies and interaction records are sent to connected services to save and retrieve them. Published posts and replies, together with associated maker details and attached media, can be shown to other users. Drafts are stored for your account and are not published as Circle posts merely because they are saved.

Blocked-maker selections, hidden-content choices, reports and the reasons you enter are sent to the auxiliary account service and saved for your account. Submitting a report records the concern; it does not guarantee an immediate review or response. For a concern requiring direct support, email us.

Avoid including identity documents, private addresses or other unnecessary sensitive information in posts, images, recordings or reports.

THREAD 04

Learning, drafts and practice timers

The auxiliary account service stores saved guides and tips, favorites, learning progress, completion status, practice-timer records and draft content. We use these records to provide your workspace, resume lessons and retain your choices.

The app also keeps account-specific display caches and unsynchronized drafts on your device. When available, cached content is displayed while the app refreshes from the server. Unsynchronized changes can remain locally if a request fails and may be sent when you retry or resume synchronization.

Signing out preserves saved records. Removing the app does not itself delete records already held by the services.

THREAD 05

Photos, camera, microphone and uploads

Photo selection is used for an avatar or craft image. Camera access is used when you choose to take a photo. Microphone access is used when you start a profile or craft-note voice recording. Recording does not start simply because you open the app.

When you save profile changes or publish content containing local media, the app uploads the relevant files to the media service and stores the returned media addresses with the profile or post. An upload may complete before the associated profile or post is successfully saved. Media selected for an unfinished action can also remain in local storage.

Uploaded media is served through Qoril’s media/CDN infrastructure. People who receive a media address may be able to access the file; do not use uploaded content to store confidential material. Images and recordings may reveal people, surroundings or embedded metadata.

You can decline permissions or change them in iOS Settings. Denial may prevent the corresponding media feature from working. Selecting a photo does not authorize browsing your entire library. Qoril does not request contacts, precise location, health information or advertising-tracking permission.

THREAD 06

Purchases, Thread Tokens and unlocks

Apple processes in-app payments. Qoril receives product and transaction information and an App Store receipt, rather than your payment-card number or Apple password.

The app sends the receipt, product identifier, transaction identifier and relevant purchase context to the primary service for purchase validation. After that service accepts the purchase, the app sends the product and transaction identifiers to the auxiliary account service to credit Thread Tokens.

The auxiliary service records your balance, credited purchases, transaction identifiers, spending and unlocked content. It uses transaction records to prevent duplicate credit and records deductions with unlocks. This auxiliary ledger relies on the app’s report of primary-service validation; it does not independently validate Apple receipts.

The app retains local pending-purchase and recovery records, including purchases accepted by the primary service but not yet credited by the auxiliary service, so an interruption does not lose the record. Uninstalling the app or closing an account does not cancel an Apple transaction or constitute a refund request.

THREAD 07

Connections and connected web features

The app communicates with authentication, startup, purchase-validation, media and auxiliary account/content services. These services receive the request data needed for the action, such as account and session identifiers, your app-generated UUID, submitted content and purchase information. Servers receiving an internet request also receive the connecting network address.

When a connected page is opened, the app can pass account/session authentication information so the page can provide the signed-in service. Web connections use authentication, heartbeats, acknowledgments and service events to maintain the session and handle updates. Embedded pages can use WebKit cookies and website storage.

The app handles foreground/background and connectivity changes to manage connections. Connected functions can send service-operation events, product/price information and camera or microphone permission results to the primary service. These support the connected feature and its operation. The app does not monitor screenshots or screen recording.

The current app does not integrate advertising networks or third-party behavioral analytics. We do not sell personal information or use it for cross-company advertising tracking. External destinations you visit handle the visit under their own notices.

THREAD 08

Storage, recipients and retention

Your information is distributed between your device, the primary services, the auxiliary account service and media storage/CDN. App caches, unsynchronized drafts, session information, local migration backups and purchase-recovery records may remain on your device. The auxiliary service stores account profiles, workspace and community records, reports and the Token ledger. Uploaded files are stored separately from those account records.

Apple receives information needed for its sign-in and payment services. Hosting, storage and delivery infrastructure processes information to operate the connected services. If you email support, the email providers involved and the support recipients receive your message and attachments. Published material is shared with its audience.

Saved records remain until removed through supported controls or handled through a deletion request. The current implementation does not apply a single automatic expiry period to account records, uploaded media or transaction history. Backup and migration copies may remain separately from active records. We may need to retain relevant information to address a dispute, prevent duplicate purchase credit or meet applicable recordkeeping obligations; contact us about the records relevant to your request.

We may disclose information where required by binding law or necessary to address misuse, protect rights or carry out a lawful organizational transfer. Do not assume that removing an app screen or a cached copy also deletes the server record or uploaded file.

THREAD 09

Your controls and account deletion

Use the available app controls to edit your profile, delete eligible posts or replies, manage saved items and blocked makers, and clear a draft. Permission changes are available in iOS Settings. Signing out is not a deletion request.

Me → Account → Delete account requests closure from the primary account service. After that service confirms closure, the app signs out, removes the account’s active local profile/workspace state and requests cleanup of the account’s records held by the auxiliary account service.

The auxiliary cleanup removes the active account profile, drafts, learning progress, timers, saved items, block/hide choices, reports, Token balance, purchase/spending history and unlock records in that account’s active record. It also removes the account’s authored posts and replies and associated interaction records handled by the service. Content already copied or exported by others is outside this account-cleanup operation.

If auxiliary cleanup is interrupted, the app retains the cleanup request and confirmation state so it can retry when reopened with a connection. Closure of the primary account is not proof that every auxiliary operation has already completed. While cleanup is pending, some account records can remain on the auxiliary service.

Uploaded image, audio and other media files are stored separately. Removing an account record, post or media reference does not automatically erase the underlying uploaded file from server storage or a delivery cache. Existing media addresses may remain accessible while those files are retained. Backups, exported copies and separately held support correspondence are not automatically removed by the active-account cleanup.

Limited transaction de-duplication, deletion-confirmation and retry records can remain after active account cleanup to prevent repeat Token credit and complete or confirm deletion. These are distinct from an active maker profile or an available Token balance. We do not state a single automatic expiry period for every such record or backup.

For uploaded-file removal, remaining records, a pending cleanup or a question about retention, contact support@qoril.app. Identify the account and relevant content or media address, preferably before closing the account when that information is still available to you. Do not send passwords, session credentials or identity tokens. We may need proportionate verification to identify the right records and will explain any retention limitation that applies.

You may also request access, a copy, correction, restriction, portability or object to processing where applicable. Withdrawing a permission affects future access; it does not recall information already submitted. Copies exported by you, other users’ copies and operating-system backups must be managed separately.

THREAD 10

Processing purposes, security and policy updates

We process sign-in, workspace, publishing and purchase data to provide the functions you request. Optional media access depends on your choice and, where required, consent. Support, service protection and dispute handling may rely on legitimate interests where permitted; legally required processing relies on the relevant obligation. A general agreement checkbox is not blanket consent to unrelated advertising or tracking.

The app uses platform permission controls, Keychain for designated secure records and protected network connections for its configured service endpoints. No system guarantees absolute security. Keep your device secure and avoid placing confidential information in public content. Your data may be processed wherever the relevant service infrastructure operates; contact us about locations and safeguards relevant to your information.

Qoril is intended for people aged 16 or older. If you believe a child below 16 has supplied information, contact us. Applicable regional rights, including the right to complain to a competent data-protection authority, continue to apply.

This edition is dated 22 October 2026. We will update this policy when our practices change and provide notice or request consent where required. Read the User Agreement for terms of use. Privacy contact: support@qoril.app.