Back to home

Service information

Privacy policy

How SortSync handles photos, documents and service information.

Updated · 2026-11-16

1. Operator and contact

SortSync is operated by 난다곰 (Nandagom). Contact ilseoengapp@gmail.com about access, correction, deletion or other privacy questions.

2. Data and purposes

We process the items you permit and information needed to classify files and manage usage, purchases and ad rewards.

  • Reduced photo copies, extracted document content and filenames, category names and descriptions: AI classification.
  • Installation identifiers, request/usage information and classification results: duplicate prevention, allowance management and result display.
  • Purchase tokens, product/transaction identifiers and purchase states: Google Play verification, restoration and credit delivery.
  • Reward transaction information and data processed by advertising SDKs: consent choices, ad delivery and duplicate-reward prevention.
  • Messages you enter in AI chat and task-related tool information: assistance with settings and classification.

3. External AI and service providers

Analysis passes through our Google Cloud relay in the United States (us-central1) to Codiv OpenJev, with Featherless Simple Jev as an alternative provider. AI chat uses a billing-enabled Google Gemini API project. Under the paid Gemini terms, inputs and responses are not used for model training; security and abuse-prevention records follow the provider’s terms. See the linked Codiv and Featherless policies for API processing and temporary caching practices.

Firebase App Check verifies app authenticity, Google Play Billing verifies purchases, and Google AdMob/UMP provide advertising and consent management. The advertising SDK may process IP-derived approximate location, app interactions, diagnostics and device/advertising identifiers for ads, analytics and fraud prevention.

Selected file copies are uploaded to Google Drive, OneDrive or WebDAV when you connect a storage account and choose synchronization. External providers may process information internationally under their policies. Our relay location does not describe every provider’s processing location.

4. Consent and originals

The app explains external transmission and obtains affirmative consent before analysis. Withdrawing consent in settings stops new analysis transmissions and automatic tasks. Excluded folders are omitted from analysis.

Classification does not move original files. Deletion you separately request follows Android confirmation. Photo content and classification criteria are not used for advertising targeting.

5. Retention and deletion

Our relay database does not store original photos, documents or AI chat text. External AI transmission still takes place. Device originals and classification records, and copies in your connected cloud, are managed separately.

Duplicate-request classification responses and request hashes are retained for up to 24 hours, with expired records cleaned approximately every five minutes. Daily request and chat counters are removed during cleanup on the next UTC date. Installation identifiers, cumulative free usage, entitlement, purchase and ad-reward records remain for allowance management, restoration and duplicate prevention until a verified deletion request is processed.

Relay diagnostic logs generated after this policy takes effect use daily rotation with a maximum 30-day retention; deployment database backups expire after seven days. Providers’ security records and older infrastructure logs follow their own retention rules. We explain deletion scope, timing and any legal retention basis individually. Not all information is deleted after 24 hours.

6. Your controls and protection

Manage file permissions, analysis consent, advertising privacy choices and cloud connections in the app and Android settings. See the deletion page for request procedures and retention exceptions.

Service communications use HTTPS. This website has no separate data-collection form or tracking SDK; inquiries are received by email.

7. Changes

Changes to operations or data practices will be reflected in this policy and its update date. The final policy must match in-app disclosures and Google Play Data safety information.