Account and data deletion
Deleting your account, and what goes with it.
This page explains how to have your eZacto account, and the data held
against it, deleted. It covers the eZacto
mobile app (com.ezacto.app on Google
Play, eZacto on the App Store). What the app handles
in the first place is set out in the
app privacy policy.
Who handles your request
The mobile app connects to the eZacto server you select. Your workspace operator controls your account and business records. Using our app does not give CONFLICT access to a customer-operated server. Contact that operator for its privacy notice and retention schedule.
If you separately contract with CONFLICT for a hosted workspace, the hosted account-closure and records-retention terms apply to that service. This page does not promise hosted availability or change the policies of independently operated servers.
Request deletion in the app
Open More → Delete Account → Request deletion. Available steps depend on your app version and workspace. Versions supporting request tracking let you review the operator's deletion policy, submit a request and keep access to its status after sign-out. Submitting a request does not itself confirm closure or require an immediate sign-out; the operator must assess and fulfil it, including any applicable retention duties. Older versions or request routes may sign you out after you acknowledge receipt. That acknowledgement also confirms only the request, not completed erasure. If your server does not support in-app requests, the app opens this page so you can contact its operator directly.
Ask for confirmation of account closure, the personal data erased, any records retained, their retention basis and period or review criteria. Deactivating a login alone does not complete every personal-data request. Removing one member does not authorize deletion of the organization's shared records or other people's data.
Apple sign-in cleanup
Builds using our Apple authentication service manage Apple's sign-in authorization separately from workspace account closure. The service uses encrypted credentials to request revocation from Apple and keeps limited confirmation information so an unavailable workspace can receive it later. A provider error leaves Apple cleanup unresolved; it is not confirmation that the workspace account or its records were erased. A workspace can assess and fulfil its own deletion duties while external cleanup is pending.
Revoking Apple authorization can affect other eZacto sign-ins associated with the same Apple authorization, including grouped apps or websites. It is not guaranteed to affect only one device or workspace. Ordinary sign-out does not itself revoke Apple authorization. If credentials are missing or outdated, completing cleanup may require a fresh Apple authorization tied to the original request; it must not recreate your workspace account.
Keep the app's pending cleanup information until the original workspace confirms receipt, or explicitly discard it if you no longer want the app to recover that delivery. Discarding a confirmation does not prove the workspace received it. The service's delivery recovery window is up to 90 days after confirmed revocation; once it expires, contact the workspace operator if completion remains unconfirmed. The app privacy policy explains credential retention and provider recovery copies. You can also review your Apple authorization in your Apple Account settings; changing it does not by itself erase workspace business records.
Account closure and required records
Account access and personal data that is no longer needed can be removed while required financial records remain. In a time-tracking and invoicing system, the evidence may include who performed the work, when it was performed, hours, rates, approvals, invoice and payment links, and the history of corrections. Removing or anonymizing necessary worker attribution can make a retained record unusable for a billing, tax or payroll audit.
Retention must be limited to the records and identifying details necessary for an applicable obligation or other lawful purpose. It does not authorize keeping every profile field, credential, support message or unbilled draft forever. The operator must determine which rules apply and explain any partial refusal of erasure. For CONFLICT's hosted services, see the US and Florida retention criteria and privacy-rights limitations.
Data CONFLICT holds separately
To request deletion of support correspondence or identifiable crash diagnostics or Apple authentication information we hold, use More → Contact support, or email privacy@ezacto.com with the subject “Account and data deletion”. Include the address associated with your correspondence and enough information to locate it. Do not send passwords, payment-card details or unnecessary customer records. We may request proportionate identity verification.
We assess data under our control, erase what is no longer needed and explain any information retained for an applicable legal duty or necessary legal claim. We cannot erase records held independently by your workspace operator, Apple or Google. Their own request channels and notices apply.
Timing, retention and backups
For requests to CONFLICT, we aim to acknowledge receipt within five business days. Where GDPR applies, we respond without undue delay and within one month; an extension of up to two further months is possible where necessary because of complexity or the number of requests, with notice and reasons within the first month. This is a response deadline, not a promise to erase records that must lawfully be retained. Other applicable statutory deadlines remain protected.
Each workspace operator controls its own backup schedule. There is no universal 90-day backup-erasure guarantee for self-hosted servers. CONFLICT's hosted terms require the applicable backup and retention schedule to be disclosed for that service; they do not give an unlimited exception for backup copies. Ask the responsible operator for the period and treatment of records restored from a backup.
Device data and store subscriptions
Use the app's sign-out action to clear its ordinary workspace login token and persisted cache. In builds supporting request recovery, limited deletion-request information remains separately in secure storage so you can check status after sign-out, including requests that did not use Apple sign-in. Pending Apple cleanup information may also remain for recovery. Remove a saved deletion-status record explicitly using its Remove action when you no longer need it. Completion or expiry of server status access does not automatically remove that device record, and removing it does not cancel the operator's deletion request. Uninstalling the app is not a reliable way to erase iOS secure-storage entries and does not erase server records or Apple's purchase history. Account deletion does not cancel an Apple or Google subscription: manage it in your store account settings.
References and your rights
Apple's account-deletion guidance permits legally required records to remain, while requiring account deletion rather than temporary deactivation where its rule applies. GDPR Articles 12 and 17 address request handling, erasure and its exceptions. See the hosted terms' legal references for the US, Florida, California, Texas and EU provisions and their respective scope.
Apple's Sign in with Apple account-deletion guidance explains credential validation and revocation. Successful provider revocation and completed workspace erasure are separate outcomes.
Contact
Questions about deletion: support@ezacto.com, or Contact support in the app.