Who we are
LeadRush is a product of PSL Systems, registered in the Netherlands with the Chamber of Commerce (KvK) under number 42075111.
Two different roles, and why it matters to you
LeadRush handles two kinds of personal data, and our legal responsibility is different for each. Confusing them is the most common way a policy like this misleads people, so it is set out first.
Your account. When you sign up as a business, we are the controller. We decide what we store about your account and why.
Your customers’ conversations. When somebody messages your business and LeadRush replies, we are the processor and you are the controller. That person is your customer, not ours. We act on your instructions, and the obligation to answer their questions and honour their rights sits with you — which is why the erasure tools described below exist in the product.
What we store
About your business
- Your business name and the plan you are on.
- Each team member’s email address, display name and role.
- A password hash — never the password itself. Hashed with bcrypt at cost factor 12, which is designed to be slow to attack.
- The WhatsApp number you connect, and the access credential for it. That credential is encrypted at rest with AES-256-GCM under a key held outside the database.
- Billing records: which plan, what amount, and the payment provider’s customer and mandate identifiers. We never see or store your card details.
About the people who contact your business
- Their phone number, and their name and email if they give it.
- The full text of every message in the conversation, in both directions.
- A written summary of the conversation, and the outcome you record against it.
- Timestamps, which are what reply-time reporting is built from.
These people never signed up for anything here and may not know LeadRush exists. That is precisely why the erasure behaviour below is built the way it is.
Technical records
- Session tokens, so you stay signed in. They rotate on every renewal, and a token presented twice is treated as evidence of theft and ends the session.
- Rate-limiting counters, which include the IP address a request came from. These exist to stop brute-force attempts.
- An audit log of significant account actions.
Where it lives
The database and application run in Frankfurt, Germany. This is a deliberate choice rather than a default: the records here are phone numbers and complete message transcripts belonging to EU residents, and where they are stored is a commitment, not a latency setting.
Some sub-processors below operate outside the EU. Where they do, transfers rely on the European Commission’s Standard Contractual Clauses.
Who else processes it
LeadRush cannot function without these services. We do not sell personal data, and we do not share it for advertising.
| Service | What it does | Where | When |
|---|---|---|---|
| Render | Hosting and managed Postgres | Frankfurt, Germany (EU) | Always |
| Meta Platforms | WhatsApp Business Cloud API — delivers and receives the messages | EU / US | Always |
| OpenAI | Generates the reply — receives message content and conversation history | US | Always |
| Mollie | Payments — holds the billing customer and mandate, never conversation data | Netherlands (EU) | When a subscription is active |
| Twilio | Missed-call detection — receives the caller's number | EU / US | When missed-call handling is enabled |
| Email provider | Transactional email — invites, alerts, verification | Depends on provider | When email delivery is configured |
The one worth reading twice is the AI provider. To write a reply, the model is sent the conversation so far — including what the customer wrote. If that is not acceptable for a particular contact, add them to the excluded-contacts list in your settings and no automated reply will be generated for them.
How long we keep it
- Conversations and leads are kept for as long as your account is active, because they are your business record. You can erase any individual at any time.
- Revoked session tokens are kept for seven days after they die. Not zero: the record is the only evidence that a stolen session was replayed, and deleting it immediately would silently discard that signal.
- Rate-limit counters are deleted one day after their window closes.
Erasure, and why it anonymises rather than deletes
When you erase a lead, everything that points at a person is destroyed: the name, the phone number, the email, and the content of every message they exchanged with you.
What remains is a de-identified shell — the conversation record, its timestamps and its outcome, with nothing left that identifies anybody. This is deliberate. Deleting the conversation outright would take your own commercial record with it: last quarter’s results would change every time somebody exercised a right, and you would have no way to explain the difference. Keeping a shell that points at no one satisfies the request while leaving your business record intact.
The compliance entry we write to prove the erasure happened records the internal identifier and the time — never the number or the name. A record that carries the data it certifies as destroyed would be worse than no record at all.
Your rights
Under the GDPR you may request access to your personal data, its correction or erasure, a copy in a portable format, or restriction of how it is used. You may also object to processing.
If you contacted a business that uses LeadRush, that business is the controller of your data — contact them first. If you cannot reach them, write to us and we will identify them and pass the request on.
You have the right to complain to a supervisory authority. In the Netherlands that is the Autoriteit Persoonsgegevens.
How we protect it
- Each business’s data is isolated at the database level, not only in application code, so a query cannot reach another tenant’s rows even if the code above it is wrong.
- WhatsApp credentials are encrypted at rest with AES-256-GCM.
- Passwords are hashed with bcrypt and are never recoverable.
- Sessions rotate and detect reuse, so a stolen token has a short and noisy life.
- All traffic is served over HTTPS.
Contact
Write to contact@onecallhome.nl for anything in this policy, including a request to exercise your rights.
Changes
When this policy changes we update the date at the top. For changes that materially affect how personal data is handled, we notify account holders directly rather than relying on you to re-read this page.