CloudInvoicePayment state is verified
Stripe and Razorpay payment outcomes are recorded only after the application checks the relevant webhook or signature. A browser redirect is not treated as proof of payment.
Customer commitment
Trust should be earned before it becomes a testimonial.
CloudInvoice does not publish invented logos, customer counts, or case studies. Customer stories will appear here only with permission. Until then, the useful thing to publish is what the product does and where its current boundary sits.
Workspace data is scoped
Authenticated client and invoice queries resolve the current organization and are intended to limit records to that workspace.
Client links are opaque
Public invoice pages use high-entropy tokens rather than sequential invoice IDs. The sender and recipient should still treat every payment link as confidential.
Invoice documents stay portable
Individual invoices can be printed or saved as PDF through the browser. Bulk data export and self-service account deletion are not available yet.
Current boundaries
What CloudInvoice does not claim.
- There is no published customer testimonial until a customer approves one.
- There is no self-service bulk export or account-deletion workflow today.
- There is no published backup-retention or historical uptime commitment.
- There is no claim of SOC 2, ISO 27001, PCI DSS certification, or an independent security audit.