Contact and support
Use only a published PRUVILO support channel
Future support will connect questions and authorized actions to the correct account, deal, payment, delivery, or dispute context.
Pre-launch preview — no support form, email, phone, messaging account, office address, operating hours, or response-time commitment is published yet.
Safeguards for every future support path
A contact method will be listed only after its ownership, access controls, operating process, and escalation path are approved.
- Keep requests in context
- Deal-specific questions should begin from the relevant authenticated deal or case when that workflow becomes available.
- Never reveal authentication secrets
- Support must not ask for a one-time code, password, full card number, or raw biometric data.
- Confirm sensitive actions securely
- Account changes and other sensitive actions require a secure in-app confirmation; high-value releases or refunds require approval.
- Preserve accountability
- Support access, internal actions, attachments, and outcomes must be scoped and recorded.
Service claims need live evidence too
See why PRUVILO will not publish uptime or incident claims before production monitoring exists.