Skip to content

Privacy Policy

Effective 2026-10-23

This English version is provided for convenience. If it differs from the Korean version, the Korean version prevails.

[사업자명] (“we”) publishes this Privacy Policy under Article 30 of the Personal Information Protection Act (PIPA) of Korea to protect the personal data of members and link visitors of the chckmy service (chck.my, the “Service”) and to handle related complaints promptly.

1. Purposes of processing personal data

  1. Member management — identifying you through Google sign-in or an email magic link, maintaining your account, preventing abuse, and sending Service notices
  2. Providing the Service — creating and publishing short links, link pages, QR codes and app install pages; inviting workspace members and managing their permissions; issuing API keys
  3. Paid plans — checking subscription status, applying plan limits, and handling payment and refund inquiries
  4. Safe operation of the Service — blocking malicious and phishing links, handling reports, limiting excessive requests, and responding to security incidents
  5. Improving the Service — analytics for service screens and the signup flow (you can turn this off; see Section 11)

2. Data we collect, how we collect it, and our basis

We process data needed to perform our contract with you without separate consent under Article 15(1)(4) of PIPA, and other data on the basis stated below. We do not process sensitive data or unique identifiers (such as resident registration numbers).

CategoryDataHowBasis
Google sign-inGoogle account email, name, profile photo URL, Google account ID, authentication tokens issued by GoogleProvided by Google with your consent when you sign inContract performance
Email magic-link sign-inEmail address, hash of the sign-in link verification tokenEntered by you; generated when a sign-in link is issuedContract performance
Sign-in sessionIP address, browser information (user agent), session creation and expiry timeGenerated automatically while you sign in and keep a sessionContract performance, security
Entered or created while using the ServiceLink page handle, title, bio and blocks; short links and destination URLs; uploaded images (profile, link preview, app icon); app name and store URLs; hash of a link password; history of link creation and changesEntered by you or generated through your use of the ServiceContract performance
WorkspacesWorkspace name, member accounts and roles, invitee email, who invited them, invitation statusEntered by the ownerContract performance
API keysKey name, the beginning of the key (for identification), hash of the key, usage countGenerated when a member issues a keyContract performance
Paid paymentsPolar customer ID, subscription product, interval and status, payment and renewal datesReceived from our payment processor, Polar. Payment method details such as card numbers are collected directly by Polar; we do not receive them.Contract performance, legal obligation
Reports (optional)Reporter email, report detailsEntered by you on the Report pageConsent (when you submit)
Visit analytics (optional)Data described in Section 11Collected automatically on measured service screens or during signupYou can turn it off in Section 11

Campaign and bulk CSV inputs and per-row processing results are stored for retries and result review. After 30 days they become inaccessible and eligible for cleanup. Deletion runs during scheduled cleanup or the next preview in that workspace, so physical deletion may be delayed. Minimal execution receipts (workspace ID, server operation key, input hash, created link ID and creation time) remain after link deletion to prevent duplicate creation, and are removed when the workspace is deleted. Receipts do not contain destination URLs or input bodies.

To apply short-link creation limits, we retain the creation event ID, account owner ID and creation time. This record contains no short link or destination URL. It remains after a link or workspace is deleted and is removed when the account is deleted.

Destination checks store link IDs, target hashes, HTTP status, latency, redirect-chain origins and statuses, and observation times. Check results do not store full URLs, paths, queries, bodies, headers or raw errors. Completed jobs and in-app notifications become eligible for scheduled cleanup after 30 days; physical deletion may be delayed. The latest per-link state is removed with the link, while active schedule settings are retained. Customer history shows only allowed actions, actors, resources and times from existing audit records, excluding sensitive details.

Customer assignments and revisions are stored as event-time snapshots in analytics, audit and check records. Restricted customer access sees records matching current access and scope; owners and workspace-wide readers retain full historical totals. Customer reports copy only minimal folder-at-event redirect aggregates, excluding visitor/resource IDs, titles and destinations. Derived report snapshots and shares have a separate retention/validity limit of up to 30 days from creation, independent of source daily aggregates. Reassignment, lost access, expiration or revocation denies reads immediately; bounded maintenance performs deletion. Raw share tokens are shown once and only hashes are stored. Tokens travel in URL fragments, not server URLs; verification bodies/tokens are not written to application logs.

3. Link visitors

When a visitor opens a short link or link page created by a member, we handle it as follows.

  1. We use request country, device, language and UTM values to choose the destination. Analytics do not store raw IP addresses, full user agents, full referrer URLs or arbitrary query strings.
  2. For customer performance analytics we count resource-level page visits, valid link redirect responses and block click redirect responses. We store only event IDs, times, resource/workspace/folder-at-event identifiers, country, approximate device type, referrer hostname and allowlisted UTM values. Our retention limits are 30 days for events and 366 days for daily aggregates. Expired data is removed in bounded scheduled batches. Scheduling delays or outages may delay physical deletion; analytics queries always exclude data beyond retention and entitlement windows. Members see 30-day summaries or up to 366-day detail and CSV according to entitlement. We do not provide visitor identities or unique-person counts. Known bots, HEAD and previews are excluded; collection can be missing or delayed. We respect browser DNT/GPC signals and the analytics opt-out cookie in Section 11. Page measurement tokens expire in 15 minutes and we do not create visitor tracking cookies.
  3. When a password-protected link is opened or many requests arrive in a short time, we briefly use the IP address for rate limiting to prevent brute-force attacks and abuse. This value disappears when the limit window ends.
  4. For a visitor who enters the correct password, we store a confirmation cookie so that the same link can be opened again (Section 10).

4. Retention

We delete personal data without delay once its purpose has been achieved. Retention periods are as follows.

  • Member and Service data: until you delete your account
  • Sign-in sessions (IP, user agent): until you sign out or the session expires (up to 30 days)
  • Sign-in link verification token: 10 minutes after issuance (invalid immediately once used)
  • Workspace invitations: until accepted, declined or cancelled, or until they expire 7 days after sending
  • Reports: 1 year after resolution (to respond to repeated violations)

Where required by law, we keep the following data for the stated periods.

  • Records of contracts and withdrawal of offers: 5 years (Act on Consumer Protection in Electronic Commerce)
  • Records of payments and supply of goods or services: 5 years (same Act)
  • Records of consumer complaints and dispute handling: 3 years (same Act)
  • Access logs for the Service: 3 months (Protection of Communications Secrets Act)

5. Deletion procedure and method

  1. We delete personal data without delay (within 5 days at the latest) once a reason for deletion arises. Data we must keep by law is stored separately from other data and deleted when the period ends.
  2. Data in databases and file storage is deleted in a way that cannot be recovered, and uploaded images are removed from storage. Data remaining in backups is deleted when the backup retention period ends. We do not create paper documents.

6. Disclosure to third parties and public information

  1. We process personal data only within the purposes in Section 1, and provide it to third parties only where PIPA Articles 17 and 18 allow, such as with your consent or under a specific legal provision. We do not currently provide personal data to any third party.
  2. Link pages, short links and app install pages are created by members to be public, so the handle, title, bio, images, links and app information a member enters can be seen by anyone.
  3. Members of the same workspace can see each other's name, email and role, and the workspace's links.

7. Processors

We outsource the following processing of personal data to provide the Service, and we manage processors under outsourcing contracts so that they handle personal data safely.

ProcessorOutsourced task
Cloudflare, Inc.Service hosting, database and file storage, sending sign-in and invitation emails, network security (DDoS protection, etc.)
Polar Software, Inc.Selling paid plans on our behalf (Merchant of Record), payment, billing and tax processing, issuing receipts
Google LLCService screen and signup analytics (Google Analytics 4)

With Google sign-in, you sign in to Google yourself and we receive the result; Google's own processing is governed by Google's privacy policy.

8. Transfers of personal data abroad

The servers of the processors in Section 7 are located abroad, so personal data is transferred abroad as follows in order to provide the Service (contract performance) (PIPA Article 28-8(1)(3)). All transfers use encrypted communication (HTTPS).

Recipient (contact)CountryData transferredPurposeWhen and howRetention
Cloudflare, Inc. (privacyquestions@cloudflare.com)USA and other countries with Cloudflare data centresData in Section 2; visit request data in Section 3Hosting, storage, email delivery, network securitySent over the network from time to time while you use the ServiceUntil you delete your account or the outsourcing contract ends
Polar Software, Inc. (privacy@polar.sh)USAMember email, name and ID; workspace ID; selected plan; IP address at checkoutSales on our behalf, payment, billing and tax processing, fraud preventionSent over the network during checkoutPer Polar's privacy policy and applicable law
Google LLC (support.google.com/policies)USAVisit analytics data in Section 11Visit analyticsSent over the network when you visit an analysed pagePer our Google Analytics data retention setting

How to refuse and its effect: The transfer to Cloudflare is essential to operate the Service, so if you do not want it, you can choose not to sign up or you can delete your account. The transfer to Polar happens only when you pay for a paid plan, and does not happen if you do not pay. Google visit analytics can be turned off in Section 11, and turning it off does not limit your use of the Service.

9. Your rights and obligations, and how to exercise them

  1. You may at any time request access to, correction or deletion of, or suspension of processing of your personal data, and withdraw your consent.
  2. You can do most of this yourself in the dashboard (editing your profile and links, ending sessions, deleting your account). For any other request, email the contact in Section 14 and, after verifying your identity, we will act within 10 days and tell you the result.
  3. You may exercise your rights through a legal representative or an authorised agent, in which case a power of attorney must be submitted.
  4. You cannot require deletion of personal data that other laws require us to keep during the required period, and a request to suspend processing may be refused under the law. If we refuse, we will tell you why.
  5. You must enter your own and others' data accurately. If you enter another person's data without authorisation and cause harm, you may be liable under applicable law.
  6. If you are in the EEA, the UK or another region with its own data protection law, you may also have rights under that law, and you may complain to your local data protection authority.

10. Cookies (automatic collection devices): installation, operation and refusal

We use the following cookies. We do not use advertising cookies.

CookiePurposeRetention
Sign-in session cookieKeeps you signed inUp to 30 days
Language cookieRemembers your selected language400 days
Link password confirmation cookieLets you reopen a link whose password you entered correctly15 minutes
Analytics opt-out cookieRemembers your choice to turn off visit analytics1 year
Additional analytics cookieRemembers that you allowed additional screen analytics1 year
Signup measurement cookieRecords a completed signup once on the next service screenUp to 10 minutes
Google Analytics cookiesVisit analytics (Section 11)Per Google settings (up to 2 years)

You can refuse or delete cookies in your browser settings. However, if you refuse the sign-in session cookie, you cannot use features that require signing in.

Music performance records also store the immutable campaign mapping identifier and server-selected release phase. Only valid, five-minute campaign navigation signatures attribute provider-child responses; direct child visits are excluded from campaign totals. Signatures contain public routing identifiers and expiry, not customer identities, and are not visitor identifiers. No raw signature is stored in analytics. The same event/daily retention and opt-out rules apply. QR and UTM labels indicate request attribution, not verified camera scans. We do not collect completed listening, installation or OAuth pre-save events without a separately configured and verified external integration.

11. Behavioral data and visit analytics

We do not serve personalised ads. We measure use of public service screens to improve the Service. You can separately allow analytics for the signup flow and the signup, login, dashboard, and report screens below. Administration and customer link analytics are separate from Google Analytics. Section 3 describes customer link analytics.

Google Analytics 4 measures views and key button clicks on public service screens. If you allow additional analytics, it also measures signup steps and use of the signup, login, dashboard, and report screens. Analytics screen paths, allowlisted campaign information, referral domains, language, browser and device information, and analytics identifiers are sent to Google LLC in the USA. We measure sign-in methods and broad failure categories. Email addresses, form contents, authentication tokens, account or workspace identifiers, and customer link addresses are excluded. Advertising personalization is disabled. Analytics cookie storage is denied in the EEA, UK, and Switzerland.

Google Privacy Policy · Google Analytics

For internal signup reporting, we retain the times of the first workspace, link page, and block creation, the first member view of a public page, and the first external visit for each owner account while the account exists. This report stores milestone times without external visitor identifiers or visit URLs.

12. Security measures

  • Administrative measures: limiting access to personal data to the minimum number of people; establishing and carrying out an internal management plan
  • Technical measures: HTTPS encryption for all traffic, database access controls, sign-in methods that do not store passwords (Google, email magic link), storing only hashes of sign-in tokens, API keys and link passwords, and rate limits on sign-in and password entry requests
  • Physical measures: data is stored in Cloudflare data centres with access control

13. Children under 14

We do not accept sign-ups from children under 14. If we learn that personal data of a child under 14 has been collected, we delete it without delay.

14. Privacy officer and access requests

For inquiries about the handling of personal data, access requests, complaints and remedies, please contact the following. We will reply and act without delay.

  • Privacy officer: [개인정보 보호책임자 성명]
  • Email: [개인정보 문의 이메일]

15. Remedies for infringement of your rights

If you need to report or seek advice about an infringement of personal data, you can contact the following Korean authorities.

  • Personal Information Dispute Mediation Committee: 1833-6972 (www.kopico.go.kr)
  • Personal Information Infringement Report Center: 118 (privacy.kisa.or.kr)
  • Supreme Prosecutors' Office: 1301 (www.spo.go.kr)
  • Korean National Police Agency: 182 (ecrm.police.go.kr)

16. Changes to this policy

This policy applies from 2026-10-23. If content is added, deleted or amended, we will announce it in the Service starting 7 days before it takes effect (30 days before for changes that are unfavourable to you or significant), and we will also notify you by email of significant changes.