Data handled by Givemora.

What we store

The service stores account and workspace identifiers, membership roles, project and environment metadata, credential hashes and prefixes, event metadata and payloads, delivery state, provider outcomes, billing records, and redacted operational audit data needed to operate the service.

How data is used

Data is used to authenticate requests, isolate workspaces, apply event policies, deliver notifications, recover failed work, measure usage, enforce quotas, process billing state, and protect the service. Raw credentials and one-time secrets are not returned from management reads.

Retention and deletion

Resolved event history is subject to the configured retention process while durable usage and audit records remain available for their operational purpose. Delivery recovery state is retained until it reaches a terminal outcome or is handled by the documented recovery process.

Your responsibility

Do not send credentials, payment secrets, or unnecessary personal data in event payloads. Use project and environment boundaries to limit access, revoke credentials that are no longer needed, and review delivery destinations.

Questions

Workspace Owners can start with the private Givemora Telegram bot and /help. A formal privacy contact and data-subject workflow will be published before public onboarding opens.