Data Processing Agreement
Last updated October 2, 2026. For customers who accepted an earlier version, the changes to this DPA take effect on November 2, 2026.
This Data Processing Agreement ("DPA") is part of the NOCRUMBS™ terms of service between Cabrera-Lalama Enterprises LLC, doing business as Web Bits, of 355 Chestnut St, 2nd Floor, Union, NJ 07083 ("Web Bits", "we"), and the customer ("you"). It applies automatically, with no signature needed, whenever we process personal data for you. If you need a signed copy, write to legal@nocrumbs.io.
1. Definitions
"Data protection law" means every law that applies to the processing of Customer Personal Data, including the EU General Data Protection Regulation ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act as amended ("CCPA"). "Customer Personal Data" means personal data that we process for you as part of the service, as Annex 1 describes. Terms such as "controller", "processor", "data subject", "personal data breach", and "supervisory authority" have the meanings given in the GDPR.
2. Roles
You are the controller of Customer Personal Data, or a processor acting for your own client, in which case we are your subprocessor. We are your processor, and a "service provider" under the CCPA. For data about your account and your team, we act as a controller under our privacy policy, and this DPA does not apply to it.
3. Your instructions
We process Customer Personal Data only on your documented instructions. The terms, this DPA, and the way you set up and use the service are your complete instructions. These include requests made with your organization's API keys: when you connect an AI tool or other software with a key, we return the statistics it asks for to that software on your instruction. That software and its provider act for you, not for us, so they are not our subprocessors, and what they do with the data is governed by your agreements with them. When you connect Google Search Console or Google Analytics to a site, we read data from your Google account on your instruction; Google acts for you under your own agreement with it and is not our subprocessor. Imported Google Analytics history reaches software you connect with an API key, or shared links, only if an owner turns that on for the site, as the terms describe. Every disclosure you set up (shared links, API keys, report and alert recipients, client logins) is made on your instruction, and the recipients are yours, not our subprocessors. If we believe an instruction breaks data protection law, we tell you. If the law requires us to process data otherwise, we tell you first unless the law forbids it.
You are responsible for having a lawful basis for the processing, for giving your visitors the notices the law requires, and for not sending us data the terms forbid.
4. Confidentiality
Everyone we authorize to process Customer Personal Data is bound by a duty of confidentiality.
5. Security
We maintain the technical and organizational measures in Annex 2, and may improve them over time, but never so that the overall protection is reduced.
6. Subprocessors
You authorize us to use the subprocessors listed in Annex 3. We bind each subprocessor to data protection terms at least as protective as this DPA, and we remain responsible for its work.
Before we add or replace a subprocessor, we update Annex 3 and email your organization's owners at least 30 days before the change. If you object on reasonable data protection grounds, write to legal@nocrumbs.io within that time. If we cannot resolve the objection, you may end the terms for the affected service and we refund the unused part of any fees you prepaid.
7. Helping you
Taking into account what we can know, we help you:
- answer requests from data subjects. Because the service holds no data that identifies a visitor, such requests can rarely be matched to stored data; if we receive one directly, we pass it to you and do not answer it ourselves;
- carry out data protection impact assessments and consult supervisory authorities, where the law requires; and
- meet your security and breach notification duties.
8. Personal data breaches
We notify you without undue delay, and in any case within 72 hours, after we become aware of a personal data breach affecting Customer Personal Data. We tell you what we know about its nature, likely effects, and the steps we are taking, and add details as we learn them.
9. Deletion and return
When you delete a site or an organization, we delete its Customer Personal Data from the app at once and from recovery copies within 7 days. Before you delete, you can ask for a copy as the terms describe. When the terms end, we delete Customer Personal Data in the same way unless the law requires us to keep it.
10. Audits
We make available the information you reasonably need to show compliance with this DPA, and we answer reasonable security questionnaires once a year. If that is not enough, or a supervisory authority requires it, you may audit our compliance once a year, at your expense, with 30 days' notice, during business hours, through an independent auditor bound by confidentiality, and in a way that does not disrupt the service or expose other customers' data.
11. International transfers
We process Customer Personal Data in the United States. Where data protection law requires a transfer mechanism, the following apply and are incorporated into this DPA:
- EU. The Standard Contractual Clauses approved by the European Commission in Decision 2021/914, Module 2 (controller to processor) where you are a controller and Module 3 (processor to processor) where you are a processor, with you as data exporter and Web Bits as data importer. Clause 7 does not apply. Under Clause 9(a), Option 2 applies, with the notice period in section 6. The optional wording in Clause 11 does not apply. Under Clause 13, the supervisory authority is the one that applies to you. Under Clauses 17 and 18, the law and courts of Ireland apply. Annexes 1 to 3 of this DPA complete the Clauses' annexes.
- UK. The International Data Transfer Addendum to the Standard Contractual Clauses issued by the UK Information Commissioner, with the Clauses as set out above; either party may end it as its Section 19 allows.
- Switzerland. The Standard Contractual Clauses as set out above, with the Swiss Federal Data Protection and Information Commissioner as the supervisory authority and references to the GDPR read as references to Swiss law.
If the Standard Contractual Clauses conflict with this DPA, the Clauses control.
12. California
As your service provider, we do not sell or share Customer Personal Data; do not keep, use, or disclose it for any purpose other than providing the service, including any commercial purpose outside our direct business relationship with you; do not combine it with personal data from other sources, except as the CCPA allows; and follow the CCPA's requirements for service providers. We tell you if we can no longer meet them, and you may take reasonable steps to stop and fix any unauthorized use.
13. Liability and precedence
Each party's liability under this DPA is subject to the limits in the terms, except where the Standard Contractual Clauses or data protection law do not allow a limit. If this DPA conflicts with the terms, this DPA controls on the processing of Customer Personal Data.
Annex 1: Details of processing
| Item | Details |
|---|---|
| Data exporter | The customer named in its NOCRUMBS account, reached through the email addresses of its organization's owners. It accepts this DPA, which counts as signing the Standard Contractual Clauses, when it accepts the terms. Role: controller, or processor for its own client |
| Data importer | Cabrera-Lalama Enterprises LLC, doing business as Web Bits, 355 Chestnut St, 2nd Floor, Union, NJ 07083, United States. Contact: privacy@nocrumbs.io. Role: processor, or subprocessor |
| Subject matter | Measuring visits to the customer's websites and producing statistics for the customer |
| Duration | While the customer uses the service, until deletion as section 9 describes |
| Nature and purpose | Receiving events from the tracking script, turning them into stored events and statistics, showing and emailing those statistics to the customer (including reports and traffic alerts), and returning them to the software the customer connects with an API key. At the customer's request, also importing daily totals from the customer's Google Analytics property, which hold no data about a single visitor, and showing the customer's Google Search Console figures, which are fetched when viewed and not stored |
| Data subjects | Visitors to the customer's websites |
| Categories of data | A visitor identifier that changes every day (a one-way hash of a daily secret value, the site's domain, the IP address, and the user agent); page path; campaign tags; whether the page address carried an advertising network's click identifier, and which network (never the identifier); referring domain; country; device size class; browser and operating system with major versions; for each page left, the scroll depth in percent and the time it was visible; event names, a random identifier and time for each event, and the event properties the customer chooses to send, including an amount and currency when the customer records one, and the address of a clicked link when the customer turns on outbound link or download tracking. The IP address and full user agent are used only in memory for each request and never stored |
| Special categories | None. The terms forbid sending them |
| Frequency | Continuous, as visitors use the customer's websites |
| Location | United States (Amazon Web Services) |
Annex 2: Security measures
- Encryption of data in transit (TLS) and at rest.
- IP addresses are never stored or logged.
- The secret value in the visitor identifier is replaced every day and deleted, so identifiers cannot be linked across days, and once a day's value is deleted, that day's identifiers cannot be traced back to an IP address. We never try to do so while it exists.
- Each part of the service has only the access it needs, and production is separated from development.
- Passwordless sign-in with emailed codes or passkeys, a fresh confirmation before sensitive changes, and rate limits on sign-in.
- Rate limits and filtering of addresses known for abuse in front of the tracking service.
- Staff access to customer accounts is limited to people who need it, and each time staff open an account, organization, or message in the admin console is recorded in a log kept for 25 months.
- Deleted data is kept in recovery copies for 7 days to undo mistakes, then removed.
- Service logs never contain IP addresses and are deleted after one month.
Annex 3: Subprocessors
| Subprocessor | What it does | Data | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Hosting, storage, content delivery, and email delivery | Customer Personal Data and account data | United States |
| Stripe, Inc. and Link | Payments for paid plans, as merchant of record | Account and billing data only, no visitor data | United States |
Google LLC provides our staff's email (Google Workspace) and is used for email only. It holds no part of the service and never receives Customer Personal Data, so it is not a subprocessor under this DPA. Our privacy policy describes what it receives about our customers.