Delete your EIZO account
Request deletion from the website or app without reinstalling the app.
Active · Version 2026-10-19.4
Request account and associated-data deletion #
On iOS or Android, open Privacy & safety, choose Account and data requests, then Delete account. The website offers the same form at /privacy, so the app does not need to be installed. Sign in, review the consequences and explicitly confirm deletion. Keep your receipt ID. We send a receipt, progress updates and completion confirmation to your verified account email after sign-in access is removed; you do not need to submit another request. If your account has no verified email, keep the receipt and contact corp@eizo.watkinsx.com for updates.
Confirmation immediately makes the account inactive and nonvisible and queues background deletion. Workers remove data in bounded steps and retry interrupted work. This process starts immediately; do not rely on a cancellation period or assume account recovery will reverse deletion. The receipt is not confirmation that all data has already been erased. It remains under review until the remaining domains and retention exceptions are resolved.
What the request covers #
The request covers the account and associated personal data across EIZO, including profile and sign-in data, owned content, comments, interactions, subscriptions and messages, subject to narrowly justified retention. It applies to the shared website/app account. Staff must verify completion across account, content, messaging, media storage, notifications and backups; disabling the login is not account deletion.
Retained records and other people’s copies #
Limited data may need to be retained for documented legal obligations, fraud prevention, security investigations or claims. Any such exception must identify the data, purpose and retention period in the response. Our target is to finish active-system deletion within 30 days of the request. We send progress updates at least every seven days while the case remains open and confirmation after verified completion. Shared ownership, unresolved execution or external copies can cause delays; staff must explain remaining work and any justified retention rather than report incomplete deletion as complete.
Publicly shared content may already have been copied by others or sent to an external service at your direction. Device downloads and third-party copies are separate from the server account. You can remove local downloads in the app; staff must explain any copies EIZO cannot control.
Managed database backup archives are private and become eligible for deletion 30 days after their original modification time. Daily cleanup normally removes them by 31 days; an interrupted cleanup can delay expiry. This schedule covers the managed database archives, not every external export, provider copy or participating device.
A separate deletion ledger records the request and account identifiers and request time so a database restore can reapply deletion requests. It is copied to a second server and kept separately from expiring database archives. These minimal recovery records remain while retained copies could restore the deleted data. A restore must replay deletion requests before the restored service is exposed to users.
The request remains under review until all six cleanup domains have supporting evidence. Verified active-account cleanup does not automatically verify backups or external copies.
A verified email address is retained separately from the erased account solely to deliver deletion receipts, progress updates and completion confirmation. It does not preserve login access. The contact is removed seven days after successful completion notification, or 30 days after completion if delivery repeatedly fails. Delivery status is monitored by staff.
If you cannot sign in #
If you cannot sign in, use account recovery or contact corp@eizo.watkinsx.com for help verifying ownership, including for a suspended account. Do not send passwords, authentication codes or unnecessary identity documents. Requests involving another person’s data require appropriate authority.