Launch position
- DecaTrend is a 13+ service at launch.
- DecaTrend does not offer standard accounts to children under 13.
- Users under 18 may be placed into Teen Mode with restricted feature defaults.
- Under-13 support should not launch unless a full parental notice, verifiable parental consent, support, deletion, and evidence-retention program is ready.
Age gate
DecaTrend should use a date-of-birth gate and region-aware rules at account creation or before access to risky features. A simple self-declared date of birth is appropriate for baseline onboarding, but higher-risk features may require stronger age assurance or adult approval.
- Ask for date of birth rather than only an over-13 checkbox.
- Use country or region information to apply higher local minimum ages where required.
- Avoid broad ID checks for every user unless the risk requires it.
- Escalate age assurance only for higher-risk features where a stronger check is justified.
Teen Mode
Teen Mode is a product state for users who are old enough to use the Service but are under 18. It should be enforced in product logic, not only described in legal text.
- No public-by-default profiles or discoverability.
- No monetization, payouts, or affiliate-style promotion without adult approval where required.
- Public sharing, community participation, direct posting, and external distribution may be restricted or require additional checks.
- Voice cloning, face editing, avatar generation, age estimation, and similar high-risk features may be unavailable or require additional consent.
- Reporting, blocking, safety review, and support-escalation paths should be easy to find.
Minor data minimization
- Collect only age and safety information needed to enforce legal and product rules.
- Do not use minor accounts for targeted advertising or unnecessary profiling.
- Keep raw verification artifacts out of the main profile where feasible.
- Retain only an age token, consent status, assurance result, timestamp, method, and scope where feasible.
- Shorten retention for failed or rejected verification and parental-consent attempts.
- Document why each minor-related field exists.
CSAM and child-exploitation material
Users may not upload, create, edit, caption, render, store, share, or post child sexual abuse material or content that sexually exploits, endangers, grooms, or targets minors.
Because DecaTrend stores and processes uploaded media and derived outputs, child-safety operations should include server-side screening, escalation, and preservation workflows as the service moves toward production scale.
- Screen stored uploads and rendered derivatives where legally and technically appropriate.
- Consider hash matching, perceptual hashing, thumbnail/key-frame review signals, classifier risk flags, and human escalation for uncertain cases.
- Preserve reportable files and relevant metadata when required or appropriate.
- Report to NCMEC CyberTipline or other appropriate channels when legal thresholds are met.
- Separate child-safety audit logs from normal analytics where feasible.
App store and mobile readiness
If DecaTrend launches mobile apps, Apple and Google child/family declarations must match the actual product. Camera, microphone, upload, analytics, ads, SDKs, and push-notification behavior should be reviewed before any children/family positioning.
Open implementation tasks
- Add DOB and region-aware age routing to onboarding.
- Add Teen Mode to the user/account model and feature gates.
- Create a parental-consent plan only if under-13 support becomes an intentional product decision.
- Create a CSAM escalation, preservation, and reporting playbook with counsel.
- Confirm North Carolina privacy-law status and federal ECS/RCS classification questions with counsel.
Contact
- Business
- Faction Community, LLC
- Address
- [placeholder-business-address], North Carolina, USA
- Support
- [email protected]
- Privacy / Data Protection
- [email protected]
- Legal
- [email protected]