Privacy policy
Effective dateNov 9, 2026
How we handle your information, and the choices available to you.
1. Searching unknown merchant industries
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.
2. Importing statement files
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.
3. Service and contact
DAYCARD compares card information and estimates rewards. The operator is Daydex. The privacy contact is 김찬형 (Kim Chan-hyung). For privacy requests, email contact@day-card.com.
4. 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.
5. Maps and location
Card map searches and map bounds are sent to Kakao Maps. Your current coordinates are used for map centering and nearby searches only when you select “My location” and grant browser permission. DAYCARD does not store location history in your account database. You can search by place name instead or revoke location permission in your browser.
6. Cookies and browser storage
- Sign-in:
__Host-daycard_sessionlasts up to 30 days; signing out ends the current session. The sign-in verification cookies__Host-daycard_challengeand__Host-daycard_kakaoare valid for up to 10 minutes. - Visitor statistics:
daycard_visitoris 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_readerlasts 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-themeand is removed when you clear browser data. - Language:
daycard-languageis 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.
7. Benefit calculations and abuse prevention
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.
8. Google advertising
DAYCARD is preparing its Google AdSense connection and site review. Ad display scripts are currently inactive in the website code. If ads are activated, Google and advertising partners may use cookies, IP addresses and device identifiers for ad delivery, measurement and fraud prevention. Required consent flows will be provided in applicable regions before activation. See how Google uses data on partner sites and Google ad settings.
9. External providers
We use OpenAI Sites and Cloudflare for hosting and storage, Google for sign-in and Analytics, and Kakao for sign-in and map features. Providers process information to deliver their services. Google's, OpenAI's and Cloudflare's global infrastructure may process data outside your country, including in the United States. DAYCARD does not sell your saved card information. Providers' own policies also apply to their processing and retention.
10. Retention, deletion and security
We keep account and saved-card information while needed for account features. Once a deletion request is verified, we delete it without undue delay except where retention is legally required. Inquiry messages are deleted after their purpose is fulfilled. Signing out does not delete your account or saved cards. Expired sign-in cookies require a new sign-in; expired server sessions are cleaned during sign-in processing. View-count records and external providers' logs and analytics follow their respective processing purposes and retention settings. Protections include HTTPS, restricted access, hashed session tokens, and HttpOnly and Secure cookies.
11. Your choices and policy updates
Email contact@day-card.com to request access, correction, deletion, restriction or withdrawal of consent. We may verify your identity to the extent needed to handle your request. Public card information and comparisons are available without an account. Changes and effective dates will be posted here, with advance notice or consent when required for material changes.