How we handle your customers’ data

What we take, where it goes, and who sees it.

For owners, office managers and operations

Lead reactivation works the people your business already knows — people who asked for a quote and never booked, customers who booked once, regulars who stopped, and facility managers who asked for a bid. We rank them by likelihood to book and work the list from the top, so your office spends its time on the people most likely to say yes.

Cleaning is lightly regulated, and we will not pretend otherwise. No federal privacy statute governs your customer list. What does apply is telemarketing law — the Telephone Consumer Protection Act and the state rules on texting — and the FTC’s rules on what advertising may claim. And there is one risk no regulation names: a cleaning company’s records often hold door codes, alarm codes and the days a home sits empty. This document sets out, control by control, how the engagement handles all of it, including the controls we run because they are right rather than because a rule requires them.

Sections 02 to 06 are the plain-English part. They show the whole system in pictures, explain the four things the ranking looks at, and follow one example lead from your CRM to your office. The sections after them are the detail to check before you sign.

01

Commitments

Ten commitments, before the detail

• 01 · Direct identifiers never reach an AI provider — Names, phone numbers, emails and service addresses stay in a secure environment. The AI provider sees a random ID and a few short facts, nothing more.
• 02 · Nothing goes out without your approval — Your owner or office manager approves every template before use. Our review sits on top of yours, never in place of it.
• 03 · Every message stays on your record — Outreach goes through your own channels, or is logged into your CRM as it is sent. Nothing off the record.
• 04 · No evidenced consent, no text message — Consent, opt-outs, Do Not Call status and quiet hours are checked at the moment of sending. Opt-outs are permanent.
• 05 · Your data serves your engagement only — No model training, no reuse across clients, no sale, no outside enrichment without your written instruction.
• 06 · Breach notice within 72 hours — As soon as possible and no later than 72 hours. No rule in your industry sets this window for a vendor; we commit to it anyway.
• 07 · Return and destruction, certified — At the end of the engagement your data, including the identity key, is returned or destroyed, and we confirm it in writing.
• 08 · No claim you cannot back up — Messages invite a booking or a quote. No made-up reviews, and no green, insured or background-check claim you have not confirmed in writing.
• 09 · A fee structure you choose — A flat fee or a results-based fee, with how each is treated set out in section 14.
• 10 · Evidence on request — Every control here has something you can inspect. We answer any vendor or security questionnaire during onboarding.

02

The whole picture

The system on one page

The system works in three zones. Names, addresses and contact details stay on your side. Our scoring works only with a random ID and a few short facts. The results come back to your side, where your business approves and sends.

Outcomes (booked, cleaned, back on a schedule) come back by random ID and improve your ranking only. G1 — the agreement and intake review — clears before any data moves. G7 covers retention and destruction.

Dashed gold-edged boxes, marked G1 to G7, are compliance gates. Nothing passes a gate until it clears. Section 03 lists what each one checks.

03

Step by step

From our first conversation to the first message

Seventeen steps in five phases. The gate marks show where a compliance check has to clear before the work moves on.

Onboard (before any data)

• 01 First conversation — How your business works its leads today
• 02 Agreement — Roles, purpose, subprocessors, 72-hour notice G1
• 03 Intake review — Lead sources, consent wording, opt-outs G1
• 04 Secure environment — In your environment, or our workstation

Prepare (on your side)

• 05 Map your stages — Your CRM statuses to eight shared stages
• 06 Check the list — Opt-outs, Do Not Call, complaints G2
• 07 Swap names for IDs — A random ID; the key stays with you
• 08 Notes into facts — Access codes stripped; fixed-list answers G3

Rank (Tez scoring)

• 09 Score — Intent, Opening, Reachability, Fit
• 10 Tier and reasons — A to D, with the top reasons
• 11 Short summary — Why call, and an opening line, checked G4
• 12 Next step — Channel by consent, and timing

Act (on your side)

• 13 Match back — The ranked list appears in your CRM
• 14 Your approval — Owner or office manager approves the wording G5
• 15 Send — Re-checked at sending; logged to your CRM G6

Learn (ongoing)

• 16 Record outcomes — Booked, cleaned, kept; a held-back group
• 17 Improve and report — Your ranking only; results you can check G7

04

The ranking

How the list is put in order

Every lead is checked first, then looked at through four factors. The factors combine into one score, and the list is sorted by it. The sorting is plain arithmetic, not an AI model, so every score can be explained in a sentence.

How the ranking gets better

• 01It starts from your team’s experience — Your office tells us how often each kind of lapsed customer or stalled quote comes back. Those estimates set the first odds, and until your results come in we say so.
• 02It corrects itself from your results — As cleans are booked, kept or declined, the odds for each reason move toward what actually happened at your business.
• 03It becomes a model of your business alone — After about 300 recorded outcomes, the ranking is fitted to your business’s results. It is never trained on, or pooled with, another business’s data.
• 04A held-back group keeps us honest — With your agreement, about one lead in ten is held back and not contacted for a set period. Comparing the two groups shows what the outreach actually changed, rather than what would have happened anyway.

05

A worked example

One lead, from your CRM to your office

Dana Whitfield is fictional. Her record is shaped like a real one, including the parts that should never travel. Follow it through the four cards, left to right and top to bottom.

1 · Your CRM record (stays with you)

2 · What we receive (leaves your side)

Never leaves your side: her name, phone, email, address, CRM ID, the note itself, the door code, the dog, the visit price, exact dates.

3 · What comes back (back to you)

4 · In your CRM (stays with you)

She agreed to appointment reminders by text, not marketing, so the next step is email. Her last paid visit was under 18 months ago, so a call from your office is not blocked by the Do Not Call list, unless she has asked you not to call. Your office sees her name here, in your own CRM, for the first time.

• 01Her door code never left your side — The code and the dog were stripped from the note before anything read it, and “until the move settles” left only as “waiting on an event.” The flag tells your office that this record holds an access code, so you can decide whether it belongs in your CRM at all.

06

The suggestion

How the “why call” note is written and checked

Each lead comes back with a reason line in fixed wording and a short summary drafted by an AI model, both written only from the facts in card 2 of section 05. The AI writes; it does not decide. The order comes from arithmetic, and your business approves anything sent.

The four checks at gate G4

• No personal data — The draft may not contain a name, number, email, address or anything about getting into a home. Names appear only as a placeholder, filled in on your side at sending.
• No claims you have not approved — No prices, discounts, plan terms, reviews, or green, insured or background-check claims unless they are on your approved list. Section 12 sets out why.
• Nothing made up — Every statement in the summary must trace back to one of the facts it was given. A statement that does not is treated as a failure.
• Your never-say list — Phrases and topics your business rules out are blocked, on top of the general rules above.

07

Roles

Your business stays in charge of the data

No federal privacy statute governs a cleaning company’s customer list; the Gramm-Leach-Bliley Act covers financial institutions, and the FTC Act’s bar on unfair practices is the only federal backstop. State privacy laws apply above size thresholds — in California, revenue over $26.625 million or data on 100,000 residents — and Texas exempts small businesses as the SBA defines them. Where one applies, you are the business or controller and we are the service provider or processor. Where none does, our contract does the same job. Either way the architecture here runs in full — for most cleaning businesses, more than the law requires.

08

Data

What we take, and what we never take

The least data that lets the list be ranked and worked. Anything that helps someone get into a home or a building is never taken.

09

The privacy layer

Where AI sits, and what it sees

Notes are where door codes and “away until the 20th” end up. So they are read where they already are, and only short answers leave. Five layers make sure of it.

10

Where it runs

Two ways to run the secure environment

The secure environment is where identifiable data lives during the engagement, and your business chooses where it sits. In both options the key table never leaves it, and the AI provider receives only a random ID and fixed-list facts.

Workstation standard, when Tez operates it

• Encrypted at rest — Full-disk encryption, as Massachusetts 201 CMR 17.00 requires on laptops, plus a separate encrypted volume for each business’s data.
• Dedicated and locked down — An OS account used only for client data, multi-factor sign-in, screen lock, current patches, endpoint protection.
• No cloud sync — Client data is never stored in a synced folder or consumer cloud backup, and is excluded from sync by configuration.
• Wiped at the end — The business’s volume is destroyed at termination and the destruction certified in writing.

11

Security and incidents

The controls, and what happens if one fails

If something goes wrong

• 01 · Contain — Stop sending, revoke the affected credential, isolate the system.
• 02 · Notify you within 72 hours at the latest — Which records and fields, what window, what we have done. Updates follow as we investigate.
• 03 · Preserve evidence — Logs, send records and the consent history are kept intact for your investigation.
• 04 · Support your notice, never pre-empt it — Customer notice is your decision, on your state’s deadline. We tell you even where no statute would, such as an exposed entry code, and never contact your customers ourselves.

12

Claims and advertising

What outreach may say about your business

No licensing board reviews a cleaning company’s marketing. The Federal Trade Commission Act does: under section 5, a claim must be true, and backed up before it is made, whoever or whatever drafted it. These are the rules the drafting is built around.

• 01Reviews and testimonials — 16 CFR Part 465 — In force since October 21, 2024: no fake reviews or testimonials, AI-written ones included, and no reward conditioned on a review being positive. Outreach may ask for an honest review; it never writes one or pays for a good one.
• 02Recurring plans — automatic-renewal law — A message may invite a former regular back; it never signs anyone up. Enrollment happens in your booking flow, with the disclosures and consent that ROSCA and laws like California’s Automatic Renewal Law require. The FTC’s click-to-cancel rule was vacated on July 8, 2025; the FTC reopened the question in March 2026.
• 03Green and non-toxic claims — the Green Guides — No unqualified “green” or “eco-friendly” (16 CFR 260.4); “non-toxic” needs evidence for people and the environment. The EPA Safer Choice service logo only if you hold that certification; otherwise “we use Safer Choice-certified products,” only where true.
• 04Trust claims — bonded, insured, licensed, checked — Only as you confirm them in writing, and no wider: “every cleaner is background-checked” only if every one is. The checks themselves are your process under the Fair Credit Reporting Act. California janitorial employers must register with the Labor Commissioner, and hiring an unregistered one draws fines, so California bids wait for your registration.
• 05Rails the drafting stops at — Damage or theft claims, injuries, billing disputes and complaints go to your office. Outreach never asks for or repeats access details or when a home will be empty, and never asks for payment. Every draft passes gate G4 first (section 06).

13

Consent

No evidenced consent, no text message

Under the Telephone Consumer Protection Act the party that sends a message can be liable for it directly, so consent is enforced in software at sending. A facility manager’s mobile is covered like anyone’s, and CAN-SPAM covers business email.

• 01 · A consent history, not a checkbox — An append-only record of source, wording, channel and date. Reminder and marketing consent are kept apart; neither is ever overwritten.
• 02 · Checked when the message sends — Consent, suppression, Do Not Call and quiet hours are rechecked at sending, not at list-building. Yesterday’s opt-out holds today.
• 03 · Lapsed customers and the 18-month window — A paid visit within 18 months, or a quote request within three, is an established business relationship: under federal rules your office may call a number on the Do Not Call list. It is not consent to marketing texts, and it ends when they ask you to stop.
• 04 · No marketing consent on file — Email, or a call from your office — not text. A number given for appointment reminders is not consent to marketing.
• 05 · Do Not Call, reassigned numbers, hours — National Do Not Call Registry and FCC Reassigned Numbers Database, results dated and stored. 8am to 9pm local time, 8pm where Florida, Oklahoma or Washington require.
• 06 · Opt-out everywhere, permanently — STOP, a request in any words, or one made to your office is honoured on every channel at once, inside the FCC’s 10 business days, and survives any re-import.

14

How we are paid

Two fee models, and how each is treated

We offer two models. Fees are set in conversation and are not in this document. What belongs here is how each model is treated. In some industries, rules limit how a marketing vendor may be paid. We know of no such rule for cleaning, so the choice comes down to how you want to pay, not what you are allowed to.

Model A: Flat monthly fee

A fixed fee for operating the service. It does not depend on cleans booked or revenue earned.

• Treatment. No cleaning-industry rule restricts it. It is an ordinary service contract.
• What to agree. The scope of the work and the term. Nothing needs measuring.
• The simplest model to budget, approve and audit.

Model B: Results-based fee

A share of revenue from reactivated customers, measured from your CRM’s own records.

• Treatment. No cleaning-industry rule restricts it either. It is a contract question, not a regulatory one.
• What to agree. What counts as reactivated, and for how long a returning regular’s visits count. Conversions come from your CRM; we never mark them.
• The fee changes nothing about consent or claims: sections 12 and 13 apply in full.

15

Subprocessors and contract

Who else touches the data, and what we sign

The full list is an exhibit to your agreement. We give 30 days’ notice before adding or changing a subprocessor.

What the agreement contains

• Roles and purpose — Your business as the owner of the data, Tez as service provider or processor; use limited to this engagement, with the contract terms state privacy laws require where they apply.
• No secondary use — No training, no sale, no reuse across clients, no enrichment without written instruction.
• Security exhibit and 72-hour notice — The controls in sections 08 to 11, as binding terms, including the never-taken list.
• Consent and claims warranty — Your representation of how the leads were obtained, and of the claims you approve about your business.
• Privacy requests — Access, correction and deletion within your deadlines — under a state privacy law where one applies, and on request where none does.
• Audit, return and destruction — Reasonable audit and questionnaire rights; return or certified destruction at termination.

16

Regulatory map

Each rule, and where it is addressed

17

References

Every requirement, traced to its source

Each commitment in this document rests on a primary source: a statute, a regulation, a regulator’s own order or guidance, or a court decision. They are listed here so you, or your counsel, can check our reading against the text. Links were current in October 2026.

18

Limits

What this document is not

• 01Not legal advice — You and your counsel decide how these rules apply to your business. This document tells them what we do so they can.
• 02Not a SOC 2 report — We do not hold a SOC 2 attestation. We answer your questionnaire and provide the policies and evidence behind each control instead.
• 03Not a cleaning company — Tez I Solutions does not clean, schedule crews, price jobs or run background checks, and holds no janitorial registration. Those, and the claims you make about them, stay yours.
• 04Not permanent — Current as of October 2026. Rules in this area are moving — the FCC’s revoke-all requirement was delayed and then narrowed by an order adopted in September 2026 that is not yet in force, and the FTC is reconsidering its rules on recurring plans. We review this document at least once a year and whenever a rule it relies on changes.
• 05Not a promise of results — A score says which leads to contact first, not who will book. Until your own outcomes are recorded, the odds behind it are estimates drawn from your team’s experience.

A1

Commitments

Ten commitments, before the detail

• 01 · Your accounts, on business terms — We work only in accounts your business owns, on business plans. Never in a personal or consumer account — ours, yours or an employee's.
• 02 · A named user, never a shared password — You add us as a named user with our own sign-in and multi-factor authentication. We never ask for a shared password, and you should never send one to us by email.
• 03 · The least access that does the job — Each connection reaches only the data its workflow needs. Admin rights are used for set-up tasks, logged, and reduced afterwards.
• 04 · Nothing goes live without your approval — Every connection, workflow and set of instructions is approved by you, in writing, before it is switched on. So is every change to one that is already running.
• 05 · Automated where it is routine, a person in the loop where it is not — Routine, rule-based work can run on its own once you have approved it: sorting and tagging, summaries for your team, filing, and fixed-wording notices such as an appointment reminder from a template you signed off. Anything that needs a decision or a judgement — a reply written for a particular customer, a price, a term, a commitment, or anything your industry's page marks for review — has a person on your side in the loop before it goes anywhere. Each workflow's data sheet (A3) states which kind it is. Where your industry's page requires a person to review every customer message, that rule applies instead.
• 06 · Your data stays in your tools — We build and test inside your workspace. We do not copy your business data into Tez's own AI accounts. Where we need examples outside your tools, we use made-up records.
• 07 · Your data serves your business only — No reuse across clients, no sale, no training of anything by us. Prompts, instructions and workflows built from your material are yours and are not reused for anyone else.
• 08 · Vendor data settings confirmed in writing — During onboarding we read each tool's current data terms, set its controls with you, and give you a written record. We re-check it whenever a vendor changes its terms.
• 09 · Incident notice within 72 hours — As soon as possible and no later than 72 hours, or sooner where your industry's page says so.
• 10 · Access removed, everything handed over — At the end, our access is removed, every credential we created is revoked or rotated, and every workflow is documented and handed over. We confirm it in writing within 30 days.

Evidence on request: every control in this document has a record you can inspect, listed in section A5. If you send us a security questionnaire, we complete it during onboarding.

A2

Accounts and access

Whose accounts, and how we get in

The AI tools, the systems they connect to and the accounts that run them all belong to your business. We are given access to them; we never hold them. That is what makes the work portable: if we part ways, everything keeps running and nothing has to be moved out of our name.

Nothing in this section starts before you have decided to work with us. The first session is a conversation. We do not ask for logins, exports or files beforehand.

Who owns what

How access is set up

• 01 · You decide what we need — We list the systems and the role each one needs, and why. You agree or strike items out.
• 02 · You add us — Usually by adding us as a user, on a call where we walk through it together. A password is never sent.
• 03 · We confirm the safeguards — Multi-factor authentication on, role as agreed, sign-in recorded in the access record.
• 04 · Reviewed every quarter — We go through the access record with you and remove anything no longer needed.
• 05 · Removed at the end — Section A5 sets out how access ends.

Roles

Where a state privacy law reaches your business, we act as your service provider or processor for the access we hold, and the agreement says so.

A3

What the tools can see

Connections, scopes, and what stays out

An AI tool connected to one of your systems can see whatever that connection lets it see. An assistant that searches your files can surface anything the person using it is allowed to open — Microsoft says of its own Copilot that it "only surfaces organizational data to which individual users have at least view permissions." So the work starts with permissions, not prompts.

Before anything is connected

• Who can see what — Before an assistant is pointed at a shared drive, inbox or CRM, we review who can open what. Folders that are open to everyone but should not be are fixed first, with your approval.
• One data sheet per workflow — Every workflow gets a written sheet: what it reads, what it writes, who sees the result, and where a person reviews it. You approve the sheet before we build.
• Add-ons are vendors too — A plug-in, connector, custom GPT or agent from a third party is another company handling your data. None is installed without your approval and a record of its data terms.

What a data sheet looks like

Illustration — not real client data.

What stays out by default

Unless your written decision says otherwise, after we have shown you what the vendor's terms and your industry's rules say, these are kept out of every prompt, instruction file and connection:

• Social Security numbers, tax IDs, driver's licence and other government ID numbers
• Full bank account and card numbers
• Passwords, access codes, gate, door and alarm codes
• Health information
• Anything your industry's page (A7) marks as restricted

Where a connection would expose one of these — a folder of scanned IDs, a CRM field holding card numbers — the connection is narrowed to leave it out, or not built.

Before a workflow goes live

AI tools make mistakes. Every workflow is built on the assumption that a draft can be wrong, which is why the review step is part of the design rather than a suggestion.

A4

Model providers and training

What the vendors do with your data, and how we check

When your team or a workflow uses ChatGPT, Claude, Copilot or Gemini, the vendor processes that data under its contract with your business. Tez is not a reseller or partner of any AI vendor, and not a party to those contracts. Whether a vendor trains its models on your data, how long it keeps prompts, whether its staff can review them, and where it processes them are set by the vendor's terms and by the plan you are on. Those terms change. So we do not promise what a vendor will do. We promise what we will do.

What we do

• 01 · List every tool — Each AI tool and AI feature you pay for, the plan it is on, and who holds a seat.
• 02 · Read the current terms — For each one we record what the vendor says about training on your data, retention, human review, where data is processed, and which admin controls exist. Each entry carries the date and the address of the page we read.
• 03 · Set the controls with you — Where a tool offers a choice — training opt-outs, retention periods, chat history, which add-ons are allowed — we recommend the most protective setting that still does what you need, and you decide.
• 04 · Give you the record — The settings record is yours, in writing. Your compliance contact can file it with your vendor reviews.
• 05 · Re-check when terms change — When a vendor changes its data terms, we re-read them, update the record and tell you if anything moved. We also re-check the whole record at least every six months.

What the main vendors said when we checked

Read on each vendor's own page on 6 October 2026. This is the vendor's statement to its customers, not a commitment by Tez. If it changes, the vendor's current terms govern, and we update your record.

Consumer plans and personal accounts

Consumer plans run on different terms from business plans — Anthropic's Commercial Terms, for one, state that they do not cover its consumer offerings. We do not do business work in consumer or personal accounts, and we do not rely on a consumer plan's settings to protect business data.

Our own tools

We use AI tools of our own to write code and documentation. Your business data does not go into them. Anything we build for you is built and tested in your workspace, or against made-up records.

A5

Records, security and incidents

What we keep, how it is protected, and what happens if something fails

Records you can inspect

Records describe what we built and changed. They live in a location your business owns, and they do not contain your customers' data.

Changes to something already running

Every change to a live workflow is described, approved by you, tested, logged and reversible — the previous version is kept. If a vendor update breaks a workflow, or a workflow starts doing something it should not, we may pause it at once to stop harm, and tell you the same day. We do not change what a workflow does without your approval.

Security controls

If something goes wrong

An incident includes a workflow sending or showing data to the wrong person, a connection reaching more than its sheet allows, a suspected compromise of a Tez sign-in, and a vendor incident we learn of that affects your workspace.

• 01 · Contain — Pause the workflow, revoke the affected credential or connection, and stop the exposure.
• 02 · Notify you within 72 hours at the latest — Which systems and data, what window, what we have done. Sooner where your industry's page sets a shorter time. Updates follow as we investigate.
• 03 · Preserve evidence — Logs, the change log and the vendor's audit records are kept intact for your investigation.
• 04 · Support your notice, never pre-empt it — Whether customers or regulators are told is your decision. We never contact your customers about it. A vendor's own incident notice comes to you under your contract with that vendor.

When the engagement ends

Everything we build is yours — documented and portable. If we part ways, it keeps working and your team knows how it runs.

A6

Limits

What this document is not

• 01 · Not legal advice — Your counsel or compliance officer decides how your industry's rules apply to your business. This document tells them what we do so they can.
• 02 · Not a SOC 2 report — We do not hold a SOC 2 attestation. If you send a security questionnaire, we complete it and provide the policies and evidence behind each control instead.
• 03 · Not the vendor — We do not run the AI vendors' systems or set their terms. Their security, retention, outages and incidents are governed by your contract with them. We are not a reseller, partner or certified provider of any AI vendor.
• 04 · Your obligations stay yours — Using AI tools does not move your duties to us: licensing, supervision, record keeping, privacy notices and your staff's use of AI remain your business's responsibility. We build to them, as your industry's page sets out.
• 05 · Not a promise about AI output — AI tools can be wrong, and confidently so. That is why anything that needs a judgement has a person in the loop, and why no workflow makes a decision your business would otherwise make.
• 06 · Not permanent — Current as of October 2026. Vendor terms and the rules on AI change often. We review this document at least once a year, and whenever a vendor term or rule it relies on changes.

A7

Cleaning

What your industry's rules mean for your AI tools

Cleaning is lightly regulated, and that does not change because an AI tool is involved. What matters most is something no rule names: your scheduling software and your team's notes often say how to get into a customer's home, and when it sits empty. An assistant connected to those systems can repeat that to anyone who asks it the right question. The rest is advertising law, because AI tools are often asked to draft the messages, reviews requests and website copy that make claims about your service.

In practice

• A workflow may draft a reply to a quote request from the details the customer gave. It does not read the job notes on that customer's past visits.
• A team assistant may answer questions about your cleaning checklists and policies. It is not connected to the scheduling system where entry instructions live.
• A drafted follow-up may say what your service includes. It may not say "eco-friendly" unless that exact claim is on your approved list.
• During the audit we check whether staff paste customer addresses or entry details into personal AI accounts. If they do, you hear it from us first.

A8

Sources

Where these rules come from

1. FTC Act section 5, 15 U.S.C. 45 — https://www.law.cornell.edu/uscode/text/15/45 2. FTC Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465 — https://www.ecfr.gov/current/title-16/chapter-I/subchapter-D/part-465 3. Restore Online Shoppers' Confidence Act, 15 U.S.C. 8401–8405 — https://www.law.cornell.edu/uscode/text/15/chapter-110 4. California Automatic Renewal Law, Cal. Bus. & Prof. Code 17600–17606 — https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=BPC&division=7.&title=&part=3.&chapter=1.&article=9. 5. FTC Green Guides, 16 CFR Part 260 — https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-260 6. Telephone Consumer Protection Act, 47 U.S.C. 227 — https://www.law.cornell.edu/uscode/text/47/227 7. FCC rules, 47 CFR 64.1200 — https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200 8. FTC, CAN-SPAM Act: A Compliance Guide for Business — https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business 9. California Consumer Privacy Act; California Privacy Protection Agency, monetary thresholds — https://cppa.ca.gov/regulations/cpi_adjustment.html

• 01NCSL, Security Breach Notification Laws — https://www.ncsl.org/technology-and-communication/security-breach-notification-laws