Data Deletion Instructions

Delete a Jinu workspace

A workspace owner can permanently delete a workspace through Jinu's authenticated deletion operation. The operation requires the exact workspace confirmation and a fresh password check. It cascades through the workspace's connections, automation rules, events, deliveries, conversations, messages, and audit records in the active database.

The dashboard control and production support contact are not yet published. Before launch, use [PRIVACY CONTACT EMAIL] for verified assistance; the operator must replace this placeholder with a monitored address.

Delete the global Jinu account

After deleting every workspace they own, a signed-in user can enter the exact DELETE ACCOUNT phrase and current password. Jinu then removes the global user record, email address, authentication sessions, and any remaining workspace memberships from the active database, and clears the current session cookie.

Account deletion is blocked while the user still owns a workspace so that tenant data cannot be orphaned. Delete each owned workspace first; membership in a workspace owned by someone else is removed with the account.

Remove Jinu through Meta

After the production Meta app is configured, removing Jinu from the relevant Meta or Instagram business integration can cause Meta to send Jinu a signed deletion request. Jinu's callback verifies that request and deletes the associated Instagram connection and its dependent tenant records. A confirmation code and privacy-preserving status URL are returned to Meta.

This route cannot be exercised until the Meta app, callback URL, and test account are configured. Removing access may also stop automations immediately.

What may remain temporarily

Active-database tenant and account records are removed by the implemented deletion operations. Raw webhook payloads are separately scheduled for redaction after 30 days. Production backup, infrastructure-log, support, legal-hold, and aggregate-data schedules remain [OWNER/COUNSEL TO DEFINE] and must be published before launch.

Request help

Contact [PRIVACY CONTACT EMAIL] with the Jinu account email and workspace name. Do not send passwords, OAuth tokens, Meta App Secret, message contents, or copies of identity documents unless Jinu provides a secure, necessary verification method.