Nimbli Privacy Policy

If you have an account

When someone clicks a Nimbli link

To redirect the visitor, we receive their request. That includes their IP address, browser (user agent) and the page they came from.

• What we keep: only counts. A total per link, a count per day for the last 30 days, and the time of the last click. Each click is a row with its day and no visitor details, and is deleted after 31 days.
• What we don't keep with a click: the visitor's IP address or user agent, or any identifier that could recognize them again, beyond the rate-limit counters below and the security logs.
• What we use the request for, without storing it:
  • to tell bots from people;
  • to protect the Service.
• Rate limits. To stop floods we count requests per network address. The count is kept under a keyed hash of the address, not the address itself, for up to a day. The key is stored in the same database, so a hash is not anonymous to us. To keep one person's pace of new links, we also keep a row with their account and the time of each link they make, for up to three days, and delete it with the account. In the first week of a free account, we also keep a row for each new link in the teams it's main owner of, with the team and the time, for up to two days, to apply the first week's limit.

On a team's own domain

A link opened on a team's custom domain is handled exactly as one opened on ni.run. The same request reaches us, through Cloudflare, and we keep only what we keep for ni.run: the name-free counts above and the security logs below. The team sees the counts, not who clicked. The certificate that lets the domain open over HTTPS lists the domain's name in public Certificate Transparency logs, as for any website.

When you use the QR code maker

While you make a code, nothing you type or upload is sent to us. The address, your colors and your logo stay in your browser. The browser remembers your last style on your device, and you can clear it with "Start fresh".

There are two exceptions. If you choose "Make a changeable code", the address you typed is sent to nimbli.app as part of the page's address, to start your short link, so it is in our server's access log for up to 14 days. And when you save a style to one of your team's short links, its colors, shapes and logo are stored with that link, and everyone in the team sees them. The maker says so before it uploads a logo.

When you report a link

We keep your report and, if you give it, your email address so we can reply.

Counts of page opens

We count how often some pages open, such as Pricing, and whether the person was signed in, without knowing who opened them. We keep those counts for 90 days.

Security logs

Our server keeps an access log: for each request, the visitor's IP address, the page asked for (for a short link, its code), the browser and the page they came from. We keep it for up to 14 days and use it to keep the Service secure and to investigate abuse. Our server's error logs can hold an email address when sending an email fails, and they roll over by size, not by time. Cloudflare, which sits in front of Nimbli, keeps its own network logs under its policy, and a visitor's browser may send Cloudflare a network-error report when a connection to Nimbli fails.

What we don't do:

• sell personal data;
• use it for advertising;
• build profiles of people who click links.

We use a small number of providers to run Nimbli. Most process data only on our instructions. Stripe is different (see below). The full list, with what each one handles, is in Sub-processors. In short:

• DigitalOcean: hosting, in the United States.

• Cloudflare: DNS, network protection, the bot check on forms for people who aren't signed in, and backups; for teams' custom domains, the certificates and the network in front of them (Cloudflare for SaaS). Cloudflare gets each certificate from a public certificate authority it chooses (today SSL.com, sometimes Google Trust Services or Let's Encrypt). The authority sees only the domain's name and publishes it in public Certificate Transparency logs.

• Google:

  • sign-in, if you choose it;
  • Web Risk, which receives the destination addresses of links when they are created or changed, and daily for recently used links, and the names of teams' custom domains when they are connected and weekly;
  • our support and abuse mailboxes (Google Workspace), where we read what you write to us.

• Stripe (its checkout and receipts may show Link): sells Pro. It is the seller of record, so it receives your name, email, billing address and payment details and uses them under its own privacy policy, not on our instructions. It tells us whether your subscription is active and when its period ends. If you ask Link to delete your data, Stripe cancels your subscription.

• Resend: sends our emails, including the sign-in emails.

• Anthropic: an AI model that helps review abuse reports and review requests. It receives:

  • the link and its destination;
  • the reason it was flagged;
  • the report text;
  • a summary of the team's history;
  • daily totals and averages (links made, clicks, reports), with no names, addresses or destinations, which it uses to write a short note for the admin.

  It never receives data about people who click links.

We may also disclose data:

• if the law requires it;
• to protect people from harm;
• as part of a sale or merger of Nimbli, with this policy continuing to apply.

• Location: data is stored in the United States.
• Transfers from the UK and EEA: if you're there, your data is transferred to the US. We rely on the safeguards our providers offer for these transfers, such as the EU-US Data Privacy Framework where a provider is certified under it, Standard Contractual Clauses and the UK addendum.

• Download each team's links as a CSV file, one file for each team you're in, from the Account page.
• Delete your account from the Account page:
  • In teams where you're the only person, the team and its links are deleted.
  • In other teams, your access ends and the team keeps its links. Where a team's activity names the address you were invited with, it reads "someone" instead.
  • If you're the only owner of a team that has other people in it, or its main owner, you can't delete your account until you make someone else an owner or the main owner. If the other owner doesn't answer, write to [email protected]: after trying to reach them, we can make them the main owner. If your Pro is active, you can't delete your account until you cancel it. The Account page tells you.
• Correct your name and password on the Account page. Your confirmed email address is how you sign in and how invitations find you, so it can't be changed: to use another, make a new account and invite it to your teams (see Help).

Depending on where you live, you may have other rights:

• to access, correct, delete or move your data;
• to object to or restrict how we use it;
• to complain to your data protection authority.

To use any of these rights, email [email protected]. We'll answer within 30 days. We don't discriminate against anyone for using their rights.

We use cookies to keep you signed in, including short-lived ones while you sign in with Google or move to qr.nimbli.app. A sign-in lasts up to 30 days.

• Cloudflare: it may set a strictly necessary cookie to protect the Service from bots.
• Forms for people who aren't signed in: Cloudflare Turnstile checks the form, which may involve its own cookie.

We use no advertising or analytics cookies.

Nimbli is not for anyone under 16, and we don't knowingly collect their data. If you think a child has given us data, contact us and we'll delete it.

If you use Nimbli for an organization, your organization controls its team's links and notes, and we process them on its behalf under our Data Processing Agreement. On a team's custom domain, we handle visitors' requests for our own purposes (security, abuse and name-free counts), as on ni.run, and the team receives only the counts.

We protect data with:

• encryption in transit (HTTPS);
• encrypted backups;
• passwords, tokens and the one-time links we email, stored in a form we can't read back;
• access limited to the people who run Nimbli. They can read account and link data, including through an AI assistant connected to Nimbli's operator console, which only reads and logs every read (see "How long we keep it").

No service is perfectly secure. If a breach affects your data, we'll tell you as the law requires. To report a security problem, write to [email protected].

For changes that matter, we'll post a notice on the site at least 30 days before they take effect, unless we must change something sooner for security or the law. The date at the top shows the last update.

URLERT LLC, 5900 Balcones Drive, Suite 100, Austin, Texas 78731, United States · [email protected]