Terms of use

Last updated 19 October 2026 · applies to the free beta

The short version. This is a free beta. It is genuinely useful and it is also unfinished, so keep your own backups. Your data is yours — take it with you whenever you like. We may need to change or stop the service, and we will tell you before we do.

What this is

Nimble Clerk is a tool for building a small CRM. It is offered free of charge during the beta so that real use can find real bugs. There is no payment, no subscription, and no contract term.

Your account

You need a Google account to sign in, and during the beta you also need an invite code. You are responsible for what happens under your account and for keeping access to your Google account secure. One person, one account — invite colleagues to a team rather than sharing a login.

Your data is yours

We claim no ownership of anything you put into Nimble Clerk. You can export all of it at any time from Settings, as JSON or CSV, without asking. We use it only to run the service for you, as described in the privacy page.

What we ask of you

Do not use it for anything unlawful, or to store data you have no right to hold.
Do not try to break into other people's workspaces, or deliberately overload the service.
If you put other people's personal information into it — customers, contacts — that remains your responsibility, including under whatever data protection law applies to you.

Handling your customers' data on your behalf

The short version. The records you put in are yours: you decide what goes in and why, and we only ever handle it to run the service for you. This section is the detail — what we will and will not do with it, who else touches it, and what happens when you leave.

Where your records contain personal information about other people, UK and EU data protection law calls you the controller and us the processor. In plain terms: it is your data and your decision; we are the people who keep the machine running.

What we do with it

We process your records only to provide the service — to store them, sync them between your devices, show them to the people you have invited, and back them up. We do not sell it, mine it, train anything on it, or use it to build any other product. If we ever needed to process it for some other reason, we would ask you first.

Everyone with access to the systems is bound to keep what they see confidential. Today that is one person.

Where it is, and how it is protected

Servers and database are in the EU (Frankfurt).
Everything travels over HTTPS. The database is hosted by MongoDB Atlas, which encrypts its storage.
The nightly backup is encrypted before it is stored, with a passphrase held separately from the backup itself.
Access to a workspace is scoped to its own organisation, and roles limit what each person on a team can do.

No system is perfectly secure, and this is a small operation rather than a large one. We would rather say that than imply otherwise.

Who else touches it

We use a small number of other companies to run the service — hosting, the database, sign-in, and backup storage. They are named individually on the privacy page, which is the current list. If we add or change one, we will update that page and tell you before it starts handling your data, so that you have the chance to object.

Anything you connect yourself is yours, not ours. If you point the daily digest at a chat channel, or connect a Resend or Postmark account so reminders send from your own address, that is a relationship between you and them on your own contract — you chose it, you can end it, and it is not on our list above. We hold an email provider key only so the reminder you press send on can be sent; we never see who you sent one to.

If something goes wrong

If we become aware of a breach affecting your data, we will tell you without undue delay and in any case within 72 hours, with what we know at the time: what happened, what data was involved, and what we are doing about it. We will not wait until we have the full picture to tell you that there is one.

Getting it back, and getting it deleted

Any time: Settings → Export backup gives you everything, as a file, without asking us.
On request: we will help you answer an access, correction or deletion request from one of your own contacts. Usually you will not need us: Settings → Data requests searches every text field of every record for a person — including names that only appear as a link, and values under fields you have since removed — and hands you a file to review before you send anything.
How long you keep it: your decision, not a period we set. We never delete your records on a schedule of our own — if a contact should have been removed two years ago, they are still there until you remove them. Settings → Data you have stopped using lists the records nothing has touched in a window you choose, so you can review them; it reports, and never deletes anything by itself.
When you leave: deleting your account deletes your workspace. Two honest caveats. Deleted records leave a small marker behind — an id and a date, no content — for up to 180 days, so that a device that has been offline learns the record is gone rather than restoring it. And a backup taken before you left still exists until it ages out of the backup retention window.

Showing our working

Ask, and we will tell you what you need to satisfy yourself that this is accurate. We are too small to host formal audits, and saying so is more useful than promising one we could not deliver.

What you should expect from a beta

It may break. That is the point of the beta; please report it.
It may be slow to wake up. The free hosting sleeps when idle, so the first request after a quiet period can take up to a minute. The app itself loads instantly from your device.
Data loss is possible. We take a daily backup, so the realistic worst case is losing up to a day's work. Keep your own export of anything important. This is the one thing we most want you to take seriously.
Features may change. Beta feedback is why.

Availability

No uptime is promised. We may change, suspend or discontinue the service. If we are going to shut it down or delete data, we will give you notice in the app with enough time to export your work.

Ending it

You can stop at any time: export your data and delete your workspace from Settings. We may suspend an account that is being used to break these terms, or to attack the service or other users.

Liability, plainly

This is provided free and as-is, without warranties. We are not liable for losses arising from using it, including lost data or lost business. Where the law where you live does not allow that to be excluded, the law wins.

These terms are written to be read and understood rather than to be exhaustive. If you need something more formal — a data processing agreement, a signed contract, an SLA — ask, and we will talk about what that would take outside the free beta.

Contact

Anything in these terms that says to ask us — a data processing agreement, help answering a request from one of your own contacts, or being the last owner of a team and unable to leave it: contact@nimbleclerk.com. The same address appears on the privacy page, and it is the only one; there is no separate support queue.