Skip to content

Privacy policy

Last updated November 7, 2026, to describe the security check on our sign-up page and the answers you give when you start using the app. For customers who accepted a version earlier than October 2, 2026, the October 2 changes take effect on November 2, 2026.

NOCRUMBS™ is website analytics made by Cabrera-Lalama Enterprises LLC, doing business as Web Bits ("Web Bits", "we", "us"), a New Jersey limited liability company at 355 Chestnut St, 2nd Floor, Union, NJ 07083, United States. This policy explains what we collect, why, how long we keep it, and the choices you have. It covers three groups of people:

  • visitors to websites that use NOCRUMBS;
  • visitors to our own website, nocrumbs.io, and to the app's sign-in and sign-up pages; and
  • our customers: people with a NOCRUMBS account and the people they invite.

Questions and requests go to privacy@nocrumbs.io.

Our role

When a website uses NOCRUMBS, the website's owner decides to measure its visitors and is responsible for that decision. For visitor data we act on the owner's behalf, as a "processor" under the GDPR and a "service provider" under California law, following our Data Processing Agreement.

For our customers' account data, for this website, and for the statistics we collect about visits to this website and the app's sign-in and sign-up pages (see "This website"), we decide how data is used and are the "controller".

Visitors to websites that use NOCRUMBS

When you open a page on a site that uses NOCRUMBS, the site's script sends us the page address, the referring address, the width of your browser window, a random identifier for the event, and the name of the event (such as a pageview) with any details the site owner chose to add. When you leave a page or hide it, the script also sends how far down you scrolled and how long the page was visible. Our servers also receive your IP address and browser user agent, as every web server does, and our content delivery network tells us your country.

From this we store, for each event:

  • the site's host name and the page path, without the query string, and without the fragment unless the site uses it to tell its pages apart;
  • campaign tags from the page address (utm_source, utm_medium, utm_campaign, utm_content, utm_term, and ref or source), which describe the link that was followed, not the person who followed it;
  • whether the page address carried a click identifier that an advertising network adds to its ads (such as Google Ads), and which network. We never keep the identifier itself, which is discarded with the rest of the query string;
  • the referring site's domain, never the full referring address;
  • your country, with no region or city;
  • a device size class (mobile, tablet, laptop, or desktop, from the window width), and your browser and operating system with major versions only;
  • the event name, the event's random identifier and time, and any custom details the site owner chose to send, which can include an amount and currency for an event such as a purchase. If the site owner turns on outbound link or download tracking, the details include the address of the link you clicked;
  • for each page you leave, how far down you scrolled, in percent, and how long it was visible;
  • a visitor identifier.

The visitor identifier is a one-way hash of a secret random value, the site's domain, your IP address, and your user agent. We use a new secret value every day (UTC) and delete each one within about an hour after its day ends. Within a single day, the identifier lets the site count your visit to several pages as one visitor. We never try to turn it back into an IP address, and once the day's secret value is deleted it cannot be linked to you or to your visits on other days or other sites.

Your IP address and full user agent are used in memory for that one request and are never stored or written to logs. To protect the service from abuse, our content delivery network also counts requests from each IP address over a few minutes, in memory, and blocks addresses that send far too many or that are known for abuse. Those counts are never stored or logged either.

NOCRUMBS sets no cookies, uses no local storage or other storage in your browser, and does not follow you across websites. We do not build profiles, and we never sell or share data for advertising. Requests from known bots, automated browsers, and localhost are not counted.

Some data protection authorities treat a short-lived identifier like ours as personal data while its secret value exists. We handle visitor data with that in mind: we use it only to produce the site owner's statistics, only on their instructions, and under our Data Processing Agreement.

The site owner decides what custom details to send with events. Our terms and documentation forbid sending names, email addresses, or other details that identify a person. If a site owner sends them anyway, the site owner is responsible, and we delete such data when we learn about it.

If a site owner imports the site's Google Analytics history into NOCRUMBS, we receive daily totals only, such as visitors per page or per country, never data about a single visitor.

Because we cannot tell who you are, we cannot find or return data about you as a visitor. If you have a question about a site's use of NOCRUMBS, contact that site's owner, who controls the data. We help site owners answer such requests.

Customers

When you create or use a NOCRUMBS account, we keep:

  • your email address, to sign you in and to send sign-in codes, invitations, reports you ask for, and notices about your account, plan, and these policies;
  • your passkeys' public keys, each with a label naming the browser and operating system it was created on, and when it was last used. Your fingerprint or face never leaves your device;
  • your active sign-in sessions, each with a label naming the browser and operating system, and when it was last used;
  • your name and, if you give them, your company, its website, your role, your team size, and how you heard about NOCRUMBS, which you enter when you start using the app;
  • the version of our terms you accepted, and when;
  • a security log of sign-ins and important changes, such as deleting or moving a site, deleting an organization or account, billing changes, creating or revoking API keys, and goals and funnels changed with an API key. It records your user id, the browser family, and a keyed hash of the IP address, never the IP address itself;
  • your organizations and sites: names, domains, settings, goals, funnels, notes on the graph, saved views, report and alert settings, shared link labels, an uploaded logo, and members and their roles;
  • your organizations' API keys: each key's name, access, sites, who created it, when it was created and last used, and how many calls it made;
  • the email addresses of people you invite or add as report or alert recipients, used only to send the invitation, the report, or the alert. Every report and alert email has an unsubscribe link;
  • a record of each email the service sends to you or to a recipient you added: the address, the kind of email, its subject, when it was sent, and whether it was delivered, delayed, bounced, or marked as spam, with the reason the receiving server gave. We keep it so we can help when an email does not arrive, never the rest of the email;
  • if you connect Google Search Console or Google Analytics to a site: the address of the Google account you used, an access grant from Google that we store encrypted, the property you chose, and the dates and outcome of any import (see "Data from Google" below);
  • your plan, subscription status, and Stripe customer number;
  • messages you send us, with their email headers. Like every email, these headers include the addresses of the mail servers that carried the message, which can include your IP address.

To protect sign-in from abuse, we count sign-in attempts per IP address. We do this with a keyed hash of the address and never store the address itself.

To keep automated programs from creating accounts, the sign-up page runs a security check from Cloudflare (Cloudflare Turnstile) before we send a sign-up code. Cloudflare receives your IP address and information about your browser and device to tell people from automated programs. We receive only whether the check passed. If you start signing up but never enter the code we send, we delete the address from our sign-in service after 7 days.

Payments. Paid plans are bought through Stripe. You enter your payment details on Stripe's checkout page, and Link, a Stripe company, sells the subscription as the merchant of record. Stripe and Link collect and keep your payment and tax details under their own privacy policies. We never see or store your full card number.

Cookies in the app. When you sign in, the NOCRUMBS app sets three cookies on its own domain, all strictly necessary for the service you asked for:

CookiePurposeLifetime
nc_sessionKeeps you signed inUntil you sign out, and at most 30 days
nc_csrfProtects your account from forged requestsUntil you sign out, and at most 30 days
nc_stepupRemembers that you just confirmed it is you, before a sensitive change5 minutes

The app uses no analytics or advertising cookies. Its sign-in, sign-up, and first setup pages count visits with NOCRUMBS itself, without cookies, as "This website" describes; the screens after them do not.

We do not send marketing email. If we ever do, we will ask first where the law requires it.

Data from Google

You can connect Google Search Console or Google Analytics to a site in its settings. Google asks you to allow NOCRUMBS read-only access, and you can disconnect at any time in the same place, which also withdraws our access at Google. Only owners and admins of the organization can connect or disconnect.

  • Google Search Console. We read the searches that led people to the site, with their clicks, impressions, click rate, and position, to show them on the site's dashboard to the people who can see the site. We fetch them from Google when they are viewed and keep them in memory for up to an hour; we do not store them.
  • Google Analytics. We list the Google Analytics 4 properties the account can read, and when you start an import, we read daily totals for the days you choose (visitors, pageviews, sessions, engagement, and their split by page, landing page, host name, source, medium, campaign, country, device, browser, and operating system) and store them with the site as its statistics. You can delete imported history at any time with "Delete imported history", by resetting the site's stats, or by deleting the site.

We use data from Google only to show it to you and your organization in NOCRUMBS. We do not use it for advertising, do not sell it, do not use it to train AI models, and do not share it with anyone except our hosting provider, which stores it for us.

Where data from Google appears. Search Console figures appear only in the signed-in dashboard. Imported Google Analytics history appears in the signed-in dashboard, to the members and clients of the site, and never in email reports or traffic alerts. It reaches AI tools and other software connected with an API key, or shared links, only if an owner of the organization turns that on for the site, each separately. Before it turns on, the owner confirms their sign-in again, confirms that they have authority to accept for the organization and that the sharing is allowed under its agreements with Google and with the recipients, and accepts that the organization alone is responsible for the sharing and for what recipients do with the data, which for AI tools can include storing it or training AI models under their own terms. Turning it off stops new answers or views from including it, but cannot recall what was already received.

A connection ends, and we withdraw our access at Google, when it is disconnected, when the site is deleted, or when the person who connected it leaves the organization or deletes their account. For your Google account itself, Google's own terms and privacy policy apply.

Why we use data

Under the GDPR, we rely on these legal bases:

PurposeLegal basis
Creating your account, signing you in, and providing the service and supportPerforming our contract with you
The answers you give when you start using the app, to understand who uses NOCRUMBS, improve it, and support youOur legitimate interest in improving the service and supporting you
Billing and plan managementPerforming our contract with you
Service emails: sign-in codes, invitations, reports, traffic alerts, plan and usage notices, and changes to our terms and policiesPerforming our contract with you, and our legitimate interest in telling you about your account
The record of emails sent, to help when one does not arriveOur legitimate interest in delivering service emails and supporting you
Connecting Google and importing or showing your Google data, when you ask us toPerforming our contract with you
Keeping records of acknowledgments you acceptOur legitimate interest in being able to show what was agreed and to establish or defend legal claims
Measuring visits to this website and the app's sign-in and sign-up pagesOur legitimate interest in understanding how people find and use our website and in improving it, with the limits described under "This website"
The security log, rate limits, the sign-up security check, and preventing fraud and abuseOur legitimate interest in keeping accounts and the service secure
Keeping records the law requires, such as tax recordsLegal obligation

We make no decisions about you by automated means that have legal or similarly significant effects.

Who processes data for us

We use these companies to run NOCRUMBS:

  • Amazon Web Services, Inc. hosts the service, stores its data, delivers it through its content delivery network, and sends and receives the service's email, in the United States.
  • Stripe, Inc. and Link process payments for paid plans. They do not receive visitor data.
  • Cloudflare, Inc. runs the security check on our sign-up page (Cloudflare Turnstile). It receives the IP address and browser and device information of people who open that page. It does not receive visitor data.
  • Google LLC provides our staff's email (Google Workspace), and we use it for email only. It holds no part of the service and none of its data. It receives the emails our service sends to our staff: an alert when you write to us, with your name, email address, and the subject but not the message, and reports on our own background jobs. It never receives visitor data.

Each processes data only to provide its services and under its data processing terms. The subprocessors for visitor data are listed on our Data Processing Agreement page. We may also disclose data when the law requires it, such as to answer a valid court order, and we tell the affected customer first unless the law forbids it.

When you connect an AI tool or other software to NOCRUMBS with an API key, we send it the statistics it asks for, on your instructions. You choose that tool and its provider. They are not our processors, and what they do with the data is governed by your agreements with them.

When you connect Google Search Console or Google Analytics, we read your data from Google on your instructions, as "Data from Google" describes. We send Google only what it needs to answer, such as the property and the dates. For your Google account, Google acts under its own terms with you and is not our processor.

Where data is stored

All NOCRUMBS data is stored in the United States (Amazon Web Services). If you are in the European Economic Area, the United Kingdom, or Switzerland, your data is transferred to the United States. For visitor data we process for customers, these transfers are covered by the European Commission's Standard Contractual Clauses and the UK Addendum in our Data Processing Agreement. Our providers also rely on the Standard Contractual Clauses and, where they are certified, the EU-U.S. Data Privacy Framework.

How long we keep data

  • Visitor analytics data is kept while the site is in NOCRUMBS, for at least the history its plan lists on our pricing page. Today we keep it until the site owner resets the site's stats or deletes the site or the organization. If we ever start deleting older data automatically, we will email customers at least 30 days before.
  • Statistics about visits to this website are kept while we measure this website with NOCRUMBS, and we delete them when we no longer need them for the purposes described under "This website". Once each day's secret value is deleted, they cannot be linked to anyone.
  • Deleted data leaves the app at once. Copies kept for recovering mistakes are removed within 7 days.
  • Account data is kept while your account exists and deleted when you delete your account. An organization's data stays with the organization until an owner deletes it.
  • The security log is kept for 25 months, including after an account is deleted, because it records who did what and holds no email or IP address.
  • Sign-in codes expire after 10 minutes, and sessions end when you sign out or they expire.
  • Service logs never contain IP addresses and are deleted after one month.
  • Payment and tax records are kept by Stripe and Link as tax law requires.
  • Messages you send us, with their email headers, are deleted two years after they arrive.
  • The record of emails sent is deleted 13 months after each email, and at once for an address whose account is deleted.
  • Records of acknowledgments, such as an owner accepting responsibility for sharing imported Google Analytics history, are kept for six years after each one, including after the account or organization is deleted, because they are the evidence of what was agreed. Each holds the wording accepted, when, the user id, and the email address of the account at the time.
  • Google access grants are deleted when the connection ends, as "Data from Google" describes. Search Console figures are not stored. Imported Google Analytics history is kept as the site's statistics until it, the site's stats, or the site is deleted.

Security

We encrypt data in transit and at rest, give each part of the service access only to what it needs, keep production separate from development, and sign people in without passwords, with emailed codes or passkeys. Sensitive changes ask you to confirm it is you again, and we record each time our staff open an account, organization, or message in our admin console. If a breach affects your data, we tell affected customers without undue delay, and the authorities where the law requires.

Your rights

Wherever you live, you can ask us to:

  • tell you what data we hold about you and give you a copy;
  • correct it;
  • delete it;
  • give it to you in a portable format;
  • stop or limit using it, or object to how we use it.

We may keep data that the law requires us to keep, or that we need to establish or defend legal claims, such as records of acknowledgments, for the periods above, even after a request to delete.

Some of this you can do yourself in the app: change and delete your sites, manage your organization's members, disconnect Google and delete imported history, delete an organization, and delete your account. For everything else, write to privacy@nocrumbs.io from your account's email address, so we can confirm the request is yours. We answer within 30 days.

If you are in the European Economic Area, the United Kingdom, or Switzerland, you can also complain to your data protection authority. If you are a California resident, you have the rights to know, delete, and correct your personal information, and we will not treat you differently for using them. We do not sell or share personal information as California law defines those terms.

Children

NOCRUMBS is a service for businesses and is not directed to children. Accounts are for people 18 and older. If we learn that we hold account data about a child, we delete it.

NOCRUMBS cannot tell how old a website visitor is, and it collects the same limited data about every visitor, with no profiles and no advertising. A site owner whose site is directed to children under 13 is responsible, under our terms, for meeting the Children's Online Privacy Protection Act (COPPA) and similar laws, including any parental consent they require. Parents with questions about a site should contact that site's owner.

This website

This website (nocrumbs.io) and the app's sign-in, sign-up, and first setup pages (app.nocrumbs.io/login, /signup, and /setup) count their visits with NOCRUMBS itself, the same way our customers count theirs. For these statistics we are the controller.

When you open one of these pages, our script, served from ncrmb.com, our own address for NOCRUMBS, sends the data described under "Visitors to websites that use NOCRUMBS", and we handle it the same way: no cookies and nothing stored in your browser; your IP address and full user agent used in memory only to make that day's visitor identifier, and never stored or written to logs; and an identifier that cannot be linked to you once that day's secret value is deleted. We send no custom details about you, and we do not connect these statistics to your account, even after you sign up or sign in.

We do not count the app's screens after you sign in (apart from the first setup page), shared dashboard links, invitations, the addresses customers' organizations use for their own branded dashboards, or our staff's admin console.

We use these statistics only to understand how people find and use our website and whether people who start signing up finish, and to improve the website and the sign-up steps. We do not use them for advertising, do not sell or share them, and do not use them to make decisions about anyone.

If your browser sends a Do Not Track signal, these pages do not count your visit. You can also block ncrmb.com in your browser or with a content blocker, and the pages work the same without it. Because these statistics cannot be linked to you, we usually cannot find, copy, or delete your visits, but you can write to privacy@nocrumbs.io with any question or objection.

Apart from that, this website sets no cookies, loads nothing from other companies, and never records visitors' IP addresses.

Changes to this policy

If we change this policy, we update the date at the top. For changes that matter, we email account holders at least 30 days before they take effect.

Contact

Web Bits (Cabrera-Lalama Enterprises LLC), 355 Chestnut St, 2nd Floor, Union, NJ 07083, United States. Email: privacy@nocrumbs.io.