Florida’s Digital Bill of Rights (FDBR) has been enforceable since mid-2024, but its reach is easy to misunderstand. Some business owners assume it applies to every company collecting customer data. Others dismiss Florida privacy law as a Big Tech concern. The FDBR’s main controller obligations reach relatively few companies, but falling outside that group does not end the privacy discussion.
For smaller Florida businesses, the next questions are practical: How do you protect personal information? Do your privacy promises match your practices? And what responsibilities have you accepted in customer and vendor contracts?
Key Takeaways
- FDBR coverage is narrow: Its main controller obligations use a revenue-plus-platform test, not simply whether a business collects customer data.
- Other laws still matter: The Florida Information Protection Act (FIPA) addresses data security and breach notification, while the Florida Deceptive and Unfair Trade Practices Act (FDUTPA) can apply to misleading privacy and security claims.
- Your promises need to match reality: A copied privacy policy can create problems if it describes protections, choices, or data-sharing practices you have not implemented.
- Contracts deserve a separate review: Customer agreements may impose security, notification, assistance, and financial obligations beyond your ordinary operating practices.
- Start with your actual data flows: Understanding what you collect and where it goes makes policy, contract, and security reviews more useful.
Three Florida Laws Relevant to Business Privacy
These laws address different parts of the privacy picture. The comparison below is a starting point, not a complete inventory of every requirement that may apply to your business.
| Law | Coverage described in this article | Main concern |
|---|---|---|
| Florida Digital Bill of Rights (FDBR) | Main controller obligations apply to businesses meeting a revenue-plus-platform test | Consumer data rights, data protection assessments, processor relationships, and limits on collection |
| Florida Information Protection Act (FIPA) | Businesses holding covered personal information about Florida residents | Reasonable security measures and breach notification |
| Florida Deceptive and Unfair Trade Practices Act (FDUTPA) | Business practices involving Florida consumers, subject to applicable legal limits | Unfair or deceptive conduct, including misleading privacy and security claims |
Who the FDBR Actually Covers
The FDBR’s controller coverage uses two conditions together: global annual gross revenue above $1 billion and a qualifying platform operation. The platform categories include certain online advertising businesses, consumer smart speakers with voice command services, and application stores or digital distribution platforms.
The revenue threshold alone is not enough, and collecting customer information alone is not enough. The details of the platform criteria and any exemptions matter when determining coverage.
For most smaller businesses, the more useful follow-up is not another threshold calculation. It is understanding the security, disclosure, and contractual responsibilities that remain.
Where Smaller Businesses Still Have Responsibilities
Protecting Personal Information and Responding to Breaches
FIPA addresses reasonable security measures and breach notification for covered personal information. It does not prescribe a single set of technical controls for every business.
A recognized framework, such as the NIST Cybersecurity Framework, can help organize security work. Its six functions, Govern, Identify, Protect, Detect, Respond, and Recover, provide a structure for identifying gaps and assigning priorities. Using a framework is an implementation approach, not the same thing as establishing that every legal obligation has been met.
Breach response also requires more than a general promise to notify someone quickly. The article’s relevant FIPA timelines include notification to the Florida Attorney General within 30 days when a breach affects 500 or more Florida residents, and a 10-day reporting period for a third-party agent notifying the business it serves. Applicable triggers, starting points, exceptions, and any separate notification duties need to be reflected in the response process.
The practical distinction: Reasonable security and applicable notification duties are legal concerns. A documented response plan is a way to prepare to meet those duties. The plan should identify who investigates an incident, who evaluates notification requirements, and how contractual deadlines are tracked.
Keeping Privacy Promises You Can Support
Having a privacy policy and following it are different things. Under FDUTPA, a mismatch between privacy or security representations and actual practices can create exposure to a deceptive-practices claim. Falling outside the FDBR’s controller threshold does not resolve that issue.
The gap can begin with a competitor’s policy or a downloaded template. Consider a hypothetical e-commerce company whose policy promises “industry-standard encryption” and “limited data sharing with trusted partners.” Customer information is actually stored in an unsecured cloud storage bucket, while advertising tools send browsing information to platforms the policy does not mention. The policy describes one set of practices; the business operates another.
The review should extend beyond the formal policy. Statements such as “we never sell your information,” “you control your data,” and “enterprise-grade security” also need to be supportable.
Understanding Your Role in Data Relationships
Your business may send customer information to CRM systems, email platforms, payment processors, analytics services, and cloud hosting providers. It may also receive information from customers and process it on their behalf. Those are different relationships, and they should not be treated as interchangeable.
When you provide services to a covered FDBR controller, separate two questions: which legal duties attach to your processing role, and which additional commitments appear in the contract. Being below the controller revenue threshold does not, by itself, answer both questions.
A Data Processing Agreement (DPA) may require specific security controls, assistance with consumer requests, support for assessments, or incident notification faster than the statutory timeline otherwise relevant to the relationship. It may also allocate investigation, notification, and other response costs.
Legal responsibilities and contractual cost allocation are related, but they are not the same. Have counsel review both rather than assuming the agreement either replaces the law or merely repeats it.
What the Enforcement Record Adds
The Attorney General’s February 2026 enforcement report described 1,496 consumer complaints received in 2025, including 685 dismissed because the targeted entity did not meet the billion-dollar threshold, and 186 Notices of Alleged Violation. The figures illustrate why coverage analysis matters, but they do not answer whether a smaller business has responsibilities under other laws or contracts.
The Roku proceedings offer a more concrete example. Florida’s October 2025 action alleged improper collection and sharing of children’s data, weaknesses in protections against reidentification, and privacy controls that overstated families’ ability to limit data use. The 2026 resolution required changes to parental controls and data practices, without civil penalties or an admission of wrongdoing.
For readers outside that platform category, the useful questions are narrower: Do privacy controls work as described? Does sharing match the disclosures? And are claims about de-identified information supported by actual safeguards? Those are review questions, not a suggestion that every business has Roku’s obligations.
The FDBR also includes a 45-day cure provision. Its availability, conditions, and effect require legal review. Do not build a response strategy around an assumed opportunity to fix a violation after receiving notice.
Questions to Ask About Your Own Business
Does Our Privacy Policy Match Our Website and Tools?
Compare the policy with an inventory of what actually runs on your website and in your customer systems. Look for specific mismatches:
- Undisclosed collection: Analytics may be mentioned, while session recording, heat-mapping, or advertising pixels are not.
- Broader sharing: The policy may describe service providers without explaining other recipients of customer information.
- Inaccurate retention: A deletion promise may conflict with records kept after account closure.
- Unavailable choices: Customers may be promised access, correction, or deletion options that do not work as described.
Advertising tools deserve particular attention. Understand whether a tool measures performance, supports audience building or retargeting, or performs several functions. Give that information to counsel when reviewing disclosures and any applicable consent or opt-out requirements. A tool’s label alone does not settle its legal treatment.
What Have We Agreed to With Vendors and Customers?
When your business sends information to a vendor, review the permitted uses, security commitments, incident-reporting terms, and deletion arrangements. Do not assume every recipient uses information only for your purposes.
When your business is the vendor, examine the commitments you are accepting. Important questions include:
- Notification: Can your incident process meet the agreement’s reporting deadline?
- Assistance: Are audit, consumer-request, and assessment duties clearly defined?
- Costs: Who pays for additional compliance work and incident response?
- Liability: How do indemnity provisions, liability caps, and exceptions interact?
There is no single contract position that suits every relationship. Ask counsel to evaluate the terms against the services, data, and risks involved.
Do Industry-Specific Rules or Exemptions Change the Analysis?
Healthcare and financial-services businesses need a more specific review. The FDBR includes exemptions involving HIPAA and the Gramm-Leach-Bliley Act, but exemptions may depend on the entity, the information, or the processing involved.
An exemption from one law should not be treated as an exemption from every security or notification obligation. HIPAA, the FTC Safeguards Rule, and FIPA may require separate analysis. Payment-card requirements also belong in the review, with PCI DSS distinguished as a contractual requirement rather than a Florida privacy statute.
Next Steps: Separate Obligations From Implementation
Confirm What Applies
Have counsel confirm your coverage, exemptions, notification duties, and any requirements affecting collection, sharing, advertising, or assessments. Include customer DPAs and vendor agreements in that review. Keep statutory duties, contractual commitments, and recommended practices distinct.
Build the Operational Picture
You can make that review more productive by assembling a clear picture of your practices:
- Inventory personal information: Record what you collect, where it is stored, who receives it, who can access it, and how long it is retained.
- Identify disclosure gaps: Compare that inventory with your privacy policy, website claims, and available customer controls. Use the findings to guide corrections to the disclosures, the practices, or both.
- Map contract commitments: Record incident-reporting deadlines, security requirements, assistance duties, and responsibility for costs.
- Review response readiness: Check whether your incident process can identify affected information, involve the appropriate advisers, and support applicable notification decisions.
- Prioritize security gaps: Use a recognized framework or relevant industry standard to organize improvements, then revisit the review as tools, vendors, and services change.
Start by comparing what your privacy policy says with what your website and tools actually do. That gives you a concrete basis for deciding what needs operational attention and what needs legal advice.





