Your business data.
A considered approach.

Workspace access requires an authenticated account. Passwords are hashed rather than stored as readable passwords. Login and selected verification or recovery requests use request limits to reduce repeated attempts.

Keep your registered email and phone secure. Use a unique password, do not share OTP codes and sign out on shared devices. Use the additional verification options available in your account.

Business records are associated with a shop or workspace. Shop context and permission checks help control access to invoices, products, customers, suppliers and other workspace records. Available actions also depend on the account role, active plan and enabled module.

Owners should review staff access regularly, assign only the permissions needed for a role and remove access when a person leaves the business. Be careful when switching between shops or exporting records.

VyapaariDesk is served over HTTPS, which encrypts information in transit between your browser and the website. The application includes browser security headers that help restrict framing, resource loading and unintended browser capabilities.

Use the official vyapaaridesk.com domain and keep your browser and device updated. If your browser shows a certificate or connection warning, avoid entering account information and contact support.

Application forms use server-side validation. Protected web actions use session-based request verification to help prevent unwanted cross-site submissions. Selected sensitive routes also use request limits.

Checks help protect normal workflows, but users should still review changes, recipients and amounts before submitting a business transaction or sharing a document.

Enabled payment, GST, document and messaging workflows may send the information required for that feature to the configured provider. External providers operate their own systems under their own terms and privacy practices.

Payment credentials requested by a checkout provider are handled through its payment flow. VyapaariDesk keeps transaction references, amounts, status and subscription records needed for the service. Share API or portal credentials only through the intended setup fields; never include them in support messages.

Review provider access before enabling a connection and remove authorisations you no longer need. See our integration overview and Privacy Policy.

Your business controls the records it adds to the workspace. Exports, downloaded files, printed documents and shared invoice links can make information available outside your account. Protect those copies and send them only to intended recipients.

Retention depends on service operation, accounting, security and applicable legal requirements. Closing an account does not necessarily remove every record immediately. A deletion request requires verification of identity and authority; some records may need to be retained.

Keep copies of business records you need and request account deletion when appropriate. Our Privacy Policy explains retention and your choices.

• Use a unique password and secure your registered email and phone.
• Review staff roles and remove access that is no longer needed.
• Check recipient details before sharing invoices or exports.
• Lock shared devices and sign out after use.
• Keep independent copies of essential business records.
• Report unexpected account activity promptly, without sending passwords or OTP codes.

These measures work together with application controls. Security safeguards reduce risk, but no internet service can promise immunity from every misuse or incident.

If you suspect unauthorised access or find a security issue, contact our support team with a factual description. Include the affected page, approximate time, account or business identifier and steps that help us understand the issue.

Remove sensitive details from screenshots. Do not send passwords, OTP codes, API secrets, payment credentials or other customers’ records. Report only information you are authorised to access.