Content Safety Policy
Laozhang API follows strict content safety standards to ensure service compliance and security.Prohibited Content
The following types of content are strictly prohibited:Serious ViolationsThese behaviors will result in immediate account suspension:
- Illegal content (fraud, money laundering, illegal transactions, etc.)
- Child safety-related content (CSAM)
- Violent extremism and terrorism
- Malicious code and hacking activities
Prohibited Content Types
Category | Description | Examples |
---|---|---|
Illegal Activities | Violating laws and regulations | Fraud, drug trafficking, illegal weapon transactions |
Harmful Content | Endangering public safety | Creating viruses, hacking tutorials, explosive manufacturing |
Violent Content | Extreme violence, gore | Detailed descriptions of torture, murder guides |
Hate Speech | Discrimination and incitement | Racial discrimination, religious persecution incitement |
Harassment | Targeted attacks on individuals | Cyberbullying, privacy violation, doxxing |
Adult Content | Pornographic, sexual content | Explicit sexual descriptions, pornographic images |
Misinformation | Deliberately spread false information | Medical fraud, financial fraud, political rumors |
Infringement | Intellectual property violations | Piracy, plagiarism, unauthorized use |
Permitted Content
The following content can be used normally within reasonable scope:Legitimate Use Cases
- Educational and research purposes (e.g., security research, medical research)
- Creative works (novels, scripts, artwork)
- News reporting and commentary
- Technical discussions (programming, cybersecurity)
- Customer service and consulting
- Content translation and summarization
Content Review Mechanism
Automated Review
All API requests undergo automated content review:- Content category classification
- Sensitive word matching
- Context semantic analysis
- User behavior pattern
- Historical violation records
Manual Review
High-risk content is manually reviewed:- Flagged suspicious requests
- User appeals
- Repeated violations
- Edge cases
Appeal Process
1
Submit Appeal
If you believe content was misjudged, submit an appeal in console
2
Provide Evidence
Provide relevant evidence:
- Request ID
- Content description
- Usage context
- Compliance explanation
3
Wait for Review
Manual review team processes within 1-3 business days
4
Get Results
Receive review results via email:
- Pass: Resume service
- Reject: Maintain original decision
Violation Handling
Handling Measures
Depending on violation severity, corresponding measures will be taken:Violation Level | Handling Measures | Duration |
---|---|---|
First Minor Violation | Warning notice | - |
Repeated Minor Violations | Temporary suspension | 24 hours |
Moderate Violation | Service restriction | 7 days |
Serious Violation | Account suspension | Permanent |
Extremely Serious | Account termination + legal report | Permanent |
Violation Examples
Case 1: Fraud Content Generation
Case 1: Fraud Content Generation
Violation Content:
User requests generation of phishing emails, fraud scriptsReview Result:
Immediately blocked, account suspendedHandling Measures:
- Permanently terminate account
- Report to relevant authorities
- Freeze remaining balance
Case 2: Adult Content Generation
Case 2: Adult Content Generation
Violation Content:
Generate explicit pornographic textReview Result:
Content blocked, record violationHandling Measures:
- First offense: Warning
- Second offense: 7-day suspension
- Third offense: Permanent suspension
Case 3: Medical Misinformation
Case 3: Medical Misinformation
Violation Content:
Generate false medical advice, cure claimsReview Result:
Content blocked, evaluate intentHandling Measures:
- Educational research purpose: Warning
- Malicious spread: Account suspension
- Serious consequences: Legal report
Case 4: Technical Discussion (No Violation)
Case 4: Technical Discussion (No Violation)
Request Content:
Discuss web security vulnerabilities, SQL injection principlesReview Result:
Within reasonable scope, permittedConditions:
- Educational purpose
- No specific attack targets
- No malicious code
- No detailed exploitation tutorials
Compliance Guidelines
Development Best Practices
Ensure application compliance:-
Content Filtering
-
Logging and Auditing
-
User Consent
User-facing Applications
If providing services to end users:1
Clear Usage Terms
Display user agreement and content policy in prominent location
2
Input Validation
Validate and filter user input
3
Output Filtering
Review and filter AI-generated content
4
Reporting Mechanism
Provide reporting channel for users to report violations
5
Record Retention
Retain necessary logs according to legal requirements
Special Scenarios
Educational and Research
If used for education or research:- Clearly indicate purpose
- Limit scope of use
- Implement access controls
- Record research process
Content Creation
If used for creative work:- Mark as fictional content
- Add appropriate content warnings
- Follow publishing platform policies
- Respect intellectual property
Medical and Legal Consultation
AI-generated content cannot replace professional advice
- Clearly indicate AI-generated
- Recommend consulting professionals
- Add disclaimer
- Do not provide diagnostic advice
Technical Implementation
Content Filtering SDK
Custom Safety Rules
Common Questions
What if false positives occur?
What if false positives occur?
False Positive Handling:
- Immediate Action:
- Check error message details
- Adjust request content
- Try alternative expressions
- If Repeatedly False Positives:
- Submit appeal request
- Provide usage context
- Explain legitimate purpose
- Wait for manual review
- Prevention Suggestions:
- Avoid sensitive words
- Provide clear context
- Use professional terminology
- Add usage intent description
How to ensure application compliance?
How to ensure application compliance?
Compliance Checklist:
- Read and understand content policy
- Implement input validation
- Add output filtering
- Display user agreement
- Implement logging
- Set up reporting mechanism
- Regular compliance audits
- Staff training
Can appeal after violation handling?
Can appeal after violation handling?
Appeal Rights:Yes, can appeal within 30 days of decision. Submit:
- Detailed explanation
- Improvement measures
- Compliance commitment
- Supporting evidence
- Submit appeal form in console
- Provide necessary materials
- Wait for review (5-7 business days)
- Receive review results
How are historical violations handled?
How are historical violations handled?
Violation Record:
- Records retained for 1 year
- Considered in review
- Affect trust level
- Minor violations: Eliminated after 6 months without new violations
- Moderate violations: Eliminated after 1 year without new violations
- Serious violations: Permanent record
Contact Us
If questions about content safety:- Email Support: [email protected]
- Appeal Submission: Submit in Console
- Reporting Violations: [email protected]
Related Resources
- Terms of Service - View complete terms
- Privacy Policy - Understand data protection policy
- Data Security - Learn about data security measures
- API Reference - View API documentation