The rules.

Treat other Algerians the way you'd treat your neighbour. Don't harass, don't scam, don't impersonate, don't promote illegal goods, don't bury people in spam. Disagree like adults. If you build an audience, take care of it.

• Harassment, threats, doxxing. Targeted abuse, threats of violence, sharing someone's personal information (address, family details, identity documents) without consent.
• Sexual content involving minors. Zero tolerance. Reported to Algerian authorities.
• Promotion of violent extremism or terrorism. Including glorification, recruitment, and operational content.
• Scams and impersonation. Pretending to be someone you're not, fake giveaways, phishing for OTPs or banking details, fake "official" accounts.
• Illegal goods. Drugs, weapons, counterfeit currency, stolen items, illicit pharmaceuticals — listing, advertising, or facilitating their sale.
• Hate speech. Attacks on people based on ethnicity, religion, region, gender, sexual orientation, disability, or migration status.
• Non-consensual intimate imagery. Sharing or re-sharing without explicit consent of every person depicted.
• Gambling. Hard-blocked under Algerian law; promotional content for offshore gambling is removed.

• Sponsored content. Brand-paid posts must be labelled "Sponsored". Brand-mission posts are auto-labelled; direct deals you make off-platform must be self-labelled.
• AI-generated content. Synthetic media (image, video, voice) representing real people must be clearly disclosed. Satire and clear parody are fine.
• Strong opinions. Political, religious, and social criticism is welcome. Personal attacks dressed up as criticism are not.
• Mature content. Cleanly age-gated content (nudity in art, explicit-language music, intense imagery) is allowed in dedicated, opt-in surfaces. It is not allowed on the default feed or in marketplace listings.

• Accurate descriptions. Photos must match the actual product. Stock photos are fine for retail items; misleading "studio" photos for handmade items are not.
• Honest pricing. No fake "original price" inflation. Sale prices must reflect real prior pricing.
• Real availability. If you can't fulfil within the stated window, don't list it.
• Verified sellers for high-risk categories. Electronics, vehicles, and high-value services require KYB verification. Particulier tier accounts can sell low-value items only.

1. Reports route to a human operator. We do not ban from a classifier alone. Automated detection prioritises the queue; a person decides.
2. Decisions carry reasons. When content is removed or limited, you're told which rule applied and given a link to read it.
3. Strikes don't accumulate silently. Each strike is visible in your account settings. Repeat violations escalate to suspension; severe violations skip directly to ban.
4. Operator audit. Every moderation action is audit-logged. Operators are themselves audited.

1. One-tap appeal on every moderation decision. Open the notification, hit Appeal, write what we missed.
2. Second operator reviews. A different operator looks at the original decision and your appeal. Decision and reasoning are returned within 5 business days.
3. Final escalation. If you remain unsatisfied, write to appeals@dziri.app for senior review.

These rules are written for the Algerian context. They align with Loi 18-07 (personal data) and the broader Algerian legal framework. Where local custom and platform policy diverge, we err toward letting Algerians decide what's appropriate among themselves — but the hard lines above are non-negotiable.

Operator-facing detail (classifier thresholds, severity scoring, escalation rules) is documented in the internal policy book and available to regulators and qualified partners on request.

Every piece of content has a Report button. Reports are confidential — the person you report doesn't see who reported them. For urgent safety issues, also write to safety@dziri.app so the operator queue can prioritise.

These guidelines are updated when the rules genuinely change. Last update: May 2026. Substantive changes are reported on /changelog.