Data Deletion Instructions
Contact Foshan Guccident Medical Co., Ltd. about deleting your business inquiry information held in Guccident CRM.
01. Send a request
Email [email protected]. You do not need a CRM staff account to send a request.
- Say whether you want information deleted or inquiry follow-up stopped. You may also ask for access or corrections.
- Provide the email address or phone number used in your inquiry. If known, include the approximate submission date and Page or form name.
- Do not attach passwords, login verification codes, identity documents, patient records or payment card details to the initial request.
The privacy contact coordinates requests. A request received through another business channel can be referred to that contact; using this email address is not the only way to exercise an applicable right.
02. Verification and response
Only information reasonably needed to verify the requester and locate records should be requested. An email address alone does not automatically establish identity.
The selected internal targets are to acknowledge receipt within 5 working days and provide a substantive response within 28 calendar days of receiving the request. Any shorter applicable legal deadline takes precedence. These targets are not an inquiry-retention period. An acknowledgement is not a completed response; any permitted extension must be explained within the original deadline.
A designated internal colleague carries out specifically approved CRM record changes and server backup-related actions after checking the scope and necessary permissions, then records the result. The privacy contact is responsible for existing Excel/CSV customer exports held on company cloud storage and handles approved actions on those files with the same checks and recording. Choosing an execution role does not itself grant access or approve a deletion.
03. Records and backups
The request is assessed against relevant CRM records and applicable retention obligations. The response should explain completed actions and any information that must be retained, including its reason and scope.
Backups and relevant logs must be considered separately. The selected manual procedure requires approved deletions to be reapplied before restored records return to business use, with the result recorded. The complete backup inventory, restrictions and clearance plans still require implementation checks; no existing backup deletion is claimed.
Guccident has decided not to add further Excel/CSV customer exports to company cloud storage. This does not cancel CRM database backups or delete existing exports. These files remain within the scope of relevant requests; deleting a CRM record does not automatically change them. Where present, related file versions, trash and downloaded or synced copies must be assessed separately. No export blocking, sync disabling or automatic cleanup is claimed.
Deleting a CRM record does not automatically delete the original submission from Meta, your Facebook account or independent copies in Yingdiantong or another service. Disconnecting an integration also does not by itself remove all stored CRM records.
04. Full privacy notice
The Meta integration is currently being tested.
For information about data uses, retention, hosting and applicable rights, read the Guccident CRM privacy policy.