Updated and effective: October 22, 2026 · Version 2026-10-22-v10
This policy explains what information CurioIsland processes, who can see it, and how you can manage or delete it.
Operated by: Jinan Anverit Information Consulting Co., Ltd
Email: support@curioisland.com
Start with what matters to you
Public App pages require no registration. Phone numbers and emails are not published with comments; comments and their attachments may be public. Help-page feedback goes to the platform, not directly to App developers. Saves, likes, usage states and code claims are linked to your account. Account deletion and privacy requests are currently handled manually by email.
This revision explains the public site’s hosting in Tencent Cloud’s Beijing region, private object storage, encrypted recovery backups and restricted local copies. It also explains private screenshot verification for self-service claims. Existing account, comment and redemption-code rules remain aligned with current features. Historical acceptance is not rewritten as acceptance of this version.
1. Scope and legal basis
Jinan Anverit Information Consulting Co., Ltd operates CurioIsland and is responsible for processing whose purposes and methods it determines. This policy covers browsing, accounts, App interactions, submissions and management, feedback, complaints and rights requests. Independently used third-party Apps, stores and websites have their own rules.
Depending on the context, necessary information is processed to provide requested services, fulfill legal duties, obtain valid consent or rely on another applicable lawful basis. Public information is used only within reasonable limits. Declining optional processing does not affect unrelated features. Where separate or renewed consent is required, we explain and obtain it; a sign-in checkbox is not a substitute.
Random or hashed identifiers are not necessarily anonymous. Information that can still be linked to a person or record remains protected.
2. Information processed by feature
| Feature | Information and purpose | Visibility |
|---|---|---|
| Accounts and sign-in | Phone number, verification workflow and results, account ID, nickname, optional avatar and email, verification values for existing passwords or recovery credentials, and sessions; for registration, sign-in and security. | Phone numbers, emails and security credentials are private. Plaintext passwords and recovery codes are not stored. |
| Document acceptance | Account, actively accepted version and time, to record acceptance for account services. | Retained by the platform; not a marketing subscription or consent to future features. |
| Saves, likes and usage | Account, App, save/alert preference, like, self-reported Using state, reason endorsements and changes; to restore interactions and maintain counts. | Personal records are account-private. Public areas may show aggregate counts, without participant account lists. |
| Browsing and statistics | Search, categories/scenes, browsing round and position, random browser ID, impression/detail/store-click events, time and necessary request information; for browse restoration, deduplication, security and aggregate statistics. | Owners see aggregates only for their authorized Apps, without visitor identities or individual browsing histories. Store clicks do not establish downloads. |
| Comments, replies and attachments | Account association, nickname at publication, text, selected images/videos, time, likes and processing state; for publication, display, replies, moderation and notices. | Published content follows discussion settings and moderation. Phone numbers, emails and internal account IDs are not attached publicly. |
| Feedback, corrections, reports and appeals | Account, affected page, issue type, text, necessary evidence, handling and receipts; Help also accepts an optional contact email solely for that issue. | Handled by authorized platform staff, not published or directly forwarded to developers. Legally required notices convey only necessary material. |
| Redemption codes | Account, offer, allocated code, claim time and duplicate-prevention records; for allocation, personal history and support. | Unallocated codes are not public; allocated codes are provided to the claimant. Offering owners manage their code stock and claim totals without receiving claimants’ phone numbers or emails through this feature. |
| App submissions and notices | Account, store link and App ID, verification task, progress and result, plus notice content, time and read state; for submissions, receipts and saved-App change alerts. | Tasks and notices are account-private. Apple public-data lookups do not include account phone numbers or emails. |
| Owner management | Account/App permissions, ownership evidence, contact information, screenshot/reason drafts, reviews, maintenance and management records; for verification and authorized App management. | Drafts, ownership evidence and management records are restricted. Self-service claims accept private App Store Connect screenshots for platform verification before granting App management access. Registration alone grants no rights. |
3. Required information, choices and notices
Public browsing does not require a phone number or email. Network requests process IP addresses, paths, times and browser information to return pages, investigate faults and prevent abuse. This does not mean every request is retained long-term or used for advertising profiles.
SMS sign-in requires an authorized mainland China number and code. A newly verified number creates an account; an existing number signs in to that account. Email sign-in requires an existing verified email and password; linking email does not set a password. Email verification/replacement depends on displayed service availability. Self-service phone changes, password setup/reset and recovery-code sign-in are currently unavailable.
Posting comments/replies, uploading their attachments, claiming codes and owner management writes require sign-in and a verified phone. Saves, App likes, reason endorsements, usage states, App submissions, Help feedback and personal records follow their account requirements without a blanket additional phone check. Ordinary comments and replies require no extra policy checkbox and do not create a new document-acceptance record.
Saving can deliver that App’s change alerts to your account; unsaving turns those saved-App alerts off. Existing alert preferences are retained. Signing in, linking email or giving a feedback contact email does not subscribe you to marketing. The current interface has no email-news subscription or personalized-feed switch; contact support to withdraw a historical subscription choice.
Current App browsing follows chosen filters and public display rules, without using your saves, likes or browsing history to produce personal-interest rankings. The independent Community, community writing and private developer-feedback service are unavailable. Mentioning future features does not authorize advance collection.
4. Public content, uploads and private materials
App comments default open without an owner claim. Current settings, platform actions or pauses may limit posting and historical visibility. Published comments, replies, attachments and publication-time nicknames can be seen, captured or saved by others. Changing a nickname may not rewrite historical attribution. Authors can delete their own main comments to withdraw public display; this does not immediately destroy all dispute evidence.
Each comment or reply accepts up to four attachments, including at most one video. Images support JPG, PNG, WebP and GIF up to 10 MB each; videos support MP4, MOV and WebM up to 50 MB and 60 seconds. Uploading sends files to the platform for processing before publication. Files are validated, converted and compressed, with common metadata removed; video may retain its original audio. Processing does not automatically conceal personal details in pictures, text or sound. Check files before uploading.
Account avatars can use presets or an optional static JPG, PNG or WebP upload up to 5 MB. They are cropped, compressed, stripped of common metadata and stored without facial recognition. Avatars currently serve account interfaces; comments may show a nickname initial. There are no public personal profiles or follower relationships. Custom avatars are served through image links that people obtaining the link may access; they are not private file storage. Avoid private details in uploaded images. Changing an avatar replaces the current image, with possible cache delays.
Help feedback and reports do not expose private correspondence to owners. Comment management provides current authorized owners and platform staff only the material needed for handling; owner actions cannot override platform decisions. Reports, appeals, ownership evidence and unpublished screenshot/reason drafts do not become public merely through submission. Legally required forwarding is limited to necessary material, masking unrelated information where possible.
Current features do not require financial accounts, health information, location history or full identity documents. Do not submit unrelated sensitive information, passwords or codes in comments, uploads or feedback. Any future necessary sensitive-data processing will first explain its need, effects and safeguards and fulfill applicable consent requirements.
5. Cookies and browser storage
These records support sign-in, language, browse restoration and statistics; they are not hardware serial numbers. Inspect, restrict or clear them in browser settings. Clearing browser data or signing out does not automatically delete server-side account records; signing in again restores access to retained records. Never send cookies or full session credentials to support.
| Item | Purpose | Duration and control |
|---|---|---|
| curio_v4_session (cookie) | Account-session credential with HttpOnly and SameSite restrictions; page scripts cannot read it directly. | Up to 30 days; sign-out invalidates the current session. Blocking it affects sign-in. |
| curio_v4_locale (cookie) and curio.v4.locale (local storage) | Remember the chosen interface language. | Language cookie lasts one year; the local value remains until replaced or cleared. |
| curio-visitor-id (local storage) | Random browser ID for deduplicating impressions, detail visits and store clicks; hashed by date on the server, without giving owners the raw ID. | No fixed automatic local expiry; clear website data to remove it. Server event retention is described below. |
| curio.v4.discovery, curio.v4.discovery-return (tab session storage) and browser history state | Store filter URL, round, loaded count and card/scroll position for returning from detail. | Position records are used only within 24 hours. Session storage ends with the tab session or manual clearing; history state can also be cleared with browser history. |
6. Providers and external links
Website infrastructure uses Tencent Cloud servers and object storage in Beijing, with access configured by the operator, to serve pages, store business information, deliver App media and maintain recovery backups. Servers process account, comment and code-claim records for the purposes described in this policy. Database recovery backups in COS are separately encrypted, and their decryption key is not stored with them in COS.
SMS authentication uses Alibaba Cloud’s phone-number verification service (阿里巴巴云计算（北京）有限公司), called by our server. Requesting or verifying a code processes the necessary phone number, request ID, authentication context, submitted code and result. No client SMS SDK is embedded; browsing alone does not send your phone number to the SMS provider.
Email verification integrates Tencent Cloud Simple Email Service (Tencent Cloud Computing (Beijing) Co., Ltd). Only when configured, available and requested does it receive the recipient, code and template content for delivery. Missing configuration or failure is reported; integration does not guarantee delivery is currently available. SMS/email delivery also involves telecom operators and recipient email services.
App data and screenshots are obtained from Apple’s official public sources. Loading an image directly from an external source can disclose IP address and browser request information to that source; platform-hosted copies do not create that direct request. App Store or developer sites handle requests and information you submit there under their own rules. Our links and public-data lookups do not append account phone numbers or emails.
There is no cross-site advertising-tracking SDK, nor a request for contacts, precise location, microphone or camera permissions. Uploads process only selected files, not the entire photo library. Providers’ independent delivery/security processing does not authorize unrestricted platform use. Material changes receive notice and applicable safeguards.
Alibaba Cloud SMS authentication API informationTencent Cloud privacy statement
8. Storage, retention and deletion
The public site’s hosting, business databases and object storage use Tencent Cloud’s Beijing, China region. COS stores App media and encrypted recovery backups in a private-access bucket. The website checks visibility before returning public images; this does not make account or database records public. The operator keeps restricted local development or recovery copies. Third-party delivery and external services have their own processing locations and rules. Changes to storage region/providers or cross-border provision will first meet notice, applicable consent and other legal requirements.
Information is kept for the shortest time necessary for its purpose. Validity, triggered cleanup and manual handling below differ: expiry does not mean every copy is physically deleted at that instant.
| Data | Period or criteria |
|---|---|
| Accounts, interactions and acceptance | Kept for account services until removal, a deletion request or the purpose ends; afterward only necessary request, dispute or legally required records remain. Undoing an interaction changes current state without necessarily erasing security/audit records. Old acceptance is not rewritten as acceptance of a new version. |
| Codes and sessions | Codes are valid for five minutes; local verification records expired for over 24 hours are cleaned on later verification creation. Sessions last up to 30 days; sign-out invalidates the current one, and expired server sessions are cleaned when later sessions are created. Provider records follow provider rules. |
| Browse rounds and deduplication events | Server rounds and display tickets are valid for 72 hours. UTC-day deduplication events are kept for 31 days; subsequent round requests trigger expired-record cleanup, at least one hour apart per process. App/day aggregates are stored separately without raw browser IDs and are not promised deletion alongside deduplication records. |
| Text drafts and uploads | Unsubmitted ordinary comment, reply and Help-feedback text exists only in page-session memory and may be lost on refresh, closure or sign-out; it is not a cloud archive. Unbound uploads are accessible only to their uploader, cannot be attached after 24 hours, and are cleaned on subsequent uploads. Bound media follows comment visibility. Owner screenshot/reason drafts are separately saved on the server under account permissions. |
| Comments and moderation evidence | Public comments remain for ongoing display. Withdrawn, hidden or removed text, replies, media and actions are handled according to disputes and rights requests, and may enter restricted manual cleanup 90 days after the latest action. Open/recently closed cases or legal holds can defer cleanup; this is neither automatic deletion at expiry nor indefinite retention. |
| Claims, feedback, ownership and reviews | Kept according to code fulfillment, issue handling, permission checks and necessary disputes, then deleted/anonymized when no longer needed. Stopping, expiring or deleting an offer does not automatically erase allocations. Public-visibility changes can affect account-page display; contact support for assistance. |
| Logs, support emails and backups | Limited to security, support, recovery and legal retention needs; no uniform automatic cleanup period is currently promised. Manual requests explain scope, grounds and cleanup arrangements. Backups not immediately erasable have restricted access/use, and confirmed deletions must be reapplied after restoration to avoid reusing deleted information. |
9. Security and incidents
Current safeguards include salted password hashes, credential verification values, sessions, server authorization, same-origin checks and API limits. Owner management checks account/App ownership, private material is excluded from public lists, and uploads have format, size and processing bounds. Safeguards do not eliminate every risk.
Actual or potential personal-data disclosure, alteration or loss receives prompt remedial action, assessment, reporting and notification as required. Notices explain affected information, causes, possible effects, measures, useful user actions and contact details. Report unusual account activity or exposed private information with page, time and necessary observations, without passwords, codes, recovery codes or full identity documents.
10. Your rights and request channels
Your lawful rights include information, choice, restriction/refusal, access, copies, correction, supplementation, deletion, consent withdrawal and account deletion, plus transfer or explanations when applicable conditions are met. A feature’s information needs do not waive other rights.
Current controls support nickname/avatar changes, email verification/replacement when available, App interactions and deletion of one’s own main comments. My Island shows account-private records. There is no self-service account deletion or complete-export button; email requests cover unavailable controls, historical records and complete copies.
- Email support@curioisland.com with the right, affected feature/page and scope. Start with a nickname, linked email or masked phone number, without full identity documents in the first message.
- We perform necessary, proportionate identity or representation/guardianship checks according to risk. If safe verification is unavailable, we explain and agree a method without disclosing another person’s data.
- We generally provide results or progress within 15 working days. Complex cases receive reasons, needed evidence and expected timing. Urgent privacy risks receive timely action without waiting for the ordinary response period.
- We act within the verified scope. If legal retention, others’ rights or unverified identity limit action, we explain the grounds and available partial measures. Reasonable requests are generally free. You can seek email review, complain to competent authorities or use a court with jurisdiction.
11. Consent withdrawal and account deletion
Email support to withdraw consent-based processing. Withdrawal does not invalidate earlier lawful processing. Necessary service/legal processing and optional processing are assessed separately, with service effects explained and unrelated services preserved. Historical email choices can also be withdrawn through support, without looking for an unavailable subscription switch.
Account deletion is manual. You may also request copies and specify public content, owner permissions, unfinished offers and browser-linked records. Once confirmed, account services stop and relevant data is lawfully deleted or anonymized. Necessary retention is explained by grounds, scope and restrictions; coordination does not justify indefinite delay. Signing out is not account deletion, and deletion does not automatically identify every browser ID you have used.
Relevant active copies are also addressed when deletion conditions are met. If law requires retention or deletion is temporarily technically difficult, processing stops except storage and necessary security, with the arrangement explained. Previous publication or support use alone is not grounds to refuse lawful deletion.
12. Minors and other rights holders
Accounts are not offered to children under 14, nor is their information actively requested. Universal document/face age checks are not performed. Other minors should read with a guardian and use age-appropriate features. Guardians can report mistaken registration or child-data submission for verification, cessation of unnecessary processing and lawful deletion. Any future child-facing service needs special rules and legally required guardian consent first.
Close relatives may lawfully request handling of a deceased user’s information for legitimate interests, except where the user arranged otherwise. Relationships, grounds and arrangements are checked only as necessary, protecting others’ rights.
13. Updates and contact
Revisions identify date, version and main changes. Material operator, purpose, scope, recipient, retention or rights-channel changes receive page notices or appropriate communication. Legally required renewed consent is obtained before new processing; silence, browsing or old records are not rewritten as new consent. New features must first have descriptions matching their actual processing.
This policy is provided in Simplified Chinese and English. Contact us to resolve discrepancies; language choice does not diminish statutory rights. The personal information processor is Jinan Anverit Information Consulting Co., Ltd. For privacy, deletion or security matters, contact support@curioisland.com.