This policy explains what Voluma processes to run the product. The design goal is simple: keep data limited to what the app needs for authentication, automation, wallet operation, trading history, and reliability.
Voluma may store account details from login, such as your user ID, email, display name, and profile image. It also stores application data you create, including conditions, wallet records, trade history, pending transaction records, webhook URLs, and related activity logs.
Trading wallet public keys, encrypted private key material, balances, token metadata, withdrawals, exports, and trade activity may be processed so the app can show wallet state and execute requested actions.
Data is used to authenticate sessions, operate the dashboard, evaluate automations, execute trades, send webhooks, show history, monitor system health, prevent abuse, and debug reliability issues.
Voluma may send or receive data through services such as authentication providers, Supabase/Postgres, Solana RPC providers, Jupiter, and webhook endpoints that you configure.
Voluma uses server-side controls such as session validation, encrypted wallet storage, rate limits, SSRF checks, and sensitive-action verification. No internet-connected system can be guaranteed perfectly secure.
Operational records may be retained while your account or automations are active. Some records may be cleaned up automatically when no longer needed for pending transactions, deduplication, reliability, or product operation.
You can delete automations, avoid configuring webhooks, avoid exporting sensitive wallet material, and stop using Voluma. Account or data deletion requests should be sent through the available support channel.
This policy may change as Voluma evolves. Continued use after changes means the updated policy applies to your use of the product.
If you have privacy questions or want to request account/data deletion, use the support channel provided in the application or repository.