Email data, exports and account removal¶
Zerohive stores the information needed to connect your work mailbox, send messages and record email linked to business work. Your email provider continues to hold the mailbox itself. An organization export or removal therefore has several parts, with different completion results.
Use this page to understand the email portion of an organization export or deletion. Confirm the final organization-wide result with the responsible administrator.
What information belongs to Zerohive?¶
| Information | What it means |
|---|---|
| Organization email settings and their history | The selected service, permitted sign-in methods, connection settings and changes to that configuration. |
| Personal mailbox connection | The person's mailbox identity, saved connection state and references to protected credentials. |
| People information used by email | The local copy of user information used by this service. Other workforce and account records have their own owners. |
| Outgoing email records | Recipient details, subject, message body, sending state and available delivery or verification evidence. This can include sensitive message content. |
| Email linked to business work | Recorded responses, verification details and records used to publish their contribution to activity reporting. |
Passwords and provider tokens are kept separately from these records and are not retrieved for this export. The exported configuration details, message content and business evidence still need controlled access.
Understand an organization export¶
The email portion of an organization export includes stored settings, mailbox connections, local people information, outgoing messages and work-linked evidence.
It does not download the provider's entire inbox, folders or attachments to make a mailbox backup. It does not prove that every other Zerohive service has completed its export, that a final package is ready, or that the package can restore a working mailbox connection.
Before relying on an export, have the responsible administrator confirm the scope, the final job result and how the package can be accessed. Plan separately for provider mailbox exports and any recovery requirement. Treat the package as sensitive organizational information.
Distinguish disconnection from organization deletion¶
Disconnecting your mailbox clears the personal connection. It does not remove all organization email records or delete messages from the provider.
Organization deletion removes the email records listed above, including settings history, mailbox connections, local people information, outgoing email records and work-linked evidence. It also requests separate background cleanup of the associated credentials.
These results must be checked separately:
| Result | What it establishes |
|---|---|
| Email data removal finishes | The listed email records for the organization have been removed. This is one part of the wider organization operation. |
| Credential cleanup finishes | The requested cleanup reached its own confirmed result. It may complete after the business records are removed. |
| Provider access is revoked | The provider-side authorization was removed through its own supported process. A Zerohive cleanup result alone does not establish this. |
| Provider messages are deleted | The provider's own message-deletion process completed. Zerohive does not perform this as part of its email data removal. |
A reported count of zero retained Email business records does not prove that backups, logs, temporary sign-in state, older configuration copies, other services or provider systems contain no related information. Retention and removal of those stores need their own verified scope and outcome.
After an upgrade or recovery¶
An older mailbox record may keep its work email and identity while requiring a fresh connection. The mailbox migration does not recover the old password or transfer it into a new connected session. Follow the supported connection guide; do not assume a familiar email address means the connection is active.
Older organization settings may also be carried forward. Their presence does not prove that provider sign-in, incoming mail or outgoing mail works. The administrator should check the current organization settings, while individuals complete their own connection when required.
If an organization has been removed or restored, ask support to confirm that older configuration copies and pending cleanup have been reconciled. Repeatedly reconnecting or changing settings can make an uncertain recovery harder to resolve. Use the provider-access recovery guidance to supply useful information without sharing credentials.
Questions for the responsible administrator¶
Before a transfer, closure or recovery, establish which organization and time period are involved, which records are required, who can receive the export and who confirms each completion result. Account for provider-held mail and records owned by other Zerohive services. Preserve the original job or support reference when the outcome is unclear.
The current interface remains a preview. Use confirmed job results when checking whether a real export, deletion or recovery has completed.