# Security model Creator Vault uses smart contracts to create & manage campaigns/bounties ### Immutability Contracts are intended to be immutable. Expect core rules to be enforced exactly as deployed. ### Campaign funds * Withdrawals follow explicit rules (goal reached or deadline reached). * Refunds are only possible before withdrawal. * Refunds require creator approval. See [Withdrawals, fees, and refunds](/documentation/creator-vault/campaigns/withdrawals-fees-and-refunds.md). ### Bounty reward pools * Rewards are deposited into an immutable pool. * Creators or Projects cannot withdraw the pool back. * Distribution happens once, after the end date. See [Bounty security](/documentation/creator-vault/bounties/bounty-security.md). ### What requires human trust * Campaign delivery and perk fulfillment are off-chain. * Refund approvals are a creator decision. * Bounty winner selection is a creator decision. ### User safety checklist * Verify URLs and social handles from official sources. * Start with small amounts when testing. * Keep transaction hashes for record keeping. * Never share seed phrases or private keys. ### Audit status coming soon... --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://creator-vault.gitbook.io/documentation/creator-vault/reference/security-model.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.