sales-man
Privacy policy
Last updated 19 September 2026.
sales-man is a tool for following up your own WhatsApp sales conversations. This policy explains what we hold, why, and how to make us delete it. It is written to be read, not to be survived.
1. Who we are
sales-man is operated by the sales-man team (“we”, “us”). For anything in this policy, write to support@sales-man.net — that address reaches a person and is also our contact point for data protection requests.
We are the controller of the account data described below. For the WhatsApp message content you bring into the service, you are the controller and we act as your processor: we only read the conversations you explicitly choose to track, and only for as long as you keep them tracked.
2. What we collect
| Data | Why | Kept for |
|---|---|---|
| Username and password hash | To let you sign in. Passwords are hashed with Argon2id and never stored in a readable form. | Until you delete your account |
| Account dates and session records | To show when you registered, to keep you signed in, and to let you sign out everywhere. | Sessions: 30 days. Dates: until deletion |
| Your chat-man.net access token | To read the WhatsApp conversations you have chosen to track. Stored encrypted with AES-256-GCM. | Until you disconnect it or delete your account |
| Messages from the conversations you track: sender, timestamp, and up to the first 2,000 characters of text. Media is recorded as a type only — we never store files. | To work out when a conversation last moved and to show you recent context. | A rolling 365 days, then deleted automatically |
| What you type about a contact: notes, company, email, LinkedIn, birthday, display name | Because you asked us to remember it. | Until you delete it or delete your account |
| Billing records held by Stripe (card details, invoices, address for tax) | To take payment. We never see or store your card number. | By Stripe, per their retention rules and tax law |
| Server logs: request path, status, coarse timing, a salted hash of your IP | To keep the service up and to spot abuse. The raw IP is not stored. | 30 days |
| An anonymous record after you delete your account: creation date, deletion date, and how many groups and contacts were tracked | To understand how the product is used over time and to meet our own accounting obligations. It holds no username, no identifier and nothing linking back to you. | Indefinitely, in anonymous form |
3. What we do not do
- We do not read conversations you have not chosen to track.
- We do not send WhatsApp messages. sales-man is read-only, by design.
- We do not sell or share your data with advertisers, ever.
- We do not use your messages or notes to train machine-learning models.
- We do not store media files, only the fact that a message contained media.
4. Cookies and analytics
We use no cookies for analytics, and no consent banner, because we store nothing
on your device. On the public pages of sales-man.net we run PostHog with
in-memory persistence and Google Analytics 4 in cookieless mode
(client_storage: 'none'). Neither writes a cookie or a localStorage entry, so
neither can recognise you on a later visit. We also honour Do Not Track and Global Privacy
Control: if your browser sends either, no analytics load at all.
The signed-in app at /app loads no analytics whatsoever. It sets two cookies,
both strictly necessary and neither used for tracking: a session cookie that keeps you
signed in, and a CSRF token that stops other sites acting as you.
5. Who processes your data
- Amazon Web Services — hosting, database and secrets. Data is stored in the AWS region we deploy to and is encrypted at rest and in transit.
- Stripe — payments and subscription management. Stripe is the controller of your payment details; see their privacy policy.
- chat-man.net — the WhatsApp connection. You hold that account directly; we act only with the token you give us, and only on the conversations you choose to track.
- PostHog and Google Analytics — cookieless visit counts on public pages only, as described above.
6. Your rights
If you are in the UK, EU or EEA, the GDPR gives you the right to access, correct, export, restrict or delete your data, and to object to processing. Similar rights apply under the CCPA/CPRA in California and under other regimes. You can act on most of these yourself:
- See and correct — everything we hold about a contact is editable in the app.
- Delete — Settings → Delete account removes your login, every tracked conversation, every stored message and every note, and cancels your subscription. Only the anonymous record in the table above survives.
- Export or anything else — email support@sales-man.net and we will answer within 30 days.
You also have the right to complain to your local data protection authority if you think we have got this wrong. We would rather you told us first.
7. Legal bases
- Contract — running your account, syncing the conversations you track, taking payment.
- Legitimate interests — keeping the service secure and available, and understanding aggregate, non-identifying usage.
- Legal obligation — tax and accounting records.
8. Security
Everything is served over HTTPS with HSTS. Passwords are hashed with Argon2id. Your chat-man.net token is encrypted with AES-256-GCM under a key held in AWS Secrets Manager and never written to logs. Session cookies are HTTP-only, Secure and SameSite=Strict. Database credentials are short-lived IAM tokens rather than static passwords. No system is perfect; if you find a problem, please tell us at support@sales-man.net and we will respond quickly and credit you if you want.
9. International transfers
Our processors may handle data outside your country. Where that happens we rely on the relevant transfer mechanism — Standard Contractual Clauses, the UK Addendum, or the EU-US Data Privacy Framework as applicable to each processor.
10. Children
sales-man is a business tool and is not intended for anyone under 16. We do not knowingly collect data from children.
11. Changes
If we change this policy in a way that matters, we will email account holders before it takes effect. The date at the top always reflects the current version.