Security
Private feedback should stay private.
HiveFive handles business records and customer feedback, so security is part of the product, not an afterthought.
Accounts and sessions
Passwords are hashed with Argon2id. Owner sessions use httpOnly cookies and rotating refresh tokens. Tokens are never stored in browser JavaScript.
Tenant isolation
Every owner route checks organization ownership. Cross-tenant reads and writes return 404, and tests cover IDOR cases.
Payments
Card and UPI details are handled by the payment provider. HiveFive stores payment status and references, not full card numbers.
Public vs private
Public review and profile pages expose only the fields intended for customers. Feedback, leads, cash records and invoices require an authenticated owner session.
Input and abuse controls
Requests are validated, rate-limited and scoped. Uploads, when enabled, will be validated by file signature and re-encoded.
AI drafts
AI prompts contain business settings and customer-selected options, not customer identity. Generated text is reviewed by the customer before posting.
Reporting a security issue
If you find a vulnerability, please email support@hivefive.in with steps to reproduce it. Please do not access other users’ data, disrupt the service or publish the issue before we have a chance to fix it.