Privacy & data handling — draft

The released manifest and observed flows are authoritative.

• Freshservice ticket IDs, statuses, fulfillment fields and related metadata, if used.
• App configuration, event metadata and operational diagnostics, if used.
• Permissions, outbound requests and third-party processing must be enumerated before launch.

No unverified hosting or retention promises are made here.

• Limit collection and access to functions supported by the validated app.
• Confirm whether anything is stored, where it is processed and which parties receive it.
• Document retention periods, export, deletion and uninstall behavior after evidence review.

Final provider identity and effective date are pending legal verification.

• Contact privacy@ankaiho.com about privacy questions.
• Avoid sharing private ticket content or credentials in support messages.
• A formally reviewed policy is required before production or public launch.