DAYCARD

Privacy policy

RevisionNov 12, 2026
LanguageEnglish

How Daydex handles information on DAYCARD and how you can exercise your rights.

1. Privacy officer

DAYCARD is operated by Daydex. Its privacy officer is Kim Chan-hyung, representative. Send privacy questions and rights requests to contact@day-card.com.

2. Information and purposes

  • Sign-in: We use the Google account identifier, email and name to identify your account and maintain sign-in. For Kakao sign-in, we use a unique Kakao account identifier and save your nickname if you consent to provide it. We do not request Kakao email addresses or profile images. DAYCARD does not store Google or Kakao passwords. Kakao authentication tokens are used only for server-side verification, are not retained and are never sent to your browser. Google and Kakao accounts are not automatically merged by email and maintain separate saved-card lists.
  • Saved cards: Cards you choose to save are linked to your account, including card identifiers and names, reward type, airline program, estimated monthly rewards, annual fees and selected card options. We do not ask for card numbers, CVCs, bank accounts or transaction statements.
  • Reward comparisons: Spending categories, amounts and options are sent to DAYCARD to calculate rewards. Calculation inputs are not saved in the calculation database or application logs. Paid orders and report downloads are not offered.
  • Inquiries: We use your reply address, name and the message you send to respond. Please do not include card numbers or passwords.
  • Access and analytics: Hosting providers may process IP addresses, browser and device details, and request logs to deliver and secure the service. Google Analytics processes page usage, cookie identifiers and device/access information for visitor statistics. To improve the service, we measure comparison starts and displayed results, card-detail views, unsupported-card selections and calculation-support requests, external card-link clicks and navigation from stories to comparisons. These events include public product identifiers, issuers, the Korean or US card market, interface language and link types. They do not include entered spending or qualifying-spend amounts, estimated rewards, sign-in account information or saved-card lists. Google signals and advertising personalization signals are disabled in the site configuration.
  • Admin visitor statistics: A daily hash of a random cookie deduplicates visits from the same browser once per Korean calendar day. We do not link a person across devices or browsers. This statistic stores no IP addresses, account IDs, emails, spending data or page paths. The browser classifies the utm_source link tag or referring site into a source category such as Instagram, Naver or Google and sends only that category. Administrators also see aggregate counts by the first source recorded per browser per day. Raw referral URLs, search terms and campaign strings are not stored in this statistic.
  • Story views: A daily hash of a random visitor cookie, post ID and date prevents duplicate daily counts. These records are not stored together with a login account or the original cookie value.

Account features are available to people aged 14 or older. We do not collect dates of birth or automatically check age. If you discover an account for a child under 14, contact the privacy officer to request deletion.

3. Statement files and optional merchant lookup

Selected PDF, Excel and CSV files and statement photos and PDF passwords are processed in browser memory, not uploaded to or stored on DAYCARD servers. Scans/photos are recognized locally with Korean and English OCR. Recognition resources are delivered by DAYCARD when needed; DAYCARD retrieves pinned public model/core resources from jsDelivr and verifies their hashes. Images, recognized text and passwords are not sent to an external OCR or analytics server. Image buffers and recognition jobs are cleaned up on completion or cancellation, and recognized data is not retained in browser storage. After review and confirmation, category totals are sent to the rewards calculation server without storage. Closing the importer releases references to the file and transactions. Categories are estimates: check the source for missing or duplicate transactions, refunds and installments.

Only when you enable the option or select “Search unknown merchants with Kakao”, unknown merchant names, normalized to remove payment-provider and legal-form prefixes, are sent directly from your browser to Kakao place search. Files, transaction amounts and dates, card/account numbers and passwords are not sent. These queries and results do not pass through the DAYCARD server and are not saved in its databases or analytics logs. Kakao policies also apply to its processing of search requests. With the option off, this external search is not used.

4. Cookies and browser storage

  • Sign-in: __Host-daycard_session lasts up to 30 days; signing out ends the current session. The sign-in verification cookies __Host-daycard_challenge and __Host-daycard_kakao are valid for up to 10 minutes.
  • Visitor statistics: daycard_visitor is a random identifier lasting up to 30 days. Deduplication hashes for today and the previous two days are retained; older hashes are deleted on the next collection request. Daily aggregate counts without identifying values are retained for reporting. Browsers blocking this cookie are not counted.
  • View counts: daycard_reader lasts up to 30 days. Daily hashes on the server support duplicate-count prevention.
  • Comparison recovery: Monthly totals, category totals, comparison settings and selected card IDs are kept in this tab’s session storage to restore a refresh. Resetting the form or closing the tab removes them. Statement files, individual transactions and file passwords are not stored.
  • Appearance: Your light, dark or device preference is stored locally as daycard-theme and is removed when you clear browser data.
  • Language: daycard-language is stored in your browser's local storage until it is cleared.
  • Google analytics and advertising: Google and third parties may place or read cookies and collect information through web beacons or similar technologies. Cookie types and duration depend on the relevant service's configuration and policies.
You can block or delete cookies in your browser privacy settings; some features, including sign-in, may be affected. You can also use the Google Analytics opt-out tool.

5. Processors and disclosure to third parties

Processing on our behalf

  • OpenAI Sites: Site hosting, network requests and service operation.
  • Cloudflare, Inc.: Traffic delivery, security and D1 database operation within the OpenAI Sites infrastructure.
  • Google LLC: Usage statistics through Google Analytics.

Third-party disclosure and external services

DAYCARD does not disclose account or saved-card data to third parties for their own purposes except as required or authorized by law or with separate consent. It does not send application or account data to card issuers.

The browser connects directly to Google and Kakao sign-in services and Kakao maps and merchant search. Google returns authentication information to DAYCARD. Kakao maps processes search terms and map areas. If you choose “My location” and give browser permission, your coordinates are passed to the Kakao map SDK to center the map. Kakao processes the current map area when you search nearby. DAYCARD does not receive device coordinates on its server or keep a location history in your account. You can disable browser location permission and search by area name. Kakao privacy policy

6. International processing and transfers

The tables describe hosting, storage and Google services. Contact contact@day-card.com with questions or for help with refusal options.

Google Sign-In
Recipient and contactGoogle LLC · Privacy contact
Countries or regionsUnited States and other countries where Google operates servers.
Purpose and dataAuthentication. Opening the sign-in dialog loads Google’s authentication tools, which can process IP and browser information. Successful sign-in returns an account identifier, email and name to DAYCARD.
Timing and methodThe browser loads the sign-in tools over HTTPS. Encrypted authentication data is exchanged at sign-in.
RetentionGoogle retains authentication and security logs under its own policy. DAYCARD sessions last up to 30 days. Account information is held until account deletion.
How to refuse and effectsSkip Google Sign-In or block Google authentication resources. This prevents access to cards saved under your Google account. Kakao sign-in and public comparisons remain available.
Google Analytics
Recipient and contactGoogle LLC · Privacy contact
Countries or regionsUnited States and other countries where Google operates servers.
Purpose and dataSite and feature usage statistics. Cookie identifiers, device/browser details, visited pages and usage events. Google temporarily uses IP for location estimation and does not log the raw IP in GA4.
Timing and methodThe browser sends data over HTTPS when you visit and use site features.
RetentionThe DAYCARD GA4 property setting applies. Google publishes retention options of 2 or 14 months for user- and event-level data in standard GA4. We are checking this property’s setting.
How to refuse and effectsUse the Google Analytics opt-out tool or block analytics scripts in your browser. Card comparisons and account features remain available.
OpenAI Sites
Recipient and contactOpenAI · Privacy contact
Countries or regionsOpenAI Sites hosting region. We are checking the specific storage country and the OpenAI contracting entity for this site.
Purpose and dataHosting and operation. IP, requests and browser information, sign-in and saved-card data, and spending totals in calculation requests are processed as needed to run the service.
Timing and methodPage visits and API requests are sent over HTTPS.
RetentionDAYCARD keeps account and saved-card data until account deletion and processes calculations temporarily. The account agreement and settings govern hosting logs and backups. We are checking the specific periods.
How to refuse and effectsStop accessing the site or contact the privacy officer. Refusing the hosting processing limits use of the site.
Cloudflare
Recipient and contactCloudflare, Inc. · Privacy contact
Countries or regionsGlobal network operated by a U.S.-based company. We are checking the actual storage country for this site’s D1 database.
Purpose and dataRequest delivery, security and database storage within the OpenAI Sites infrastructure. Depending on the feature, this includes IP and request details, account, session and saved-card data, and values used to prevent duplicate counting.
Timing and methodThe network processes connections when the site is accessed. Database operations go through the application server.
RetentionSee the DAYCARD retention section below. Cloudflare publishes 7- or 30-day D1 point-in-time recovery windows depending on plan. We are checking the applicable plan and network-log retention.
How to refuse and effectsStop accessing the site or contact the privacy officer. Refusing this processing limits use of the site.

7. Your privacy rights

Email contact@day-card.com to request access, correction, deletion, restriction or withdrawal of consent. A legal or authorized representative may also submit a request. We verify identity or authorization only as needed. Tell us the sign-in provider you used and leave out passwords and card numbers. Account closure and deletion

8. Retention and deletion

  • Account and saved-card information is kept until account deletion, and inquiry messages until the matter and follow-up are completed. Records required by law are kept separately until the applicable period ends.
  • When retention ends, DAYCARD deletes the relevant records from its operational database and inquiry storage. Retained electronic files are securely erased so they cannot be recovered. Access to hosting backups is restricted, and backups expire according to their retention schedule.
  • Daily visitor deduplication hashes are kept for the current and previous two days. Older records are deleted on subsequent counting requests. Story view records prevent duplicate counts. Weekly card rankings use a public card ID, the action (detail view or inclusion in the top comparison results), the date, and a daily browser hash. Spending amounts, account IDs and files are not included. Records are kept for the current and previous six days and older ones are deleted on later counting requests. Monthly spending goals and amounts stay on this device and can be removed under My account. Aggregate daily totals without identifying values are retained as statistics.

Spending categories, amounts and selected calculation options are sent to the DAYCARD server to calculate rewards. They are not saved in the calculation database or application logs. A daily keyed hash derived from the connection IP and request counters is used to limit excessive requests; raw IP addresses are not saved in this database. Expired counters and hashing keys are deleted on subsequent requests. Hosting providers may separately process network logs under their policies.

DAYCARD uses HTTPS, restricted administrative access, hashed session tokens and HttpOnly and Secure cookies.

9. Complaints and dispute resolution

10. Version history

We publish the effective date and material changes and give advance notice or seek consent where required.

Back to top ↑