Character Count Design for Terms of Service and Privacy Policies - Balancing Legal Requirements with Readability
Terms of service and privacy policies are legal contracts between service providers and users. Yet their character counts continue to balloon year after year - studies show it takes an average of over 30 minutes to read the full terms of major services. Designing documents that maintain legal comprehensiveness while staying within a character count users will actually read is a challenge requiring collaboration between legal and UX teams. This article presents practical approaches to character count design grounded in domestic and international legal requirements.
Terms of Service for Major Services - Character Count Reality
Let's first examine how many characters actual services publish in their terms of service. The following data surveys the character counts of each service's Japanese-language terms.
| Service | Terms Character Count | Estimated Reading Time | Sections | Last Updated |
|---|---|---|---|---|
| Apple (Media Services) | ~35,000 chars | ~44 min | 30+ | 2024 |
| Google (Terms of Service) | ~12,000 chars | ~15 min | 15 | 2024 |
| Amazon (Terms of Use) | ~18,000 chars | ~23 min | 20+ | 2024 |
| X (formerly Twitter) | ~15,000 chars | ~19 min | 12 | 2024 |
| LINE | ~20,000 chars | ~25 min | 25 | 2024 |
| Mercari | ~22,000 chars | ~28 min | 20+ | 2024 |
Google's relatively short terms (~12,000 characters) result from separating service-specific conditions into separate documents (additional terms of service). This "layered approach" is an effective strategy for character count design, as discussed later. Apple's Media Services terms exceed 35,000 characters because they consolidate conditions for multiple services - iTunes, App Store, Apple Music, and Apple TV+ - into a single document.
Why Terms of Service Keep Growing - Structural Factors
Several legal and business structural factors drive the inflation of terms of service character counts.
- Legal risk avoidance: Lawyers operate on the principle that "what isn't written isn't agreed upon," attempting to cover every risk scenario. This results in detailed descriptions of even low-probability events, inflating character counts
- Regulatory complexity: The number of applicable regulations keeps growing - GDPR, Japan's Act on the Protection of Personal Information, the Telecommunications Business Act, the Specified Commercial Transactions Act, and more. Disclosing everything each regulation requires inevitably increases character counts
- Feature expansion: Single platforms now offer payments, messaging, content distribution, advertising, and more, each requiring its own usage conditions
- Litigation response: Repeated "patch-style revisions" that add clauses addressing past litigation issues cause documents to bloat
- International expansion: Supporting multiple jurisdictions (Japan, EU, US, etc.) requires adding jurisdiction-specific provisions
These factors interact to continuously push character counts upward. Yet as character counts increase, user read-through rates decline, normalizing the state of "agreed but unread." The layered approach introduced next addresses this contradiction.
The Layered Approach - A Practical Solution to the Character Count Problem
The layered approach divides legal documents into multiple tiers, providing information progressively based on user interest level. GDPR Recital 58 also recommends this as a means of "transparent information provision."
| Layer | Name | Recommended Chars | Content | Display Method |
|---|---|---|---|---|
| Layer 1 | Summary | 500-1,000 chars | Plain-language summary of key provisions | Displayed directly on consent screen |
| Layer 2 | Overview | 2,000-5,000 chars | Bullet-point highlights of each section | Expandable accordion UI |
| Layer 3 | Full Text | 10,000-30,000 chars | Legally complete full terms | Link to separate page |
The Layer 1 summary is not a legally binding document but supplementary material to aid user understanding. Adding a note like "This summary is for reference only; only the full text has legal effect" mitigates legal risk while improving readability.
This approach is essentially the same as the structure in business email character count design - "convey the key point in the subject line, supplement with details in the body." User attention is finite, and designs that present the most important information first are essential.
GDPR Character Count-Related Requirements
The GDPR (General Data Protection Regulation) sets specific requirements for how privacy policies should be written. While no article directly regulates character counts, the following principles indirectly affect character count design.
| GDPR Article | Requirement | Impact on Character Count |
|---|---|---|
| Art. 12(1) | Provide information in a concise, transparent, intelligible, and easily accessible form | Requires avoiding verbose legal language and writing in plain terms |
| Art. 12(1) | Use clear and plain language, especially for information addressed to children | Requires minimizing jargon and adding explanations |
| Art. 13 | Disclose controller identity, processing purposes, legal basis, retention periods, data subject rights, etc. | Many required disclosures necessitate a certain character count |
| Art. 14 | Provide information about personal data not obtained directly from the data subject | Additional explanation needed when third-party data acquisition exists |
| Recital 39 | Enable natural persons to be aware of collection, use, consultation, and processing of personal data | Technical processing must be explained in non-technical language |
GDPR's requirements for "concise and intelligible" and "disclose all necessary information" are inherently contradictory. To resolve this, the European Data Protection Board (EDPB) recommends the layered approach. Providing a concise summary in Layer 1 and the legally complete full text in Layer 3 satisfies both requirements simultaneously.
Japan's Personal Information Protection Act and Privacy Policy Character Counts
Japan's Act on the Protection of Personal Information (2022 amendment) doesn't prescribe writing methods as specifically as GDPR, but clearly defines required disclosures.
- Specification and publication of purpose of use (Art. 21): Specify the purpose of use as precisely as possible and notify or publish it. Vague descriptions like "used for marketing" are insufficient - specifics like "used for product recommendation displays" are required
- Third-party provision matters (Art. 27): When providing personal data to third parties, specify the scope of recipients, data items provided, and means of provision
- Publication of retained personal data matters (Art. 32): Publish the business operator's name, purposes of use, disclosure request procedures, and complaint contact
- Security control measures (Art. 23): Publish an overview of measures taken for personal data security management (added in 2022 amendment)
A privacy policy meeting these requirements needs at minimum 3,000-5,000 characters. Adding web service-specific items like cookie usage, analytics tools, and ad delivery service integrations, 8,000-15,000 characters is the typical range.
Writing Techniques for Improving Readability
Improving legal document readability requires not just reducing character counts but refining document structure and expression. Many techniques used in press release character count design apply to legal documents as well.
| Technique | Before | After | Character Change |
|---|---|---|---|
| Active voice conversion | "Your personal information is collected by us" | "We collect your personal information" | Shorter and clearer |
| Eliminating double negatives | "We are not without responsibility" | "We are responsible" | Significantly shorter |
| Using bullet points | "We collect name, address, phone number, email address, and date of birth" | "We collect: Name / Address / Phone / Email / Date of birth" | Greatly improved readability |
| Consolidating definitions | Repeating "The Service means..." in each clause | Define once in a definitions section, then reference "the Service" | Eliminates repetition |
| Specific headings | "Article 5 (Miscellaneous)" | "Article 5 (Data Retention and Deletion)" | Content clear from heading alone |
Legal-specific expressions like "shall," "including but not limited to," and "notwithstanding the foregoing" are sometimes necessary for legal precision, but overuse severely degrades readability. Working with legal teams to identify clauses that can be rewritten in plain language and improving them incrementally is the realistic approach.
Privacy Policy Structure Template
Here's an effective privacy policy structure with recommended character counts.
| Section | Recommended Chars | Content | Priority |
|---|---|---|---|
| Introduction | 200-400 chars | Policy purpose, scope, last updated date | Required |
| Information We Collect | 500-1,000 chars | Types of data collected, collection methods | Required |
| Purpose of Use | 300-800 chars | Specific purposes for each data type | Required |
| Third-Party Sharing | 300-600 chars | Recipients, shared data, legal basis | Required |
| Data Retention and Deletion | 200-400 chars | Retention periods, deletion criteria and methods | Required |
| User Rights | 300-600 chars | How to request disclosure, correction, deletion, suspension | Required |
| Cookies and Tracking | 300-600 chars | Technologies used, opt-out methods | Required for web services |
| Security Measures | 200-400 chars | Technical and organizational data protection measures | Required |
| Children's Privacy | 100-300 chars | Age restrictions, parental consent | Required for applicable services |
| Policy Changes | 100-200 chars | Notification method for changes, effective date | Required |
| Contact | 100-200 chars | Data protection officer contact information | Required |
Following this template yields a total privacy policy of approximately 2,600-5,500 characters. Compared to optimal blog post length, this is roughly the length of a single blog article. At this range, it's realistic for users to read the entire document.
You can find related books on legal document design on Amazon. Learning from both legal and UX perspectives enables more practical document design.
Terms of Service UI Design and Character Count
Character count design for terms of service is closely tied not just to document content but also to the UI that displays it. The same 10,000-character terms can yield vastly different read-through rates depending on presentation.
- Scrollable text box: A small text box embedded in the consent screen requiring scrolling. Read-through rates are extremely low (estimated under 5%). EU consumer protection directives may judge this approach as "insufficiently transparent"
- Accordion UI: Collapsible sections users can expand selectively. Read-through rates improve partially (20-30% for sections of interest)
- Step format: Terms split into multiple steps showing 1-2 sections each. Keeping each step to 500-1,000 characters has improved read-through rates to 40-50% in some cases
- Highlights + full text link: Key provisions (data usage purposes, third-party sharing, cancellation terms) displayed with highlights, full text available via link. Highlighted section read-through rates exceed 60%
Combining step format with highlights is currently the most effective UI pattern. Each step displays a 500-1,000 character summary, with links to the full text for users wanting details.
Multilingual Legal Documents and Character Count Variation
Global services need to provide terms of service in multiple languages. Character count variation between languages affects layout and UI design.
| Language | Ratio vs. 10,000 Japanese Characters | Notes |
|---|---|---|
| English | ~120-140% | Fewer words but more characters including spaces |
| German | ~140-160% | Long compound words tend to significantly increase character count |
| French | ~130-150% | More articles and prepositions make it longer than English |
| Chinese (Simplified) | ~80-90% | High information density of characters reduces count |
| Korean | ~95-105% | Roughly equivalent to Japanese character count |
| Arabic | ~110-130% | Right-to-left script requires UI layout mirroring |
German versions exceeding 1.5 times the Japanese version is not uncommon. When designing the Layer 1 summary of the layered approach, design the layout based on the language with the highest character count, then adjust other languages to have extra whitespace.
Update Frequency and Character Count Trends
Terms of service aren't created once and forgotten - they're regularly updated for legal amendments, feature additions, and litigation responses. With each update, clauses are added and character counts trend upward.
Looking at update frequency for major services, 1-2 updates per year is standard. Google performs roughly annual major revisions, while Apple updates alongside new service launches. Major legal changes like Japan's Personal Information Protection Act amendment (2022) or the EU's Digital Services Act (2024) trigger simultaneous terms revisions across many services.
To curb character count growth, it's important to "consolidate" alongside "additions" during updates. Specifically, these approaches are effective:
- Merging duplicate clauses: Consolidate similar clauses added through past revisions to eliminate redundancy
- Removing discontinued service clauses: Delete clauses for services no longer offered
- Separating into additional documents: Extract service-specific conditions into supplementary terms to keep the base terms concise
- Reviewing definitions: Clean up the definitions section and remove unused defined terms
Measuring Read-Through Rates
Improving terms of service character count design starts with measuring current read-through rates. For web service terms pages, the following metrics can be tracked.
| Metric | Measurement Method | Benchmark |
|---|---|---|
| Time on page | Analytics tools | 30%+ of full read time is good |
| Scroll depth | Scroll event tracking | Percentage of users scrolling 75%+ |
| Accordion expansion rate | Click event tracking | Compare expansion rates to identify high-interest sections |
| Time to consent | Consent button click time - page load time | Under 3 seconds suggests "agreed without reading" |
| Bounce rate | Analytics tools | High bounce from terms page suggests character count is a barrier |
If the vast majority of users consent in under 3 seconds, it means the terms are effectively unread. In this case, UI-level improvements like introducing the layered approach or highlighting key provisions are needed. The fundamental solution isn't just reducing character counts but transforming the structure into something users want to read.