Customer support
Support and privacy requests
For ClientSupply support, account access, privacy, security, cancellation or data requests, email leveriano@clientsupply.com.au.
What to include
- Your name, account email and workspace name.
- A short description of the problem or request.
- The approximate time, page and safe reference visible in the application.
- Whether work is blocked, a privacy concern is involved, or a security issue may be urgent.
Never send a password, MFA code, session cookie, invitation token, reset link, API key, database credential or full customer export.
Support process
- We verify the requester and workspace scope before discussing account or customer information.
- We classify the request as operational support, privacy/data request, security incident, billing/access issue or another bounded category.
- We investigate using the least information needed, preserve relevant evidence and explain the next safe step.
- We confirm what was done, what remains retained or unresolved, and any follow-up required.
ClientSupply is founder-operated. Requests are handled on Australian business days when the founder is available. No guaranteed response or resolution time is promised.
Privacy and data requests
You may ask for access to or correction of account information, request account/workspace closure, or ask how operational data is handled. We verify identity and scope first. Deletion, retention, audit records, billing evidence and backup expiry are separate questions; we will explain any retained category rather than promise immediate deletion from every backup.
Security concerns
Use the subject line “security concern” for suspected unauthorised access, wrong-recipient email, tenant-isolation issues, lost data or exposed secrets. Do not put the suspected secret in the email. We will preserve evidence, contain the affected workflow where necessary and communicate verified facts.
Support access boundary
Support content access is not currently exposed through a general founder console. We do not silently impersonate customers or browse unrelated workspaces. Any future exceptional access would require explicit authorisation, a named support identity, a reason, a bounded scope, an expiry and audit evidence.