PRECISION IN VIEWDEEPCAM / PRIVACY
Privacy Notice
How we process your information, retain it and handle privacy requests.
Privacy Policy v1.0 · Effective 2026-10-28
1. Scope and controller
DentalX Co., Ltd. processes information needed for product, sales and meeting enquiries, email verification, warranty registration and service requests through the DeepCAM website. This policy does not authorize collection of camera-stored patient images or clinical records through this website. The website does not provide patient-data/file uploads, membership accounts, online payments or marketing subscriptions.
2. Purposes information and collection
Email verification: email address, verification reference/time, failed-attempt count and consent version. Product/sales/meeting enquiries: name, email, topic and message are required; organization and country are optional. Warranty: name, email, model, serial number, purchase date and seller are required; organization is optional. Service: name, email, model, serial number, issue details and operating system are required; organization and app version are optional. Information is collected through forms and follow-up emails provided by the user; references, consent, case and delivery records are generated. IP/browser information is used for delivery and security; rate-limit identifiers are HMAC protected. Optional fields may be omitted. Do not send patient names, health data, clinical footage, government identifiers or passwords.
3. Processing and transfer grounds
Collection and use through the forms rely on explicit consent for the disclosed purposes. Separate disclosure and consent for international transfers is the default route, distinct from collection/use consent. Where a statutory notification route applies to outsourcing/storage necessary for a contract, its purpose and ground are identified separately; general enquiries are not automatically treated as a contract exception. Information is not used for unrelated marketing or automatic contract confirmation.
4. Retention periods
Request, consent and case records and related company email copies are retained only as needed, within five years of initial receipt. Initial consent lasts 24 months, with explicit-renewal reminders 30 and 7 days before expiry. Opening a link or silence is not renewal; no renewal extends beyond the five-year cap. Processing stops upon purpose completion, withdrawal or expiry; documented legal holds are separated before deletion. These are company limits, not statutory patient-record periods. Codes are valid for 10 minutes; expired verification email/code-check values in the database are cleared within 24 hours. Duplicate sent outbox bodies are cleared within 30 days. Company verification emails are removed from operational use within 24 hours under the operating process; Trash and provider recovery copies follow the deletion procedure below.
5. Deletion and recovery copies
Deletion reason, target and policy version are recorded in a work ledger; database and company-controlled mailbox/workflow copies are handled together. Electronic records are deleted or their identifying values/body are irreversibly removed; paper copies are shredded or otherwise destroyed. Moving email to Trash is not permanent deletion. Operational-folder removal, Trash state and permanent-deletion confirmation are recorded separately; a designated administrator confirms permanent deletion where no supported automated API exists. We do not promise immediate physical disappearance of Lark recovery copies or plan-dependent Cloudflare D1 recovery history. Residual recovery copies are excluded from business use. After restoration, the external deletion ledger is reapplied before service resumes. Legal holds identify the exact data, ground, end date and authorized access. The customer's own inbox is outside company deletion control.
6. Disclosure and processors
We do not sell customer information or disclose it for advertising. Disclosures outside the stated purposes require separate consent or another applicable legal ground. Cloudflare supplies web/API, D1 and Turnstile services; Lark handles verification, acknowledgement and response emails. If separately enabled, Lark Base handles minimal workflow identifiers without newly copying customer names, emails or enquiry bodies. The service-specific transfer table below identifies recipients, information, country scope, timing/method, purposes, retention and refusal options. Unused provider products and advertising vendors are not represented as our processors.
Service-specific processing and transfer disclosure
Recipient entity location, observed storage region, edge requests and provider support/recovery are distinguished. This is not an exclusive-country storage promise; disclosures rely on official contracts and service/country-scope documentation.
Entity location, organization storage region, global edge and provider-own processing are disclosed by service below. Cloudflare group-recipient countries for its own processing are not combined into a Workers/D1 execution-country list.
Web delivery, security and Workers requests
| Recipient and contact | Cloudflare, Inc. dpo@cloudflare.com |
|---|---|
| Processing role | Processor for web/API delivery; provider network-security data has a separate policy scope |
| Information transferred | IP, connection/routing and browser data; after forms open, verification email and submitted enquiry/product/support data during API processing |
| Countries, scope and evidence | Recipient entity: United States. Web/Workers requests are processed at Cloudflare global data centers according to routing (official network list below). DPA support/subprocessing and D1 storage are separate. The Korean addendum’s 15 group-recipient countries are not treated as Workers execution locations. |
| Timing and method | HTTPS/TLS automatically on page visits and requests |
| Purpose | Website delivery, request handling and malicious-traffic protection |
| Retention | API responses use no-store. Persisted request records follow the D1 row. Provider security/network data follows its purpose-based policy; a fixed period is not confirmed |
| Processing ground | Form email/name/message data requires separate international-transfer consent before verification. Before form consent, IP/routing/browser information necessary for web delivery is still processed; form consent is not applied retroactively to that processing. Necessary web delivery/security, minimization and provider roles are distinguished. |
Sources: Official source 1 · Official source 2 · Official source 3 · Official source 4 · Official source 5 · Official source 6
D1 request, consent and workflow records and recovery history
| Recipient and contact | Cloudflare, Inc. dpo@cloudflare.com |
|---|---|
| Processing role | Storage/query processor |
| Information transferred | Submitted fields, verification/consent version and time, workflow/delivery records and internal IDs; patient information is not requested |
| Countries, scope and evidence | Recipient entity: United States. The production primary database was observed in Japan (NRT). APAC is a location preference, not an exclusive Japan storage contract. Support/recovery processing follows Cloudflare DPA/subprocessor scope. Edge request processing is distinct from primary database storage. |
| Timing and method | Worker-to-D1 binding on verification, submission and workflow actions |
| Purpose | Enquiry responses, warranty/support review, consent history and disaster recovery |
| Retention | Requests up to 60 months with explicit 24-month renewal checks and earlier deletion on purpose completion/withdrawal. Sent outbox bodies 30 days; expired verification/rate-limit records within 24 hours after expiry. Provider recovery history is 7 days on Free or 30 days on Paid, separate from live-row deletion |
| Processing ground | Separate international-transfer consent under PIPA 28-8(1)(1), distinct from collection/use consent and disclosed before verification. |
Sources: Official source 1 · Official source 2
Turnstile protection of verification requests
| Recipient and contact | Cloudflare, Inc. dpo@cloudflare.com |
|---|---|
| Processing role | Processor for protecting this site; Cloudflare acts separately as controller when processing signals to improve detection |
| Information transferred | Signals including IP, TLS fingerprint, User-Agent, Sitekey/origin and verification token. We do not pass names or enquiry bodies as Turnstile verification parameters |
| Countries, scope and evidence | Site-protection requests use Cloudflare’s global network. For Cloudflare’s own detection-improvement processing, its Korean addendum lists group recipients in the US, UK, Singapore, Australia, Germany, Portugal, France, Japan, Canada, Netherlands, UAE, India, Mexico, Malaysia and Sweden. That list is not extended to D1/Workers storage or execution. |
| Timing and method | Browser signal transmission and server HTTPS verification when online verification is enabled; the current closed forms do not load the script |
| Purpose | Bot detection/blocking and provider detection improvements |
| Retention | Distinguish company D1 verification records from provider-held signals; do not claim the company’s 24-hour cleanup promise applies to provider signals |
| Processing ground | The browser Turnstile widget loads after collection/use and separate transfer consent. Delegated site protection is distinguished from Cloudflare’s own detection-improvement processing, which follows its Turnstile privacy addendum. |
Sources: Official source 1 · Official source 2
Lark Mail verification, receipt and staff emails and company-controlled copies
| Recipient and contact | Lark Technologies Pte. Ltd. privacy@larksuite.com |
|---|---|
| Processing role | Processor of company-controlled business data |
| Information transferred | Email address, name, enquiry/product/support content, reference and delivery metadata; workflow reminders primarily contain reference and task link |
| Countries, scope and evidence | Recipient entity: Singapore. DeepCAM organization data residency is Japan in Admin settings. Lark’s published server countries are the US, Singapore and Japan; support/subprocessing scope also applies. This does not guarantee that all processing occurs exclusively in Japan. |
| Timing and method | TLS SMTP and Lark Mail during verification, submission, staff notification and staff replies |
| Purpose | Email verification, acknowledgement/responses and internal staff case handling |
| Retention | Company case emails follow the case end condition. Verification emails are managed for removal from operational use within24 hours; Trash and permanent-deletion confirmation are recorded separately. API Trash is not reported as permanent deletion. Provider recovery/backups follow provider policy and re-deletion after restoration. Customer inboxes are outside company control. |
| Processing ground | Separate international-transfer consent under PIPA 28-8(1)(1), distinct from collection/use consent and disclosed before verification. |
Sources: Official source 1 · Official source 2 · Official source 3
Internal Lark Base enquiry workflow table
| Recipient and contact | Lark Technologies Pte. Ltd. privacy@larksuite.com |
|---|---|
| Processing role | Processor of company-controlled business data |
| Information transferred | Enquiry reference/internal ID, topic/language/receipt time, queue and response/meeting/follow-up state. Customer names, organizations, email and enquiry bodies are not newly synchronized; staff consult company email |
| Countries, scope and evidence | Organization Japan residency verified; distinguish Base history/recovery and support scope from storage-location guarantees |
| Timing and method | After explicit operational enablement, synchronize scoped cases and staff edits through HTTPS API |
| Purpose | Queue, unanswered-enquiry and meeting follow-up management; Messenger is not an adopted workflow channel |
| Retention | Follow the case’s end condition. Check history/recovery after row deletion and re-delete following restoration. Never delete the whole shared table to erase one case |
| Processing ground | Separate international-transfer consent under PIPA 28-8(1)(1), distinct from collection/use consent and disclosed before verification. |
Sources: Official source 1 · Official source 2
Refusal and its effects
Refusing international-transfer consent prevents online verification/submission. Product resources remain accessible without an account. Email also uses Lark and is not a transfer-free alternative. Discuss other contact/processing arrangements with the company.
7. Rights refusal and withdrawal
Request access, correction, deletion, restriction or withdrawal at svc@deepcam.ai. Include the request type and case reference if available. Do not send ID copies, passwords or verification codes in the initial request. Identity/authority checks are limited to what is necessary; applicable legal restrictions and their scope are explained. Refusing required processing or necessary international transfer may limit online verification/submission; general product resources remain accessible without an account. Discuss alternative contact and processing arrangements with staff. GDPR rights requests, where applicable, normally receive a response within one month; necessary extensions and reasons are notified within that first month.
8. Safeguards cookies and automation
Safeguards include HTTPS/TLS, role-limited access, provider-encrypted secret management, input validation/rate limiting, minimal workflow data and deletion records. This website has no advertising/behaviour-tracking tags; Turnstile is used for security when intake is enabled. Browser cookie restrictions may limit some verification functions. Intake, verification, notifications and retention checks may be automated, but warranty eligibility, contracts, meetings and medical judgments are not decided solely automatically. The service is not directed to children under 14; identified child data is handled appropriately. Incidents are notified/reported as required, with containment, rights handling and re-deletion after restoration.
9. Contact and changes
Privacy officer: Hekjun Jang, svc@deepcam.ai. Controller: DentalX Co., Ltd., representative Namjong Kim, business registration 467-86-04047, Room 308, 3rd floor, Daerim Plaza, 804 Deongneung-ro, Nowon-gu, Seoul, Republic of Korea. Changes identify the version, effective date and substance on the website. Where fresh consent is required, notice/consent precedes the change. Other companies' policies or provider certifications are not represented as legal certification of our service.
Policy identifier: deepcam-privacy-1.0