# Vantemio Donations: donor and creator rules

Revision 2026-10-16 · Product policy specification · In development

## 1. Scope

These rules accompany the [Donations technical paper](donations.md). The inspected payment implementation is testnet-only. Publication of this policy does not enable real payments. The accepted release must identify its operator, available functions, network, assets and applicable terms before checkout.

Support is separate from a Market purchase and does not by itself promise a product, service, investment return or tax receipt. If a creator offers rewards or deliverables, their terms and fulfilment responsibilities must be disclosed separately before payment. A transaction label cannot replace those obligations.

## 2. Information before authorization

The donor must be able to review creator identity, recipient, network, asset and amount, current fee accounting/collection method and separate network cost. The current 1% ledger allocation must not be presented as an implemented on-chain deduction: the prepared transaction sends the full amount to the creator. Changes to recipient or profile version require a fresh review; an already submitted transfer must be reconciled before another authorization.

The creator must keep the authorized payout profile current and protect account access. A wallet connection does not grant unrestricted spending or permission to reuse credentials for another service.

## 3. Messages and creator conduct

Optional messages may appear in the creator's stream presentation. Do not include credentials, private contact details, other people's personal information, impersonation, threats, prohibited content or executable instructions. Review and restriction procedures must identify the applicable rule and preserve decision history. The current sanitation code is not a complete moderation system or a guarantee that content is appropriate.

Creators must describe support accurately and avoid fabricated affiliation, guaranteed outcomes or misleading payment requests. Removal of an alert is not a cancellation of the underlying transfer.

## 4. Delivery questions and refund requests

A confirmed transfer, an accounting entry and a visible alert are distinct outcomes. An unavailable or hidden alert must not trigger an automatic second charge. Investigations use the original intent, chain, transaction hash, creator and relevant event time.

Deleting a website entry does not reverse a blockchain transfer. Any agreed correction or refund requires its own authorized operation, reasons and linked record; it must not replay the original payment. These product rules do not purport to waive mandatory rights. They do not promise an automatic refund engine or create a Boson purchase-dispute procedure for a support transfer.

## 5. Data and privacy

Wallet addresses and transaction records may be public on-chain; a display name or hash does not guarantee anonymity. Creator history and overlay access must remain scoped to the authorized creator. Private account identifiers, secrets and credentials must not enter public alerts or metadata. Explain message visibility, provider roles and retention for the accepted release under the [Privacy Policy](privacy.md) and [data request procedure](data-deletion.md). A data request does not erase public blockchain history.

## 6. Compromised access and incidents

Revoke exposed overlay access and secure the affected account through supported controls. Reports must never request seed phrases or private keys. Retain the original transaction reference; uncertainty requires reconciliation rather than repeated payment. Restrictions and incident recovery must preserve transaction history and permitted remedies.

## 7. Changes and support

Material changes to fees, recipients, supported networks or product rules require a dated revision and disclosure before a new authorization. Earlier transactions retain their original evidence and terms record. Contact [support@vantemio.com](mailto:support@vantemio.com) with the public transaction reference and issue summary, without wallet secrets or unnecessary personal data.

[Technical paper](donations.md) · [Donations roadmap](donations-roadmap.md) · [Terms](terms.md)