세이프클릭
Privacy Policy
최종 수정일: May 4, 2026
1. Information We Collect
1.1 Required Information
| Category | Data Collected | Purpose |
|---|---|---|
| Guardian account | Email address | Account creation and device pairing |
| Solo (Protect my device) account | Supabase anonymous UUID | Minimum identifier for self-protection without pairing. No email or name collected. |
| Pairing code | Temporary code (discarded after pairing) | Securely linking guardian and protected devices |
| URL inspection records | SHA-256 hash of URLs only | Detecting malicious links and generating alerts |
| Sender information | SHA-256 hash of sender name and phone number | Detecting smishing patterns |
Important: Original URLs, phone numbers, sender names, and message content are never transmitted to or stored on our servers. All hashing is performed on-device.
1.2 Optional Information
No optional information is currently collected.
1.3 Auto-generated / On-device data (not transmitted)
| Item | Storage | Retention | Purpose |
|---|---|---|---|
| FCM token | Device local | Deleted immediately on unpair | Sending push alerts to guardian device |
| Weekly warning event log | Device local | Auto-deleted after 14 days | In-app history display |
2. How We Use Your Information
- Malicious link detection: URL hashes are checked against the Google Safe Browsing API
- Guardian alerts: Dangerous events trigger push notifications to the guardian device via FCM
- Service operation: Managing device pairing and aggregating warning history
- Service improvement: Anonymized statistical analysis only
3. Data Retention
| Data | Retention | Deletion |
|---|---|---|
| Server-side event records (hashed) | 90 days | Automatic expiry |
| Guardian email | Account lifetime | Immediate on account deletion request |
| FCM token | Pairing lifetime | Immediate on unpair |
| On-device warning log | 14 days | Automatic expiry |
4. Third-party Processors
We do not sell or share your personal data for advertising purposes.
| Processor | Task | Data shared |
|---|---|---|
| Google LLC (Safe Browsing) | URL threat lookup | SHA-256 URL hashes |
| Supabase, Inc. | Authentication and storage | Email, hashed event records |
| Google LLC (Firebase Cloud Messaging) | Push notifications | FCM token |
| Cloudflare, Inc. | API processing and caching | Request hashes (transient) |
5. Your Rights
You may exercise the following rights at any time:
- Access: View the information we hold about you
- Correction: Fix inaccurate information
- Deletion: Delete your account and all associated data
- Restriction: Stop specific processing activities
Contact us at the address below and we will respond without undue delay.
6. Account & Data Deletion
6.1 Automatic Deletion
- Anonymous (Solo) accounts: Automatically deleted after 30 days of inactivity.
- Server event records (hashed): Auto-expired after 90 days.
- On-device warning logs: Auto-expired after 14 days.
- FCM tokens: Deleted immediately upon unpair or app removal.
6.2 Manual Deletion Request (Immediate)
You may request immediate deletion of your account and all associated data through one of two channels:
- In-app deletion: App Settings → Account → Delete Account (available on all plans).
- Email request: Send an email to support@getsafeclick.com with the subject "Account Deletion Request" and your registered email in the body.
6.3 Deleted Data and Processing Time
We delete the following data within 48 hours of receiving a request:
- Guardian email / anonymous UUID
- All server-side hashed event records
- FCM token
- Pairing information (links to family members)
Original URLs, phone numbers, and message contents are never transmitted to our servers in the first place, so no separate deletion procedure is required.
7. Security Measures
- Encryption in transit: All server communication is encrypted with TLS 1.2 or higher.
- On-device hashing: Original URLs, phone numbers, and contacts are never transmitted — only SHA-256 hashes are used.
- Access control: Supabase Row Level Security ensures you can only access your own data.
- Data minimisation: We collect only the minimum information required to provide the service.
8. International Scam Call/SMS Alert
Calls or messages from international prefixes (non-Korean, +82 excluded) where the sender is not in your saved contacts are automatically detected on-device and shown as a fullscreen warning. The detection works as follows:
8.1 On-Device Processing Principles
| Item | How it works |
|---|---|
| NLS notification title analysis | Performed entirely on-device. Message body / raw sender number are NEVER sent to the server. |
| READ_CONTACTS permission | Not requested. Saved-contact matching uses the sender info (name or number) that Android OS already displays in the notification. |
| Whitelist | Users can register trusted senders/prefixes locally (Room DB) to bypass detection. Device-level, not synced to server. |
8.2 Information Sent to Server (Alert Statistics Only)
| Item | Detail |
|---|---|
| SHA-256 hash of sender number | Raw number NEVER transmitted. Used to count distinct user attempts. |
| International prefix | Example: "+006". Used for prefix distribution statistics. |
| Channel | sms / call / kakao etc. Used for channel distribution statistics. |
| Guardian notification (when family-paired) | Only SHA-256 hash + prefix + channel + senior device label sent via FCM. Message body / raw sender number are NOT transmitted. |
Important: Message body / raw sender number / saved contacts data are NEVER transmitted to the server through any path. Only on-device NLS notification title regex matching + SHA-256 hashing are performed.
8.3 Guardian Escalation Relay (Family Pairing + Guardian "Mark as Danger")
| Item | How it works |
|---|---|
| Escalation data transmission | When a guardian selects 'Mark as Danger', only the SHA-256 hash + prefix is relayed via FCM to the senior device. |
| Server storage (permanent or transient) | The server does NOT store escalation relay data permanently or transiently. Data is discarded immediately after FCM relay. |
| Senior device local storage | The escalated sender's SHA-256 hash is stored in the senior device's Room DB. The raw sender number is never stored. |
9. Revision History
| Version | Date | Changes |
|---|---|---|
| 1.0 | 2026-04-21 | Initial release |
| 1.1 | 2026-04-21 | Detection data sources section added |
| 1.2 | 2026-04-22 | Solo mode anonymous account guidance added |
| 1.3 | 2026-04-23 | Operator business information added |
| 1.4 | 2026-04-30 | Section 6 (Account & Data Deletion) added with 30-day inactivity auto-delete and manual request procedures |
| 1.5 | 2026-05-04 | Section 8 added — International Scam Call/SMS Alert privacy provisions |
| 1.6 | 2026-05-04 | Section 8.3 added — Guardian escalation relay: no server storage principle |
10. Operator Information
| 항목 | 내용 |
|---|---|
| 상호 | 이호트레이더스 |
| 사업자등록번호 | 525-38-00249 |
| 대표자 | 윤준호 |
| 사업장 소재지 | 서울특별시 구로구 고척로33라길 14-20, 102호 |
| 개인정보 처리 담당자 이메일 | krisakma@gmail.com |
| 고객센터(CS) | 010-3236-6754 |
| 카카오톡 문의 | ehotraders |