Mouse Keyring Privacy Policy

1. Scope and contact

This policy explains how TRY handles personal information through the Mouse Keyring app and mouse-kiring.com. It describes purposes and choices and how to exercise your rights. Send privacy questions or deletion requests to try.team.biz@gmail.com.

Kakao, Naver and email-code sign-in are being prepared. The additional Kakao fields described below will be processed only after permission approval, integration with an independent identity-verification provider, implementation and testing, and launch of the relevant feature. This collection plan does not apply to the currently available Google sign-in.

2. Account and device records

For Google sign-in, we use the account identifier and email address for authentication, license association and support. A Google display name is optional. After Kakao or Naver sign-in launches, we will use the selected provider’s account identifier and email address for the same purposes. We do not request Kakao or Naver profile nicknames or photos. Email-code sign-in is an independent option for people who cannot use social sign-in or choose email instead. It uses the email address and a one-time verification request for authentication, license association and support. No additional email code is required after successful Kakao, Google or Naver sign-in. We do not store social-provider passwords, and email-code sign-in uses no password. Accounts from different sign-in methods are not merged automatically solely because they share an email address.

We receive order identifiers and products and amounts and currency and order email and payment or refund status and timestamps from Lemon Squeezy. These support purchase verification and license delivery and accounting and dispute handling. We do not directly store full payment-card numbers.

We process license details and a hash of a randomly generated installation identifier and platform and device label and app version and last validation time. These support the three-device limit and device management and abuse prevention.

3. Planned Kakao fields and purposes

The following collection plan applies after Kakao sign-in and CI comparison launch. Required and optional fields and their purposes will be explained in the consent flow before collection starts. The server does not currently collect the name, CI, phone number, gender or age range listed below.

Refusing required fields prevents completion of the relevant Kakao sign-up flow. Refusing optional phone number, gender or age range, or the absence of these values at Kakao, does not prevent sign-up, sign-in or purchase. Optional fields are not used for individual marketing contact or decisions about prices, purchase eligibility or refunds.

CI from Kakao will be used only for a temporary comparison against CI obtained directly from an independent identity-verification provider. If no such directly obtained CI exists, the provider’s separate verification flow must be completed before comparison. Kakao CI does not replace identity verification and will not be retained as a persistent member identifier. The identity-verification provider and collection process will be disclosed separately after selection and integration.

4. Information for optional features

App images without image-sync consent and images used in the website demo stay on the device or in the browser. Synced images are private and retrievable only by authenticated devices on the same license.

5. Cookies and measurement

Essential security cookies maintain sign-in. The page URL determines the display language. A random measurement cookie lasts 24 hours. Funnel events, campaign labels and device categories are retained for 90 days and may be linked to an internal account identifier after sign-in. These analytics records do not contain email addresses, authentication tokens or payment payloads. Configured Google Analytics, Microsoft Clarity and Meta tools may measure visits and advertising performance. Browser DNT/GPC signals and previous analytics refusals are respected. Test activity is separated from production reports.

Starting with app version 1.0.24, we associate selected built-in characters, custom-image keyring use, keyring count, visibility and capture time with your account through its device and license to improve the service. Usage statistics never contain images, filenames, screen contents or cursor coordinates. Sharing is enabled by default and can be turned off under Settings → Account → Share keyring usage statistics. It is separate from settings and image sync and never enables that feature without consent.

6. External services and information transfers

Google, Kakao, and Naver provide the social account authentication you select. Resend delivers email verification codes. Lemon Squeezy acts as merchant of record and processes orders and payment and tax and refunds. OpenAI Sites and Cloudflare provide website hosting and server and storage infrastructure.

Global providers may process information outside Korea. Recipients and processing locations and retention arrangements depend on the feature and provider contract. Contact us for international-processing inquiries. Publishing this policy does not replace legally required notices or a valid basis for international transfers.

7. Retention and deletion

Account identifiers and email addresses and, when available, display names from the selected sign-in method are retained while needed for the account and license and support. Email verification codes and challenges are valid for only 10 minutes and become unusable immediately after successful verification. After a verified account-closure request we delete account information within 30 days. Records needed for legal retention or dispute handling are kept only for that purpose and period. Following a verified account-closure or deletion request we remove information that is no longer needed.

After this plan is activated, names will be retained while needed for purchaser-account confirmation and support; optional phone numbers, gender and age range will be retained while needed for their stated purposes. Information no longer needed will be deleted within 30 days after a verified withdrawal of optional consent, deletion request or account closure. Unneeded individual source records will be deleted when the aggregation purpose ends. CI received from Kakao will be processed temporarily in memory for comparison and discarded without delay once the comparison finishes. It will not be retained in databases, logs, analytics records or backups. Retention and deletion of CI obtained directly from the separate identity-verification provider will be explained in that process’s own notice and consent; this Kakao collection plan does not itself initiate that collection or retention.

Where Korean e-commerce retention rules apply they require five years for contract and withdrawal and payment and supply records; three years for complaint and dispute records; and six months for advertising records. Bug reports and attachments are kept while needed for support and then deleted subject to applicable dispute-record obligations.

Disabling sync or unlinking a device removes the settings and images that device stored on the server.

Administrator audit records for license reveals and status changes and device removal contain the action and target identifier and timestamp and are retained for 90 days. They exclude full license keys and passwords and report contents. Electronic records due for deletion are removed from reuse by the service.

Only the latest usage report for each device is retained, for up to 90 days. Disabling usage sharing deletes that device’s report; unlinking the device or closing the account also deletes its reports. Offline deletion is queued and retried when connected. Separately consented settings and image backups follow the deletion rules for that feature.

8. Requests about your information

Email us to request access or copies or correction or deletion or account closure or processing restrictions or withdrawal of consent. We request only information needed to verify your identity and explain any restriction such as mandatory retention.

Refusing optional Kakao fields does not restrict sign-up or purchase. Users may withdraw optional consent and request deletion. The required Kakao name and CI comparison fields apply only after the relevant sign-up feature launches.

9. Safeguards and children

We apply safeguards including administrator access restrictions and protected communication and encrypted license information and protected authentication tokens. Sign out on shared devices and check that report attachments do not contain unnecessary personal information.

10. Policy changes

We update this page and its effective date when our processing practices or applicable requirements change. Changes with material effects on users such as collection scope or purpose follow required advance notices and legal procedures. This policy does not itself constitute consent where consent is required.